Hostel Buddy- Find Hostels everywhere!

Software Requirements Specification

<Version 1.0>

20th October 2022

Project Members
TY CSE (BatchA2)
Anurag Kushal Tajne (36023)
Bushra Shakil Sorathia (36031)
Table of Contents Page No
1. INTRODUCTION 1

1.1 PURPOSE
1
1.2 SCOPE
2
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS 3
1.4 REFERENCES 4
1.5 OVERVIEW 4
2. GENERAL DESCRIPTION 5

2.1 PRODUCT PERSPECTIVE 5

2.2 PRODUCT FUNCTIONS 6
2.3 USER CHARACTERISTICS 7
2.4 GENERAL CONSTRAINTS 8
2.5 ASSUMPTIONS AND DEPENDENCIES 9
3. SPECIFIC REQUIREMENTS 10

3.1 EXTERNAL INTERFACE REQUIREMENTS 11

3.1.1 User Interfaces 13
3.1.2 Hardware Interfaces 13
3.1.3 Software Interfaces 14
3.1.4 Communications Interfaces 15
3.2 FUNCTIONAL REQUIREMENTS 16
3.2.1 <Functional Requirement or Feature #1> 17
3.2.2 <Functional Requirement or Feature #2> 18
3.3 DESIGN CONSTRAINTS 19
3.3.1 Standard Development Tools 19
3.3.2 Web Based Product 21
3.3.3 LOGICAL DATABASE REQUIREMENTS 23
4. ANALYSIS MODELS 24

4.1 DATA FLOW DIAGRAMS (DFD) 25

4.2State Transition Diagrams (STD) 27
4.3Usecase Diagram 30

Software Requirements Specification Page

1. Introduction
This document will propose all the features and procedures to develop the system. This
document specially containing details about objectives, scope limitations, process model,
primary requirements, team development, possible project risks, project schedule, and finally
monitoring and reporting mechanisms.
As the name specifies “HostelBuddy” is a web portal developed for managing various
issues related to finding a hostel till getting an actual hostel. For the past few years the number of
educational institutions is increasing rapidly. Thereby the number of hostels is also increasing for
the accommodation of the students studying in this institution. And hence there is a lot of strain
on the person who are running the hostel and the software’s are not usually used in this context.
This particular project deals with the problems of every other person out there who is running
errands in order to find a proper place to reside, this web portal will make searching very easy
for every one out there and it will also avoid the problems which occur when carried manually.
Identification of the drawbacks of the existing system leads to the designing of
computerized system that will be compatible to the existing system with the system which is
more users friendly and m ore GUI oriented. We can improve the efficiency of the system, thus
overcome the drawbacks the existing system.
1.1Purpose

The purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. This document describes the project's target audience and its
user interface, hardware and software requirements. It defines how our client, team and audience
see the product and its functionality.
As the web portal signifies finding the hostels near you so that one can save the time and
efforts it will take to actually go and find one.

Software Requirements Specification Page

1.2Scope

The goal is to design a robust software for the management of a web portal that will
enhance the quality of living for all the people who are staying out of their towns. In the project,
we will fully automate the entire working of the hostels. Whenever a student will search for the
hostels near him/her, he/she will automatically get all the details of the hostels as per his/her
choices. If he/she visits the website and wanted to enquire about it more, he/she can directly
contact to the owner of the hostel. The admin will keep a track of all the users and the hostel
owners. Any complaints regarding carpentry works, plumbing issues and AC repairs will be
catered in similar way. The students will be asked to fill the feedback after they take the
admission in the respective hostels so that their valuable feedback will be fruitful for an another
person in the near future. The students can also give mess feedback and suggestions via an
appropriate form.

1.3 Definitions, Acronyms, and Abbreviation

Database:
A database is an organized collection of structured information, or data, typically stored
electronically in a computer system. A database is usually controlled by a database management
system (DBMS). Together, the data and the DBMS, along with the applications that are
associated with them, are referred to as a database system, often shortened to just database.
Data within the most common types of databases in operation today is typically modeled
in rows and columns in a series of tables to make processing and data querying efficient. The
data can then be easily accessed, managed, modified, updated, controlled, and organized. Most
databases use structured query language (SQL) for writing and querying data.

Bootstrap:
Bootstrap is a free, open source front-end development framework for the creation of
websites and web apps. Designed to enable responsive development of mobile-first websites,
Bootstrap provides a collection of syntax for template designs.
As a framework, Bootstrap includes the basics for responsive web development, so
developers only need to insert the code into a pre-defined grid system. The Bootstrap
framework is built on Hypertext Markup Language (HTML), cascading style sheets

