lOMoAR cPSD| 43196434

lOMoAR cPSD| 43196434

BIMS SRS
SOFTWARE SPECIFICATION REQUIREMENTS
FOR BUSINESS INFORMATION MANAGEMENT
SYSTEMS

BY ANGELA MUENI
 lOMoAR cPSD| 43196434

Table of Contents
INTRODUCTION .......................................................................................................2
OBJECTIVES ...........................................................................................................2
SCOPE ...................................................................................................................2
ACRONYMS AND ABBREVIATIONS ........................................................................3
TARGET AND USERS .................................................................................................3
TARGET .................................................................................................................3
USERS ...................................................................................................................3
OVERVIEW ...............................................................................................................3
THE OVERALL DESCRIPTION .....................................................................................4
PRODUCT PERSPECTIVE ........................................................................................4
BUSINESS REQUIREMENT .....................................................................................5
FUNCTIONAL REQUIREMENTS .................................................................................5
ADMIN: .................................................................................................................5
EMPLOYEE: ...........................................................................................................6
CUSTOMER: ..........................................................................................................6
MEMBERSHIP REGISTRATION TO THE ENTERPRISE ...............................................6
DETAILED INFORMATION ......................................................................................7
REQUIREMENT ATTRIBUTES .................................................................................7
CUSTOM ATTRIBUTES ...........................................................................................7
DAILY BUSINESS ACTIVITIES ..................................................................................8
USER CHARACTERISTICS ........................................................................................8
NONFUNCTIONAL REQUIREMENTS..........................................................................9
PERFORMANCE REQUIREMENTS ..........................................................................9
LOGICAL DATABASE REQUIREMENTS ....................................................................9
DESIGN CONSTRAINTS ..........................................................................................9
SECURITY, TECHNOLGY STACK ...............................................................................10

1
 lOMoAR cPSD| 43196434

SOFTWARE SYSTEM ATTRIBUTES ........................................................................10

REFERENCES ..........................................................................................................10
USE CASE DIAGRAM...............................................................................................11
CLASS DIAGRAM ....................................................................................................13
SEQUENCE DIAGRAM FOR BIMS ............................................................................14
STATE CHART DIAGRAM ........................................................................................16
ACTIVITY DIAGRAM ...............................................................................................17
COMPONENT DIAGRAM ........................................................................................18
DEPLOYMENT DIAGRAM ........................................................................................19

INTRODUCTION

The world of business has become more digitized and companies are focusing on
innovative technologies that will help them enhance business processes and
transactions, while decreasing cost. This is where Enterprise Resource Planning
(ERP) systems come into play. Not only do they integrate different subsystems
into one huge system sharing one database, but also they help to improve
productivity and bring more profit.

OBJECTIVES
1. Help businesses improve their performance in conducting and executing
processes and transactions
2. Create a platform that will increase productivity by simplifying employee
jobs.
3. Develop a platform that is going to integrate systems across multiple
locations to better serve the customer
4. Help business organizations to standardize global business operations 5.
Position a business for growth and reducing working capital.

SCOPE
The Scope of the project is as follows:-

2
 lOMoAR cPSD| 43196434

1. To build a system through which an organization or enterprise can manages

their activities
2. The enterprise shall be able to manage it performance
3. The enterprise shall be able to plan budget, predict and report on its
financial results
4. To show progression or regression of the enterprise

ACRONYMS AND ABBREVIATIONS

ERP –Enterprise Resource Planning.
ID: Identifier
GUI: Graphical User Interface
HTML: Hypertext Markup Language
SRS –Software Requirement Specification

SMEs: Small and Medium-sized Enterprises

TARGET AND USERS

TARGET

We are aimed at targeting SMES, Big Corporations and companies.

USERS
User group 1: Business owners

User group 1: Business managers

User group 3: Employees working with business organizations

User group 4: Customers

OVERVIEW
This SRS is organized as follows:- Section

2 gives an overall idea of product.

Section 2.2 describes the business requirement of the ERP software

Section 3 describes the Functional requirement related to ERP software

Section 4 describes the specific requirement related to an enterprise.

3
 lOMoAR cPSD| 43196434

This section also describes the nonfunctional requirement related to ERP

software.

THE OVERALL DESCRIPTION

PRODUCT PERSPECTIVE
System Interfaces

The software runs on latest versions of Chrome on Firefox on Windows, Linux and
Mac.

The software also runs on android and OiS systems

User Interfaces

The software application GUI provides menus, toolbars, buttons, containers, grids
which allows the user to control with ease by a keyboard and a mouse.

No external hardware interface is required

Hardware Interfaces

NA

Software Interfaces

The application allows import a structured MS Word document via HTML data
format.

The application allows import / export a list of requirements from / to MS Excel

sheet via CSV data format.

The application stores enterprise information data in JSON format to enable easy
integration with 3rd party applications.

Communications Interfaces

