Software Requirement Specification for Digital Publishing Software

This document provides a detailed description of a digital publishing software, including its purpose, features, interfaces, and constraints. It is intended for software developers, stakeholders, and relevant authorities for approval.

Software Requirement Specification for Digital Publishing Software 1
Software Requirement Specification for Digital Publishing Software
Student
Course
Tutor
Institutional Affiliations
State
Date
Contents

Software Requirement Specification for Digital Publishing Software 2
1. Introduction.........................................................................................................................................3
1.1 Purpose........................................................................................................................................3
1.2 Document Conventions................................................................................................................3
1.3 Intended Audience and Reading Suggestions..............................................................................4
1.4 Project Scope...............................................................................................................................4
1.5 References...................................................................................................................................5
2. Overall Description..............................................................................................................................6
2.1 Product Perspective.....................................................................................................................6
2.2 Product Features..........................................................................................................................7
2.3 User Classes and Characteristics..................................................................................................8
2.4 Operating Environment................................................................................................................9
2.5 Design and Implementation Constraints......................................................................................9
2.6 User Documentation....................................................................................................................9
2.7 Assumptions and Dependencies...................................................................................................9
3. System Features.................................................................................................................................10
3.2. Language selection....................................................................................................................11
4. External Interface Requirements........................................................................................................12
4.1 User Interfaces...........................................................................................................................12
4.2 Hardware Interfaces...................................................................................................................12
4.3 Software Interfaces....................................................................................................................12
4.4 Communications Interfaces.......................................................................................................13
5. Other Nonfunctional Requirements...................................................................................................14
5.1 Performance Requirements........................................................................................................14
5.2 Safety Requirements..................................................................................................................15
5.3 Security Requirements...............................................................................................................15
5.4 Software Quality Attributes.......................................................................................................15
6. Other Requirements...........................................................................................................................15
7. References.........................................................................................................................................16
8. Appendix A: Glossary.......................................................................................................................19
9. Appendix B: Issue list........................................................................................................................19
10. Appendix C: Questionnaire...........................................................................................................20
11. Appendix D: Interview..................................................................................................................20

Software Requirement Specification for Digital Publishing Software 3
Software Requirement Specification for Digital Publishing Software
1. Introduction
1.1 Purpose
This document aims at publishing a detailed description of a digital publishing software. The
document will explicitly illustrate the purpose as well as features of the system, the software
interfaces, what the software is expected to carry out, how the system will react to external
stimuli as well as the constrain under which the software is expected to operate. This SRS is
intended for both the software developers and the stakeholders of the organization where the
software will be used, the paper will also be submitted to relevant authorities for it to be
approved.
1.2 Document Conventions
This subsection describes typographical and graphical that was followed when this software
requirement specification was being written (Rico, and Sayani, 2009, pp. 174-179):
a) The document has been written with times new roman font, size 12 in order for it to be
readable with people under visual disabilities.
b) Headings and subheadings of this document are written in bold in order to easily
distinguish them from normal text.
c) The graphical represented in this document are made clear enough and shall be visible for
people with color blindness.

Software Requirement Specification for Digital Publishing Software 4
1.3 Intended Audience and Reading Suggestions
This SRS document is intended for the following individuals:
The document is intended for the software developers who can review the capabilities of project
so as to understand where their efforts are required in order to add more features of improve the
application. The document set the guideline for the development of this digital publishing
software (Stodden, and Miguez, 2013, pp. 71).
The document can also be used by project testers as a basis for their testing strategies due to the
fact that some bugs can be easily found using the software requirement document. By this, the
software testing will be organized methodologically.
The software requirement document is also can also be used by the application users who would
like to read about what the software can do.
1.4 Project Scope
The software will be a digital publishing through which documents will be published on a
website by editors. The software will be designed in order to increase the productivity of editors
through provision of tools that will aid in automatic article review and publishing process that
would (if the software were not there) be done the manual way. By improving the efficiency and
productivity of editors’ work, the software is intended to meet the needs of the editor while
remaining easy to use and understand.
To be more specific, the software is developed to enable an editor to work with and
communicate with a group of authors and reviewers to publish documents and articles in a
website. The system is intended to facilitate the communication by reviewers, authors, and
editors through email (Carreiro, 2010 pp.219-235). Reply forms which are preformatted will be

