Using MIL-STD-498 and ISO/IEC for OOD and RAD

Transcription

1 Using MIL-STD-498 and ISO/IEC for OOD and RAD Lewis Gray, Ph.D. Software Technology Conference April 24, 1996 API (Ada PROS, Inc.) Grassy Hill Court Fairfax, Virginia USA FAX: Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 1

2

3 This Presentation is Elaborated in the STC 96 Proceedings TITLE: Using MIL-STD-498 and ISO/IEC 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 Software Life Cycle Processes (What it does, waterfall bias, reviews, non-hier design, CASE, U.S. adoption) Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 2

4 This Presentation is About OOD Booch Macro Process -- Booch Micro Process - MIL-STD ISO/IEC My role Your role OOD meta-model -all OOD methods- Your past experience with OOD Your software development goals Your OOD method Your tailored project standard Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 3

5 Major Topics Booch O-O life cycle Booch O-O practices Using MIL-STD-498 with O-O Using ISO/IEC with O-O Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 4

6 Booch Macro Process For Each Software Release Repeat after major releases Analysis Concept Design Maintain Implement Technical managers plan it, not developers Includes planning, risk management, tools, engineering, reviews, documentation, process and product evals., process improvement... Incremental: successive enhancements Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 5

7 Waterfall Model Concept document review Analysis document review Design document review Implement document review Maintain 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 document Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 6

8 Incremental Model Concept Analysis document review Design Design Design Implement Implement Implement Maintain Maintain Maintain 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 document Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 7

9 Spiral Model: Each Release Concept One or many releases Analysis Risk reduction emphasis Requirements are defined with prototypes Design review Exit criterion from requirements activities is usually successful review Implement Maintain Design, code, test, release, maintain can be done like waterfall model Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 8

10 Evolutionary Model A (OOD) Concept Analysis Design Implement Maintain 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 releases Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 9

11 Evolutionary Model B (OOD) Concept Analysis Booch s process MIL-STD-498 s Evolutionary model Design review Implement Maintain Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 10

12 Booch O-O life cycle Major Topics Booch O-O practices Using MIL-STD-498 with O-O Using ISO/IEC with O-O Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 11

13 Specify interfaces & implent n Booch Micro Process for Classes and Objects Identify Identify rel nships Identify semantics 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 diagrams specifications, software Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 12

14 Coad and Yourdon s OOA ( 90) Identify Objects Identify Structures Define Structures Define Attributes (and instance connections) Define Services (and message connections) Booch s micro process Identify classes and objects Identify class and object relationships Identify class and object relationships Identify class and object relationships Identify class and object sem antics Specify class and object interfaces and im plem entation Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 13

15 Booch s Object-Oriented Design ( 94) Refine p roject data dictionary as rep ository of s y stem abstractions Develop sp e cific a tio ns fo r each abstraction, write interface for each class, early object diag ram s and inte ra c tio n d ia g ra m s, look for o pportunities for reuse Produce class diag ram s, object diag ram s, and module diag ram s, org anize models into subsy stem s, m ap classes and objects to modules Finalize class sp ecifications, module diag ram s, p roduce executable model of sy stem Booch s micro process Identify classes and objects Identify class and object sem antics Identify class and object rela tionship s Specify class and object interfaces and implementation Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 14

16 Major Topics Booch O-O life cycle Booch O-O practices Using MIL-STD-498 with O-O Using ISO/IEC with O-O Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 15

17 Seven Issues with DOD-STD-2167A Related to OOD: In the Proceedings 1 Perceived preference for waterfall development model 2 C om patibility w ith increm ental / evolutionary development models 3 Dependence on formal reviews and audits 4 Compatibility with Ada / O-O methods 5 Distinction betw een requirem ents and design 6 Em phasis on preparing docum ents 7 Use of CASE tools Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 16

18 MIL-STD-498 Software Development and Documentation 5 December 94 MIL-STD-498 solved the problems with DOD-STD-2167A without creating any new ones. Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 17