NA

Memory Constraints

NA
4
 lOMoAR cPSD| 43196434

Operations

NA

Site Adaptation Requirements

NA

BUSINESS REQUIREMENT
• To make the enterprise history sheet
• To sign the and deliver customer pledge
• Verification of the customer’s information
• To record the attendance for weekly meeting
• To record the key field day activities
• For Processing and handling
• Registration of new members and customers

• Verification of the customers

• Agreement between customer and enterprise

FUNCTIONAL REQUIREMENTS

ADMIN:
The admin shall view business transactions, transfer, and balance sheet,

The admin can delete or add new employee,

Get access to employee information,

Access data from different departments and manage salaries

The admin shall add customer and view customers list,

The admin shall accept payments,

Admin shall see the list of accounts and also view account balance,

Admin shall read emails,

5
 lOMoAR cPSD| 43196434

Admin shall be allowed to change the general setting of the software to place
restrictions

EMPLOYEE:
Account:

The software shall allow the account to automatically or manually create

accounting entries.

The categorize expenses and view all accounting operations,

Update user account

Other employees:

Other employees shall;

Add or delete customer,

Read customer mails and respond to them,

Not view financial transactions,

Update products and services

Update user account

CUSTOMER:
The customer shall access the dashboard and view products,

See all other services offered by the business,

Make new deposit,

MEMBERSHIP REGISTRATION TO THE ENTERPRISE

This is used to register a new member Input:

The new member shall fill membership application form for the enterprise

Process:

The member shall select the country,

6
 lOMoAR cPSD| 43196434

The system shall display the region,

The member shall enter Name with no figure and special character

The member shall enter the place,

The member shall enter the date.

Output:

The Annexure is filled and submitted

The system shall generated the application number

DETAILED INFORMATION
The application shall allow users to show and hide a pane displaying detailed
information about custom attributes, discussion, traceability links or history of
changes activities of the company.

The application shall display the enterprise activities.

The application shall allow for mailing and messaging panel.

The application shall allow users to expand or collapse a dashboard.

REQUIREMENT ATTRIBUTES
The application shall allow users to edit the heading of a selected section.

The application shall allow users to paste an HTML content copied from MS Word,
Excel or other application into the text description of the selected requirement.

CUSTOM ATTRIBUTES
The application shall allow users to define custom attributes which cannot be
changed.

The application shall allow users to set a type of each custom attribute as follows:
Boolean, integer number, real number, string, date, or XHTML.

The application shall allow admin users to remove custom attributes.

The application shall allow admin users to edit custom attributes of the selected
requirements.
7
 lOMoAR cPSD| 43196434

DAILY BUSINESS ACTIVITIES

Input:

The enterprise user will enter the records of daily activities of the enterprise.
Process:

The enterprise-user shall choose the product name.

The system shall display the total number of products.

The enterprise-user will able to enter the number of products available in stock

The enterprise-user shall enter the date and time that the activity is being
recorded.

The enterprise-user shall be to enter the important issues discussed and planning
done.

The enterprise-user shall record any information for any query on problem solving

The enterprise-user shall also enter the profit raised, or a deficit encountered.

The enterprise-user shall also enter any decision made to improve on the business

The enterprise-user shall enter product that saw a deficit and those that saw an
increase in value

The system shall generate a graph of sales against price and also a pie chart
reflecting information entered by user.

Output:

The enterprise-user shall save the information the daily activities and record all
the information related to the enterprise

USER CHARACTERISTICS
The user shall have a minimum level of education

The user shall have some experience with Microsoft Word and Microsoft Excel

The user shall have technical experience with graphs and charts.

8
 lOMoAR cPSD| 43196434

NONFUNCTIONAL REQUIREMENTS
Maintainability:

The software should regularly repair itself.

The software should restart itself in case of a downtime Portability

and Compatibility:

The software should be portable so much that moving from one operating system
to the other operating systems should not be a problem.

The software should not be affected by third-party software or application in the

systems it operates on.

The application shall run in the latest version of popular browsers like Chrome or
Firefox browsers.

PERFORMANCE REQUIREMENTS
Startup Time: The application should display the GUI within 10s after it is started.

Edit Response Time: The application should display updated values within 1s after
user triggers the edit operation.

Smooth Scrolling: While a user scrolls the requirements table, the application
should not display scrolling jerks longer than 200ms. The software should be
portable

LOGICAL DATABASE REQUIREMENTS

The application shall encrypt the persistent application data.

DESIGN CONSTRAINTS

The possible constraints to the developer will

include:

• regulatory policies
• hardware limitations
• interfaces to other applications
9
 lOMoAR cPSD| 43196434

• parallel operation
• control functions
• higher-order language requirements
• reliability requirements
• safety and security considerations

SECURITY, TECHNOLGY STACK

SOFTWARE SYSTEM ATTRIBUTES

Availability:

