Software Design Specification

Table of Contents

• 1. Introduction - (Extensions of SRS)
  • 1.1 Purpose
  • 1.2 Scope
  • 1.3 Definition, Acronyms, or Abbreviations
  • 1.4 References (extensions of SRS)
• 2. Decomposition Description (part 1)
• 2.1 Preliminary Design of Architecture
• 2.2 GUI Components with layouts, navigation
• 2.3 Database Components - Database Tables, Segments, or Objects
• 2.4 Data Dictionary - Attributes, Database Components, GUI Components
• 3. Decomposition Description (cont')
  • 3.1 Component, Module or Item 1 Preliminary Description
    Class Diagram at the Design Level (iterative)
  • 3.2 Component, Module or Item 2 Preliminary Description
    Sequence Diagram (iterative)
  • 3.3 Data Dictionary with Attributes, Classes, Sequence Diagrams
• 4. Component Detail Design Document
  • 4.1 Component, Module 1. or Item 1 - FOR EACH CLASS
    • 4.1.1 Structure - super type and sub types of this class
    • 4.1.2 Function - methods of classes with signatures
    • 4.1.3 Interfaces - collaborating classes
    • 4.1.4 Program Interrupts - N/A
    • 4.1.5 Timing and Sequencing - N/A
    • 4.1.6 Sequential Control Feature - N/A
    • 4.1.7 Storage Allocation - where class housed (c/s)
    • 4.1.8 Application Data - the attributes for each class
    • 4.1.9 Detailed Design Description - narrative description of each method
  • 4.2 Component, or Module 2 - class 24.3
  ...
  
  • 4.n Component or Module n - class 4

2.1 Preliminary Design of Architecture

2.2 GUI Components with layouts, navigation

2.3 Database Components

• Database Table Definitions
• Database Table Classes Definitions
• Database Definition

2.4 Data Dictionary

• Attributes, database components, GUI components
• Entries for every table
• Every screen (no in design terms)

3.1 Component, Module or Item 1 Preliminary Description - Class Diagram at Design Level (iterative)

3.2 Component, Module or Item 2 Preliminary Description - Sequence Diagram (iterative)

Revised and Expanded SDP

At this point you would have to re-plan, and update the SDP.

You would have needed to schedule the programmers, the database analysts, the database builders, the people who are doing the html, javascripts, etc. if needed. You would need to schedule all the programming staff. While a little project would not be a problem, a large one might even hire a different contractor at this point.

Due to the limited scope and schedule, you are not required to include this in the SDS for the project in this course, but you should continue to revise and refine your plan to keep your project on track.