Software Requirements

Specification
for

< CD Management System >

Version 1.0

Prepared by <Sameer Khan = 61844 & Ahmer = 61035>

<PAF KIET>

<Date created>
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics....................................................................................................2
2.4 Operating Environment..................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies.....................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose 

The purpose of this document is to specify the software requirements for the project of CD 
Management System. The scope of the product that is covered in this SRS is briefly described as 
below:­ 
 Problem statements
 Use cases
 Flow of events
 Activity diagrams
 Realization of use cases
 Interaction Diagram  
 Entity Relationship Diagram
 Class Diagram

1.2 Intended Audience and Reading Suggestions

The intended audience of this document consist the following:­
 Supervisor of the project
 Developers
 Management of the company

The document is in the flow as suggested for Unified Software Development (USD)

1.3 References

 IEEE. IEEE Std 830­1998 IEEE Recommended Practice for Software Requirements Specifications. 

IEEE Computer Society, 1998.
Software Requirements Specification for <Project> Page 2

2. Overall Description

2.1 Problem Statements

A well-known brand can serve the customers and audience in order to help in their
purchasing. It was very time consuming part when your customers are in a rush on this
point your searching need has be fast as sometimes they need plenty of different items
like someone need music collection of different singers, movies collection old and new mix
and they also need software cd`s, you would only entertain this customer in this scenario
if another customers come and ask for different cd like gaming cd on this spot you must
have a fast searching option that could search for you quickly and tell about your query.
The CD management system enables the computerized record of Customer`s information,
CD`s information & Sales. CD Gallery is a project aimed at management of CD’s in a CD
Gallery. We are facilitating our customers by providing them good prints by using good
quality cd`s. It is used to maintain and sale of CD`s from the gallery easier. We are serving
our customers in the Defence and Clifton areas of Karachi, we have expanded our
services to most areas of the city, with plans to serve other major cities of Pakistan as
well, in the near future.

2.2 Product Functions

2.2.1 Administrators
 Admin should be able to insert, modify and delete CD.
 Can accept or reject a new user according to the policy or payment methods.
 Can get the information about customer to whom CD has been sold.
 Add and edit CD categories and arrange CD`s by categories.
 Add and edit authors and publishers information.
 Can record CD returned by users.

2.2.2 Normal Users

 The member should be provided with the updated information about the books catalog.
 Members are given an access to check their account’s information and change it.
 Members have the ability to search through books by subject, title, authors or any
information related to the book.
 Can extend the period of borrowing books according to the library policy.
 The customer may suggest a book to be brought to the library book collection.
Software Requirements Specification for <Project> Page 3
Software Requirements Specification for <Project> Page 4

2.3 Flow of Events

In this section, flow of events against each use case shall be described for actor

ADMIN
First of all here Admin is an actor and has following use cases:­

A) Login
B) Add CD
C) View CD 
D) Sell CD
E) Make Payment
F) Company payment 
G) View CD Info
H) Generates reports 
I) Add Customer
J) Customer Info
K) Search CD
L) View Inventory
M) Logout

A. Flow of Events for the Login use case:

1.1 Preconditions:
The use case of authentication must be executed before the use case of login
1.2 Main Flow:
The use case of Login begins with entering the username and password provided to the 
Admin for login purposes. The system authenticates the username and password and 
allows the Admin to enter into the system.

1.3 Sub Flows: 
The system authenticates and verifies the username and password provided to the Admin
(E­1). The use case of Authentication will be executed as a sub flow.

1.4 Alternative Flows:
(E­1): An invalid Admin ID number is entered. The user can re­enter a password or 
terminate the use case.

B. Flow of Events Add CD:
1.1 Preconditions:
1.2 Main Flow:
1.3 Sub Flows:
1.4 Alternative  Flows:
C. Flow of Events View CD:
1.1 Preconditions:
1.2 Main Flow:
1.3 Sub Flows:
1.4 Alternative  Flows:

D. Flow of Events Sell CD:
Software Requirements Specification for <Project> Page 5

1.1 Preconditions:
 1.2   Main Flow:
 1.3   Sub Flows:
1.4 Alternative Flows:

E. Flow of Events Make Payment:
1.1 Preconditions:
1.2 Main Flow:
1.3 Sub Flows:
1.4 Alternative Flows:

F. Flow of Events Company Payment:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

G. Flow of Events View CD Information:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

H. Flow of Events Generate Reports:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

I. Flow of Events Add User:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

J. Flow of Events Customer Info:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

K. Flow of Events Search CD:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

L. Flow of Events View Inventory:
a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

M. Flow of Events Logout:
Software Requirements Specification for <Project> Page 6

a. Preconditions:
b. Main Flow:
c. Sub Flows:
d. Alternative Flows:

2.4 Operating Environment

The product is developed by using Dot net technology with SQL.

2.5 Design and Implementation Constraints

Application will be created on C# win form application using SQL server for data base.

3. External Interface Requirements

3.1 User Interfaces

First Screen of the system would be a login screen which would ask for the username and
password of the employee and on successful verification would transfer the user to the main
page where the user would be able to see dashboard. The user then be able to see main page
dashboard and can access to different functionalities of the system by clicking on various buttons
that are provided on each page.

3.2 Hardware Interfaces

Processor = 2.4 GHZ

Memory = 2 GB Ram
Disk space = 80 GB required (20 GB for database management system)
Display = 800 * 600 (1024 * 786 High color 16bit recommended)

3.3 Software Interfaces

The software interface will be created on Visual Studio windows form application using C# and 
SQL server Management Studio for database
Software Requirements Specification for <Project> Page 7

3.4 Communications Interfaces

<Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.>

4. Other Nonfunctional Requirements

4.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements as
specific as possible. You may need to state performance requirements for individual functional
requirements or features.>

4.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well
as actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>

4.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.>

4.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. Write these to be specific, quantitative, and verifiable when possible. At the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.>
Software Requirements Specification for <Project> Page 8

4.5 Business Rules

<List any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. These are not functional requirements in
themselves, but they may imply certain functional requirements to enforce the rules.>

5. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: To Be Determined List
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>