Software Requirement Specification for Digital Publishing Software 5
used in every stage of article progress in order to have a uniform review process; form’s location
will be configurable through the maintenance option of the software. The software will also have
a list of database which will have a list containing articles, authors and reviewers.
1.5 References
This software requirement specification complies with or references the following documents:
1. Interactive digital HTLM 5 digital publishing platform for magazines, catalogs, and
more. Retrieved from: <http://fliphtml5.com/>
2. The project will comply with open process framework convention stated as follows Van
(Lamsweerde, 2009, pp. 2):
 The SRS framework and content standard which specify the content as well as format
of this software requirement specification.
 SRS template which provides an outline for this specification.
 SRS inspection checklist that is used for inspecting this SRS.
 The use case use modeling guidelines documenting the guidelines for developing the
use case model that specify functional requirements for this document.
2. Overall Description
2.1 Product Perspective
The digital publishing software will be a time saving system for authors, editors and reviewers of
articles. The system is expected to reduce the work that would be done by secretory manually; it
will therefore improve efficiency and productivity of the organization. All that the users will do
is to install it in the system for free and used it.

Software Requirement Specification for Digital Publishing Software 6
The following shows a simple diagram that shows the major components of the software, the
system connection as well as the external interfaces of the system (Rathod, Onepatont Software
Ltd, 2014, pp.14).
2.2 Product Features
The digital publishing software is expected to provide its users with the following important
functions and key features (Mahecha-Nieto, and León, 2010, pp. 214-223):
Author
The reader
Editor
DB
manager
r
Online
publications
The publishers
Manager
Digital publishing
System
Reviewer

Software Requirement Specification for Digital Publishing Software 7
1. The user login and sign up interface where all users will be required to submit their
details to the system data base.
2. PDF conversion capability: the system will be able to convert PDF documents into e-
book files that all devices are compatible with.
3. The software is cloud based, it will allow its users to store everything in a virtual space
where they can be accessed anytime and anywhere.
4. The system will have an inbuilt authoring platform where authors will be able to directly
create content and publish the content online.
5. The layout selection of the system will be fixed and reflow able in order to allow the use
of the content which has images.
6. The system support all types of multimedia enrichment.
7. The system has DRM protection and secure publishing. This will prevent any misuse,
theft and copyright violation in every field of work.
2.3 User Classes and Characteristics
All kinds of users
The digital publishing software is a powerful tool and an easy application to use. As such all
users with a basic experience with computers and smartphones will be able to effectively use it
(Bryant, Eastman Kodak Co, 2011, pp. 14).
The open source application developers and contributors
The application developers: anybody with a very good background knowledge of computer
programming so as to understand and extend the project’s source code (Al-Sharafat, and
AbuSeileek, 2012, 192-211).

Software Requirement Specification for Digital Publishing Software 8
Translators: this involves individuals from all age group with a good knowledge of language.
Anybody who would like to help the publishers’ community is welcome to contribute in any way
he or she can.
2.4 Operating Environment
The digital publishing application will run in the following windows: windows XP/ windows
vista, windows 7, windows 8, windows 10. It is also able to run in android. The application is
written in a windows dependent language, it is therefore unfortunate that the application will not
run in a mac book and linux-based operating system unless it is open in a web platform (Satish,,
2014, pp. 18-20).
2.5 Design and Implementation Constraints
The digital publishing application is developed under the general license GNU version 2, June
1991. All developers and users of the application should comply and adhere to the terms and
conditions for the above license.
2.6 User Documentation
To ensure a proper operation of the digital publishing application software, the application users
must have a knowledge of the system user interface as well as the system execution parameter.
On the off chance that an individual parameter is submitted to the software, the program
execution will not occur.
In case any technical issue is experienced while using the application, do not hesitate to contact
us through the contact in the “contact us page.”

Software Requirement Specification for Digital Publishing Software 9
2.7 Assumptions and Dependencies
It is assumed that the digital publishing application users are computer literate and are familiar
with windows operating system. The application is developed using a windows friendly
programming languages; linux and MacBook operating system will not be compatible with the
system.
3. System Features
In this section, the application’s functional requirements and its features is described. The
features will be described in details in order to help in the future editing and extensions
(Willinsky, 2018, pp. 57-59). They are the features which have been already in the application,
as such, there is no priority given. However, priority will be needed for the development of the
features that will be included in the following parts of the document (Lassila-Merisalo, 2014, pp.
1-15).
3.1. User profile
3.1.1. Description and Priority
This is a section which contains the user details and credentials. It is this part that the
application user will edit his or her details if needed. This feature should be given
the highest priority as it stores sensitive user details.
3.1.2. Stimulus/Response Sequences
For the application user to manage his profile, the user go to the profile in the application
menu. The user can either select “create your own profile” or choose “customize.”

