Project Title 2018-19

Chapter 3

SOFTWARE REQUIREMENT SPECIFICATIONS

Give a brief introduction about SRS in the context of your project (in 2 paragraphs)

3.1 Functional Requirements

In software engineering, a functional requirement defines a function of a software system or its component.
A function is described as a set of inputs, the behavior, and outputs (see also software). Functional requirements may be
calculations, technical details, data manipulation and processing and other specific functionality that define what a
system is supposed to accomplish. Functional requirement should be explained using UML diagrams such as use
case, sequence diagrams etc.

3.2 Nonfunctional Requirements

Non-functional requirements (also known as quality requirements), which impose constraints on the design or
implementation (such as performance requirements, security, or reliability)

Note: 3.1 and 3.2 are compulsory. Depending on its applicability to your project you can also can explain
Architectural Requirements, Structural Requirements, and Behavioral Requirements, Domain Requirements
, Use requirements ……..which can be 3.3 , 3.4 …….

3.5 System Requirements

You need to explain the Hardware and software requirements of your project.

Page 1
Project Title 2018-19

Chapter 4

SYSTEM ANALYSIS AND DESIGN

Give a brief introduction about analysis and design in the context of your project (in 2 paragraphs)

4.1 System Analysis

Analysis done for arriving at the design should be explained.

4.2 High Level Design

4.2.1 System Architecture

Sub systems, modules and their interactions should be explained using block diagrams.

4.2.2 DB Design

Use data flow diagrams to explain the flow of data in sub systems and modules

4.2.3 DB table structure

Should specify the tables with their various fields

4.3 Low Level Design

Detailed description of each module should be given. Should use class diagram ,sequence diagram ,Activity
diagram ,deployment diagram diagram (any one is compulsory ,can use more than one diagrams to show the
low level design )

4.4 User Interface Design

Design of Interfaces provided for the user to interact with the system should be specified (No snapshots)

Note:
*UML diagrams are used for representing the design details of a project. Choose a minimum of 5 UML diagrams which are suitable
for representing your project design details.
*Identify the Sub systems, modules and their interactions represent it using UML diagrams such as
Class Diagram
Component Diagram
Deployment Diagram

Page 2
Project Title 2018-19

Object Diagram
Package Diagram
Profile Diagram
Composite Structure Diagram
Use Case Diagram
Activity Diagram
State Machine Diagram
Sequence Diagram
Communication Diagram
Interaction Overview Diagram
Timing Diagram

Page 3