System Design Specification

[Project Name]
[Project ID]
Project Name

Software Design Specification

Approval – Note

(If applicable)

Approved: Accepted:
[Sponsor/Customer]

________________ _____________________

[Designator] [Project Manager]

Name: Name:

Date: Date:

Accepted: Reviewed:

__________________ ______________________

[Delivery Head] [Quality Head]

Name: Name:

Date: Date:

Page 2 of 10
Internal
 Project Name

Software Design Specification

Revision History

Reviewed/
Prepared
Version Date Description of Version approved
by
by

Page 3 of 10
Internal
Project Name

Software Design Specification

Table of Contents
 

1 Introduction.............................................................................6
1.1 Identification....................................................................................................... 6
1.2 System Overview............................................................................................... 6
1.3 Document Overview.......................................................................................... 6
1.4 Scope...................................................................................................................... 6
1.5 Assumptions........................................................................................................ 6
1.6 Constraints........................................................................................................... 6
1.7 Open Issues......................................................................................................... 6
1.8 Exclusions............................................................................................................. 6
1.9 Reference.............................................................................................................. 6
1.10 Definitions, acronyms and abbreviations.................................................6

2 System Architecture..............................................................7
2.1 Logical Architecture.......................................................................................... 7
2.2 Physical Architecture........................................................................................ 7
2.3 Architectural Tier-Partitioning......................................................................7
2.3.1 <Tier 1>.............................................................................................................. 7

3 Design considerations..........................................................7
3.1 Accessibility......................................................................................................... 7
3.2 Performance considerations..........................................................................7
3.2.1 Application Start-up.......................................................................................... 7
3.2.2 Control Population............................................................................................. 7
3.2.3 Screen Population.............................................................................................. 7
3.2.4 Field and Screen Validation.............................................................................7
3.2.5 Response on saves on database.....................................................................7
3.2.6 Navigation from one screen to another........................................................7
3.2.7 Shutting down the application........................................................................7
3.3 Constraints........................................................................................................... 7
3.3.1 Design Constraints............................................................................................ 7
3.3.2 Development Constraints.................................................................................7
3.4 External Interface considerations...............................................................8
3.4.1 Interface Identification and Diagrams...........................................................8
3.4.2 Project-unique Identifier of Interface............................................................8
3.5 Internal Interface considerations...............................................................8
3.5.1 Interface Identification and Diagrams...........................................................8
3.5.2 Project-unique Identifier of Interface............................................................8

Page 4 of 10
Internal
Project Name

Software Design Specification

3.6 Security Strategy............................................................................................... 8

3.7 Environment considerations..........................................................................8
3.7.1 Ideal Environment............................................................................................. 8
3.8 System considerations.....................................................................................8
3.8.1 Hardware considerations..................................................................................8
3.8.2 Software considerations...................................................................................8
3.8.3 Tools and Technology.......................................................................................8
3.8.4 Computer Communication considerations....................................................8
3.9 Reliability.............................................................................................................. 8
3.9.1 Availability.......................................................................................................... 8
3.9.2 Backup & Recovery........................................................................................... 8
3.9.3 Fall-back mechanism........................................................................................ 8
3.10 Multi-Language Strategy.................................................................................9
3.11 Error Handling Strategy..................................................................................9
3.12 Multi-user Strategy........................................................................................... 9
3.13 Scalability............................................................................................................. 9
3.14 Flexibility............................................................................................................... 9
3.15 Portability............................................................................................................. 9
3.16 Performance Criteria........................................................................................ 9
3.17 COTS Tools / Libraries/ Components.........................................................9
3.18 Audit & Logging strategy................................................................................9
3.19 Integration Sequence.......................................................................................9
3.20 Deployment Strategy......................................................................................10
3.21 Alternate design consideration...................................................................10

4 GUI Design..............................................................................10
5 Object Model..........................................................................10
6 Data Flow Diagram..............................................................10
7 Entity Relationship Diagram............................................10
8 Appendix..................................................................................10
 

Page 5 of 10
Internal
Project Name

Software Design Specification

1 Introduction

1.1 Identification
[This section shall contain a full identification of the system and the software to
which this document applies. This includes identification number(s), title(s),
abbreviation(s), version number(s), and release number(s) as applicable]

1.2 System Overview

[This section shall briefly state the purpose of the system and the software to
which this document applies. It shall describe the general nature of the system
and the software. Summarize the system development history, operation, and
maintenance. Identify the project sponsor, acquirer, user, developer, and
support agencies. Identify the current and planned operating sites. List other
relevant documents.
Reference can be given to the SRS section]

