STUDENT NAME

SYSTEM

SESSION: 2014-2016

IT, Islamia University,

Bahawalpur
SOFTWARE DESIGNDCS&
DESCRIPTION
DOCUMENT

VERSION: 1.0

SDD Document 1.0

Page 0 of 3

05/27/16

Revision History
Name

Date

Reason For Change

Version

11-05-2016

Initial Draft

1.0 Draft

15-05-2016

Revision, Designing

2.0 Draft

20-05-2016

Revision, Final

3.0 Final

Document Approval
Signed

Name

Designation
Supervisor

SDD Document 1.0

Page 1 of 3

Dated
25-05-2016

05/27/16

Table of Contents

1. INTRODUCTION
1.1 Purpose

1.2 Scope

1.3 Overview 2
1.4 Reference Material 2
1.5 Definitions and Acronyms 2
2. SYSTEM OVERVIEW

3. SYSTEM ARCHITECTURE 2
3.1 Architectural Design

3.2 Decomposition Description 2

3.3 Design Rationale

4. DATA DESIGN

4.1 Data Description

4.2 Data Dictionary

5. COMPONENT DESIGN

6. HUMAN INTERFACE DESIGN

6.1 Overview of User Interface 3

6.2 Screen Images

6.3 Screen Objects and Actions 4

7. REQUIREMENTS MATRIX 4
8. APPENDICES

1. INTRODUCTION

SDD Document 1.0

Page 2 of 3

05/27/16

The Software Requirement Specification (SRS) was the basic part of Library Member Info
System (LMIS) project and hence we know that a project is divided into sub parts for
completion or development. Developing software is not easy as it is consider. To avoid the
complexities and problems the whole process to make the software is divided into SRS Software
Requirement Specification, SDD Software Design Documentation and implementation
(coding of Design phase) parts.

1.1 PURPOSE
On the completion of SRS it is now advised to complete the second part of final project
i.e. SDD. SRS tells us the requirements to make a system on the basis of needs. In the SRS we
determine how the requirements vary with the time or how can we develop the software
according to requirements. But in SDD the requirements meets to its actual form. SDD describes
the SRS in the graphical or visual form. For the fully understanding of the user of the software the
SDD phase is going to develop in design manners so that anyone can understand the working of
the software accordingly.

1.2 SCOPE

1.3 OVERVIEW
The overall system design objective is to provide an efficient, modular design that will reduce the
systems complexity, facilitate change, and result in an easy implementation. This will be accomplished
by designing a strongly cohesion system with minimal coupling. In addition, this document will provide
interface design models that are consistent, user friendly, and will provide straight forward transitions
through the various system functions.
The software design document divided in sections with various subsection. The sections of the
design document are:
INTRODUCTION
SYSTEM OVERVIEW
SYSTEM ARCHITECTURE
DATA DESCRIPTION

SDD Document 1.0

Page 3 of 3

05/27/16

 DATA DICTIONARY
COMPONENT DESIGN
HUMAN INTERFACE DESIGN
REQUIREMENTS MATRIX

1.4 REFERENCE MATERIAL

Ralph, Paul (2012). "The Illusion of Design in Software Development". Engineering
Sommerville, I. Software Engineering, 8th edition
IEEE Standard 10162009, IEEE Standard for Information Technology Systems Design
Software
Design Description, IEEE Computer Society, 2009.
Roger Pressman, Software Engineering, 5th Edition, Chapter 21: Object Oriented Analysis, and
Chapter 22:, The Object-Oriented Design Process 2001.
Eu Tak, Kong , Mail Puccino, (email Client), available at http://www.kingkongs.org/mailpuccino/

1.5 DEFINITIONS AND ACRONYMS

Term\Abbreviation

Explanation

L.M.I.S

Library Member Info System

S.D.D

Software Design Document

E.R.D

Entity Relationship diagram

D.F.D.

Data flow diagram

A.P.I

Application Programming Interface

I.E.E.E

Institute of Electrical and Electronics Engineers

International Standard Book Number (ISBN) is a 13-digit number that is utilized as a one of a kind
identifier for books. ISBN is utilized globally.

SDD Document 1.0

Page 4 of 3

05/27/16

2. SYSTEM OVERVIEW

3. SYSTEM ARCHITECTURE
The architecture design is as follows:-

Architectural
Design

Hardware

Database

Software

Design

design

design

Software Design:
Hardware Design:
Database Design:
3.1 ARCHITECTURAL DESIGN

3.2 DECOMPOSITION DESCRIPTION

ER Diagram:

3.3 DESIGN RATIONALE

HISTORY-BASED RATIONALE:Consists of the design history the sequence of events that occurred while performing the design
the information given in the whole SDD is based on the historical irony, The past time was old

SDD Document 1.0

Page 5 of 3

05/27/16

fashioned and designed the documentation with old methods. The confliction arise and the system
making with the new time development.
The methods using in this SDD is totally based with new settings. The system development is
concern with the new titles, graphs, charts, design documentation, activity diagrams, sequence
diagrams and flow charts which will completely explains the working in understandable manners.
If it would not use then system would be considered as old one.

4. DATA DESIGN
4.1 DATA DESCRIPTION

Process Flow Diagram:

4.2 DATA DICTIONARY

5. COMPONENT DESIGN
The system is capable to do work according to the direction. Every simplest or complex component is
responsible to do work which is assigned to it. The system considers every component as best efficient
way component for the mutual cooperation of the whole process. Component design follows as:-

Hardware
SDD Document 1.0

Software
Page 6 of 3

Database
05/27/16

The short detail of the component design working describes as the user after log in to the
system will choose an option for the submission or other action. Consider an example if a user
choose the option to save the project, he or she will press the tab of submission. The given data in
the text box will be stored in the database and a user can also retrieve the data on demand.
Suppose he or she want to see his or her data of project proposal submission, the user will only
click to the data showing tab the stored data in the database will be retrieved and a user can print
it as well.

6 HUMAN INTERFACE DESIGN

After log in to the system the user will be prompted to the new options, where he or she can choose the
option according to the requirement. Now some options are showing to the main page. The user can
register itself by choosing the register option. The user can choose the option for taking the idea of its
project. If he or she is ready to submit its project then user can choose the option of submit button. A user
can change its project member after allowing from department. A user can also see its marks of project by
choosing the right option of see marks after project submission. A user can also see its marks of second
phase by choosing the option of second phase submission. All information regarding to its project is
available all time in menu options.

6.1 SCREEN IMAGES

It is a concept to make the screen images according to the design documentation so that on the time of
coding design it will be useful to make the system similar to this design.
The hand drawn or automated drawing tool images is as follows:-

6.2 OVERVIEW OF USER INTERFACE

7. REQUIREMENTS MATRIX

Componen
ts:
Requirem
ents from
SRS

Login
logout
Compon
ent

SDD Document 1.0

Main
Functional
ity
Componen
t

Settings
Compon
ent

Social
Compon
ent

Page 7 of 3

Trade
Compon
ent

Data
Services
Compone
nt

Remote
Server
Compon
ent

05/27/16

(Use
case):
UC1
UC2
UC3
UC4

SDD Document 1.0

X
X
X

X
X

X
X
X

Page 8 of 3

X
X
X

X
X
X
X

X
X
X
X

05/27/16