Online Magazine Management System - Software Requirements Specification

This document outlines the software requirements for an online magazine management system, including data flow diagrams, use cases, and hardware/software interface requirements.

Software Requirements Specification 1
Online Magazine Management System
Name
Institution
Date

Software Requirements Specification 2
Table of Contents
List of figures..................................................................................................................................4
1.0 Introduction.........................................................................................................................5
1.1 Purpose.............................................................................................................................5
1.2 Document Convention....................................................................................................5
1.3 Intended Audience..........................................................................................................5
1.4 Scope.................................................................................................................................6
2.0 Overall Description.............................................................................................................7
2.1 Perspective.......................................................................................................................7
2.2 User Characteristics........................................................................................................7
2.3 Operating Environment.................................................................................................7
2.4 Design and Implementation constraints.......................................................................8
2.5 Assumptions and Dependencies.....................................................................................8
3.0 Specific System Requirements...........................................................................................9
3.1 Data Flow 1......................................................................................................................9
3.2 Data Flow 2......................................................................................................................9
3.3 Use case..........................................................................................................................10
4.0 External Interface Requirements....................................................................................12
4.1 User Interface................................................................................................................12
4.2 Hardware Interface.......................................................................................................12

Software Requirements Specification 3
4.3 Software Interface.........................................................................................................12
4.4 Communication Interfaces...........................................................................................12
5.0 Non-Functional Requirements........................................................................................13
5.1 Performance Requirements.........................................................................................13
5.2 Availability Requirements............................................................................................13
5.3 Security Requirements.................................................................................................13
6.0 Conclusion.........................................................................................................................13
References.....................................................................................................................................14

Software Requirements Specification 4
List of figures
Figure 1: Data Flow Diagram for Magazine request.................................................................9
Figure 2: Magazine Production Data Flow Diagram.................................................................9
Figure 3: Magazine Management Use Case Diagram..............................................................10

Software Requirements Specification 5
1.0 Introduction
1.1 Purpose
The proposed Online magazine Management system will be as a result of development form the
php and the javascript hence running as a web application. Having considered all this, a resultant
website making good use of the MySQL as a database that if freely available and is capable of
running in many platforms. The main objective of this project is to develop an online magazine
management system that will enable the recording of all the information about the magazines.
This research paper ought to bring out the clear explanation of the online magazine management
system with some dataflow diagrams. These diagrams are meant to provide the design of the
structured analysis of a system [5].
1.2 Document Convention
All the procedures laid down by the software requirements specifications we followed to the
point. Several components and the particular segments were clearly arranged together to get the
final product of the online magazine management system. This being a document with a resultant
means of payment, its with no doubt that it is later on considered a very important document for
the whole process of development [4].
1.3 Intended Audience
Having developed the online magazine management system, another factor to consider is the
final audience to whom the system aims at satisfying their needs. Of importance to note is that
the system is relevant throughout all the stages of life from students to the teachers and finally
the general public. Information being displayed through the system allows all the sections of the
society to at least be represented. This system could be of much importance during the times of

Software Requirements Specification 6
promotions, any advertising on the surveying procedures and the rewarding process done to
several customers by their companies [3].
1.4 Scope
All the libraries within the town appear to be the most appropriate scope to this research paper.
The proposed online magazine management system will be put into good use at all the stations in
the city. From the planning set in place, the magazines and the journals will all be put into an
organized set from which every user will be able to get a clear view of the same. All the
information needed by the general public will be provided here in this proposed online magazine
management system.

Software Requirements Specification 7
2.0 Overall Description
2.1 Perspective
The magazine seller and the end user, that is the customer, are brought together by this proposed
online magazine management system whereby the seller will be able to interact fully with the
clients through the web application whereas the customer will get all his or her daily need via the
same web application. Through this, we get to explore very many advantages that comes along
with the online operations since the user will be able to carry out his or her own activities at the
comfort of their wishes. Updates to the database with the relevant information will allow
everybody from all over the world to get to fit to the system, that is to say, the proposed system
will cater all the needs for all the people regardless of the profession, be it a teacher, a student or
whoever needs any service from the system.
2.2 User Characteristics
Whoever is in the position to acquire this online material happens to fit the required attributes.
Any person having an internet connection is capable of accessing these materials stored in the
online magazine management system. Through the various interaction with the system, a user
gets to know the required and the desired characteristics all together.
2.3 Operating Environment
The proposed system will make good use of a number of personnel from the source to the final
destination of the paper. The first section begins with the suppliers whose main work will be to
provide the raw material needed for the processing of the materials, another section will be
dealing with the finance management whereby all the financial transactions are well managed.

