1. Model Based System Engineering Approach to Managing Requirements in a Multi-Agency/Multi-Stakeholder Environment of Science and Technology/Research and Development Projects
Magda Batista-Carver
Federal Aviation Administration – Electrical Computer Engineer
The George Washington University EMSE PhD Candidate
Dr. Thomas Mazzuchi, D. Sc.
Dr. Shahram Sarkani, Ph.D., P.E.
May 16, 2012

2. Overview Motivation Challenges with Traditional Systems Engineering
Improving Management of Complex System Development
Why MBSE
Conceptual Model
Application
Analysis Framework
Notional Application Model
Conclusion

3. Challenges with Traditional SE
Traditional System Engineering is paper based
Acceptable for smaller/single user systems
Large complex system development proves to be immensely challenging
Difficult to understand, track, manage and articulate effects of requirements changes
Document management approach does not support effective communication among distributed teams
Limited validation and verification resulting in late identification of issues
Poses development risk to projects operating in S&T/R&D environment

4. Motivation
As the US debt increases, there is less funding available for Science &Technology (S&T)/Research & Development (R&D) Government Agency projects
Government Agencies repeatedly criticized for long development and acquisition cycles
Government agencies are pooling their funds for projects of similar interests resulting in System Engineers needing to address multi-agency requirements and complex project missions during product development
These complex projects need to be seamlessly integrated into a complex system of systems
Complex S&T systems development requires more robust, efficient and effective ways to manage requirements than traditional SE

5. Improving Management of Complex System Development
Model Base System Engineering (MSBE) approach is more suitable for development of complex systems in the multi-stakeholder environment.
What is MBSE?
Layered approach to system development and requirements management
Stresses common language and term definition at the beginning
Uses modeling throughout the system’s lifecycle to support
Systems engineering and systems development
Design and analysis
Verification and validation
Supports integration of diverse models
To fully specify and analyze systems

6. Why Model Based System Engineering?
Modeling performed at all layers of development
Improved approach to requirements validation and verification
Improved understanding of the overall system being developed
Early identification of problems
Cost avoidance potential
Improved overall productivity

7. Conceptual Model

8. Application Potential Case Study
Joint Strike Fighter (J-35) is a multi-agency/multi-national program under development since 2001
Since achieving design maturity in 2007, JSF has undergone over 20,000 changes
Current total acquisition cost is $283 B, a cost growth of 34.7% of the baseline total acquisition cost
Currently estimating a 5 year schedule slip for system development

9. Analysis Framework Multi-Agency/Multi-Stakeholder R&D/S&T Project
Joint Strike Fighter (J-35)
STOVL CV
CTOL

10. Notional Application

11. Conclusions
Organizations are moving towards more complex system development in collaboration with other organization who have similar needs/interests
Acquisition timelines are lengthy, costly and often times result in programs not meeting all of the intended scope
MBSE can potentially address some of the challenges not met by traditional SE in a Multi-Stakeholder environment
Define terms from all stakeholders early in development process
Develop systems in increasing layers of complexity
Improve communications between developers and stakeholders
Allow for understanding of requirements changes to overall system

12. Thank You!
Contact Information
Magda Batista-Carver
(202)
Thomas A. Mazzuchi, D.Sc.
(202)
Shahram Sarkani, Ph.D., P.E
(888)

13. References
Azizian, N., Mazzuchi, T., Sarkani, S. & Rico, D. (2011). A Framework for Evaluating Technology Readiness, System Quality, and Program Performance of U.S. DoD Acquisitions. Systems Engineering (14)4.
Director, Operational Test and Evaluation FY 2011 Annual Report.
Estefan, J. (2007). Survey of Model-Based Systems Engineering (MBSE) Methodologies. INCOSE MBSE Focus Group.
Government Accountability Office (2010). Joint Strike Fighter Additional Costs and Delays Risk Not Meeting Warfighter Requirements on Time. GAO
Government Accountability Office (2010). Joint Strike Fighter Significant Challenges Remain as DoD Restructures Program. GAO T.
Government Accountability Office (2011). Joint Strike Fighter Restructuring Places Program on Firmer Footing, but Progress is Still Lacking. GAO T.
Goyette, E., Hein, J., Lamar, B. & Ring, S. (2005). Integrated Architecture-Based Portfolio Investment Strategies. 10th International Command and Control Research and Technology Symposium, The Future of C2.

14. References continued
Harvey, D. & Logan, P. (2010). Architecting the Problem Space: An Architecture Framework-Based Method for Definition of User Requirements. 4Th Asian-Pacific Conference on Systems Engineering (APCOSE 2010), Keelung, Tawain.
INCOSE (2011) Systems Engineering Handbook (Version 3.2.1).
OMG (2012). MBSE Wiki. Retrieved on April 23, 2012 at
Ramos, A.L., Ferreira, J.V., and Barcelo, J. (2012). Model-Based Systems Engineering: An Emerging Approach for Modern Systems. Systems, Man and Cybernetics, IEEE Transactions on 42(1) 101 – 111.
Rouse, W. B and Sage, A.P (2009). Handbook of Systems Engineering and Management (2nd edition). John Wiley and Sons, Inc., Hoboken, New Jersey.
Vitech (2011). A Primer for Model-Based System Engineering (2nd edition). Vitech Corporation.