Using MIL-STD-498 and ISO/IEC 12207 for OOD …

1 APIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 1 Using MIL-STD-498 and ISO/IEC 12207 for OOD and RADAPI (Ada PROS, Inc.)12224 Grassy Hill CourtFairfax, Virginia 22033-2819 FAX: Lewis Gray, Software Technology Conference April 24, 1996 APIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 2 This Presentation is Elaborated in the STC 96 Proceedings TITLE: Using MIL-STD-498 and ISO/IEC 12207 with OOD and RAD --39 pages, 34 figures OUTLINE:Object-Oriented Development (OOD)(Booch s model, OOA, O-O design)Rapid Application Development (RAD)(Martin s model, require s, design, coding) MIL-STD-498 Software Development and Documentation (What it does and why, waterfall bias, reviews, non-hier design, require s, CASE) ISO/IEC 12207 Software Life Cycle Processes (What it does, waterfall bias, reviews, non-hier design, CASE, adoption)APIAPIC opyright 1996 by Ada PROS, Inc.

2 All rights reserved worldwide. Lewis Gray - 3 This Presentation is About OOD Your past experience with OOD Your software development goals Your OOD method Your tailored project standardOOD meta-model-all OOD methods-Booch Macro Process -- Booch Micro Process - MIL-STD-498 - ISO/IEC 12207My roleYour roleAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 4 Major TopicsBooch O-O practicesBooch O-O life cycleUsing MIL-STD-498with O-OUsing ISO/IEC 12207with O-OAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 5 Booch Macro ProcessFor Each Software Release Technical managers plan it, not developers Includes planning, risk management, tools, engineering, reviews, documentation, process and product evals.

3 , process Incremental: successive enhancementsConceptAnalysisDesignImpleme ntMaintainRepeat after major releasesAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 6 Waterfall Model MIL-STD-498 Grand Design One release All requirements are defined first Design is carried out before coding, usually in two stages Exit criteria from each activity are usually successful review of traditional documentConceptAnalysisDesignImplementMa intaindocumentreviewdocumentreviewdocume ntreviewdocumentreviewAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 7 Incremental Model MIL-STD-498 Incremental Many releases All requirements are defined first Within a release, design is carried out before coding Exit criteria from requirements activities are usually successful review of documentConceptAnalysisDesignImplementMa intainDesignImplementMaintainDesignImple mentMaintaindocumentreviewAPIAPIC opyright 1996 by Ada PROS, Inc.

4 All rights reserved worldwide. Lewis Gray - 8 Spiral Model: Each Release One or many releases Risk reduction emphasis Requirements are defined with prototypes Exit criterion from requirements activities is usually successful review Design, code, test, release, maintain can be done like waterfall modelDesignImplementMaintainConceptAnaly sisreviewAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 9 Evolutionary Model A (OOD) Booch s process MIL-STD-498 s Evolutionary model Many releases Each release may include a requirements - design -code - test - release -maintain sequence Each release contributes to defining requirements for later releasesConceptAnalysisDesignImplementMa intainAPIAPIC opyright 1996 by Ada PROS, Inc.

5 All rights reserved worldwide. Lewis Gray - 10 Evolutionary Model B (OOD)DesignImplementMaintainConceptAnaly sisreview Booch s process MIL-STD-498 s Evolutionary modelAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 11 Major TopicsBooch O-O practicesBooch O-O life cycleUsing MIL-STD-498with O-OUsing ISO/IEC 12207with O-OAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 12 Booch Micro Process for Classes and Objects Developers plan it Represents daily activities of individuals or small teams Occurs in Analysis (OOA), Design (OOD), Implementation (OOP) Outputs are class diagrams, object diagrams, interaction diagrams, state transition diagrams, module , softwareIdentifyIdentify semanticsIdentify rel nshipsSpecify interfaces & implent nAPIAPIC opyright 1996 by Ada PROS, Inc.

