Software Requirements Specifications

Title: Online Weapons Purchase

System

Name: Muhammad Nofil Bhatty

ID: F2016065089
Section: W-3
Requirement Engineering Processes
1- Requirements Elicitation:-

 Define product vision and project scope:-

Online weapons purchase system is used to provide ease of access, quality, 24/7,
secure delivery weapons availability to the user.

Weapons shall only be given to the user if he/she is local i.e. not living overseas,
has the weapons license and has no criminal background.

 Identify user classes and their characteristics:-

Customer shall be buying a/are specific weapons according to his taste. He can
be of army, police, bodyguard, general public etc.

Army shall be buying for defense purposes, police for protection against armed
criminals, bodyguards for guarding their hirers, general public for a personal
interest of using them in an un-harmful way etc.

 Distribute questionnaires:-
A product champion shall be given certain questionnaires according to their
requirements so that they will help in developing the system according to their
proposed requirements.

2- Requirement Analysis:-

 Model the application environment:-

Our application shall interact with various external interfaces like police
database management system, user identity system, security system etc. which
shall be in the context of our proposed system.

 User interface and technical prototype:-

 A working prototype along-with good graphical user interface (GUI) shall be
given to the user for checking so that they will give their suggestion on that
system and convey any misunderstanding in the requirements.

 Prioritize requirements:-
User taste related activities shall be prioritized in order to make a good
impression of the system to increase its users.

 Create a data dictionary:-

Weapons related terminologies shall be given accordingly to facilitate the user
and to eliminate any ambiguities in the system.

3- Requirements Specification:-

 Adopt requirement document templates:-

Our system shall be adapting the SRS template to provide a consistent structure
for recording various groups of requirements-related information.

 Identify requirement origins:-

Each requirement of our system shall be traced back to its origin in order to
contact a specific stakeholder when a change in that specific requirement is
requested.

 Record business rules:-

Each business rule of our system i.e. checking a person’s weapons license,
checking his locality, checking his criminal background etc. shall be properly
documented in our system.

4- Requirements Validation:-
 Review the requirements:-
Each requirement of our system shall be reviewed and corrected accordingly. For
this a small team of reviewers such as analyst, customer, developer and tester
should be deployed.
  Test the requirements:-
Each requirement of our system shall be tested and corrected accordingly. For
that various tests shall be written for each requirement.

 Simulate the requirements:-

Simulation should be made of the whole system and shown to the user so that to
check whether the system is in accordance with the user’s proposed
requirements.

5- Requirements Management:-

 Establish a requirements change control process:-

Our system shall be ready in order to accommodate any change so that a chaos
must not happen in any case.

 Perform impact analysis on requirement changes:-

Each requirement change in the system shall be analyzed in such a way that
what changes are needed to be made if one happens.

 Maintain a history of requirement changes:-

Each requirement change shall be having an appropriate history so that one can
know how a specific requirement is into its current state in our system.

6- Knowledge:-

 Train business analysts:-

Every business analyst shall be trained whether he has the appropriate title or
acting as one.

 Educate stake holders about requirements:-

 Every stakeholder shall be given education about the requirements related
terms, key concepts and practices of our system so that they understand what to
say in the requirements.

 Create a glossary:-
A glossary of the whole system should be made to clear the misunderstandings.
It must include synonyms, acronyms or abbreviations, terms that can have
multiple meanings, and terms that have both domain specific and everyday
meanings in order to minimize misunderstandings.

7- Project Management:-

 Select an appropriate software development life cycle:-

Our system shall be a selecting software development life cycle which is the best
according to our system.

 Track the effort spent on requirements:-

Our project management team shall be tracking their expends on requirement
development and management activities in order to estimate the required
investments on future projects.

 Analyze, document and manage requirements-related risks:-

In order to avoid unanticipated events our team shall be identifying and

documenting risks related to requirements as part of the project’s risk-
management activities.