19 DOD-STD-2167A General Requirements 4.1 Software Development Management 4.6 Transitioning to Support 4.5 Software Configuration Management 4.2 Software Engineering 4.3 Formal Qualification Testing 4.4 Software Product Evaluations Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 18

20 DOD-STD-2167A Major Activities System Requirements Analysis/Design Software Requirements Analysis SOFTWARE (I) CHANGE Preliminary Design Functional Baseline Allocated Baseline Detailed Design Developmental Configuration Coding and Testing Integration and Testing I Testing System Integration and Testing SRR Reviews SDR SSR PDR CDR TRR FCA PCA FQR Product Baseline Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 19

21 DOD-STD-2167A s Waterfall Bias Concept document review Analysis document review Design document review Implement document review Maintain 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 document Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 20

22 Elements of MIL-STD-498 Development MAJOR ACTIVITIES: No sequence for the 25 activities, no linking Project Planning and Oversight System Requirements Analysis System Design Software Requirements Specification Software Design Software Implementation etc., etc. Joint Reviews REVIEWS: No schedule for the 2 kinds of joint reviews DELIVERABLE DATA: Alternatives to 22 traditional documents are recommended SDP SIP STP SUM SCOM STD SPS SDD DBDD COM STrP SVD STR SIOM SRS SSDD IDD OCD SSS IRS FSM CPM Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 21

23 O-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 Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 22

24 Real Software Design DOD-STD-2167A s Translation Problem DOD-STD-2167A Figure 3 "Example of a system breakdown and I decomposition" G C H I A D E B F J I (SRS) I (SRS) IRS SEGMENT (SSS) IRS HWCI (PIDS) SYSTEM (SSS) HWCI (PIDS) HWCI I (SRS) NON-DEVELOPMENTAL SOFTWARE SAME USED BY DIFFERENT s SEGMENT (SSS) HWCI (CIDS) IRS HWCI HWCI HWCI FIGURE 3. Example of a system breakdown and I decomposition. translation Software Design Document (SDD) 4.X X 4.X.Y Y 4.X.Y.2 Y Design K M L N Compilable Ada Compilable Ada Design Language Design Language the technical product of the software designers used by the Government to evaluate the technical product of the software designers Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 23

25 DOD-STD-2167A s Linking Problem Design Software Testing CM I I I <integrated SW> <integrated SW> Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 24

26 MIL-STD-498 Compatibility with Non-Hierarchical Designs SYSTEM (SSS) I (SRS) I (SRS) IRS SEGMENT (SSS) IRS HWCI (PIDS) HWCI (PIDS) HWCI I (SRS) SEGMENT (SSS) HWCI (CIDS) IRS HWCI HWCI HWCI Encourages documenting engineering decisions with actual engineering records, e.g., class, object, and module diagrams, class specifications, state transition diagrams Avoids forcing hierarchical software designs NON-DEVELOPMENTAL SOFTWARE SAME USED BY DIFFERENT s FIGURE 3. Example of a system breakdown and I decomposition. Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 25

27 Software Units: Design MIL-STD-498 s Software Unit is Not Software 3.45 Software unit. An element in the design of a I "The developer shall define and record the architectural design of each I (identifying the software units comprising the I, their interfaces, and a concept of execution among them) and the traceability between the software units and the I requirements " "The developer shall develop and record a description of each software unit " Software Unit or Software Software "The developer shall develop and record software corresponding to each software unit in the I design " "The developer shall establish test cases test procedures, and test data for testing the software corresponding to each software unit " "The developer shall test the software corresponding to each software unit " The developer shall identify the entities to be placed under configuration control The identification scheme shall be at the level at which entities will actually be controlled, for example, computer files, electronic media, documents, software units, configuration items. Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 26

28 New Concepts in MIL-STD-498 Design Software Testing CM I I I SW Unit SW Unit <integrated SW> <integrated SW> <SW> <CM entity> <CM entity> <CM entity> Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 27