6 All rights reserved worldwide. Lewis Gray - 13 Coad and Yourdon s OOA ( 90)Id e ntify ObjectsIdentify classes and objectsId e ntify StructuresIdentify class and objectrela tionship sD efine Struc turesIdentify class and objectrela tionship sDefine Attributes (andinstance connections)Identify class and objectrela tionship sD efine Servic es (andm essage connections) Identify class and objectsem antics Specify class and objectin te rfa c e s a n dim p lem enta tionBooch s micro processAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 14 Booch s Object-Oriented Design ( 94)Refine project datadictionary as repository ofsystem abstractionsIdentify classes and objectsDevelop spe c ific a tio n s fo reach abstraction, writeinterface for each class,early object diagra m s a n din te ra c tio n d iagra m s, lo o k fo ropportunities for reuseIdentify class and objectsem a nticsProduce class diagra m s,object diagra m s, a n dmodule diagra m s, o rganizemodels into subsystem s, m apclasses and objects tomodulesIdentify class and objectre la tio n sh ip sFinalize class specifications,module diagra m s.

7 Pro d u c eexecutable m odel of systemSpecify class and objectinterfaces andim plem entationBooch s micro processAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 15 Major TopicsBooch O-O practicesBooch O-O life cycleUsing MIL-STD-498with O-OUsing ISO/IEC 12207with O-OAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 16 Seven Issues with DOD-STD-2167A Related to OOD: In the Proceedings1 Perceived preference for waterfall development model2C o m p a tib ility w ith inc re m e nta l /evolutionary development models3 Dependence on formal reviews andaudits4 Compatibility with Ada / O-O methods5D istinc tio n b e tw e e n re q uire m e nts a nddesign6 Emphasis on preparing documents7 Use of CASE toolsAPIAPIC opyright 1996 by Ada PROS, Inc.

8 All rights reserved worldwide. Lewis Gray - 17 MIL-STD-498 Software Development and Documentation5 December 94 MIL-STD-498 solved the problems with DOD-STD-2167A without creating any new 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 18 DOD-STD-2167A General Development Qualification Product Configuration to SupportAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 19 DOD-STD-2167 ASystemRequirementsAnalysis/DesignDetail edDesignCoding andCSU TestingCSC Integrationand TestingCSCI TestingSOFTWARE (CSCI) CHANGEA llocated BaselineSoftwareRequirementsAnalysisPrel iminaryDesignSystem Integrationand TestingPDRSSRTRRFQRFCACDRSDRSRRF unctional BaselineProduct BaselinePCAD evelopmental ConfigurationMajor ActivitiesReviewsAPIAPIC opyright 1996 by Ada PROS, Inc.

9 All rights reserved worldwide. Lewis Gray - 20 DOD-STD-2167A s Waterfall Bias One release All requirements are defined first Design is carried out before coding, usually in two stages Exit criteria from each activity are usually successful review of traditional documentConceptAnalysisDesignImplementMa intaindocumentreviewdocumentreviewdocume ntreviewdocumentreviewAPIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 21 Elements of MIL-STD-498 Development Joint ReviewsSIPSTPSDPSTrPSSDDSDDSTDSTRIDDOCDD BDDSIOMSSSSUMSCOMCOMSRSIRSSVDSPSFSMCPMMA JOR ACTIVITIES:No sequence for the 25 activities, no linkingREVIEWS: No schedule for the 2 kinds of joint reviewsDELIVERABLE DATA:Alternatives to 22 traditional documents are recommendedProject Planning and OversightSystem Requirements AnalysisSystem DesignSoftware Requirements SpecificationSoftware DesignSoftware Implementationetc.

10 , 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 22O-O Software Design DOD-STD-2167A s Translation Problem DOD-STD-2167A s Linking Problem MIL-STD-498 Compatibility with Non-Hierarchical Designs MIL-STD-498 s Software Unit New Concepts in MIL-STD-498 APIAPIC opyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 23 Real Software DesignDOD-STD-2167A s Translation ProblemABCDEFGHIJKLMNS oftware Design Document (SDD)DOD-STD-2167 AFigure 3"Example of a system breakdown and CSCI decomposition"Compilable AdaDesign LanguageCompilable AdaDesign CSC CSU CSU Y Designthe technical product of the software designersused by the Government to evaluate the technical product of the software designersSYSTEM(SSS)SEGMENT(SSS)SEGMENT( SSS)CSCI(SRS)CSCI(SRS)CSCI(SRS)IRSIRSHW CI(PIDS)HW CI(PIDS)HW CI(CIDS)