The goal of this stage is to translate the user-oriented functional design specifications into a set of technical, computer-oriented system design specifications; and to design the data structure and processes to the level of detail necessary to plan and execute the Construction and Implementation Stages. General module specifications should be produced to define what each module is to do, but not how the module is to be coded. Effort focuses on specifying individual routines and data structures while holding constant the structure and interfaces developed in the previous stage. Each module and data structure is considered individually during detailed design with emphasis placed on the description of internal and procedural details. The primary work product of this stage is a system design that provides a blueprint for the coding of individual modules and programs.
Input:
The following items provide input to this stage.
SEM Templates:
-
Functional Design document
-
Maintenance Plan
-
Requirements Specification
-
Requirements Traceability Matrix
-
Software Configuration Management Plan
PMM Templates:
-
Project Plan
-
Quality Management Plan
-
Security Plan
Other Inputs:
High-Level Activities:
The remainder of this chapter is divided into sections that describe the specific high-level activities performed during this stage. These activities represent the minimum requirements for a large information systems engineering effort. Notes are provided, as applicable, to assist in customizing these lifecycle stage requirements to accommodate different sizes of information systems engineering efforts. The high-level activities are presented in the sections listed below.
6.1 Design Specifications for Modules
6.2 Design Physical Model and Database Structure
6.3 Develop Integration Test Considerations
6.4 Develop System Test Considerations
6.5 Develop Conversion Plan
6.6 Develop System Design
6.7 Develop Program Specifications
Touch Points:
The following touch points are involved in System Design Stage:
Contracts and Procurement
E-Michigan
Enterprise
Architecture (EA)
Infrastructure Services
Security
-
Review MDIT and Agency Security Policies
-
R
eview
State
and Federal Laws and Regulations
-
Revise Network Diagram and Data Flow Diagrams
-
Review Final Risk Analysis with OES recommended security controls
Output:
Several work products are produced during this stage. The work products listed below are the minimum requirements for a large project. Deviations in the content and delivery of these work products are determined by the size and complexity of the project. Explanations of the work products are provided under the applicable activities described in the remainder of this chapter.
SEM Templates:
-
Conversion Plan (initial)
-
Maintenance Plan (revised)
-
Requirements Traceability Matrix (revised)
-
Software Configuration Management Plan (final)
-
Software Testing Checklist (final)
-
System Design Checklist (final)
-
System Design Document (final)
-
Test Plan (initial)
-
Test Reports (initial)
PMM Templates:
-
Project Plan (revised)
-
Security Plan (revised)
Review the Project Plan for accuracy and completeness of all System Design Stage activities and make any changes needed to update the information.
Review Process:
Quality reviews are necessary during this stage to validate the product and associated work products. The activities that are appropriate for quality reviews are identified in this chapter and Chapter 2.0, Lifecycle Model. In addition, a Critical Design Review is conducted once the System Design Document is developed. The time and resources needed to conduct the walkthroughs and Critical Design Review should be indicated in the project resources, schedule, and work breakdown structure.
Structured Walkthrough (SWT)
Requirements for a peer review or a more formal structured walkthrough are documented under Review Process at the end of each Task, Subtask, or Activity section in this stage. The State of
Michigan
guide titled Structured Walkthrough Process Guide provides a procedure and sample forms that can be used for SWTs. This document is available on the MDIT SUITE website.
Stage Exit
Schedule a Stage Exit as the last activity of the System Design Stage to enable the project approvers to review project deliverables and provide a concur/non-concur position to the project manager. The State of
Michigan
guide titled Stage Exit Process Guide provides a procedure and sample report form that can be used for stage exits. This document is available on the MDIT SUITE website.
Complete System Design Stage
Printer Friendly
Text Version 
Email Page
