Software Design Document (SDD) Template

Background

Software design is a process by which the software requirements are translated into a
representation of software components, interfaces, and data necessary for the implementation
phase. The SWDD shows how the software system will be structured to satisfy the requirements.
It is the primary reference for code development and, therefore, it must contain all the information
required by a programmer to write code. The SWDD is performed in two stages. The first is a
preliminary design in which the overall system architecture and data architecture is defined. In the
second stage—i.e., the detailed design stage—more detailed data structures are defined and
algorithms are developed for the defined architecture.

This template is an annotated outline for a software design document adapted from the IEEE
Recommended Practice for Software Design Descriptions. The IEEE Recommended Practice for
Software Design Descriptions have been reduced in order to simplify this assignment while still
retaining the main components and providing a general idea of a project definition report. For
your own information, please refer to IEEE Std 1016 1 for the full IEEE Recommended Practice
for Software Design Descriptions.

1
Available to LANL users at http://ieeexplore.ieee.org/browse/standards/collection/ieee
 (Crime Report Management System)
Software Design Document (SDD)

Name: Dipanshu
Lab Section: A
Workstation:

Date: (28/09/2022)
 Software Design Document

TABLE OF CONTENTS
1.0 INTRODUCTION................................................................................................................................................4

1.1 Purpose.................................................................................................................................................................4

1.2 Scope.....................................................................................................................................................................4

1.3 Overview...............................................................................................................................................................4

1.4 Reference Material...............................................................................................................................................4

1.5 Definitions and Acronyms...................................................................................................................................4

2.0 SYSTEM OVERVIEW.........................................................................................................................................4

3.0 SYSTEM ARCHITECTURE...............................................................................................................................4

3.1 Architectural Design............................................................................................................................................4

3.2 Decomposition Description..................................................................................................................................5

3.3 Design Rationale..................................................................................................................................................5

4.0 DATA DESIGN....................................................................................................................................................5

4.1 Data Description..................................................................................................................................................5

4.2 Data Dictionary....................................................................................................................................................5

5.0 COMPONENT DESIGN.....................................................................................................................................5

6.0 HUMAN INTERFACE DESIGN.......................................................................................................................5

6.1 Overview of User Interface..................................................................................................................................5

6.2 Screen Images......................................................................................................................................................6

6.3 Screen Objects and Actions.................................................................................................................................6

7.0 REQUIREMENTS MATRIX..............................................................................................................................6

8.0 APPENDICES.....................................................................................................................................................6

3
 Software Design Document

1.0 INTRODUCTION

1.1 Purpose

The crime report management system can help in storing the records
related to the criminals, cases, complaint record, case history and so on.
This can allow a person to enter or delete the records if necessary. All these
records can be maintained in a single database.

1.2 Scope

This document id intended for the users, developers and testers. Users will be
able to view whether the document covers all the task to be accomplish
according to them. Developers and testers will be able to verify the working
they will do with the help of this document.

1.3 Overview

The entire project has been developed keeping in view of the distributed client server
computing technology, in mind. The specifications have been normalized up to 3NF
to eliminate all the anomalies that may arise due to the database transaction that are
executed by the general users and the organizational administration. The user
interfaces are browser specific to give distributed accessibility for the overall system.
At all proper levels high care was taken to check that the system manages the data
consistency with proper business rules or validations. The authentication and
authorization were crosschecked at all the relevant stages. The user level accessibility
has been restricted into two zones namely. The administrative zone and the normal
user zone.

1.4 Reference Material

The purpose of this project is to assist the users, be in Pakistan, and to write
complaints in emergencies to avoid unnecessary paperwork and wait, to get security
tips while sitting at their homes and upload videos and images of unwanted criminal
whenever the users’ needs to avoid or has complication while reaching out to the
police station. It will have all the contacts of the police station to tell the users what
to do in certain situation. It will display emergency contact according to the cities
(useful for the people who are new in the country)

4
 Software Design Document

1.5 Definitions and Acronyms

DFD-Data Flow Diagram
SRS-Software Requirement Specification
ER-Entity Relational Diagram
SDD-System Design Document

2.0 SYSTEM OVERVIEW

 Provides the searching facilities based on various factors. Such as Crime, Police
Department, Public, Complaint.
 Online Crime Management System also manage the Solutions details online for public
details, Complaint details, Crime.
 It tracks all the information of Criminal, Solutions, Public etc.
 Manage the information of Criminal.
 Shows the information and description of the Crime, Police Department.
 To increase efficiency of managing the Crime, Criminal.
 It deals with monitoring the information and transactions of Public.
 Manage the information of Crime.

3.0 SYSTEM ARCHITECTURE

3.1 Architectural Design

System will operate on any operating system like Microsoft Windows, Apple macOS.
Linux, Android and Apple's iOS on latest as well as old versions., hardware of any
contain at least 4 GB ram good processor etc. used of any registered company like
dell, HP etc. It also easily coexists with other applications like google maps etc.

3.2 Decomposition Description

Describe the logical characteristics of each interface between the software

product and the users. This may include sample screen images, any GUI
standards or product family style guides that are to be followed, screen layout
constraints, standard buttons and functions (e.g., help) that will appear on
every screen, keyboard shortcuts, error message display standards, and so
5
 Software Design Document
on. Define the software components for which a user interface is needed.
Details of the user interface design should be documented in a separate user
interface specification.

3.3 Design Rationale

Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the
first step in the development phase for any engineered product or system. The
designer’s goal is to produce a model or representation of an entity that will later be
built. Beginning, once system requirement has been specified and analyzed, system
design is the first of the three technical activities -design, code and test that is required
to build and verify software

6
 Software Design Document

4.0 DATA DESIGN

4.1 Data Description

The Crime report management System is a system used to report crimes. This project
will be done using VB 6.0 as front end, and MS Access as back end. It can used to
report crime. This project is mainly useful for police stations.

4.2 Data Dictionary

This system will help to manage all the activities in a police station using computers.
Currently, all the works are done manually, by computerizing all the activities inside a
police station can be managed easily and effectively.

5.0 COMPONENT DESIGN

The design of input focuses on controlling the amount of input required, controlling
the errors, avoiding delays, avoiding extra steps and keeping the process simple. The
input is designed in such a way so that it provides security and ease of use with
retaining the privacy. The dialog to guide the operating personnel in providing input.

6.0 HUMAN INTERFACE DESIGN

6.1 Overview of User Interface

The “Unique model of Criminal Record Management System in the perspective of Somalia”
will be very useful for the police department. It designed, implemented and tested
successfully. This research work is found to be working effectively and efficiently. The
simplicity and friendly are the advantages of this system. The application is made user-
friendly and securely so that anyone can use and access the application by providing login id
and password. The research is conducted and is built with all possible options such as a
searching option for criminal for future investigation, criminal and crime registration, etc.
6.2 Screen Images
Display screenshots showing the interface from the user’s perspective. These can be hand
drawn or you can use an automated drawing tool. Just make them as accurate as possible.

6.3 Screen Objects and Actions

A discussion of screen objects and actions associated with those objects.

7
 Software Design Document

7.0 REQUIREMENTS MATRIX

Provide a cross-reference that traces components and data structures to the requirements in your
software requirements specification (SWRS) document.

Use a tabular format to show which system components satisfy each of the functional requirements
from the SWRS. Refer to the functional requirements by the numbers/codes that you gave them in
the SWRS.

8.0 APPENDICES

This section is optional.

Appendices may be included, either directly or by reference, to provide supporting details that could aid in
the understanding of the Software Design Document.