How to Break Mammoth-Sized Projects into Bite-Sized Pieces Esther Johnson and Kevin Nguyen Northrop Grumman SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Overview • Avoiding typical software development problems • Accurately design the intended system based on the acquired requirements – Capturing customer requirements • Translating the requirements • Trace Requirements • Transition from Systems to Software • Architecture Development Process • Experiences • Customer Comments 2 SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Most Common Reasons for Software Project Failure • Poor communication among stake holders in order to understand a project requirements • Poor planning on resources and activities • Poor quality control • Poor estimation • Poor risk identification and management If you don’t understand what the Customer wants, you can’t build it. 3 SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Today’s Systems of Systems Are Too Complex To Play “Bring Me A Rock” Key, T, Compare, Allocator Externals::UI_SMap arg1 UI_SMap::Key UI_SMap::Compare Externals::OS_Database 1 1 1 1 1 1 1 1 Externals::SocketUDP OS_Database::arg1 UI_SMap::Allocator UI_SMap::T 1 1 T, Allocator Externals::UI_SVector 1 1 Externals::SocketInterface UI_SVector::T UI_SVector::Allocator Externals::AppFramework 1 1 class_2_copy 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 class_0_copy_3 class_1 class_4 class_2_copy_0 class_1_copy_copy_0 1 1 1 1 1 1 1 1 T T 1 1 1 1 1 1 1 1 1 1 class_2 class_1_copy class_0_copy_2 class_1_copy_copy_1 class_0_copy_1 Externals::Index Externals::Allocator 1 1 1 1 Index::T Allocator::T 1 1 1 1 class_5 class_1_copy_0 class_1_copy_copy class_4_copy class_0_copy_0 1 1 class_0 1 1 class_5_copy_0 class_0_copy_5 class_0_copy class_1_copy_1 class_0::class_2 class_1_copy_copy_2 class_0_copy_4 class_3_copy class_5_copy class_3 4 SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Sustainable Architecture Development – Motivation • Traditional Systems and Software Architecture Processes Are Stressed To Meet Demands Of Software Intensive Service Oriented Architecture Systems Visualization • Sustainable Architecture Goals: Application App App App – Increase “Visual Bandwidth” To Improve SE -SWE Application App App App Communication from womb to tomb Common Services – Work At Higher Level Of Abstraction To Manage Large-scale System Complexity Integrated Infrastructure – Demonstrate Correct Functionality/Performance Early In Communication Hardware/OS Lifecycle Using Models – Enable Process Automation And Performance Analysis Via Smart, Integrated Toolset – Early Involvement Of Test And Stakeholder Communities Redefine the Way We Design and Build Systems of Systems SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05 5
Northrop Grumman’s Architecture in Practice • Exploits a sustainable Model Driven Architecture Development Processes • Provides the framework to support customers, management, and architects working towards common goals Customer • Provides tangible steps and example artifacts to allow architects to clarify requirement understanding with various stakeholders Success • Encourages customer input/feedback Project Architect Manager • Iterative process helps to catch design deficiency early • Endows customers, managers, architects, and developers with the same understanding of the requirements by illustrating the architecture in a concise, common language Keys to Success 6 SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Model Driven Architecture Development Highlights Input Purpose Collaboration Document Customer Understand - System Engineers work with customers to understand their Requirements customer’s requirements requirements - Start a concept model to support the effort of breaking the system requirements to hardware, and software requirements System Initial - System Engineers work with Senior architects and Test Hardware/ architecture engineers to convey knowledge as well as clarification of any Software with CSCIs misunderstanding Requirements - Refine/derive requirements - Develop test plan System Expand the - Software Engineers and Architects work with Subject Matter Software model to CSCs Expert to further breaking the architecture down to CSCs Requirements - Generate ICDs and data information - Refine test plan ICDs Develop - SMEs support software engineers to design and develop Interfaces interfaces for internal/external interfaces Test plan Verify/Validate - Software engineers, and test engineers collaborate to verify the design system performs as expected 7 SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Key Ingredients in Model Driven Architecture Development • Each of the phase of architecture development Input revolves around this circle of activities Presentation Process • Horizontally, these steps allow architects to absorb input from both customers and managers which leads to customer satisfaction and align the design with a corporate product Manage Artifacts line • Vertically, this process allows technical experts such as system engineers, architects, software engineers and test engineers to work in lock steps • The project is built on top of the previous success step • Collective efforts are deposited in one elaborated system architecture which is used to generate appropriate documentation each phase 8 SEI Architecture Technology User Network Conference, Wednesday, 18 May2011, Architecture is Not Just for Architects Approved for Public Release, Control No. 11-0359 , dtd. 11-04-05
Recommend
More recommend
