Software Requirements Specification - Online Magazine System

This document presents a comprehensive Software Requirements Specification (SRS) for an Online Magazine Management System (OMMS), adhering to IEEE standards. It outlines both functional and non-functional requirements, architectural design, and design decisions. The document covers various aspects including product perspective, functions, design constraints, and specific system requirements detailed through use cases for readers, recommendations, subscriptions, and magazine publishers. External interface requirements such as user, hardware, and software interfaces are specified, along with communication and licensing needs. Non-functional requirements focus on security and performance. Appendices include a glossary, elicitation report, and team meeting minutes, providing a thorough overview of the system's development and requirements.

ASSIGNMENT 1: SPECIFICATION
By: (Name)
(Course title)
(Tutor name)
(College name)
(Date)

Table of Contents
Table of figures................................................................................................................................4
Section One: Introduction................................................................................................................5
Purpose.........................................................................................................................................5
Document conventions.................................................................................................................5
Audience......................................................................................................................................5
Scope............................................................................................................................................6
References........................................................................................................................................6
Section Two: Overall description....................................................................................................7
Product perspective......................................................................................................................7
Product Functions........................................................................................................................7
Design constrains.........................................................................................................................7
Functional requirements...............................................................................................................8
Section Three: Specific system requirements..................................................................................9
Reader use case............................................................................................................................9
Use case: Send recommendation................................................................................................10
Use case: Send subscription.......................................................................................................10
Use case: Magazine publisher....................................................................................................11
Use case submit an article..........................................................................................................12
Magazine publisher use cases....................................................................................................12
Section four: External Interface requirements...............................................................................13
User interface requirements.......................................................................................................13
Hardware interfaces requirements.............................................................................................14
Software interfaces requirements...............................................................................................14
Communication interface...........................................................................................................14
Licensing requirements..............................................................................................................14
Copyright, legal, and others.......................................................................................................15
Section five: Other non-functional requirements..........................................................................15
Security......................................................................................................................................15
Performance...............................................................................................................................15
Section seven: Other requirements................................................................................................15
Documentation...........................................................................................................................15

System features..........................................................................................................................16
Logical structure of data............................................................................................................16
References......................................................................................................................................17
Section Eight: Reflection...............................................................................................................18
Appendix A: Glossary................................................................................................................18
Appendix C: Elicitation Report..................................................................................................20
Appendix D: Team Meeting minutes.........................................................................................21
Minute 1.................................................................................................................................21
Minute 2.................................................................................................................................22
Minute 3.................................................................................................................................22
Minute 3.................................................................................................................................23

Table of figures
Figure 1: Search article diagram......................................................................................................8
Figure 2: Send recommendation......................................................................................................9
Figure 3: Send Subscription.............................................................................................................9
Figure 4: Magazine publisher........................................................................................................10
Figure 5: Submit article.................................................................................................................11
Figure 6: Magazine Publisher........................................................................................................11
Figure 7: Logical data structure.....................................................................................................16
Figure 8: System functional Requirements....................................................................................17

Section One: Introduction
This is a software specification document which is in accordance with IEEE standard.
This document contains both functional and non-functional requirements for the Online
Magazine Management System. The SRS document describes the architectural design and design
decisions.
Purpose
This SRS document entails a complete software requirement for the Online Magazine
Management System (OMMS). The document gives a detailed design which is needed to
implement the system. This document also provides a visibility design. It also provides
information that is needed for software support. The document contains both functional and non-
functional requirements. In addition, the document contains guidelines for website developers.
Document conventions
This SRS document is divided into major sections which are an introduction, specific
system requirements, overall description, external interface requirements, other non-functional
requirements, other requirements, and reflection. Each of the parts is divided into sub-sections to
explain each section. In addition, the documents contain Appendices which contains analysis
model, issues lists, glossary, team meeting minutes, and elicitation report (Anderson, 2009).
Audience
The audience is intended to system analysts, developers, project sponsors, and project
managers of the web application. To the project managers will them in the publication of review
outcomes. It will also help in having a clear overview of project requirements. To the project
sponsors, the document will give them knowledge of the project cost. To the developers, there

will have that knowledge of the required internal workings of the system. The document will also
be useful to the users of the system as they will be aware of the system functionality. This means
that they would be aware of the characteristics of the system and the required software to run the
system.
Scope
Online magazine management system (OMMS) is developed to assists magazine
publishers in expanding the readership of their magazines content. The system allows integration
of reader subscriptions, digital content, and advertisement. This document describes the
interface, operations, and quality assurance requirements of the OMMS. The document has been
prepared after a number of consultations with the project team and other relevant factors needed
to develop the system. Some of the characteristics of the system include a login facility to the
system users. The system should also allow searching for magazines according to date. The
administrators should be able to insert magazines (Arain & Low, 2010)
References
Anderson, T., 2009. Software : requirements, specification and testing by Tom Anderson. 2nd ed.
Chicago: John & Wiley.
Arain, F. M. & Low, S. P., 2010. IT-based project change management system by Faisal
Manzoor Arain. 1st ed. New York: John & Wiley.
Behforooz, A. & Hudson, F. J., 2017. Software engineering fundamentals. 3rd ed. London:
London Press.
Black, R., 2018. Advanced software testing. 3rd ed. London: Rocky Nook Press.
Fairclough, J., 2016. Software engineering. 1st ed. New York: London Prentice Hall.

