Software Requirement specification
SRS
1. INTRODUCTION
This
SRS document is for a software house’s website (Anysoftwarehouse.com) This document
provides overview of the SRS for our website.It includes purpose of our website.
It provides scope of website and definitions and reference and the overview is also
written in SRS.
1.1
Purpose the purpose of this SRS document is to define website’s
functionality, parameters and goals, requirements for design, requirements of
clients which he wants from our software house. It may also contains the description
and sequence of steps to build this site
1.2 Scope our
website will provide all information about our services, our reliable and
remarkable projects, our recent projects and quality which will help people to
make decisions about which is best for them. There will be login panel for
users, employees and authority. People can contact our developers to get information
about their products and about any query.
1.3 Definitions, Acronyms,
Abbreviations
|
SRS
|
Software Requirement specification
|
|
Admin
|
Manager of System
|
|
User
|
Someone Interacts with System
|
|
Privileged user
|
User having Specific Rights
|
|
IEEE
|
Institute of Electrical and Electronics Engineering
|
|
FAQ
|
Frequently Asked Questions
|
|
ASP
|
A Programing Language
|
1.4 References
IEEE Guide for Developing Software Requirements
Specifications, IEEE Std 1233, 1998 Edition,
IEEE
Software Engineering Standards Committee, “IEEE
Std 830-1998,
IEEE Recommended Practice for
Software Requirements Specifications”, 1998.
Remaining section is about the system, data requirements and
characteristics of the user. The 1st section of this document is about the
purpose and scope of this product and second Section is about the system, in
this section system or product is described which consist of functionality of
the web and its interaction with the user and with system on which it is
running and the 3rd section of this document is about the
requirements of the system in detail including performance and functional
requirements and also external interface.
2.
Overall Description
This Document provides the background for those requirements which are
described in section 3 like external interface, performance and functional
requirements, these information are described in such a way that these are
easily understandable. This is overview of the system. It also provides
information about the stakeholder and its nature which is going to use it. Last
part is about the constraints and assumptions
2.1 Product Perspective As
our website is independent so it is not a part of any larger system. Our
website is totally self-contained so it is not dependent to any other site or
program.
Our site has
ability to operate in different constraints like as:
1- System Interface
2- User interface
3- Hardware Interface
4-Software Interface
5- Memory Constraints
6- Operations
7- Site adaption Requirements
2.1.1 System Interface System interface may consist of CPU
monitor and the user of system. User may be a visitor of the site or the client
of our software house. User can visit our website, our work, our projects,
latest events occurring in our software house and the latest news and also can
contact our developers about their queries and their requirements about their
product.
2.1.2 User Interface A
user can visit our website, can search within our site, can view our gallery,
can contact to our developers but he will not be able to make any kind of
change to our site. He can use our site at different web browsers it is
flexibility of our site. He can also view website in different configuration.
So user interface is consisting of configuration characteristics.
2.1.3 Hardware Interface This
is about the type of the hardware which should use for our website and it also
includes other specific hardware like mouse, keyboard and printer. Is Keyboard
can operate on our site or not similarly specified situations in which a mouse
should operate or not. Hardware and Processor should be most efficient so a user may get best results.
2.1.4 Software Interface Software Interfaces includes required
software product to complete the project. As for the front end of the website
visual studio may be used and for the back end and for storing record Oracle
database is used. So different software used in completing the project
2.1.6 Operations Our website provides different modes of operations such as
management operations and authorized operations
2.1.7 Site
adaptation requirements our
website will represent our software house. This will help us to show our
achievements. People will visit this and they will be assured that we can
fulfill their needs in a best way.
2.2 Product Functions
This includes all the major functions
of the website which it will perform as management and authorized functions.
Admin can make changes to the site. He can update the data, news, events and
Projects and a user can view all these things. Workers can also create their
accounts and can see their current status and details. Visitors will be able to
contact to the developers for any query. Our website will consist of following
menus or pages:
Home: All basic information will be on homepage.
News & Events: This will consist of all latest news and
occurring Events of our software house.
Projects: our all completed projects will be listed in
this menu. A visitor can visit them.
Register: This menu is for the registering the privileged
users.
Login:
This is for the admin and privileged user to login to the site.
Contact us:
Visitors can contact to our admin for any query or can give their
feedback.
2.3 User
characteristics
User of the website may be a client,
worker and Admin.
A client usually can visit our site and will see our projects
and services and can contact our developers if he wants a service from us or
simply he can feed back us.
An employee or worker can just login to his account and can
see and update his current status and details.
On the other Hand, Admin can visit the site, login and can
make changes and updates the data.
2.4 Constraints
Developer should limit
the privileges of
the user so
that they cannot
harm system server. Website should be efficient and it
should work on all browsers without any problem and issue
2.5 Assumption and dependencies
To run a website a source or operating system as Windows and Mac or
Mobile is required, so it is a dependent and without any operating system a
website can’t run so operating system is necessary for it
3.
Specific Requirements
This section is about the inputs and outputs.
Inputs which our website can support and what will be the required outputs.
3.1
External Interface
External interface is about the interaction with website of the user or
admin. User and privileged users can visit site, they can use register button
to register in the site and have facility to login. Admin can login to the site
and can perform different operations. If admin or privileged user enter wrong
name or password( which is not same as were in register form) to login then
site will not give access to their account and operation will be fail and then
he can try again to login. In login panel characters, symbols and numbers will
be supported.
3.2
Functions
Visitors can only visit the site they are
not allowed to make any change in the site.
Employee can register himself and then can see his details,
on the other hand admin can make changes to the site and can manage the data
but for this he have to login to the site and for the login he have to write
correct information in login input boxes, if he inputs wrong information then
site will reject it and he have to input correct information. Privileged users
have to provide all required information to
site to register. He is allowed to use characters and numbers and symbols in
input fields.
3.3
Performance Requirements
Since a website may be viewed by hundred, thousand viewers
simultaneously so it should in such condition that it can handle this number of
viewers. So for this purpose there should be enough powerful server machines
and high speed internet access and its data base should also capable to manage this
number of users at the same time.
3.4
Standard compliance
Database will store all records and data and when changes are made then
database will store updates.
3.5
Design constraints
This should specify design constraints that
can be imposed by other standards, hardware limitations.
3.6
Software System Attributes
There are a number of
attributes of software that can serve as requirements. It is important that
required attributes be specified so that their achievement can be objectively verified.
3.6.1 Reliability
All
functions of the website are fully reliable and fulfil the requirements.
3.6.2 Availability
Required
functions are available and able to perform at their demand.
3.6.3 Security
Website’s
security is strict. Visitors just can visit the site and cannot make any change
to the site. No one can login to another’s account and see their information.
3.6.4 Maintainability
Maintenance
can be performed at any time when needed. Functions of the site are easily
modifiable.
3.6.5 Portability
Website can run on any operating system such as windows, Linux and mac.
It can run on any web browser.
3.7
Organizing the specific Requirement
3.7.1 System Mode
Our
website can run on normal mode.
3.7.2 User Class
There
are 3 types of user
1. Admin
2.
Employee
3.
Privileged user
3.7.3 Objects
Different
objects can perform different actions depending on their role.
Sets of objects may share attributes and services. These are
grouped together as classes.
3.7.4 Feature
Our website includes different
features like News, Events, projects, Expertise, register & Login page
which perform different functions and each of these pages having different
features respectively.
3.7.6 Response
Functions defined in the form of Response:
Response 1: All Users interacting with
the system.
Response 2: All functions performed by the users.
3.8
Additional Comments
All the
required functionalities of system are described above are working properly.
All inputs and outputs are Responsive.
All the document is created using
English language.
0 comments:
Post a Comment