1

Online Software Repository

Software Requirements Specification

Version 1.0

  

Group Id: F19022834A

Supervisor Name: Mam, Komal Saleem

 2

Revision History
Date Version Description Author
(dd/mm/yyyy)
23/11/2019 1.0 Online Software Repository” mc170403179
that will contain different types
of computer application
software. The available software
will be either licensed or free.
All software will be available
with their categories according
to their specific genre like
(Multimedia software, Microsoft
Office, Database Software etc.).
For licensed software, the user
will must register him/herself
on the website. There will an
online instant chat box on the
website for the 24/7 guidance
of customer
 3

Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

 4

SRS Document

Scope of Project:

The principle point of this undertaking is to build up an intelligent site that encourages
the client with an on-the-click usefulness which is valuable to discover Software for any
category with various classifications like Software’s, full versions and , trial versions and
make your own container and so on and client can get them whenever. The point of this
application is to helpful online download and online purchasing full version and trial
software.

Functional Requirements:
User Module
1. Sign up page for new users.
2. Sign in page for downloading the facility of software and personal help.
3. Only registered users can download software.
4. An instant chat box will be available at home page for 24/7 help.
Admin Module
1. Admin will maintain proper record of available software and customers in
database.
2. Admin will add the categories of the software.
3. Admin will manage all software (add or remove).
4. Registered users (customers) can purchase licensed software by using
5. Payment methods (Paypal, Credit card, Debit card).
The website will allow the visitors to search the software by different
filters.
Non Functional Requirements

 Manageability
 Usability
 Performance
 Reliability
 Maintainability
 Availability
 Accessibility
 5

Use Case Diagram:

Online Software Repository

Place Holder <<include>> Log In

<<include>>

Cancel Order

add Category
Search Category

Delet Category

Order

user admin
Update Category

Payment Mode

Manage Record

Registration
 6

Usage Scenarios:

Use Case Title Login

Use Case ID OSR1
Actor(s) User, Admin
Description User opt to login to the website
Pre-Conditions User must have internet access.
Extend (s) Nil
Include (s) Nil
Task Sequence Exception
(i) User Open the website. Invalid user name or password
(ii) Click on login button appears on main page.
(iii) Enter his Use name and password.
(iv) Click on login button.

Post Conditions Action performed successfully, User logged in successfully

Alternative Path Redirected to login page with error message.
Author (s) mc170403179

Use Case Title Register

Use Case ID OSR 2
Actor(s) User
Description User opt to register to the website
Pre-Conditions User must have internet access.
Extend (s) Nil
Include (s) Nil
Task Sequence Exception
(i) User Open the website. Server not found
(ii) Click on register button appears on main page.
(iii) Enter his Use name and password and other details.
(iv) Click on Register button.

Post Conditions Action performed successfully; User registered successfully

Alternative Path Cancel operation. Registration not done.
Author (s) mc170403179
Use Case Title Add Category / Sub Category
 7

Use Case ID OSR 3

Actor(s) Admin
Description Admin opt to add / update / delete
Pre-Conditions User must have valid login ID and Password.
Extend (s) Nil
Include (s) Nil
Task Sequence Exception
(i) Admin add Item details / particulars. Invalid input details
(ii) Admin has update / change information about any
category.
Post Conditions Action performed successfully, User Enter Item or details successfully
Alternative Path Redirected to main page with error message.
Author (s) mc170403179

Use Case Title View Category / Search

Use Case ID OSR 4
Actor(s) User
Description User opt to check fare
Pre-Conditions User can view / search Items without login ID and Password.
Extend (s) Nil
Include (s) Nil
Task Sequence Exception
(i) User Click on view Available Items. Invalid input details
(ii) User Select item and quantity.

Post Conditions Action performed successfully, User check the fare.

Alternative Path Redirected to main page with error code.
Author (s) mc170403179

Use Case Title Make Order

 8

Use Case ID OSR 5

Actor(s) User
Description User opt to check availability, Edit, Delete, Quantity / Order
Pre-Conditions User must have valid login ID and Password.

Extend (s) Nil

Include (s) Nil
Task Sequence Exception
(i) User Click on view available product. Invalid input details
(ii) User select city and date.
(iii) System display Items and available Item.
(iv) User selects a product for order.

Post Conditions Action performed successfully, User check availability and order selected
product
Alternative Path Redirected to main page with error code.
Author (s) mc170403179

Use Case Title Made Payment

Use Case ID OSR 6
Actor(s) User
Description User opt to pay
Pre-Conditions User must have valid login ID and Password.
Extend (s) Nil
Include (s) Nil
Task Sequence Exception
(i) User click on via online payment Invalid input details
(ii) User pay through Paypal, Credit card, Debit card mode.
(iii) System display Total price & invoicing.
(iv) User click on payment mode cash at delivery.
Post Conditions Action performed successfully, User made payment successfully.
Alternative Path Redirected to main page with error code.
Author (s) mc170403179
 9

Adopted Methodology
The Waterfall model:
The Waterfall Model was first Process Model to be introduced. It is also referred to as a
linear-sequential life cycle model.  It is very simple to understand and use.  In a
waterfall model, each phase must be completed fully before the next phase can begin.   At
the end of each phase, a review takes place to determine if the project is on the right path
and whether or not to continue or discard the project. In waterfall model phases do not
overlap.

To follow the water fall model one must proceed from one phase to the next in purely
sequential manner. For example, first phase “requirements” is complete and set as stone
then we move to the next phase. The documentation of requirement is prepared and then
design phase started to implement the requirements depicted. After the design phase
completion, designs will hand over to the coders for design implementation. After coding
it is being analyzed to depict the errors in the code and then these errors are removed, and
documented. Then in the next phase separately produced components are being integrated
and tested. And we move toward the close out of the project.
Reasons for choosing the Methodology
VU process was chosen model for the following reasons
 Waterfall methodology is simplest of all methodologies but it had following drawbacks
 Waterfall methodology is strictly sequential which does not allow any development out
of sequence which is not good for this project
 In waterfall testing of software is not easy as the next iteration is only started after fully
completing the last iteration.
 If some changes are to be made in the software in some later stages it is virtually
impossible in waterfall methodology
 Agile model is only for small and team work projects so it was not an option

 Spiral model which is an extension of waterfall model is the right model. For added
simplicity the original waterfall model is mix with this model
 In this model a starting design is available which could be developed further
 10

 Prototype can be develop on which, strengths and weaknesses of the design could be
tested
 In future prototypes, previous builds can be evolved.
 Inclusion of waterfall model will keep it simple enough.
 Testing is possible with prototypes.
 More than one prototype can be built at a time.
 Final system will be built on the best prototype.
The spiral model combines the idea of iterative development with the systematic,
controlled aspects of the waterfall model.

Spiral model is a combination of iterative development process model and sequential

linear development model i.e. waterfall model with very high emphasis on risk analysis.
It allows for incremental releases of the product, or incremental refinement through each
iteration around the spiral.

Vu process model is combination of water fall and spiral model. This process model
maximizes the quality of system and reduces the risk and disadvantages. Easily
understandable in pictorial:
11
 12

Work Plan / Gantt Chart

G antt charts are useful tools for planning and scheduling projects. They allow
you to assess how long a project should take, determine the resources needed, and lay out
the order in which tasks need to be carried out. They are useful in managing the
dependencies between tasks.

When a project is under way, Gantt charts are useful for monitoring its progress.
You can immediately see what should have been achieved at a point in time, and can
therefore take remedial action to bring the project back on course. This can be essential
for the successful and profitable implementation of the project. We plan our work and
make a Gantt chart for that.