Hass, A. M. J., 2016. Guide to advanced software testing by Anne Mette Jonassen Hass. 2nd ed.
Chicago: John & Wiley .
Hentzen, W., 2018. The software developer's guide. 1st ed. New York: New York Press.
Reifer, D. J., 2014. Software management. 1st ed. London: London Press.
Schmidt, R. F., 2015. Software engineering : architecture-driven software development. 1st ed.
Chicago: Elsevier Press.
Smith, D. D., 2013. Designing maintainable software. 1st ed. New York: Springer.
Stephens, R., 2014. Beginning software engineering. 2nd ed. New York: John & Wiley Press.
Thayer, R. H. & Dorfman, M., 2017. Software engineering. 1st ed. Chicago: John and Wiley.
Section Two: Overall description
Product perspective
OMMS is a web-based application that will be used by magazine publishers and the
general public; those people who like reading magazines. The developers of the system will be
looking to expand magazine readership across the internet. The system will integrate
advertisement, digital content. The system will be accessed by both wired and wireless devices.
Product Functions
The system will support management of various electronic publications. Also, the system
will allow easy access to digital files. In addition, will manage the submission of articles which
will include videos, pictures, music, and artwork. All this content ought to be uploaded quickly

with ease. The system also ought to quickly provide online advertising and ad-manager which
should quickly process the submission. Other product functions are placing a discussion board
for visitors to discuss magazines topics and public forums.
Design constrains
Design constrain Description
Application Server Web sphere application server (WAS)
IDE RAD
J2EE Services Java servlets, JAXB, JDBC, and core java
Scripting JavaScript, CSS
Database DB2
Functional requirements
The system will have a login screen where every user of the system will login. The
system administrators who is entitled to maintain the system will use password and username.
The system administrator will have various functions. First is to register magazine publishers and
add any feature which is relevant to the system. Magazine publishers will be required to upload
magazines contents, videos, music, and pictures. The system will also provide inbox to the admin
users who will view all discussions and any requests from the customers.
Magazine publishers logins to the system, uploads magazines content to the system if
any, view requests by customers if any, view public forums if any, and able to edit magazines
details if need arises. The magazine publisher can also search magazines, modify a magazine,
approve or reject a request by customers, and add or remove a magazine. Customers will login to
the system after registering with the system. There will have to register in the system using a

valid email address which will be verified by sending a link into that email. Users will then be
prompted for username and password. The user can then proceed to view uploaded magazines,
videos, and pictures. In addition, the users can search for a certain digital content. The search
will be based on the author of that article, date of publication, and subject. Search results are
listed with details of the article.
Section Three: Specific system requirements
Reader use case
Brief description
The reader first logins to the system using their username and passwords. There are then
prompted to make subscriptions of they have not so. In the system there are monthly
subscriptions which are monthly, quarterly, and annual subscription. The reader can then be able
to view articles and even search for articles (Reifer, 2014).
Figure 1: Search article diagram
Reader
Search Article

Steps for this process
 The reader logins
 The reader then chooses to search an article by author, keyword and even category
 The reader then selects the desired article
 The system presents the article to the reader
 The reader can then discuss about the article
Use case: Send recommendation
Figure 2: Send recommendation
This is a use case by a customer where they can recommend for publishing of a certain article
and editing of others.
Use case: Send subscription
Figure 3: Send Subscription
Reader
Send
Response
Reader
Send
subscription
Fee

In here a customer is required to send a subscription fee based on his choice.
Use case: Magazine publisher
Figure 4: Magazine publisher
Article submission process
Brief description process
1. The author logins into the system
2. Submits an article for consideration
3. The editor views the request by the author and submits it to reviewers for consideration
4. Reviewers of the article submit it back to the editor with comments
Rewrite Review
Active
Article
Submit Publish

5. The editor then submits to the editor either with a revision which ought to be done,
declined or accepted.
Use case submit an article
This is for the accredited author
1. Logins into the system
2. Submits a digital content article
Diagram: Submit an article
Figure 5: Submit an article
Diagram: Use case editor
Magazine publisher use cases
Figure 6: Magazine Publisher
Reviewer
Submit
Review
Update
Info
Editor
Handle Art
Ck Status