Software Requirement Specification for Digital Publishing Software 10
By choosing “create your own profile” the user will be able to create a new profile
if he or she had not open an account earlier. When the user select “customize”, a
pop up window containing the user’s profile will appear (Lee, and Lin, 2012, pp.
420-424). From this window, the user will be able to edit his profile. The user will
also find an option to add an image where he can choose to add his or her profile
picture.
3. 1.3. Functional Requirements
For the user to create a profile, he or she must have an active email, phone number and a
secure password containing a minimum of eight characters (a mixture of letters,
numbers and special characters. Failure to provide the aforementioned
requirement, the user will be rejected by the system.
3.2. Language selection
3.2.1. Description and Priority
2. This feature enables the application users to choose their preferred language. This feature is
given a medium priority. The application has five translations of the program that is
available for whoever wants to translate it into one of the five languages. The default
language, however is UK English.
3.2.2. Stimulus/Response Sequences
3. For the application user to change the preferred language, the user go to menu, and select
languages. Upon selecting the language, a list of five languages will appear. From here, the
user then select his preferred language.

Software Requirement Specification for Digital Publishing Software 11
3.2.3. Functional Requirements
4. The user cannot select any language apart from the available languages.
4. External Interface Requirements
4.1 User Interfaces
This user application interface for this application is just a common windows interface. No more
additional interface is required for this application.
4.2 Hardware Interfaces
The online publications will be run by a server. The server will have a high speed internet.
Physical machine should be appropriately chosen by the organization that will use the
application; the connection speed of readers will depend on the hardware installed for the
application and not the application itself. The manager of publications will run the editor’s
computer which will enable access to the system database.
4.3 Software Interfaces
This application has a cloud based server where it allows its users to store and retrieve
documents. All the user need to do is to sign in to his account, select the article the user require
and the click download button. The system provides an option for searching for an article by the
name of the article or the author’s name as well as “update the article” option.
The following procedure shows data entity.

Software Requirement Specification for Digital Publishing Software 12
Data Description Comment
Title Title of the Article One
Author Name of one Author There may be many authors
Abstract The article’s Abstract Help in keyword search
Content Body of article
Category Subject There may be several of
them.
Table 1: The document entity.
4.4 Communications Interfaces
The following protocol will be followed during communication with the application.
a. Ref selection
The user will first select either of the following reference:
i. Submit article
ii. Submit review
b. Trigger
The user triggers communication by selecting a mailto link.
c. Precondition
The user will then proceed to a precondition. This is “communicate”, the page is linked from
the online article page.

Software Requirement Specification for Digital Publishing Software 13
d. Basic path
From this page, the client email facility will be invoked.
e. Post-condition
The email is sent at this page.
The process is simplified in the following diagram
5. Other Nonfunctional Requirements
5.1 Performance Requirements
The system is not a heavy application, it therefore require a few resources in order to work. The
application is developed not to delay the system, it has a direct response system. Moreover, the
software user will not have a hard time updating the application, all the user need to do to update
Review
Reviewer
Article
Author
writes
sent to
write
s
has

Software Requirement Specification for Digital Publishing Software 14
the application is to click a button where new version of the application will be accessed, by this,
the software will be updated to its latest version.
5.2 Safety Requirements
For safety reasons, the server where the digital publishing application will be hosted will have its
own security the system from unauthorized access Safa, and Von Solms, 2016, pp. 14;
Abdulkhaleq, Wagner, and Leveson, 2015, pp.2-11). The publication manager’s computer will
also have its own security. The editor will be the only person who will be given physical access
into the computer. Aside from this the system users will be required to use strong password in
order to prevent their account from penetration by frauds.
5.3 Security Requirements
The following shows critical security management requirements for the system:
 Avast antivirus to be installed in the publication manager’s PC.
 Cyber security management policies
5.4 Software Quality Attributes
The significant quality attribute of the software is the cloud based attribute. This feature is
important to its users as the system can be accessed anywhere at any time.

Software Requirement Specification for Digital Publishing Software 15
6. Other Requirements
The GNU General Public License refers to a standard software license which assures the
application’s end users the freedom to use.
7. References
Abdulkhaleq, A., Wagner, S. and Leveson, N., 2015. A comprehensive safety engineering
approach for software-intensive systems based on STPA. Procedia Engineering, 128, pp.2-11.