Software Requirements Specification Page

(CSS) and JavaScript. Web developers using Bootstrap can build websites much faster without
spending time worrying about basic commands and function.

HTML:
Hypertext Markup Language is a markup language used to design static web pages.

HTML5:
HTML5 is a core technology markup language of the Internet used for structuring and
presenting content for the World Wide Web. As of October 2014 [update] this is the final and
complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The
previous version, HTML 4, was standardized in 1997.

JavaScript:
A scripting language developed by Netscape to enable Webauthors to design
interactive sites. Although it shares many of the features and structures of the full Java language,
it was developed independently. Javascript can interact with HTML source code, enabling Web
authors to spice up their sites with dynamic content. JavaScript is endorsed by a number of
software companies and is an open language that anyone can use without purchasing alicense. It
is supported by recent browsers from Netscape andMicrosoft, though Internet Explorer supports
only a subset, which Microsoft calls Jscript.

1.SRS Software Requirement Specification.

2.SQL Structured Query Language.
3.CSS Cascade Style Sheets
4.HTML HyperText markup Language

1.4 References

Internet Sources:

http://www.mindlogicx.com/mindQ.html
https://docs.oracle.com/en/database/database.html

Software Requirements Specification Page

http://www.w3schools.com/sql/
http://www.tutorialspoint.com/sql/
http://www.w3schools.com/html/
https://msdn.microsoft.com/en-us/library/windows/desktop/ms669985.aspx
https://www.oracle.com/in/database/what-is-database/#WhatIsDBMS

1.4Overview

The product will run as a website wherein when the concerned person opens the home
page of the website, the person will be asked to sign up if it’s the first time he or she is using the
portal. If they have been using the site, they will be asked to log in. Once they log in, a prompt
will appear in which they will have to select the option which include their choices regarding the
hostels and the filters they wants to make changes into feedback and others. In the ‘other’ option,
a box will appear in which the student can directly contract to the owner as well .
We will create a well-integrated portal for the management of all the hostels and other
facilities like laundry etc . Since, the incumbent hostel system lacks enough interaction between
students and the owner, our priority will be to increase the interaction between all the
stakeholders of the project those includes the admin, the owner, and the students. In our website,
students can make request to to get admitted in any one of the hostels of their choice. The owner
will have to register his hostel at the admin portal earlier. After registering the admin will get the
data regarding that particular hostel and then he will keep on updating the data on the web portal
for the easy implementation of the students. The students on the other hand if signed in into the
website they also have to put all of their details which will be provided to the owner of the hostel
for the easy flow of the systems. The students can directly contact with the owner of the hostel
and can enquire more about the same. Though there will also be the visuals or the images and
videos of the dorm rooms, Pg rooms, etc. Once the student take the admission task, the students
will be asked to give the feedback about the work done by the staff and make any complaint if
there is any. In case of mess management all the feedbacks received from the students will be
carefully monitored by the mess manager in the form of bar graphs and pi charts and necessary
actions will be taken for the smooth functioning of the mess.

Software Requirements Specification Page

2. General Description
2.1 Product Perspective

The Existing System:

The present system is a manual system or a semi-automated system. Manual system

involves paper work in the form of maintaining various files and manuals. Maintaining critical
information in the files and manuals is full of risk and a tedious process; may lead to leakage of
papers.

 The existing system needs to save his information in the form of excel sheets or Disk Drives.

 There is no sharing is possible if the data is in the form of paper or Disk drives.

 The manual system gives us very less security for saving data; some data may be lost due to
mismanagement.

 It’s a limited system and fewer users friendly.

 The existing system need to travel to the actual location to register in a hostel.

 In the existing system there is too much of wastage of time and efforts.

The Proposed System:

The development of this new system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach.
 User Friendliness is provided in the application with various controls provided by system
Rich User Interface.
 The system makes the overall project much easier and flexible for the students and for the
owners.
 It can be accessed over the Intranet as well as internet.
 The up loader’s information files can be stored in centralized database which can be
maintained by the system.
 This can give the good security for overall system because data is not in client machine.

Software Requirements Specification Page

 Authentication is provided for this application only registered members can access the
system.
 This will in turn even help the small scale businessmen to prosper their businesses and to
excel in their Entrepreneurship career.