1.3 Document Overview

[This section shall summarize the purpose and contents of this document and
describe any security or privacy considerations associated with its use.]

1.4 Scope
[This section shall summarize the scope of application.
Reference can be given to the SRS section]

1.5 Assumptions

1.6 Constraints

1.7 Open Issues

1.8 Exclusions
[This section shall summarize the out of scope elements (such as hardware
installation)]

1.9 Reference
[This section shall list the number, title, revision, and date of all documents
referenced in this report.]

1.10 Definitions, acronyms and abbreviations

[This section shall provide details regarding all the definitions, acronyms and
abbreviations used in this document.]

Page 6 of 10
Internal
Project Name

Software Design Specification

2 System Architecture

2.1 Logical Architecture

[Add a logical architecture diagram and provide a detailed description]

2.2 Physical Architecture

[Add a physical architecture diagram and provide a detailed description]

2.3 Architectural Tier-Partitioning

2.3.1 <Tier 1>

Objective
[Objective of tier]
Functionality
[Functionality of tier]
Links to other Tiers
[Any links to other tier]

3 Design considerations

3.1 Accessibility

3.2 Performance considerations

3.2.1 Application Start-up

3.2.2 Control Population

3.2.3 Screen Population

3.2.4 Field and Screen Validation

3.2.5 Response on saves on database

3.2.6 Navigation from one screen to another

3.2.7 Shutting down the application

3.3 Constraints

3.3.1 Design Constraints

3.3.2 Development Constraints

Page 7 of 10
Internal
Project Name

Software Design Specification

3.4 External Interface considerations

3.4.1 Interface Identification and Diagrams

3.4.2 Project-unique Identifier of Interface

3.5 Internal Interface considerations

3.5.1 Interface Identification and Diagrams

3.5.2 Project-unique Identifier of Interface

3.6 Security Strategy

3.7 Environment considerations

3.7.1 Ideal Environment

3.8 System considerations

3.8.1 Hardware considerations

3.8.2 Software considerations

[Operating system etc]

3.8.3 Tools and Technology

[The following tools will be used:]
Type Software
Development Tools Visual Studio 2005
Reporting Service Reporting Services 2005
Database SQL Server 2005
Framework .NET 2.0 framework
The programming language used for all application development will be C#.>

3.8.4 Computer Communication considerations

3.9 Reliability

3.9.1 Availability

3.9.2 Backup & Recovery

3.9.3 Fall-back mechanism

Page 8 of 10
Internal
Project Name

Software Design Specification

3.10 Multi-Language Strategy

3.11 Error Handling Strategy

3.12 Multi-user Strategy

3.13 Scalability

3.14 Flexibility

3.15 Portability

3.16 Performance Criteria

3.17 COTS Tools / Libraries/ Components

[Specify details of any off-the shelf or existing component used.]

3.18 Audit & Logging strategy

[Specify the strategy for logging actions related to application debugging, error
conditions, success messages along with the type of logging i.e. file or
database.]

3.19 Integration Sequence

[Specify strategy for sequence of integration so that modules or sub modules
get integrated other dependent module will not get affected. For example,
User Creation Module and Login Module will be integrated first before any
transactional module/sub module.]
Sr. Module/Sub Module Predecessor Module
Successor Module (s)
No. Name (s)
Main Module -> Master
Main Module -> Login Main Module ->
1 Page, Main Module ->
Module Creation of Activity.
User Creation
Main Module ->
Creation of Activity,
PMIS->Selection of
2 Creation of Sub PMIS->Create Unit Cost
Activity
Activity, Creation of
Sub Activity

Page 9 of 10
Internal
Project Name

Software Design Specification

3.20 Deployment Strategy

[Specify the procedure and tools used for build making, packaging and
installing the Software/System]

3.21 Alternate design consideration

(Refer DAR template)

4 GUI Design
[Add reference to the GUI design specification]

5 Object Model
[Add reference to the object model diagrams]

6 Data Flow Diagram

[Add reference to the Data Flow Diagram]

7 Entity Relationship Diagram

[Add reference to the Entity relationship Diagram]

8 Appendix
[Appendixes may be used to provide information published separately for
convenience in document maintenance (e.g., charts, classified data). Each
appendix shall be referenced in the main body of the document where the data
would normally have been provided as applicable. Appendixes may be bound as
separate documents for ease in handling. Appendixes shall be lettered
alphabetically (A, B, etc.)]

Page 10 of 10
Internal