Conference Day Two: Wednesday, April 29, 2009

8:00 Chairperson’s Opening Remarks

8:10 Making DOD Lessons Learned Come Alive And Be Practical

• Describe the BPCh approach to practice recommendations for systems and software programs, and acquaint listeners to the resources available at the site
• Share lessons learned in the process of building BPCh regarding effective approaches to sharing knowledge across programs
• Report our findings regarding essential areas related to system engineering affecting program success

Dr. Forrest Shull
Division Director
Fraunhofer Center – Maryland

8:50 Modeling And Analysis Of Interoperability In Systems Of Systems Environments

• Decision support in complex systems of systems environments
• Three tempos and the need for alignment
• Type three agility – shifting from supply sided to demand driven business models

William B. Anderson
Senior Member of the Technical Staff, Research, Technology, and System Solutions Program, Software Engineering Institute
Carnegie Mellon University

10:15 Constructing Change-Tolerant Systems Using Capability-Based Design

• Localizing and minimizing the impact of change in complex emergent systems
• Designing for technology maturation and insertion over lengthy development life-cycles
• Using capabilities as a basis for specifying system functionality and design

Dr. James D. Arthur
Software Engineering Research Group, Computer Science Department
Virginia Tech University

10:55 Towards Testable Architectures: A Model Driven Approach

• Disjointed artifacts breed ambiguity
• Solving the ambiguity problem is a key step towards requirements engineering and testable architectures
• Both functional and non-functional requirements need to be defined using a formal method, using a model driven approach
• Testable architecture using a MDA approach provides a declarative description of the components and their interactions

Said Tabet
Consultant, No Magic
Inc.

1:00 Learning From Systems Engineering Success And Failure

• How systems learn ... after they are built
• Integrating the social and behavioral factor(s)
• Expanding systems engineering to impact the enterprise

Dr. Jon Beard
Lead Information Systems Engineer
The MITRE Corporation

1:40 CASE STUDY: NAVAIR’s Coast-To-Coast Support Of The E-2C Hawkeye Using Distributed TSP

• An Overview Of NAVAIR And The E-2C
• Software Engineering Processing
• Delivering Quality Product On Cost And On Schedule

Jeffrey Schwalb
NAVAIR Associate Fellow
NAVAIR Process Resource Team

2:50 CASE STUDY: Lessons Learned From Integrating Security Into The Development Of The Navy's First Netcentric Destroyer, The USS Zumwalt (DDG-1000)

• Building Security In vs. Bolting Security On: Lessons learned from integrating a Security Requirements Traceability Matrix (SRTM) into the system engineering process.
• Building Security In across a System of Systems: Lessons learned from leading a Security Cross Product Team (CPT).
• Building Security In across Layers of Abstraction: Lessons learned from applying Defense in Depth (DiD)

Thomas Augustine
PMS 500 Security Architect
SPAWAR Systems Center Pacific (Code 53625)

3:30 A Fundamental Approach To Improving Software Quality

• Software as a product, and its relationship to quality management
• Applying best practices in software construction
• Cost/benefit analysis – is quality really free?

Rick Spiewak
Lead Software Systems Engineer
The MITRE Corporation

4:10 End Of Conference

[ Register Now] · [ Next: Testing and Evaluation Focus Day: Monday, April 27, 2009 ]