240 likes | 376 Views
INCOSE 2002. July 31, 2002 Yves Lacerte Architecture Technology Corporation Eden Prairie, MN. Agenda. Thesis Crusader system overview Software architecture objectives Technology upgrade Concluding remarks and questions. Thesis. Modern ground based weapon systems
E N D
INCOSE 2002 July 31, 2002 Yves Lacerte Architecture Technology Corporation Eden Prairie, MN
Agenda • Thesis • Crusader system overview • Software architecture objectives • Technology upgrade • Concluding remarks and questions
Thesis • Modern ground based weapon systems • Depend more and more on electronics and software • Complex, correct and safe operations • Merge multiple domains • Automobiles, avionics, and industrial controls • Require software architecture that • Is highly adaptable • Obsolescence, technical refresh • Provides a firm technical foundation for evolutionary growth • Support a family of ground based weapon systems
Challenges • Complex requirements • Diverse teams at multiple locations • Infusion of multiple technologies • Interoperability with other systems • Resilience to change • Support for meeting hard real-time requirements • Fault tolerance
Software Architecture Objectives • Modularization • Distributed environment • Separation of concerns • COTS and open standards • Model based
Modularization • Components and patterns • Proven solutions • System composition • Gluing things together • Component certification • More complex • Obsolescence • Maintain knowledge of the architecture and software components impacted by hardware and vice versa
Separation of Concerns • Real-time constraints • Hard real-time task MUST meet its computing deadline • Soft real-time task is a task whose utility is reduced if its deadline is missed • Other constraints • Safety-critical and security issues • Process allocation • Processes and processors dedicated to perform hard-real time processing • Separate processes to manage external communications
COTS & Open Standards • Open architecture • Conforms to a set of well-known standards such as those found in JTA-Army • Resilience to change • Promotes reusability • Real-time common operating environment • Middleware not unlike DIICOE
Model Based • Automatic code generation through a visual model • Code consistency and quality • Applicability • Design reuse is important and the corresponding code is difficult to write • Early experiments • 17% of the code is unsuitable for automatic code generation • Of the remaining 83% of the code, approximately 40% is automatically generated
Technology Upgrade • Long development cycle • Support at least three generations of electronics over development lifecycle • Technologies • Fibre Channel • Single Board Computers • Digital Motor Control • Controller Area Network (CAN)
Fibre Channel • New network backbone • Supports its own, as well as higher level protocols such as IP and SCSI • Very fast transfers of large amounts of information • Compatible with the requirements of JTA-Army
Single Board Computers • New more powerful SBCs • Re-deploy software • Take advantage of multiple CPUs on each SBCs • Judicious partitioning • Impact limited to device drivers
Digital Motor Control DMC • Move heavy equipment • Very fast, and very reliably • Federated design • Specialized computers implement low-level control of equipment • Tight dependency between hardware and software • Hardware upgrade causes a redesign of the associated software SBC R / D Resolver Prox Switch Brake
Controller Area Network (CAN) • Obsolescence • Replace MIL-STD 1553 • Auto industry challenges • Highly reliable systems with very low production costs • Straightforward integration • Network management software already exists • Abstraction for each device on the network already exist • Dependency on the network protocol isolated to the low level software
Conclusions • Technology upgrades must occur faster and be cheaper • Collapsing development lifecycles, digital innovation and externalization increase pressure • Adaptive architectures • Ability to enable rapid changes due to a changing external environment (technologies and requirements) • Sustainable competitive advantage • Trade capital for staff • Standard configurations • Err on the side of overcapacity not undercapacity • Lower total cost of ownership
Presentation Time • Each speaker will have 25 minutes • Plan on: • About 2-3 minutes for set-up, speaker intro • About 17-19 minutes for you to present • About 4-5 minutes for Q&A • Session Chairs will indicate 5 and 2 minutes to-go • Plan to stay within your time limit
Presentation Equipment • Computer projection equipment will be provided • All authors are requested to use this mode of presentation • We will accommodate only PowerPoint format for electronic presentations • A vugraph projector will be available as a back-up; bring a set of vugraphs as a fallback
Presentation Equipment (Cont.) • A laser pointer will be provided • Both a podium and a lavaliere microphone will be available • All presenters will need to use microphones since session roomsare large
Submittal of Presentations • Please bring two PC floppies, CD or Zip disks of your presentation to the conference -- one disk for back up, just in case • Presentations will be preloaded the evening prior to your talk. • Bring your labeled PC disk, CD or zip disk (e.g. Track 1 Session 2- McKinney, Tues. 15:00) to the Speaker Ready Room between the hours of 2:30 pm - 7pm the day prior to your presentation for preloading.