Académique Documents
Professionnel Documents
Culture Documents
Version 1.0
Date
(dd/mm/yyyy)
04/08/2015
Version
1.0
Revision History
Description
Software Requirements
Specification Document
Author
MC
Name..
Table of Contents
The work and resources that go into the creation of the product or service are essentially the
things that frame the scope of the project. The scope of the project outlines the objectives of the
project and the goals that need to be met to achieve a satisfactory result. Every project manager
should understand how to define the project scope and there are some steps that can be followed
when doing this.
To define a project scope, you must first identify the following things:
1.
Project objectives
2.
Sub-phases
3.
Tasks
4.
Resources
Non-functional requirements
Non-functional Requirements: specify the quality of the system, is mostly related to the
satisfiability of the user.
Non-functional requirements describe how the system works, while functional requirements
describe what the system should do.
The definition for a non-functional requirement is that it essentially specifies how the system
should behave and that it is a constraint upon the systems behavior.
Some typical non-functional requirements are:
Scalability
Capacity
Availability
Reliability
Recoverability
Maintainability
Serviceability
Security
Regulatory
Manageability
Environmental
Data Integrity
Non-Functional Requirements are as follows:
Usability:
This application can be used by a single user at a time
Performance:
Application should perform all of its functions excellently and effectively
without any inconvenience.
Availability:
This application will be available free for everyone
Portability:
The application can easily portable from one desktop application to
another
User Friendly:
Application will have a user friendly interface.
Scalability:
This application should be more scalable and allow management
to add more functionality.
Use cases can be employed during several stages of software development, such as planning
system requirements, validating design, testing software, and creating an outline for online help
and user manuals
4. Usage Scenarios
A usage scenario, or scenario for short, describes a real-world example of how one or more
people or organizations interact with a system. They describe the steps, events, and/or actions
which occur during the interaction. Usage scenarios can be very detailed, indicating exactly how
someone works with the user interface, or reasonably high-level describing the critical business
actions but not the indicating how they're performed.
High-Level Example
Scenario: ATM banking for the week.
1. Ali khan places her bank card into the ATM.
2. Ali successfully logs into the ATM using her personal identification number.
3. Ali deposits her weekly paycheck of $350 into her savings account.
4. Ali pays her phone bill of $75, her electric bill of $145, her cable bill of $55, and her water
bill of $85 from her savings account
5. Ali attempts to withdraw $100 from her savings account for the weekend but discovers
that she has insufficient funds
6. Ali withdraws $40 and gets her card back
5. Adopted Methodology
It is decided to select VU process Model that is a Combination of Water Fall model and Spiral
Model.
The waterfall model is a sequential design process, used in software development processes, in
which progress is seen as flowing steadily downwards (like a waterfall) through the phases of
Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and
Maintenance.
The spiral model, also known as the spiral lifecycle model, is a systems development method
(SDM) used in information technology (IT). This model of development combines the features
of the prototyping model and the systems development life cycle (SDLC).