Software Requirements Specification Page

2.2 Product Functions

The system after careful analysis has been identified to be presented with the following modules:

 Web Registration

 Administrator

 Hostel Owner

1. Web Registration:

The system has a process of registration. Every downloader i.e. the owner of the
particular hostel of the should submit complete details of his hostel facilities along with code,
name, contact details, videos for reference, ratings given by other students earlier, email ids etc.
in the form of registration. When registration completed an automatically generated password is
sent to the CS for login into the system. By using that user id and password he/she can log into
the system.

2. Administrator:

Administrator is treated as a super user in this system. He can have all the privileges to
do anything in this system i.e. us on the admin side can have the access to all the interactions
happening between the user and the owner of the hostel. Admin can contact directly to both the
sides while enquiring about the data redundancy and to check whether its safe or not because
nowadays data has become very sensitive in terms of conspiracy and all the cyber crimes
happening that can hinder the improvement of our portal.

Another tasks done by the administrator is he can go and check personally and could give
the real time ratings to the users or we can say authenticated feedback as it would be easier for
the users to trust to the particular site . He can Supervise entire system. System generates a
unique password of the every particular entry of the new or existing hostel particular upload
which is been shown on the registered mobile number of the users and to the visitors conducting
body of that particular center.

Software Requirements Specification Page

3. Hostel Owner:

The hostel owner of the hostel enters the username as the hostel code & password which
is sent as security code for each time he/she logs in and access the data of students who wishes
to take entry in their respective hostels. Different kind of reports is generated by the system.

Authentication:

Authentication is nothing but providing security to the system. Here everyone must enter
into the system through login page. For registering a secure email communication is used. The
login page will restrict the UN authorized users. A user must provide his credential like user Id
and password for log into the system. For that the system maintains data for all users.

Whenever a user enters his user id and password, it checks in the database for user
existence. If the user is exists he can be treated as a valid user. Otherwise he/she will be treated
as a normal visitor of the website.

2.3 User Characteristics

In this project of ours the user will search for the hostels near him/her and will enquire
about it through directly contacting with the owner or will be given various images and videos to
look upto.
An OTP will come to every user who will register to our website for the authentication of
their identity as well as for the assurance. The user will also be provided by various facilities like
the mess and laundry. His/her feedback will be given after every stay and during stay as well so
that the other people can take the advantage of the same.
The images and the videos will be uploaded by the hostel owner as well and we can refer
to that. Any inappropriate entry or uploading of any unauthorized data will be strictly prohibited.

Software Requirements Specification Page

2.4 General Constraints

The general constraints of the HostelBuddy is that we are developing this for the students
and all the working professionals out there who are searching a sound place to live in. We are
trying to save the time and efforts required to go and actually find a place. This portal will make
it vwery easy for the users and for the young entrepreneurs too who are striving hard to keep up
with this business industry. We will provide them a platform where they can prosper their
business and strive for the success of our portal so that more and more users will turn towards
our web portal and should look it as a reputed portal to look upto.

The product should be able to perform the following operations:

1] It must be able to authenticate the login id and be able to create new login id
for the students residing in the hostels only and for the staff as well.
2] It must be able to initiate requests by the user in the various categories mentioned.
3] It must be able to take the feedback from the students once the task is completed and also be
able to take the mess feedback

2.5 Assumptions and Dependencies

 The size of the database increases day-by-day, increasing the load on the database back up
and data maintenance activity. so that we need large database.
 The Admin of the system who looks after every action happening in the portal must have
knowledge and awareness of this system.so here full system depends on the admin and the
hostel owners.

Software Requirements Specification Page

3. Specific Requirements
3.1 External Interface Requirements

3.1.1 User Interface

 The system has a process of registration. name, contact details, email ids etc. in the form
of registration. When registration completed an automatically generated password is sent
to the CS for login into the system. By using that user id and password he/she can log
into the system.

 The goal is to design the software used for proper management of hostels and
automate the current process. The user types are listed followed

I. Hostel Staff
II. Mess Manager
III. Administrator
IV. Students

Our goal is to develop a software that should be easy to use for all types of users.
Thus while designing the software one can assume that each user type has the
following characteristics:

I. The user is a computer-literate and has little or no difficulty in using the

software keeping in mind the software is user friendly.
II. In order to use software a user must be aware of the internal working and
expected to know how things work.
III. All the guidelines about the use of software will be informed to the user
once the user signs up on the software or web page.
IV. Administrator is treated as a super user in this system. He can have all the
privileges to do anything in this system.