Software Requirements Specification 8
This will involve the collection of cash, the debts and the payment of the supplied for the raw
materials they provide respectively.
2.4 Design and Implementation constraints
The online magazine management system will with a very high percentage be required to
provide accurate information to the relevant audience. In order to meet this requirement, there is
need that all the information should be well entered into the system correctly and regular updates
be made accordingly. Processing of the financial data should also be accurate to avoid the
mismanagement of the funds. Therefore, in order to make well configured system some of the
challenges need to be addressed well before deploying the program to the final users. A well-
maintained system must be having some more techniques that have been implemented before
deployment [1].
2.5 Assumptions and Dependencies
The proposed online magazine management system has its own assumptions such as the internet
connection is available all through, therefore, in order to fully get the whole operational system,
we have assumed that internet is available everywhere.

Software Requirements Specification 9
3.0 Specific System Requirements
3.1 Data Flow 1
Figure 1: Data Flow Diagram for Magazine request
3.2 Data Flow 2
Figure 2: Magazine Production Data Flow Diagram

Software Requirements Specification 10
3.3 Use case
Use case Description
Name Add the magazine and the staff details to the
system.
level The use case diagram falls in the sub-
functional level in the system design and
development process. Having considered the
functional and the non-functional
requirements in the previous section.
Primary actor The Customer and the Staff member
Stakeholder The customer who creates an account, the
staff member who updates the magazines
details on the system. The system
administrator who is responsible for the error
correction and system update.
Main success scenario The user or the customer enter the login
credentials. The system processes the
provides details and authenticates them. He or
she is given the permit to proceed to the other
features of the website.
Alternative flow During the test, the system is undertaking
through a simple registration process where

Software Requirements Specification 11
the user creates an account with incorrect
details apart from the required, probably there
will be an error. This is solved by the expert
within a short time.
Specific requirement The time required for the system to process
all the login and registration request should be
within very dew seconds.
Figure 3: Magazine Management Use Case
Use case for login
Use case Description
Name The customer logins to the system
level Primary level of data security
Primary actor The Customer and the Staff member
Stakeholder The customer must enter his or her
credentials, the system validates and grant
access.
Main success scenario The customer is granted access to the system
so as to view all other features

Software Requirements Specification 12
Use case for logout
Use case Description
Name The customer or the Staff member can logout
from the system once he or she is done with
the daily transaction to the system
level Primary level of data security
Primary actor The Customer and the Staff member
Stakeholder The system automatically clears the use
session and all the pending information ate
saved.
Main success scenario Goodbye message is displayed.
Use case for inventory
Use case Description
Name The use case displays the item for sale. The
staff member can view. Modify or delete.
level Primary level
Primary actor The Staff member
Stakeholder The staff member searches for all the data in
the system to validate what exactly are they
offering to the clients.

Software Requirements Specification 13
Main success scenario List of magazines is displayed.
Use case for updating data
Use case Description
Name The staff member login to the system and
checks some information that need to be
updated in the system
level Primary level
Primary actor The Staff member
Stakeholder Once the system validates the staff member, a
list of items ready for update are displayed.
Main success scenario New data are accepted to the system.
Use case for checkout
Use case Description
Name The customer finally sums up all the
requested items. An proceed to making the
payment.
level Primary level
Primary actor The Customer

Software Requirements Specification 14
Stakeholder The payment facilitators and the customer.
Main success scenario A confirmation message for a successful
purchase is displayed.
Use case for purchasing
Use case Description
Name The customer logins to the system and make
the purchase order
level Primary level
Primary actor The Customer
Stakeholder The customer must enter his or her credentials
in order to be allowed to make the purchase of
the item.
Main success scenario A receipt is granted to the customer.
Use case for checking stock
Use case Description
Name The staff member queries for the stock level

Software Requirements Specification 15
level Primary level
Primary actor Staff member
Stakeholder The staff sends a request for the stock level
Main success scenario The staff is given the final level off the
requested stock item
Use case for reordering
Use case Description
Name The staff checks for the less quantity
magazine in the stock level and reorders for
more.
level Primary level
Primary actor Staff member and the supplier
Stakeholder The system will display the product to be
reordered
Main success scenario Request is sent to the prospective supplier
Use case for validating staff account
Use case Description
Name The staff logins to the system
level Primary level

