Project Name
Software Engineering
Project Report
()
Submitted by:
Supervisor:
Name (Roll no. )
Dr. V.B.Singh
DCAC LOGO
2018
Department of Computer Science
Delhi College of Arts & Commerce
University of Delhi
Content
Problem Statement
Process Model
1.
Software Requirement Specification
1.1
Overall Description
1.1.1 Product Functions
1.1.2 User Characteristics
1.1.3 General Constraints
1.1.4 Assumptions and Dependencies
1.2
External Interface Requirements
1.2.1 User Interfaces
1.2.2 Hardware Interfaces
1.2.3 Software Interfaces
1.3
Functional Requirements
1.3.1 FR 1
1.3.2 FR 2
1.3.3 FR n
1.4
Performance Requirement
1.5
Design Constraints
1.6
Data Flow Diagram
1.7
Data Dictionary
2.
Estimations
2.1
Function Points
2.2
Efforts
3.
Scheduling
4.
Risk Management
5.
Design
5.1
System Design
5.2
Data Design
6.
Coding
7.
Testing
8.
References
Problem Statement
A Software is to be developed to manage an Vehicle Showroom and its
service centre.The software will interact with a various types of customers and
employees of the showroom.
The software will be used to generate bill for the customers coming for the
vehicle purchase or vehicle service. It will also store the details of all the employees
working in the showroom to generate their salary receipts.Apart from these it will
store the details of extra accessories that a cutomerwants. Software will be accessed
by the administrator .
Process Model
The process model choosen by us is Waterfall Model.We have choosen this model
because of the following features:
● Waterfall model is easy to understand and implement.
● Our project is small and waterfall model proves to be quite useful in
representing these type of projects.
● Completing the work stage by stage is easy and linear flow of waterfall model
will help us in achieving this task.
● Requirements are clear and fixed.
● If requirements are not much clear at the start of the project than also we can
use this model as we can embed iterations in waterfall model.
1. Software Requirement Specification
1.1 Overall Description
1.1.1 Product Functions
1.1.2 User Characteristics
1.1.3 General Constraints
1.1.4 Assumptions and Dependencies
1.2 External Interface Requirements
1.2.1 User Interfaces
1.2.2 Hardware Interfaces
1.2.3 Software Interfaces
1.3 Functional Requirements
1.3.1 FR 1
1.3.2 FR 2
1.3.3 FR n
1.4 Performance Requirement
1.5 Design Constraints
1.6 Data Flow Diagram
ZERO LEVEL DFD
EVEL 1 DFD
s
1.7 Data Dictionary
Data
status =
Description
1 or 0
2. Estimations
2.1 Function Points
Questions
1.Does the system require reliable backup and recovery ?
2.Are specialized data communications required to transfer information to or from the applications
3.Are there distributed proceessing functions ?
4.Is performance critical ?
5.Will the system run in an existing ,heavily utilized opeartional environment ?
6.Does the system require online data entry?
7.Does the online data entry require the input transaction to be built over multiple screens or operations ?
8.Are the ILFs updated online ?
9.Are the inputs,outputs,files or inquires complex?
10.Is the code designed to be reusable ?
11.Is the internal processing complex?
12.Are conversion and installation included in the design?
13.Is the system designed for multiple installations in different organizations?
14.Is the application designed to facilitate change and ease of use by the user?
Sum of Fis:
Functional point=113*(0.65+(0.01*33))
=110.74
Scale
5
4
3
4
3
0
0
0
3
2
3
0
3
3
33
2.2 Efforts
3. Scheduling
4. Risk Management
5. Design
5.1 System Design
5.2 Data Design
6. Coding
7. Testing
8. References