1 / 25

WG12 Software Primer For RTVIS Committee

WG12 Software Primer For RTVIS Committee. September 10, 2002. Software Development Cycle. Issues Duplicate information contained in multiple standards IEEE 730 Quality Assurance IEEE 830 Requirements Specification IEEE1016 Design Description

wanda
Download Presentation

WG12 Software Primer For RTVIS Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WG12 Software PrimerForRTVIS Committee September 10, 2002

  2. Software Development Cycle

  3. Issues • Duplicate information contained in multiple standards • IEEE 730 Quality Assurance • IEEE 830 Requirements Specification • IEEE1016 Design Description • Conflicting customer requirements such as references to these standards in the same specification: • ATA 102 Software Manual • IEEE J-Std-016 Software User Manual

  4. Issues • Duplicate standards • EIA/IEEE J-Std-016 • EIA/IEEE 12207 • These documents contain similar requirements that are listed in different sections. • Some differences between these standards • 12207 finally superceded J-Std-016

  5. Issues • IEEE 12207 combined many requirements into one document but other documents still exist or are under active review. • Withdrawn documents • 1074.1 Life Cycles (see 12207) • 1348 CASE Tools

  6. Issues • Active Working Groups • 610 Terminology • 730.1 Quality Assurance (SQAP) • 828 Configuration Management (SCMP) • 829 Test Procedures (STPr) • 830 Requirements Specification (SRS) • 1012 Verification & Validation (SVVP/SVVR) • 1016 Design Description (SDD) • 1058.1 Project Management Plan (SPMP)

  7. Issues • 1063 Software User Documents (SUD) issued in 2001 • CMM implementation – How do you satisfy the process needs against the documentation needs • System complexity – separation of hardware and software • End user needs – from planning, through development and maintenance

  8. Issues • Project size – stand alone processors to large systems using multiple processors • Project implementation • Processors that are treated separately (vehicle systems) • Multiple processors treated as one (control systems)

  9. Actions Taken • Froze the input as of January 1, 2002 • Accepted 12207 as the general guideline • Confirmed that documents required are needed to comply with CMM requirements • System functional requirements - not addressed only address software process

  10. Standard Contents • Life cycle model • Document submittals • Documents required • Hard copy format

  11. Life Cycle

  12. Document Submittal (based on end user needs) Type 1 – Install and use Type 2 – Planning Type 3 – Requirements and interfaces Type 4 – Testing Type 5 – Complete documents

  13. Document Submittal

  14. Documents Required • Project planning and oversight • Elements – design and testing • Release • Documents required for all projects regardless of end user needs

  15. Project Planning and Oversight • Software Project Management Plan (SPMP) • Software Quality Assurance Plan (SQAP) • Software Configuration Management Plan (SCMP) • Software Verification and Validation Plan (SVVP) • Software Verification and Validation Report (SVVR)

  16. Software Elements • Software Requirements Specification (SRS) • Interface Control Document (ICD) - optional • Software Design Description (SDD) • Database Design Description (DBDD) - optional • Software Requirements Traceability Matrix (SRTM)

  17. Software Elements • Software Test Plan (STP) • Software Test Procedure (STPr) • Software Test Report (STR)

  18. Software Release • Software Version Description (SVD) • Software User Manual (SUM)

  19. Document Outline • Tabular Form • Column Listing • Section number • Change from reference standard • Content list • Applicability • Comments

  20. Column Meaning Section - same for each document Change – identified if additional, modified or not required from reference standard Content – section title Applicability – mandatory or recommended (optional) Comment – provides additional information on usage or source

  21. Sample Table - SQAP

  22. Sample Table – STP

  23. Hard Copy Format Title sheet – project name, document name, number and revision Inside title – revision history 1.0 Purpose Purpose, scope, objectives, software item covered, standards and maintenance

  24. Hard Copy Format 2.0 References Documents, abbreviations and definitions 3.0 and higher Per the requirements for each document

  25. Conclusions • Document submittals – customer specified • Documents required – all needed to support understanding, control and maintenance • Hard copy format – if delivered in that media • CMM – supports the process

More Related