Software Requirements Specification Page

  Another tasks done by the administrator is he can Supervise entire system. System
generates a unique password of the particular upload which is sent on the registered
mobile number of the appointed member of this system

Whenever a user enters his user id and password, it checks in the database for user
existence. If the user is exists he can be treated as a valid user. Otherwise he/she will be
treated as a normal visitor of the website

3.1.2 Hardware Interfaces

 Intel Pentium 4 ( 2.8 GHz ) Processor and Above

 RAM 1 GB and Above
 System Type 32-bit and above
 HDD 40 GB Hard Disk Space and Above

3.1.3 Software Interfaces

Operating System: Windows XP or later:

Microsoft Windows is a meta family of graphical operating systems developed,

marketed, and sold by Microsoft. It consists of several families of operating systems, each of
which cater to a certain sector of the computing industry. Active Windows families
include Windows NT, Windows Embedded and Windows Phone; these may encompass
subfamilies, e.g. Windows Embedded Compact (Windows CE) or Windows Server. Defunct
Windows families include Windows 9x and Windows Mobile.

Database Server: Microsoft SQL Server

Software Requirements Specification Page

 A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database.
A database is a structured collection of data. Data refers to the characteristics of people,
things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single complete unit
of data, called a record (it can also be referred to as raw or an occurrence). Each record is made
up of a number of fields. No two fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time, you
define any additional fields or change the definition of existing fields.

Microsoft Internet Explorer

Internet Explorer is a series of graphical web browsers developed by Microsoft and
included as part of the Microsoft Windows line of operating systems, starting in 1995. It was first
released as part of the add-on package Plus! for Windows 95 that year. Later versions were
available as free downloads, or in service packs, and included in the Original Equipment
Manufacturer (OEM) service releases of Windows 95 and later versions of Windows.
Internet Explorer is one of the most widely used web browsers, attaining a peak of about
95% usage share during 2002 and 2003.[6] This came after it managed to win the first browser
war against Netscape, which was the dominant browser in the 1990s. Its usage share has since
declined with the launch of Firefox (2004) and Google Chrome (2008), and with the growing
popularity of operating systems such as OS X, Linux, iOS and Android that do not run Internet
Explorer. 

SmartDraw

SmartDraw is a visual processor used to create flowcharts, organization charts, mind

maps, project charts, and other visuals. SmartDraw is compatible only with Windows operating
systems. Since version 7, it uses Microsoft’s Fluent User Interface in conjunction with automated

Software Requirements Specification Page

panels specific to each type of diagram.It integrates with Microsoft Word, Excel, PowerPoint and
Microsoft Project; it can export diagrams to common image formats and PDF format.

Microsoft Visual Studio .Net 2008 or later

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft.

It is used to develop console and graphical user interface applications along with Windows
Forms or WPF applications, web sites, web applications, and web services in both code together
with managed code for all platforms supported by Microsoft Windows, Windows
Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silver light.
Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The
integrated debugger works both as a source-level debugger and a machine-level debugger. Other
built-in tools include a forms designer for building GUI applications, designer, class designer,
and database schema designer. It accepts plug-ins that enhance the functionality at almost every
level including adding support for source-control systems and adding new toolsets like editors
and visual designers for domain or toolsets for other aspects of the software development
lifecycle .

3.1.4 Communications Interfaces

Visual C# .Net

Microsoft Visual C# is Microsoft's implementation of the C# specification, included in

the Microsoft Visual Studio suite of products. It is based on the ECMA/ISO specification of the
C# language, which Microsoft also created. While multiple implementations of the specification
exist, Visual C# is by far the one most commonly used. [1] In most contexts, an unqualified
reference to "C#" is taken to mean "Visual C#."

3.2 Functional Requirements

Software Requirements Specification Page

I. Provide residents the ability to lodge a complaint about an issue in the room. Through our
websites, residents have the right to register a complaint regarding different issues in the room
related to maintenance or cleaning. The residents just need to select the type of complaint from a
list of complaints including AC repairs, other electrical complaints, plumbing problems or if they
want their room to be cleaned. This will save their time of going to caretaker’s office and then
writing a complaint. Then the problem will take 3-4 days to be solved.

II. Provide residents the ability to lodge a complaint about mess food and hygiene. Residents
will no longer have to write about the mess complaints in the register which are not read by
anyone in the mess management. They can register a complaint by one click through or web
portal. Taking into consideration different parameters, a form is made to monitor the quality and
taste of food. After filling form, the residents can also give suggestions or register a complaint in
the others box.

