.

Software Requirements
Specification
For

College Campus
Version 1.0 approved

Prepared by : KAVYA Y. CHAUDHARI

DATE: 26th September 2021

VSITR
Software Requirements Specification

Page ii

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

Revision History
Name Date Reason For Changes Version
Software Requirements Specification

Page 3

1. Introduction
1.1 Purpose

The purpose of Campus Exchange application is to exchange different items

between the students of the campus. The main objective of Campus Exchange
web application is there is not any interaction between the students of any campus
so, for overcome this problem this application is very useful and it is not only
saves lot of time but also make interaction between the students. For students,
they upload items according to the category and give that item to others as
free/sell/rent and there is no need of go to shop and buy it at more money etc.

1.2 Document Conventions

Main Section Titles

• Font: Times
• Face: Bold
• Size: 16

Sub Section Titles

• Font: Times New Roman

• Face: Bold
• Size: 14

Other Text Explanations

• Font: Times New Roman

• Face: Normal
• Size: 14

1.3 Intended Audience and Reading Suggestions

Document is intended for the students of any one campus who want to give or
sell any used material to other students. First of all they should be register
themselves on the site for login in the application. They must have to register
themselves using their enrolment number. And then they exchange the materials
or things between other students of that campus.
Software Requirements Specification

Page 4

1.4 Product Scope

Scope of this project is very broad in terms of other exchange application. Few
of them are:-

This can be used in educational institutions as well as in any company for

exchange between employee.

Can be used anywhere any time as it is a web based application.

There is one restriction that if any item is approve by admin than only student
upload that item. No restriction that student only upload the material of study,
they also upload any other things like music related instruments, electronic
things, etc.

1.5 References

(1) Object Oriented Modelling And Design With UML.

(2)

2. Overall Description
2.1 Product Perspective

The product is independent and totally self-contained. It is totally depend on

users.
So we can say that it is not depend on others it is independent. It is maintain by
admin or the mentor.
Software Requirements Specification

Page 5
2.2 Product Functions

• Register
• Login
• Email/Message notification
• Upload items
• Manage item
• Chat
• payment
• Feedback

2.3 User Classes and Characteristics

Administrators: They are able to add new users to the system and permit them
to access the application and give permission to upload the item. They can also
delete any user or delete any uploaded item and manage payment, feedback and
notifications. They can also see the profile of any student .

Client Users: They login at the client level and this is to get access to the
campus exchange at the client level. They can also view their profile and others
profile and update own profile.

2.4 Operating Environment

Particulars Client System Server System

Operating System Windows 7 and above Windows NT
Processor Pentium 4, 1.2 GHz Core I7, 2.80GHz
Hard Disk 40 GB 100 GB
RAM 512MB 4GB
Framework .NET Framework .NET Framework

2.5 Design and Implementation Constraints

Each student must keep their password as confidential. More over the user must
have individual ID for creating a login in the Campus Exchange System.

Only Administrator can control student addition and deletion in the Campus
Exchange System.
Software Requirements Specification

Page 6
2.6 User Documentation

No user documentation provide.

2.7 Assumptions and Dependencies

• Each User must have a User Id and password.

• There is only one Administrator.
• Server must always run under Windows system.
• Internet connection is a must.

3. External Interface Requirements

3.1 User Interfaces

New Registrations: This utility is to create new users in the Campus exchange
System.

Login Screen: This is for the Administrator to get into the software. It requires a
user name and password.

User Login (Client Side): The user has to give a login id and password by which
he or she can access the Campus Exchange Site.

3.2 Hardware Interfaces

Screen resolution of at least 800X600 is required for proper and complete

viewing of screens.
High resolution will accepted.

3.3 Software Interfaces

• Any windows based operating system.

• SQL Server Database.
Software Requirements Specification

Page 7

3.4 Communications Interfaces

• IIS Server

4. System Features
4.1 System Feature

4.1.1 Validity Check:

System provides validity when student registered. System
compares the whole registration to the static database. Student can only
login when the given information is right.
4.1.2 Sequence Information:
All the information regarding to the item detail, item list, display of
search item should be handled sequentially that is data should be stored
only in particular sequence to avoid any inconvenience.
4.1.3 Error handling:
If any of the validations or sequence flow does not hold true then
appropriate error message will be prompted to the student for doing
the needful.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

This subsection specifies numerical requirements placed on the software or on

the human interaction with the software, as a whole. Numerical requirements
will include:
*300 terminals will be supported at a time
*All the transactions will be processed within seconds.
Software Requirements Specification

Page 8
5.2 Safety Requirements

In the system there are login and password facilities for security of the database.
Backup of our project and databases will be taken regularly.

5.3 Security Requirements

The security system features from having a login for all the students to access
the software. The login details will be used in the system also. So the chances of
the software getting intruded are very less.

5.4 Software Quality Attributes

The source code of the product is going to be open as this is going to be open
source software. It will be free for further modifications and improvements.

5.5 Business Rules

Illegal duplication of the reports should be strictly dealt with. The administrator
should have full details of the user while a user is getting registered to the
system.

6. Other Requirements
Appendix A: Glossary
--------Not Applicable--------

Appendix B: Analysis Models

Use Case Diagram:-

A Use Case Diagram at its simplest is a representation of user’s interaction with

the system that shows the relationship between user and different use cases in
which the user is involved.