29 Major Topics Booch O-O life cycle Booch O-O practices Using MIL-STD-498 with O-O Using ISO/IEC with O-O Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 28

30 ISO/IEC s Key Processes ORGANIZATION (figure from Dr. Raghu Singh) O F MANAGEMENT 1 DOCUMENTATION INFRASTRUCTURE TRAINING IMPROVEMENT ACQUISITION SUPPLY E: 4 T E: 4 E T E P E (T)/E F JOINT REVIEW E: 3 AUDIT E: 3 (I)V&V E: 3 E P E M 2 CM E E PROJECT QA E: 3 V&V E: 3 F E: ACQ T: SUB E E F 3 PROBLEM RESOLUTION OPERATION E: 3 T MAINTENANCE E: 2,3 E DEVELOPMENT E: 1,2,3 4 TAILORING F O Organizations acquire software through projects Projects participate in contracts MIL-STD-498 corresponds to Development process of ISO/IEC O: THE SAME POINTS, ACQ: ACQUISITION, SUB: SUBCONTRACT E: EXECUTE, F: FEEDBACK, M: MANAGE, P: PARTICIPATE, T: TASK PDCA Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 29

31 Compatibility with O-O Life Cycle Models This International Standard does not prescribe a specific life cycle model or software development method. (par. 1.5) The developer shall define or select a software life cycle model appropriate to the scope, magnitude, and complexity of the project. The activities and tasks of the development process shall be selected and mapped onto the life cycle model Activities and tasks may overlap or interact and may be performed iteratively or recursively. (par ) Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 30

32 Software Design with ISO/IEC Topic all by itself! ISO/IEC also avoids the translation and linking problems with DOD-STD-2167A. ISO/IEC requires developers to create software components and to record their design. The standard is compatible with any design method and any relationship between design elements, as the requirements in MIL-STD-498 are. Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 31

33 Looking Ahead to US DOD-STD-2167A Defense System Software Development, Feb 88 ISO ISO/IEC Software Life Cycle Processes, Aug A 7935A DOD-STD-7935A DoD Automated Information Systems (AIS) Documentation Standards, Oct US MIL-STD-498 Software Development and Documentation, Dec 94 J-STD (Trial Use Std) Software Life Cycle Processes, Software Development, Sep 95 <US 12207> Software Life Cycle Processes, planned for Dec 96 Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 32

34 Planned Logical Structure of US Forward: U.S. Introduction ISO/IEC as is (no changes) ISO/IEC Annexes J-STD-016 Annexes (including new technical annotations and J-016 product descriptions [i.e., content of former 498 DIDs]) Physical structure of US could be facing pages of ISO and US annotations Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 33

35 Bringing it Home Booch Macro Process -- Booch Micro Process - MIL-STD ISO/IEC Your role Your OOD method Your tailored project standard Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 34

36 Using MIL-STD-498 with OOD MIL-STD-498 is a checklist of activities to consider when planning a software development project. It s intended for experienced, skilled readers. It s not a textbook, manual, or handbook on how to develop software. MIL-STD-498 defaults to requiring all activities. Don t let this happen! First, understand your software process. Then tailor MIL-STD-498 to apply your process. Use the project SOW to make as much of the software process self documenting as is appropriate. Establish an early acquisition or supply milestone to decide what is appropriate. Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 35

37 Preparing for US by Investing in MIL-STD-498 Competence ISO/IEC is more abstract, more general, than MIL-STD-498. MIL-STD-498 is more abstract than DOD-STD-2167A and earlier military software development standards. Standards assume more today. US will bridge between MIL-STD-498 and ISO/IEC Learn how to perform your one software process with MIL-STD- 498, establish practices to do it. Your practices will be compatible with US 12207, and as a result with ISO/IEC also. Copyright 1996 by Ada PROS, Inc. All rights reserved worldwide. Lewis Gray - 36