III. Provide contact numbers of maintenance worker in charge.

Once a complaint is registered through our web portal, the resident will get the details of the
worker assigned to get the issue resolved. For example, if a resident wants his room to be
cleaned, after registering to get the room cleaned, he will get the details like name of the worker,
his mobile number and the time he will come to clean the room.

IV. Provide mess manager the ability to view the detailed feedback of the residents. In the
current scenario, no one reads the complaints and suggestions listed by the residents in the mess.
Now, a detailed feedback in the form of bar graphs will be given to the mess manager and the
head of the mess managers of the university. Each and every suggestion will reach the mess
manager and a proper action will be taken by the mess manager for smooth functioning.

Output Design:

Software Requirements Specification Page

 Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provides a permanent copy of the results for later
consultation. The various types of outputs in general are:
 External Outputs, whose destination is outside the organization.
 Internal Outputs whose destination is within organization
 User’s main interface with the computer.
 Operational outputs whose use is purely within the computer department.
 Interface outputs, which involve the user in communicating directly.
Output Definition:
The outputs should be defined in terms of the following points:
 Type of the output
 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output
It is not always desirable to print or display data as it is held on a computer. It should be decided
as which form of the output is the most suitable.

Output Media:
In the next stage it is to be decided that which medium is the most appropriate for the
output. The main considerations when deciding about the output media are:
 The suitability for the device to the particular application.
 The need for a hard copy.
 The response time required.
 The location of the users
 The software and hardware available.

Software Requirements Specification Page

 Keeping in view the above description the project is to have outputs mainly coming under
the category of internal outputs. The main outputs desired according to the requirement
specification are:

The outputs were needed to be generated as a hot copy and as well as queries to be
viewed on the screen. Keeping in view these outputs, the format for the output is taken from the
outputs, which are currently being obtained after manual processing. The standard printer is to
be used as output media for hard copies.
Input Design:

Input design is a part of overall system design. The main objective during the input
design is as given below:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.
Input Stages:
The main input stages can be listed as below:
 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

Input Types:

It is necessary to determine the various types of inputs. Inputs can be categorized as

follows:

Software Requirements Specification Page

 External inputs, which are prime inputs for the system.
 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the system?
 Interactive, which are inputs entered during a dialogue.

Input Media:

At this stage choice has to be made about the input media. To conclude about the input
media consideration has to be given to;
 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 Portability

Keeping in view the above description of the input types and input media, it can
be said that most of the inputs are of the form of internal and interactive. As Input data is to be
the directly keyed in by the user, the keyboard can be considered to be the most suitable input
device.

Error Avoidance:

Software Requirements Specification Page

 At this stage care is to be taken to ensure that input data remains accurate form the stage
at which it is recorded up to the stage in which the data is accepted by the system. This can be
achieved only by means of careful control each time the data is handled.

Error Detection:

Even though every effort is make to avoid the occurrence of errors, still a small
proportion of errors is always likely to occur, these types of errors can be discovered by using
validations to check the input data.

Data Validation:

Procedures are designed to detect errors in data at a lower level of detail. Data
validations have been included in the system in almost every area where there is a possibility for
the user to commit errors. The system will not accept invalid data. Whenever an invalid data is
keyed in, the system immediately prompts the user and the user has to again key in the data and
the system will accept the data only if the data is correct. Validations have been included where
necessary.
The system is designed to be a user friendly one. In other words the system has been
designed to communicate effectively with the user. The system has been designed with popup
menus.
User Interface Design:
It is essential to consult the system users and discuss their needs while designing the user
interface:

User Interface Systems Can Be Broadly Classified As:

User initiated interface:

The user is in charge, controlling the progress of the user/computer dialogue. In the
computer-initiated interface, the computer selects the next stage in the interaction.

Software Requirements Specification Page

Computer initiated interfaces:

In the computer initiated interfaces the computer guides the progress of the user/computer
dialogue. Information is displayed and the user response of the computer takes action or displays
further information.

User Initiated Interfaces:

User initiated interfaces fall into two approximate classes:

1. Command driven interfaces: In this type of interface the user inputs commands or queries
which are interpreted by the computer.
2. Forms oriented interface: The user calls up an image of the form to his/her screen and fills
in the form. The forms oriented interface is chosen because it is the best choice.

Computer-Initiated Interfaces:

