Software Requirements

Specification
for
Automated Project Monitoring
System
Version 1.0 approved
Prepared by
eano
Pasa
!ugade
"a#iwag
Repub#ic of t$e P$i#ippines
%ureau of &mmigration
Marc$ 1 ' (01)
Copyright 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose........................................................................................................................................... 1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope................................................................................................................................. 1
1.5 References...................................................................................................................................... 1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics....................................................................................................2
2.4 Operating Environment..................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies.....................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................ 3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces......................................................................................................................... 3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1
1. Introduction
1.1 Purpose
This document specifies the Software Requirements Specification(SRS) for the Automated
Project Monitoring System. It describes the scope description and overview of a conceptual model
of a Web-Based Computer application for the section of General Service in the Bureau of
Immigration, Republic of the Philippines. Also, It describes the functional scope of the software,
design constraints and system interface.
1.2 Document Conventions
<Describe any standards or typographical conventions that were followed when writing this SRS,
such as fonts or highlighting that have special significance. For example, state whether priorities
for higher-level reuirements are assumed to be inherited by detailed reuirements, or whether
every reuirement statement is to have its own priority.!
1.3 Intended Audience and Reading Suggestions
<Describe the different types of reader that the document is intended for, such as developers,
pro"ect managers, mar#eting staff, users, testers, and documentation writers. Describe what the
rest of this SRS contains and how it is organi$ed. Suggest a seuence for reading the document,
beginning with the overview sections and proceeding through the sections that are most pertinent
to each reader type.!
1.4 Product Scope
The Automated Project Monitoring System is a Web-Based Computer application used for
monitoring the progress of different activities or projects such as acquisitions, upgrades,
maintenance etc. such that all of the details of the projects are stored in a database. The application
can be viewed by all personnel but only authorized personnel can alter its content.
The Automated Project Monitoring System addresses the management of different activities or
projects. The system will be implemented to automate the manual project monitoring board to
provide the management a easily updates of the projects progress, update changes or completion of
each projects, show total completion rate of the projects, record current and completed projects and
generate reports more efficiently.
.
Software Requirements Specification for <Project> Page 2
1.5 References
[1] Software Requirements Specification for
Project Management System project Online Internet. [November, 10, 2007] Available
WWW.http://se.inf.ethz.ch/courses/2011b_fall/dose/slides/requirements/Doc1.pdf
[2] Software Requirement Specification Online Internet. [January 28, 2005] Available WWW
http://www.cs.utah.edu/~jamesj/ayb2005/docs/SRS.htm#1.2
[3] Web Based Project Monitoring System Online Internet. [June 2011] Available WWW
http://cpwdpims.nic.in/pims/download/PMSHelpFile.pdf
[4] Gui Prototyping Tools Online Internet. [November 10,2013] Available WWW
http://c2.com/cgi/wiki?GuiPrototypingTools
2. Overall Description
2.1 Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example, state
whether this product is a follow-on member of a product family, a replacement for certain existing
systems, or a new, self-contained product. %f the SRS defines a component of a larger system,
relate the reuirements of the larger system to the functionality of this software and identify
interfaces between the two. & simple diagram that shows the ma"or components of the overall
system, subsystem interconnections, and external interfaces can be helpful.!
2.2 Product Functions
<Summari$e the ma"or functions the product must perform or must let the user perform. Details
will be provided in Section ', so only a high level summary (such as a bullet list) is needed here.
*rgani$e the functions to ma#e them understandable to any reader of the SRS. & picture of the
ma"or groups of related reuirements and how they relate, such as a top level data flow diagram
or ob"ect class diagram, is often effective.!
2.3 User Classes and Characteristics
<%dentify the various user classes that you anticipate will use this product. +ser classes may be
differentiated based on freuency of use, subset of product functions used, technical expertise,
security or privilege levels, educational level, or experience. Describe the pertinent characteristics
of each user class. ,ertain reuirements may pertain only to certain user classes. Distinguish the
most important user classes for this product from those who are less important to satisfy.!
2.4 Operating Environment
<Describe the environment in which the software will operate, including the hardware platform,
operating system and versions, and any other software components or applications with which it
must peacefully coexist.!
Software Requirements Specification for <Project> Page 3
2.5 Design and Implementation Constraints
<Describe any items or issues that will limit the options available to the developers. -hese might
include. corporate or regulatory policies/ hardware limitations (timing reuirements, memory
reuirements)/ interfaces to other applications/ specific technologies, tools, and databases to be
used/ parallel operations/ language reuirements/ communications protocols/ security
considerations/ design conventions or programming standards (for example, if the customer0s
organi$ation will be responsible for maintaining the delivered software).!
2.6 User Documentation
<1ist the user documentation components (such as user manuals, on-line help, and tutorials) that
will be delivered along with the software. %dentify any #nown user documentation delivery formats
or standards.!
2.7 Assumptions and Dependencies
<1ist any assumed factors (as opposed to #nown facts) that could affect the reuirements stated
in the SRS. -hese could include third-party or commercial components that you plan to use,
issues around the development or operating environment, or constraints. -he pro"ect could be
affected if these assumptions are incorrect, are not shared, or change. &lso identify any
dependencies the pro"ect has on external factors, such as software components that you intend
to reuse from another pro"ect, unless they are already documented elsewhere (for example, in the
vision and scope document or the pro"ect plan).!
3. External Interface Requirements
3.1 User Interfaces
<Describe the logical characteristics of each interface between the software product and the
users. -his may include sample screen images, any 2+% standards or product family style guides
that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that
will appear on every screen, #eyboard shortcuts, error message display standards, and so on.
Define the software components for which a user interface is needed. Details of the user interface
design should be documented in a separate user interface specification.!
3.2 Hardware Interfaces
<Describe the logical and physical characteristics of each interface between the software product
and the hardware components of the system. -his may include the supported device types, the
nature of the data and control interactions between the software and the hardware, and
communication protocols to be used.!
3.3 Software Interfaces
<Describe the connections between this product and other specific software components (name
and version), including databases, operating systems, tools, libraries, and integrated commercial
Software Requirements Specification for <Project> Page 4
components. %dentify the data items or messages coming into the system and going out and
describe the purpose of each. Describe the services needed and the nature of communications.
Refer to documents that describe detailed application programming interface protocols. %dentify
data that will be shared across software components. %f the data sharing mechanism must be
implemented in a specific way (for example, use of a global data area in a multitas#ing operating
system), specify this as an implementation constraint.!
3.4 Communications Interfaces
<Describe the reuirements associated with any communications functions reuired by this
product, including e-mail, web browser, networ# server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. %dentify any communication
standards that will be used, such as F-3 or 4--3. Specify any communication security or
encryption issues, data transfer rates, and synchroni$ation mechanisms.!
4. System Features
<-his template illustrates organi$ing the functional reuirements for the product by system
features, the ma"or services provided by the product. 5ou may prefer to organi$e this section by
use case, mode of operation, user class, ob"ect class, functional hierarchy, or combinations of
these, whatever ma#es the most logical sense for your product.!
4.1 System Feature 1
<Don0t really say 6System Feature 7.8 State the feature name in "ust a few words.!
4.1.1 Description and Priority
<3rovide a short description of the feature and indicate whether it is of 4igh,
9edium, or 1ow priority. 5ou could also include specific priority component ratings,
such as benefit, penalty, cost, and ris# (each rated on a relative scale from a low of
7 to a high of :).!
4.1.2 Stimulus/Response Sequences
<1ist the seuences of user actions and system responses that stimulate the
behavior defined for this feature. -hese will correspond to the dialog elements
associated with use cases.!
4.1.3 Functional Requirements
<%temi$e the detailed functional reuirements associated with this feature. -hese
are the software capabilities that must be present in order for the user to carry out
the services provided by the feature, or to execute the use case. %nclude how the
product should respond to anticipated error conditions or invalid inputs.
Reuirements should be concise, complete, unambiguous, verifiable, and
necessary. +se 6-;D8 as a placeholder to indicate when necessary information is
not yet available.!
<<ach reuirement should be uniuely identified with a seuence number or a
meaningful tag of some #ind.!
REQ-1:
REQ-2:
Software Requirements Specification for <Project> Page 5
4.2 System Feature 2 (and so on)
5. Other Nonfunctional Requirements
5.1 Performance Requirements
<%f there are performance reuirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and ma#e suitable
design choices. Specify the timing relationships for real time systems. 9a#e such reuirements as
specific as possible. 5ou may need to state performance reuirements for individual functional
reuirements or features.!
5.2 Safety Requirements
<Specify those reuirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be ta#en, as well
as actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product0s design or use. Define any safety certifications that must be
satisfied.!
5.3 Security Requirements
<Specify any reuirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
reuirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.!
5.4 Software Quality Attributes
<Specify any additional uality characteristics for the product that will be important to either the
customers or the developers. Some to consider are. adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. =rite these to be specific, uantitative, and verifiable when possible. &t the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.!
5.5 Business Rules
<1ist any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. -hese are not functional reuirements in
themselves, but they may imply certain functional reuirements to enforce the rules.!
Software Requirements Specification for <Project> Page 6
6. Other Requirements
<Define any other reuirements not covered elsewhere in the SRS. -his might include database
reuirements, internationali$ation reuirements, legal reuirements, reuse ob"ectives for the
pro"ect, and so on. &dd any new sections that are pertinent to the pro"ect.!
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. 5ou may wish to build a separate glossary that spans multiple pro"ects or the entire
organi$ation, and "ust include terms specific to a single pro"ect in each SRS.!
Appendix B: Analysis Models
<*ptionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
Appendix C: To Be Determined List
<,ollect a numbered list of the -;D (to be determined) references that remain in the SRS so they
can be trac#ed to closure.!