THe Provider Ltd.

Web Publishing System

Software Requirements Specification

Version <1.0>
Web Publishing System Version: 1.0
Software Requirements Specification Date: 20/02/2016
SRS_1.0

Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>

Confidential THe Provider Ltd., 1999 Page 2

Web Publishing System Version: 1.0
Software Requirements Specification Date: 20/02/2016
SRS_1.0

Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms and Abbreviations 4
1.4 References 4
1.5 Overview 5

2. Overall Description 5

3. Specific Requirements 6
3.1 Functionality 6
3.1.1 <Functional Requirement One> Error! Bookmark not defined.
3.2 Usability Error! Bookmark not defined.
3.2.1 <Usability Requirement One> 6
3.3 Reliability 6
3.3.1 <Reliability Requirement One> Error! Bookmark not defined.
3.4 Performance 6
3.4.1 <Performance Requirement One> Error! Bookmark not defined.
3.5 Supportability 7
3.5.1 <Supportability Requirement One> Error! Bookmark not defined.
3.6 Design Constraints Error! Bookmark not defined.
3.6.1 <Design Constraint One> Error! Bookmark not defined.
3.7 Online User Documentation and Help System Requirements Error! Bookmark not defined.
3.8 Purchased Components Error! Bookmark not defined.
3.9 Interfaces Error! Bookmark not defined.
3.9.1 User Interfaces Error! Bookmark not defined.
3.9.2 Hardware Interfaces Error! Bookmark not defined.
3.9.3 Software Interfaces Error! Bookmark not defined.
3.9.4 Communications Interfaces Error! Bookmark not defined.
3.10 Licensing Requirements Error! Bookmark not defined.
3.11 Legal, Copyright and Other Notices Error! Bookmark not defined.
3.12 Applicable Standards Error! Bookmark not defined.

4. Supporting Information Error! Bookmark not defined.

Confidential THe Provider Ltd., 1999 Page 3

Web Publishing System Version: 1.0
Software Requirements Specification Date: 20/02/2016
SRS_1.0

Software Requirements Specification

1. Introduction
1.1 Purpose
The purpose of this document is to present a detailed description of the Web Publishing System. It will
explain the purpose and features of the system, the interfaces of the system, what the system will do, the
constraints under which it must operate and how the system will react to external stimuli. This document is
intended for both the stakeholders and the developers of the system and will be proposed to the Regional
Historical Society for its approval.
1.2 Scope
This software system will be a Web Publishing System for a local editor of a regional historical society.
This system will be designed to maximize the editor’s productivity by providing tools to assist in
automating the article review and publishing process, which would otherwise have to be performed
manually. By maximizing the editor’s work efficiency and production the system will meet the editor’s
needs while remaining easy to understand and use.
1.3 Definitions, Acronyms and Abbreviations
Term Definition
Active Article The document that is tracked by the system; it is a narrative that is
planned to be posted to the public website.
Author Person submitting an article to be reviewed. In case of multiple
authors, this term refers to the principal author, with whom all
communication is made.
Database Collection of all the information monitored by this system.
Editor Person who receives articles, sends articles for review, and makes final
judgments for publications.
Field A cell within a form.
Historical Society Database The existing membership database (also HS database).
Member A member of the Historical Society listed in the HS database.
Reader Anyone visiting the site to read articles.
Review A written recommendation about the appropriateness of an article for
publication; may include suggestions for improvement.
Reviewer A person that examines an article and has the ability to recommend
approval of the article for publication or to request that changes be
made in the article.
Software Requirements A document that completely describes all of the functions of a
Specification proposed system and the constraints under which it must operate. For
example, this document.
Stakeholder Any person with an interest in the project who is not a developer.
User Reviewer or Author.

1.4 References
UC Specification of
[This subsection should provide a complete list of all documents referenced elsewhere in the SRS. Each

Confidential THe Provider Ltd., 1999 Page 4

Web Publishing System Version: 1.0
Software Requirements Specification Date: 20/02/2016
SRS_1.0

document should be identified by title, report number (if applicable), date, and publishing organization.
Specify the sources from which the references can be obtained. This information may be provided by
reference to an appendix or to another document.]
1.5 Overview
The next chapter, the Overall Description section, of this document gives an overview of the functionality
of the product. It describes the informal requirements and is used to establish a context for the technical
requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written primarily for the
developers and describes in technical terms the details of the functionality of the product.
Both sections of the document describe the same software product in its entirety, but are intended for
different audiences and thus use different language.
2. Overall Description
2.1 Scenario
The Web Publishing System has four active actors and one cooperating system.
The Author, Reader, or Reviewer accesses the Online Journal through the Internet. Any Author or
Reviewer communication with the system is through email. The Editor accesses the entire system directly.
There is a link to the (existing) Historical Society.
<< The division of the Web Publishing System into two component parts, the Online Journal and the
Article Manager, is an example of using domain classes to make an explanation clearer. >>
2.2 Use Case

Rea
der

Aut Online
hor Journal

Article
Manager
Review HS
er DB
Web Publishing
System

Edito
r
Figure 1 - System Environment

Confidential THe Provider Ltd., 1999 Page 5

Web Publishing System Version: 1.0
Software Requirements Specification Date: 20/02/2016
SRS_1.0

3. Specific Requirements
3.1 Functionality
ID Description Priority

F001 The reader can search article Must

F002 The user can communicate with each other Must

F003 The manager can add author Must

F004 The manager can add reviewer Must

F005 The user can update his profile Must

F006 The manager can update an article status Must

F007 The user can enter a communication Must

F008 The manager can assign reviewer to review an article Must

F009 The author can check status of his paper Must

F010 The manager can publish an article Must

F011 The author can remove an article Must

3.2 Security
SENF01. (MUST) The server on which the Online Journal resides will have its own security to prevent
unauthorized write/delete access
SENF02. (MUST) There must be no restriction on read access.
SENF03. (MUST) The use of email by an Author or Reviewer must be on the client systems and thus is
external to the system.
SENF04. (MUST) The PC on which the Article Manager resides must have its own security.
SENF05. (OPTIONAL) Only the Editor shall have physical access to the machine and the program on it.

3.3 Reliability
RNF01. (MUST) The system must provide 91.2 % of time available ( xx.xx%), hours of use, maintenance
access, degraded mode operations etc.
RNF02 (MUST) The system must provide minimum 351 days Mean Time Between Failures (MTBF).
RNF03 (MUST) The system must provide maximum 24 hours Mean Time To Repair (MTTR).
RNF04 (OPTIONAL) The system shall maintain maximum 1 bugs/KLOC.

3.4 Performance
PNF01 (MUST) The system must provide maximum 2.5 msec response time for a transaction.
PNF02 (MUST) The system must provide minimum 500 transactions per second
PNF03 (MUST) The system must maintain minimum 1.500 customers.
PNF04 (MUST) The system must maintain minimum 1.000.000 transaction per year for 10 years.

Confidential THe Provider Ltd., 1999 Page 6

Web Publishing System Version: 1.0
Software Requirements Specification Date: 20/02/2016
SRS_1.0

3.5 Supportability
SPNF01 (OPTIONAL) The system shall support United Nations International languages

Confidential THe Provider Ltd., 1999 Page 7