Presentation on theme: "Model Based System Engineering Approach to Managing Requirements in a Multi-Agency/Multi-Stakeholder Environment of Science and Technology/Research and."— Presentation transcript:
1Model Based System Engineering Approach to Managing Requirements in a Multi-Agency/Multi-Stakeholder Environment of Science and Technology/Research and Development ProjectsMagda Batista-CarverFederal Aviation Administration – Electrical Computer EngineerThe George Washington University EMSE PhD CandidateDr. Thomas Mazzuchi, D. Sc.Dr. Shahram Sarkani, Ph.D., P.E.May 16, 2012
2Overview Motivation Challenges with Traditional Systems Engineering Improving Management of Complex System DevelopmentWhy MBSEConceptual ModelApplicationAnalysis FrameworkNotional Application ModelConclusion
3Challenges with Traditional SE Traditional System Engineering is paper basedAcceptable for smaller/single user systemsLarge complex system development proves to be immensely challengingDifficult to understand, track, manage and articulate effects of requirements changesDocument management approach does not support effective communication among distributed teamsLimited validation and verification resulting in late identification of issuesPoses development risk to projects operating in S&T/R&D environment
4MotivationAs the US debt increases, there is less funding available for Science &Technology (S&T)/Research & Development (R&D) Government Agency projectsGovernment Agencies repeatedly criticized for long development and acquisition cyclesGovernment 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 developmentThese complex projects need to be seamlessly integrated into a complex system of systemsComplex S&T systems development requires more robust, efficient and effective ways to manage requirements than traditional SE
5Improving 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 managementStresses common language and term definition at the beginningUses modeling throughout the system’s lifecycle to supportSystems engineering and systems developmentDesign and analysisVerification and validationSupports integration of diverse modelsTo fully specify and analyze systems
6Why Model Based System Engineering? Modeling performed at all layers of developmentImproved approach to requirements validation and verificationImproved understanding of the overall system being developedEarly identification of problemsCost avoidance potentialImproved overall productivity
8Application Potential Case Study Joint Strike Fighter (J-35) is a multi-agency/multi-national program under development since 2001Since achieving design maturity in 2007, JSF has undergone over 20,000 changesCurrent total acquisition cost is $283 B, a cost growth of 34.7% of the baseline total acquisition costCurrently estimating a 5 year schedule slip for system development
11ConclusionsOrganizations are moving towards more complex system development in collaboration with other organization who have similar needs/interestsAcquisition timelines are lengthy, costly and often times result in programs not meeting all of the intended scopeMBSE can potentially address some of the challenges not met by traditional SE in a Multi-Stakeholder environmentDefine terms from all stakeholders early in development processDevelop systems in increasing layers of complexityImprove communications between developers and stakeholdersAllow for understanding of requirements changes to overall system
12Thank You!Contact InformationMagda Batista-Carver(202)Thomas A. Mazzuchi, D.Sc.(202)Shahram Sarkani, Ph.D., P.E(888)
13ReferencesAzizian, 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. GAOGovernment 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.
14References continuedHarvey, 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 atRamos, 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.