Online Magazine Management System Software Specification Document

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.

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

As viewed from the use case
The editor can update an author, publish an article, send or receive an article, and handle artistic
work.
Section four: External Interface requirements
User interface requirements
The user of this system is expected to be always on the internet. The user is also expected
to be internet literature. The main system will have an online Magazine Management System
main HTML page and a link to a certain author. The authors are also expected to have
knowledge on the internet and also be also be able to have email attachments. The editors of the
system need to be windows literate and at the same be able to use similar tools. There also
expected to be computer literate and be able to design articles using software such as Adobe, and
publishers (Schmidt, 2015).
There is only two link to the external system which is the historical link; this is a database
used to verify membership of reviewers. Second is a link to PayPal; in here clients of the system
are required to pay their subscriptions through the online platform.
Hardware interfaces requirements
This system requires to run over the internet. This means that all the hardware ought to
connect over the wide area network. Some of the hardware required for WAN-LAN, Modem,
Publish Art

and Ethernet Cross-Cable. Users require devices such as a computer, and mobile devices
(Hentzen, 2018).
Software interfaces requirements
The system will communicate to the editor for a new author. The system shall
communicate to a customer of a new article. The system shall communicate to an author after a
review of a certain article. The system shall alert the system administrators after subscription
payment. The user gadget is required to have VLC software to support videos, pdf reader to
support pdf files, and picture manager to read picture files (Hass, 2016).
Communication interface
The system will communicate using the HTTP Protocol for communication over the wide
area network. The communication within the organization will be via TCP/IP protocol suite
(Stephens, 2014).
Licensing requirements
There will be no licensing requirements which will be used
Copyright, legal, and others
OMMS will display copyrights, product warranties, and trademark
Section five: Other non-functional requirements
Security
The OMMS system will host on a server with high speed of internet connection. The
article manager shall run on the editors PC which must have connection to Microsoft Access
2013 version. The user computer computers must be running Windows operating system. The
system must maintain the three aspects of security which are confidentiality, data integrity, and

availability; the system will provide 24*7 hours availability. The system will also be serviceable
and recoverable in times of system failures. All the users of the system will be authenticated
before interacting with the system (Fairclough, 2016).
Performance
All the system components are very simple. In addition, the system will have all the
characteristics and services meaning that they will be no complexity in the design of the system.
This, in turn, enhances performance (Black, 2018).
Section seven: Other requirements
Documentation
The system will contain documentation. The manual will include a system overview, a
complete configuration of the software and network. The user manual will also include the
technical details, contact information, and back-up procedures. All the features and screenshots
of system workings will always be provided (Behforooz & Hudson, 2017).
System features
The system will control sessions and user access. The data will be stored in a secured
server. The system will also be to handle multiple requests from customers and also be able to
handle multiple computations. The system will no maximum number of concurrent users. The
time expectations after submitting a request are one second (Smith, 2013). The system will also
be in a position to accommodate increased volumes, users, and workloads. The system will also
resist accidental usage and provide access only to legitimate users (Thayer & Dorfman, 2017).

Logical structure of data
The data is to be stored in an internal article manager database as shown below it the
appendix
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 Eight: Reflection
Appendix A: Glossary
Abbreviation Description
OMMS Online Magazine Management

System
Users Magazine content developers,
Customers, and system
administrators
HTML Hyper Text Markup Language
PC Personal Computer
HTTP Hyper Text Transfer Protocol
PDF Portable Document Format
Appendix B: analysis Models
Logical data structure
Figure 7: Logical data structure
Reviewer
Author

System functional requirements
System functional requirements
Figure 8: System functional Requirements
Review
Article
Write
s sent to
write
s
has

Appendix C: Elicitation Report
There will be ten interview questions which are:
 How shall the system provide online help to customers?
 How will users of the system register for surveys and newsletter in the customer profile?
 Will the system have a provision of online help?
 Will the system display FAQ’s?
 Will the system provide a shopping cart when customer are paying their subscriptions?
 Will the system allow users to print magazines or even download videos?
 Will the system display ratings for a certain magazine or article?
Author
Reader/customer
Editor
HS and
PayPal DB
Online Journal
Article Manager
Web Publishing
System
Article
reviewer

 Will system display ratings of a certain article or display views of a certain video or
picture article?
 What are some of the security measures the system will take?
Appendix D: Team Meeting minutes
Minute 1
Present
1. (Student name 1)-Project Manager
2. (Student name 2)- Project Sponsor
3. (Student name 3)- System Analyst
4. (Student name 4)- Project Member 1
5. (Student Name 5) – Project member 2
Agenda
MIN 01/2018: Allocation of duties and specification of duties
MIN 02/2018: Description of the overall system by the project sponsor
MIN 03/2018: Designing of questionnaires to be sent to all the project stakeholders
MIN 04/2018: Other system functionalities would be done in the next meeting
MIN 03/2018: Adjournment of the meeting
Minute 2
1. (Student name 1)-Project Manager
2. (Student name 3)- System Analyst
3. (Student name 4)- Project Member
4. (Student Name 5) – Project member

Absent with apologies
1. (Student name 2)- Project Sponsor
Agendas
MIN 01/10/2018: Reading and confirmation of the previous meetings
MIN 02/10/2018: Reading of project requirements of the system by the system analysis
MIN 03/10/2018: Analyzing of questionnaires
MIN O4/10/2018: Establishing of system functional requirements
MIN 05/10/2018: Other system requirements should be outlined in the next meeting
MIN 05/10/2014: Adjournment of the meeting
Minute 3
Present
2. (Student name 1)-Project Manager
3. (Student name 2)- Project Sponsor
4. (Student name 3)- System Analyst
5. (Student name 4)- Project Member 1
6. (Student Name 5) – Project member 2
Agendas
MIN 001/10/2018: Listing of functional and non-functional requirements
MIN 002/10/2018: Listing of security requirements

MIN 003/10/2018: Listing of system features
MIN 004/10/2018: Listing of add INS and the required technology
MIN 005/10/2018: designing of the system
MIN 006/10/2018: Presentation would be done in the next meeting
Minute 3
Present
1. (Student name 1)-Project Manager
2. (Student name 2)- Project Sponsor
3. (Student name 3)- System Analyst
4. (Student name 4)- Project Member 1
5. (Student Name 5) – Project member 2
In attendance
1. Magazine publisher
2. Senior Editors
3. Accredited Authors
MIN 0001/10/2018: Description of the team members
MIN 0002/10/2018: an overview of the system
MIN 0003/10/2018: Description of the system functionalities and features
MIN 0004/10/2018: A presentation of the whole system by the project manager
MIN 0001]5/10/2018: Meeting adjournment