Software Requirement Specification for Digital Publishing Software 16
Al-Sharafat, S.A. and AbuSeileek, A.F., 2012. The effectiveness of vocabulary learning website
games on English language learners' communication skills. International Journal of Learning
Technology, 7(2), pp.192-211.
Bryant, S.M., Eastman Kodak Co, 2011. Method system of software for publishing images on a
publicly available website and for ordering of goods or services. U.S. Patent 8,069,092.
Carreiro, E., 2010. Electronic books: how digital devices and supplementary new technologies
are changing the face of the publishing industry. Publishing research quarterly, 26(4), pp.219-
235.
Lassila-Merisalo, M., 2014. Story First. Publishing Narrative Long-Form Journalism in Digital
Environments. Journal of Magazine & New Media Research, 15(2), pp.1-15.
Lee, Y.J. and Lin, C.J., 2012. Usability evaluation of the online publishing software applied to
web-to-print: using Tintint website in Taiwan as an example. In Applied Mechanics and
Materials (Vol. 145, pp. 420-424). Trans Tech Publications.
Mahecha-Nieto, I. and León, E., 2010, November. Digital web library of a website with
document clustering. In Ibero-American Conference on Artificial Intelligence (pp. 214-223).
Springer, Berlin, Heidelberg.
Rathod, Y.C., Onepatont Software Ltd, 2014. Method and System for Dynamically Publishing,
Sharing, Communication and Subscribing. U.S. Patent Application 14/008,192.
Rico, D.F. and Sayani, H.H., 2009, August. Use of agile methods in software engineering
education. In 2009 Agile Conference (pp. 174-179). IEEE.

Software Requirement Specification for Digital Publishing Software 17
Safa, N.S., Von Solms, R. and Furnell, S., 2016. Information security policy compliance model
in organizations. Computers & Security, 56, pp.70-82.
Satish, S., 2014. Content management software–Drupal: Open source software to create library
website. In International Conference on Library Space–Content Management for Networked
Society (pp. 18-20).
Stodden, V. and Miguez, S., 2013. Best practices for computational science: Software
infrastructure and environments for reproducible and extensible research. Available at SSRN
2322276.
Van Lamsweerde, A., 2009. Requirements engineering: From system goals to UML models to
software (Vol. 10). Chichester, UK: John Wiley & Sons.
Willinsky, J., 2018. Scholarly associations and the economic viability of open access
publishing. Demonstration Journal of the Health Sciences Theme, 1(2).
8. Appendix A: Glossary
Term Definition
Author This refer to the writer of an article
Database Collection of all the information monitored by this system.

Software Requirement Specification for Digital Publishing Software 18
Editor This refer to the person who receives articles, sends articles
for review, and makes final judgments for the articles.
Reader Anyone visiting the site to read articles.
Review A recommendation for an article.
Reviewer This is the person that examines the article published
Software Requirements
Specification
This is a document that describes the functions of a
software that is to be used.
User Reviewer or Author.
9. Appendix B: Issue list
The application does well in the following areas:
 Fast in processing data
 Has user friendly interface
 Has good navigation system
 Easy to update
 Accept all file format
 Email configuration is well set
The application, however, needs improvement on:
 There are no reporting features
 Search is not clear; may be difficult to find for new users

Software Requirement Specification for Digital Publishing Software 19
10. Appendix C: Questionnaire
This appendix presents questionnaires used for designing this software specification:
About the organization
I. What does the organization do?
II. What are the goals of the company’s goals and objectives?
Goals
Objectives
About the software?
I. Which kind of software do you want to develop for the organization?
II. What does the organization want to use the application for?
III. Who will use the software?
IV. Which features do you want for the application?
V. In which operating system do you want the software to be used?
11. Appendix D: Interview
The following shows the interview questions used for this SRS.
Facts about the organization
Name of the company:
Department responsible for the project:

Software Requirement Specification for Digital Publishing Software 20
Role of the department:
Identity issues in the company
1. What problems does the organization experience in its daily activities?
a) Why do you experience the problems?
b) Have you been addressing the problem? If yes, how have you been addressing the
issues?
c) How would you like to address the problem?
The company users
a) Who are going to be the users of the application?
b) What is their level of education?
c) Do they have any computer skills?
d) What is your future plans concerning platform?
e) What are the training do you need concerning the use of the system?