The following computer – initiated interfaces were used:

1. The menu system for the user is presented with a list of alternatives and the user chooses
one; of alternatives.
2. Questions – answer type dialog system where the computer asks question and takes action
based on the basis of the users reply.
Right from the start the system is going to be menu driven, the opening menu displays the
available options. Choosing one option gives another popup menu with more options. In this
way every option leads the users to data entry form where the user can key in the data.

Error Message Design:

The design of error messages is an important part of the user interface design. As user is
bound to commit some errors or other while designing a system the system should be designed to

Software Requirements Specification Page

be helpful by providing the user with information regarding the error he/she has committed. This
application must be able to produce output at different modules for different inputs.

3.3 Design Constraints

3.3.1 Standard Development Tools

The application shall be built using a standard web page development tool that conforms
to Microsoft’s GUI standards.

3.3.2 Web Based Product

There are no memory requirements:

The computers must be equipped with web browsers such as Internet explorer. The
product must be stored in such a way that allows the client easy access to it. Response time for
loading the product should take no longer than five minutes. A general knowledge of basic
computer skills is required to use the product.

3.3.3 Logical Database Requirements

SQL SERVER 2008

A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database.
A database is a structured collection of data. Data refers to the characteristics of people,
things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single complete unit
of data, called a record (it can also be referred to as raw or an occurrence). Each record is made
up of a number of fields. No two fields in a record can have the same field name.

Software Requirements Specification Page

 During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time, you
define any additional fields or change the definition of existing fields.

4. Analysis Models
Spiral Model
Here in the Online Question Paper Delivery System the spiral model will use as analysis
model.
The steps for Spiral Model can be generalized as follows:
 The new system requirements are defined in as much details as possible. This usually
involves interviewing a number of users representing all the external or internal users and
other aspects of the existing system.
 A preliminary design is created for the new system.
 A first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system, and represents an approximation of the characteristics of the
final product.
 A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning an designing the second prototype.
4. Constructing and testing the second prototype.
 At the customer option, the entire project can be aborted if the risk is deemed too great.
Risk factors might involved development cost overruns, operating-cost miscalculation, or
any other factor that could, in the customer’s judgment, result in a less-than-satisfactory
final product.
 The existing prototype is evaluated in the same manner as was the previous prototype, and
if necessary, another prototype is developed from it according to the fourfold procedure
outlined above.
 The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.

Software Requirements Specification Page

  The final system is constructed, based on the refined prototype.
 The final system is thoroughly evaluated and tested. Routine maintenance is carried on a
continuing basis to prevent large scale failures and to minimize down time.

4.1s Data Flow Diagrams (DFD)

Admin Data
Admin
Storage

Download
Downloader Downloader Papers

System Process

Fig:Context 0th Level Diagram

Enter Yes Yes User

Open Login Username Check
Home
Form and User
Page
Passwor
d

No

Validates Data

Software Requirements Specification Page

 Fig: login DFD

Admin Details Data Flow:

1st level DFD:

Login Master Downloader

Open Form

Downloaders
Registration
Manage
Exam
Manage Master
Manage
Enter Login Subject
College Manage
Details Master
Master Branch
Master

Upload Logout
Validates Data Paper

Data Storage

Fig:Admin Details Data Flow 1st level DFD

Software Requirements Specification Page

Downloader Details Data Flow:
1st level DFD:

Login Master

Open Form

Manage
Contact Details

Enter Login
Details

Download Logout
Paper

Verification Validates Data

Fig:Downloader Details Data Flow 1st level DFD

Software Requirements Specification Page

Admin Details Data Flow:
2nd level DFD:

Downloader

Send
Manage
Password Via
Downloader
SMS

Send Security
Code Via SMS

Display
Downloader
Registration

Manage Manage
College Branch
Master Master Display Manage Exam
Branches Master

Display
Colleges Manage
Displays
Subject Upload Paper
Subjects
Master

Fig:Admin Details Data Flow2nd level DFD

Software Requirements Specification Page

Downloader Details Data Flow:
2nd level DFD:

Login Master

Manage
Downloaders Update
Contact
Login Details
Details

Download

Fig: Downloader Details Data Flow 2nd level DFD

4.2 State Transition Diagram

Fig: Downloader Details

Software Requirements Specification Page

 Fig: Admin Details

Software Requirements Specification Page

4.3 Usecase Diagram

Fig: Usecase of OQDS

Software Requirements Specification Page