Ieee Standard 1016 1998 Template by iqf18603

VIEWS: 350 PAGES: 7

More Info
									System Development
 Life Cycle Outline


Detailed Design Specification



                  March 2009


Health and Human Services Agency, Office of Systems Integration
Project Management Office                                   Detailed Design Specification
Office of Systems Integration                                                March 2009

Revision History
                                      REVISION HISTORY
     REVISION/WORKSITE #        DATE OF RELEASE    OWNER         SUMMARY OF CHANGES
Initial Draft – SDLC Outlines   August 29, 2008   OSI-PMO   Initial Release

OSI Admin 5355v2                   03/26/09       OSI-PMO   Updated document to reference
                                                            that this outline should be used
                                                            when developing RFP
                                                            requirements. Updated the roles
                                                            to reflect responsibilities
                                                            associated with the Detailed
                                                            Design Specification.




OSIAdmin #5355                                                                             i
Project Management Office                                                                                 Detailed Design Specification
Office of Systems Integration                                                                                              March 2009

                                                        Table of Contents
1. PURPOSE ........................................................................................................................................ 1
2. SCOPE ............................................................................................................................................. 1
3. RESPONSIBILITIES ........................................................................................................................ 1
   3.1 CONTRACTOR .......................................................................................................................... 1
   3.2 PROJECT M ANAGER ................................................................................................................ 1
   3.3 CONTRACT M ANAGER .............................................................................................................. 1
   3.4 SYSTEMS ENGINEER ................................................................................................................ 1
   3.5 QUALITY M ANAGER ................................................................................................................. 1
   3.6 PROJECT TEAM ....................................................................................................................... 2
4. DETAILED DESIGN SPECIFICATION OUTLINE .......................................................................... 2
   4.1   COVER PAGE ........................................................................................................................... 2
   4.2   REVISION HISTORY .................................................................................................................. 2
   4.3   TABLE OF CONTENTS ............................................................................................................... 2
   4.4   OVERVIEW ............................................................................................................................... 2
    4.4.1 Purpose ............................................................................................................................ 2
        4.4.2       Scope ............................................................................................................................... 2
      4.5   SYSTEM ARCHITECTURE .......................................................................................................... 2
      4.6   DATA DICTIONARY ................................................................................................................... 2
      4.7   DOMAIN DESIGN ...................................................................................................................... 3
       4.7.1 Domain Charts ................................................................................................................ 3
        4.7.2       Domains ........................................................................................................................... 3
      4.8   DATA DESIGN .......................................................................................................................... 3
       4.8.1 Static Data ....................................................................................................................... 3
        4.8.2       Dynamic Data .................................................................................................................. 3
        4.8.3       External Interfacing Data ............................................................................................... 3
        4.8.4       Data Transformation ....................................................................................................... 3
      4.9   USER INTERFACE DESIGN ........................................................................................................ 3
       4.9.1 User Interface Design Overview .................................................................................... 3
        4.9.2       User Interface Navigation Hierarchy ............................................................................. 4
      4.10      OTHER INTERFACES ................................................................................................................. 4
      4.11      OTHER DESIGN FEATURES ....................................................................................................... 4
      4.12      REFERENCES ........................................................................................................................... 4
      4.13      GLOSSARY .............................................................................................................................. 4
      4.14      APPENDICES............................................................................................................................ 4




OSIAdmin #5355                                                                                                                                           ii
Project Management Office                                  Detailed Design Specification
Office of Systems Integration                                               March 2009


1. PURPOSE
This document should be used by the Office of Systems Integration (OSI) projects
to assist in defining RFP requirements. This document provides guidance in the
uniform development of the Detailed Design Specification (DDS) document. The
purpose of the DDS is to establish and communicate, in sufficient detail, how the
properties of the system or software requirements will be transitioned into a design.
Expectations for the aspects of the system or software features and performance
can be compared with the design to identify any design flaws. This document was
based on the following Institute of Electrical and Electronics Engineers (IEEE)
Standards: IEEE Standard (STD) 1016-1998, IEEE STD 1220-1998, IEEE STD
1471-2000.

2. SCOPE
The DDS is a product that is produced during the System Development Life Cycle
(SDLC). The SDLC is a conceptual model used for project management that
describes a series of phases involved in a system development project. The OSI has
defined the following phases as part of the SDLC model: Requirements Analysis,
Design, Development, Test, Implementation, and Transition to Maintenance and
Operations (M&O).
The DDS is constructed during the design phase of the SDLC and is a deliverable of
this phase. All information in the DDS should be consistent and should address all
documented system or software requirements.