Software Requirements Specification 16
Primary actor The Staff member
Stakeholder The staff enters the account details, the
manager on the other hand checks for the
validity of the entered information.
Main success scenario The staff member details are updated in the
system.
Use case for resetting password
Use case Description
Name Either the staff or the customer enters his
logins credentials to reset
level Primary level
Primary actor The Customer and the Staff member
Stakeholder Both the customer and the staff are required
to enter the required credentials to change.
Main success scenario Change of login password.
Use case for searching a magazine
Use case Description
Name The customer enters the name of the system
level Primary level

Software Requirements Specification 17
Primary actor The Customer
Stakeholder The customer searching for the online
magazine
Main success scenario The searched magazine is displayed to the
customer.
Use case for deleting a magazine
Use case Description
Name The staff member enters the id for the
magazine.
level Primary level
Primary actor The Staff member
Stakeholder The staff member responsible for stock and
inventory.
Main success scenario The magazine is removed from the system
Use case for deleting a customer
Use case Description
Name The staff member enters the customer id to
remove from the system.
level Primary level
Primary actor The staff member

Software Requirements Specification 18
Stakeholder The staff member dealing with the human
resource in the company.
Main success scenario The desired details for the customer are fully
removed from the system.
3.4 Activity diagram
4.0 External Interface Requirements
4.1 User Interface
The graphical user interface for the online magazine management system is provided via a web
browser. The user is provided with several menus to navigate through especially in selection of
the mode of the user, be it a student, a teacher, or any other member of the public.

Software Requirements Specification 19
4.2 Hardware Interface
Any mobile device including a mobile phone, a personal computer and that has a display screen
with the keyboard for the data input. These connected devices will be used in the relaying of the
information to the end user.
4.3 Software Interface
The software required for this online magazine management system is an operating system for a
personal computer and an android version from 4.4 and above. A total of 2 GB memory is need
in order or ensure that the program is up and running well.
4.4 Communication Interfaces
Communication is the best aspect to be considered herein, given the fact that the system will be
running from a server somewhere, then we say, there is need to provide a platform where the
final administrator can communicate with the end user as was of understanding the user
requirements for the system to run well as expected. Platforms such as the live chats, and the
feedback email should be provided to ensure flow of information. Through this process we need
a network uplink and a corresponding downlink to ensure successful communication [2].
5.0 Non-Functional Requirements
5.1 Performance Requirements
This is concerned with how the system will respond to the changes that could occur in the event
that updates are done to the system. The online magazine management system will be able to
respond to a request within a very short period of time, let’s say, a three section respond time
will be enough to say that the system meets all the requirements for the performance.

Software Requirements Specification 20
5.2 Availability Requirements
Having stated that the system will be running on an online platform, then we say, the system will
be available at all times the user needs some information. No manual functionality has been
added to system hence it is operational 24 hours a day. The unlimited access provides an
assurance that the system will be fully operational.
5.3 Security Requirements
The online magazine management system will be having several sections for instance, the
student section and the teacher’s section. Through this division, we get to know that a student
will never get to the teacher’s section, this beings to us an attention where security issue is
considered, every person using this online magazine system will be provided with the login
credential based on their level. This will ensure integrity throughout the operation of the system.
6.0 Conclusion
The development of the Online magazine management system will not only benefit the users but
also be a source of revenue to the entire government. The implementation will result to creation
of job opportunity especially to the Information Technology experts who will be required to train
the people on the user and also make the regular system updates to the system.

Software Requirements Specification 21
References
[1] Ann Sykes, T. Support structures and their impacts on employee outcomes: A longitudinal
field study of an enterprise system implementation. MIS quarterly, 39(2), 2015.
[2] Birk, Martin, and Paul Shala Henry. "Method and apparatus for configuring a communication
interface." U.S. Patent Application 14/560,215, filed June 9, 2016.
[3] Lynch, W., Neuhauser, A., Arshi, T., & Jain, A. U.S. Patent No. 8,990,142. Washington, DC:
U.S. Patent and Trademark Office, 2015.
[4] Mollahosseini, R. The Responsibility of Signatories in Commercial Documents for Payment
of the Document in Iranian Law in Comparison to French Law and the Geneva Convention
Uniform Law. J. Pol. & L., 9, 78, 2016.
[5] Xiong, H., Zhang, H., Dong, X., Meng, L., & Zhao, W. DFDVis: A Visual Analytics System
for Understanding the Semantics of Data Flow Diagram. In International Conference of
Pioneering Computer Scientists, Engineers and Educators (pp. 660-673). Springer, Singapore,
2017.