A use case diagram can identify the different type of users of a system
and the different use cases and will often be accompanied by other type of
diagram as well as.
Software Requirements Specification

Page 9

E-R Diagram:-

▪ Entity–relationship model (ER model) is a data model for describing the

data or information aspects of a business domain or its process
requirements, in an abstract way that lends itself to ultimately being
implemented in a database such as a relational database. The main
components of ER models are entities (things) and the relationships that
can exist among them.
Software Requirements Specification

Page 10
▪ Entity-relationship modelling was developed by Peter Chen and published
in a 1976 paper. However, variants of the idea existed previously, and
have been devised subsequently such as super type and subtype data
entities and commonality relationships.
Student_id
Image Password Email

Date
* Manage 1 1
Item Admin
uploaded item
*
Item_id
1

Item
Item type
description
Upload

Student_id
1 Student_name
Er-no.
Student
Email
Password
1 1
Ph_no.
Send request

View

Do
Message
1 Time
Give
Date Time
Chat Amount
*
Date *

Sender_id Student_id Payment_id Payment

Receiver_id Description
* Student_id
Date Rating Give or
feedback Manage
* feedback

Sequence Diagram:-

▪ A Sequence diagram is an interaction diagram that shows how processes

operate with one another and in what order. It is a construct of a message
sequence chart. A sequence diagram shows object interactions arranged
in time sequence. It depicts the objects and classes involved in the
scenario and the sequence of messages exchanged between the objects
needed to carry out the functionality of the scenario. Sequence diagrams
are typically associated with use case realizations in the Logical View of
the system under development. Sequence diagrams are sometimes called
event diagrams or event scenarios.
▪ A sequence diagram shows, as parallel vertical lines (lifelines), different
processes or objects that live simultaneously, and, as horizontal arrows,
the messages exchanged between them, in the order in which they occur.
This allows the specification of simple runtime scenarios in a graphical
manner.
Software Requirements Specification

Page 11

Admin Student System

Registration

Successfully added message

Login

Access

Upload item

Ask for approval

Give permission

sucessfully added

Request to view items

Show all uploaded items

Chat
Request for buy or cell item

Status show sold or cancel

Do payment

Check or view payment details

View details

Give feedback

View all feedback

Add or delete feedback

View profile

Show all user profile

Software Requirements Specification

Page 12
Class Diagram:-

▪ In software engineering, a class diagram in the Unified Modelling

Language (UML) is a type of static structure diagram that describes the
structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.

User
Is a

Student Item
-Student_id : int -Item_id : int
-Er-no. : int -Student_id : int
-Student_name : string -Iten type : string
-Image : string Admin
-Email : string Upload Manage -Email : string
-Password : string -Date : int
-Ph_no. : int 1 * -Item description * 1 -Password : string
+upload() +View user()
+Add detail()
+View() +Manage item()
+Submit()
+Delete() +Delete feedback()
+Login()
+update() 1 +View Payment()
1 Manage
1 1 * Give * 11
*
Feedback
-Student_id : int Manage
-Date : int Feedback
-Rating : int 1 View
Chat chat
-Description : string
-Message : string Payment
+Add()
-Sender_id : int -Payment_id : int *
+Submit()
-Receiver_id : int * -Student_id : int
+View()
-Date : int -Date : int
+Delete()
-Time : int -Time : int
Do +Send Request() -Amount : int
*+Accept Request()
+Add amount()
+Send message() +Pay money()
+View chat() +Cancle()
Pay +Delete chat() *
+View()
Software Requirements Specification

Page 13
Activity Diagram:-

▪ Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency.
In the Unified Modelling Language, activity diagrams are intended to
model both computational and organisational processes (i.e. workflows).
Activity diagrams show the overall flow of control.
Activity diagram for Admin

Login

No

Yes

Profile view Manage uploaded item View or delete feedback View payment detail

Logout
Software Requirements Specification

Page 14

Activity diagram for Student

Software Requirements Specification

Page 15

Registration

Login

No

Yes

View or update profile Upload item Payment Feedback Chat

Logout
Software Requirements Specification

Page 16
Data Flow Diagram

▪ A Data Flow Diagram (DFD) is a graphical representation of the "flow” of

data through an informative system, modelling its process aspects. A DFD
is often used as a preliminary step to create an overview of the system.
DFDs can also be used for the visualization of data processing (structured
design).
▪ A DFD shows what kind of information will be input to and output from
the system, where the data will come from and go to, and where the data
will be stored. It does not show information about the timing of process or
information about whether processes will operate in sequence or in
parallel.

Data Flow Diagram – 0th Level / Context Level

Software Requirements Specification

Page 17
1.0
Login Check
Access Add
Register/ Student detail
login Acknowledgement
Access
Login Add detail

Successful
2.0
Manage uploaded item Add detail
Item detail
Acknowledgement
Upload
Admin
item

Success

3.0

Add item

Give or view Notification

notification

4.0
Student

Upload or delete Manage

item item

Request for chat

5.0
Accept for chat Add Chat
message
Chat detail
Send/receive message Acknowledgement

View chat

Add payment detail 6.0

Check
Pay money Payment
Payment Acknowledgement detail
View payment

7.0
Write feedback
Add
Feedback
feedback
View feedback Acknowledgement detail

Data Flow Diagram – 1st Level .