3. RESPONSIBILITIES
   3.1 Contractor
        The Contractor is responsible for developing, updating, and obtaining
        approval for the DDS, if it is included as a requirement in the contract. The
        DDS should be based upon the System Requirements Specification (SyRS)
        and/or the Software Requirements Specification (SRS) document
   3.2 Project Manager
        The Project Manager is responsible for coordinating the efforts of those
        involved in the DDS development, review, and approval.
   3.3 Contract Manager
        The Contract Manager verifies that the DDS deliverable is provided,
        reviewed, and approved.
   3.4 Systems Engineer
        The Systems Engineer may provide input in developing the DDS.
   3.5 Quality Manager
       The Quality Manager should verify the quality of the DDS according to the
       requirements and based upon the System Requirements Specification
       (SyRS) and/or the Software Requirements Specification (SRS) document.


OSIAdmin #404ba565-934c-4cc6-9846-056f3b23b30c.doc                                      1
Project Management Office                                  Detailed Design Specification
Office of Systems Integration                                               March 2009

   3.6 Project Team
        The project team member(s) is responsible for assisting in the development
        of the detailed design specification document based upon the System
        Requirements Specification (SyRS) and/or the Software Requirements
        Specification (SRS) document.

4. DETAILED DESIGN SPECIFICATION OUTLINE
   This outline specifies the minimum content elements for the DDS. Document
   formatting is not defined; all formats are acceptable, if the content elements are
   complete.
   4.1 Cover Page
         Provide a cover page with the necessary content, such as the name of the
         document, date, and the Office of Systems Integration logo and footer.
   4.2 Revision History
         Provide a revisions history table with column titles: Revision Number, Date
         of Release, Owner, and Summary of Changes.
   4.3 Table of Contents
         Provide a table of contents with a list of the document sections and the
         pages on which they begin.
   4.4 Overview
         Provide high-level introductory information about the DDS. Provide an
         overview of the entire system or software design.
        4.4.1 Purpose
              Describe the purpose of the DDS and its intended audience. Describe
              the system or software design approach.
        4.4.2 Scope
              Describe the scope of the system or software to be produced.
   4.5 System Architecture
         Provide a figure diagram with descriptions that depicts the overall system
         architecture, including the system components in software, hardware, or
         any other relevant system component.
          Describe the System Architecture in more detail in the Conceptual Solution
          Architecture, Logical and Physical Data Models.
   4.6 Data Dictionary
         Provide a reference to the Data Dictionary that contains descriptions of
         each element of the system.
          Describe the Data Dictionary in more detail in the Logical and Physical
          Data Models.




OSIAdmin #404ba565-934c-4cc6-9846-056f3b23b30c.doc                                      2
Project Management Office                                   Detailed Design Specification
Office of Systems Integration                                                March 2009

   4.7 Domain Design
         Document the system or software domain design in the subsequent
         subsections. The domain views provide perspective and structure in the
         process of representing the design.
          Describe the domain design in more detail in the logical and physical
          service and technology models.
        4.7.1 Domain Charts
              Provide a figure diagram depicting the set of system or software
              domains with major components and their relationships.
        4.7.2 Domains
              Tailor this section to contain the information to comprehensively
              document the domains, components, functions and tasks of the system
              or software design.
   4.8 Data Design
         Document the system or software data contained in databases and other
         data structures that are shared between design elements.
          Describe the data design in more detail in the logical and physical data
          models.
        4.8.1 Static Data
              Describe any static data, which is stored by the system and the end of
              execution and retrieved later for additional processing. Provide a
              diagram of the logical data model or entity relationships for the data.
        4.8.2 Dynamic Data
              Describe any dynamic data used by the system that is not stored after
              the execution is complete.
        4.8.3 External Interfacing Data
              Describe any external interfaces’ data design and configurations.
              Discuss their purposes and provide a diagram where appropriate.
        4.8.4 Data Transformation
              Describe any necessary transformation of data formats or structure
              that will take place. If data transformations will occur, include the
              purpose and configuration of the data transformation with design
              elements or mapping rules.
   4.9 User Interface Design
       4.9.1 User Interface Design Overview
             Provide a description of the user interfaces for the system or software
             based upon any associated requirements related to the need for the
             interface.



OSIAdmin #404ba565-934c-4cc6-9846-056f3b23b30c.doc                                      3
Project Management Office                                 Detailed Design Specification
Office of Systems Integration                                              March 2009

        4.9.2 User Interface Navigation Hierarchy
              Provide description diagrams of the navigation hierarchy for the user
              interface. This diagram should depict how a user would move through
              the interface.
   4.10 Other Interfaces
        Describe the design of any additional interfaces that were not described in
        the previous sections.
   4.11 Other Design Features
        Describe the design of any additional features that were not described in
        the previous sections.
   4.12 References
        Provide any references used in the creation of the DDS.
   4.13 Glossary
        Provide an alphabetized list of definitions for special terms and acronyms
        used in the document.
   4.14 Appendices
        The appendices should contain material that is too detailed or large to be
        included in the main body of the document. Refer to each appendix in the
        main body of the text where the information applies.




OSIAdmin #404ba565-934c-4cc6-9846-056f3b23b30c.doc                                    4

								
To top