The software shall be accessible to the user any time, that 24hrs of the day to the
admin and employee.

The add costumer shall only be available only during working hour.

If the system fails, the user shall restart the software

Security:

Information about the user shall be hidden to the public

The application shall not send any project data to the Internet.

Keep specific log or history data sets

Utilize certain cryptographic techniques

The application shall sanitize any data input or imported by users.

The application shall constantly check activities logging.

REFERENCES
Pdf file by Libor Bus, Eccam s.r.o (24.6.2020)

IEEE Guide to Software Requirements Specifications (Std 830-1993).

10
 lOMoAR cPSD| 43196434

How to build ERP Software System for your own business by DDI development
[Updated 2019]

How to build a custom erpsystem by Katerina Reshetilo [Updated 2019]

USE CASE DIAGRAM

A Use Case is a description of a set of interactions between a user and the system.
This diagram is a valuable aid during analysis. Developing Use Cases helps us to
understand requirements. By building up a collection of Use
Cases, we can describe the entire system we are planning to create, in a very clear
and concise manner. Use cases are usually described using verb/noun
combinations.
Along with the name of the use case, we will provide a full textual description of
the interactions that will occur between the user and the system.

Actor in Business Information Management Systems

Customer

Employee

Accountant

Business Administrator Add

new employee:

To add new employee, the admin login into the system and add new employees.
This will require a set of information. This use case includes the verification of the
employee information.

Add new customer:

11
 lOMoAR cPSD| 43196434

Add new customer is can be done by the admin,

Make order:

Making an order, the customer will have to login into the software. This will
include authentication of the information provided by the customer. The software
interface should allow for the user to view through the available products and
services from which the customer can make an order.

Make payment:

The customer make pays for the item which he/she from the available products
on the business site. Payment will be accepted by the accountant.

Check item:

When a customer pays for an item, the employee, the accountant or the business
administrator can check on the item. The item will then be released to the
customer.

Check transactions:

The system software allows for the admin and the accountant to check sales and
transactions. If new sales and new transactions have been made, then the admin
or the accountant can update sales or update transactions.

12
 lOMoAR cPSD| 43196434

Use case diagram

CLASS DIAGRAM
Drawing class diagrams is an essential aspect of any object oriented design
method. They are used to show the different objects in the system, their
attributes, their operations and the relationships among them.
Class:
A class represents an object or a set of objects that share a common structure and
behavior. They are represented by a rectangular box that includes rows of the
class name, its attributes and its operations.

13
 lOMoAR cPSD| 43196434

Class for the Business information management system

Sale
Transaction
Business Admin
Accountant
Employees
Customer
Product
Make order
Business organization
Class diagram

SEQUENCE DIAGRAM FOR BIMS

The sequence diagram illustrates how the different parts of the system interact
with each other to carry out a function and the order in which the interaction
occurs when a particular use case is executed.

14
 lOMoAR cPSD| 43196434

Sequence diagram

STATE CHART DIAGRAM

A state chart diagram is used to model how the state of an object changes in its
lifetime. State chart diagrams are good at describing how the behavior of an
object changes across several use cases executions. State diagrams allow us to
model the possible states that an object can be in. The model allows us to capture
the significant events that can act on the object, and also the effect of the events.

15
 lOMoAR cPSD| 43196434

State chart diagram

ACTIVITY DIAGRAM
An activity diagram is a special case of a state chart diagram in which all or most
of the states are activity states and all or most of the transitions are triggered by
completion of activities in the source state. Each activity is shown in a rectangle
and each swim lane handles each object. The activity diagram covers for a
customer who wants a product to the business administrators who check sales
and update the company’s transactions. Here the activity started when a
customer login, the system displayed the available products and the customer
placed an order. The accountant then request payment while sending the order
for processing by other employee. The customer pays for the product and
receives the product. The activity ends with the employee reporting sales to the
accountant and the business admin who then update the company’s transaction
chart.

16
 lOMoAR cPSD| 43196434

Activity diagram

COMPONENT DIAGRAM
Component diagrams are used to visualize the components of the system and the
dependency relationship between them. They provide a high level view of the
components within a system. They thus describe the physical artifact of our
system including the files, executables, and also libraries and documents.

17
 lOMoAR cPSD| 43196434

Component diagram

DEPLOYMENT DIAGRAM
Deployment diagrams are used to describe the static deployment view of a
system. They visualize the topology of the physical components of the system
where the software components are deployed. It thus shows the execution
architecture of a system including nodes such as hardware or software.

Diagram Description:
The deployment diagram for the BIMS shows the sever processor which distribute
and configure them to the internet. The cache server is used to store the
transactions which are done by the customer at the time shortage of memory
until the memory storage should extended. The database is placed at the head
branch of company.
The enterprise computer or any member’s pc is connected to the local area
network.

18
 lOMoAR cPSD| 43196434

Deployment diagram

19