|
|
||||||||||||||||||||
SOKOINE UNIVERSITY OF AGRICULTURE
DEPARTMENT OF INFORMATICS
FACULTY OF SCIENCE
COURSE
CODE: INF 300.
COURSE
NAME: INFORMATION SYSTEM ANALYSIS AND DESIGN.
|
||||||||||||||||||||
|
||||||||||||||||||||
Question: To prepare Software requirement
specification for SUA SACCOS Management system
Table
of contents
1. Introduction
A
SACCOS is a short form for savings and Credit cooperative society. This deals
with savings and borrowing of the money from your savings. SUA SACCOS management system was developed so as
to help the members to save money as well as borrowing from their accounts. Not
only that but also to provide education to its members on how to build their
capital. Hence they improve their living standards.
SUA
SACCOS is among of the SACCOS in Tanzania which involves workers from Sokoine
University of Agriculture. This deals with both saving and borrowing of the
money. A customer saves the money to his or her account each month and after
having a savings he or she may borrow a loan for different purposes.
1.2
Purpose
The purpose of this software requirement
specification (SRS) is to clearly describe the system development called SUA
SACCOSS MANAGEMENT SYSTEM; the
major purpose is to meet the financial needs of all its members
men/women, old/young, rich/poor in particular, by encouraging savings and
granting loans to the members.
1.3
Document Conventions
The
format of this Software Requirement Specifications (SRS) savings and Credit
cooperative society (SACCOSS SYSTEM) is simple. Bold face and indentation is
used on general topics and or specific points of interest also the line spacing
is 1.5. The remainder of the document
will be written using the standard font, New Times Roman.
1.4
Intended Audience and Reading Suggestion
This document is intended for, developers, project managers,
users of the SUA SACCOS and other stakeholders, testers, and documentation
writers. Rest of the document describes the software in more detail. This
document is divided into the following sections:
·
The overall description
section where, the perspective of the product, its features, user constraints,
operating environment and design and
implementation constraints are described.
·
System features, where
major system features are described.
·
External interface
requirements including, user Interfaces, hardware interfaces, software
interfaces and communication interfaces are described.
1.5
Product Scope
The
SUA SACCOS will be used to help its member to save their money and then allow
them to borrow according to their amount deposited. Also the system can allow
the customer or member of the system to pay the money borrowed. Also the system
give interest to the member due to their money deposited. So through borrowing
money they can increase their economy. Also this system help the member who get
some problems like losing a family member, because when the member loss his or
family member like a child, wife or husband then the system tend to give him or
her some amount of money as a confrontation.
1.6
References
IEEE
P1058/D2.1, Draft Standard for Software Project Management Plans, dated 5
August 1998.
IEEE
Std 1233, 1998 Edition, IEEE Guide for Developing System Requirements
Specifications.
IEEE
Std 1016-1998, IEEE Recommended Practice for Software Design Descriptions.
2. OVERALL
DESCRIPTION
This
section will give an overview of the whole system. SUA SACCOS management system
will be explained in its context and origin to show how the system interacts
with other systems and introduce the basic functionality of it. It will also
describe what type of stakeholders that will use the system and what
functionality is available for each type. At last, the constraints and
assumptions for the system will be presented.
2.1 Product perspective
The
SUA SACCOS management system will be designed so as to replace the old system
which existed and performed all functions manually. Due to the need to computerize
the system with the aim of automating functions within the system. With all
these needs, the main purpose is to improve the efficiency of the existing SUA
SACCOS management system by improving the efficiency of the functions performed
by a system. Not only that but also the need to keep all the details up to
date.
2.2 Product functions
With
the SUA SACCOS management system, the users such as customers and managers will
easily perform different functions as follows;
Customers
·
Customers should be able to login into the
SUA SACCOS management system
·
Customers can request for being registered
as a member of SUA SACCOS management system.
·
Can receive their own accounts
·
Customers can deposit money into their
accounts
·
Customers can withdraw money from the
account
·
Customers can borrow a loan from the
deposits she/he have made
·
Customers can get the payment
notifications such as registration notification, payment notification,
borrowing notifications.
·
Customers can view various details for
example membership details, deposit details, borrowing details as well as
payment details.
Managers
·
Should be able to login into the SUA
SACCOS management system.
·
Can register customers who request for
registration
·
Can create accounts for the customers
·
Can view various details regarding their
customers such as deposits made, borrowing details as well as payment details
·
Can update various information of a
customer
2.3 User classes and characteristics
There are two
types of users that interact with the SUA SACCOS management system: These include customer and the manager who
have more knowledge about the internal contents of the SUA SACCOS management
system .Each of these users has different use of the system so each of them has
their own requirements.
The SUA SACCOS
management system users can only login into the system to get the requirements
she/he needs. This means that the user needs to be aware with the login
activity from which is able to obtain and do what she/he needs. In order for
the users to get a relevant requirement she is looking for from the system, she
must select exactly what she needs from a variety of functions offered by s
system.
The proper user interface, user’s manual, online help and
the guide to install and maintain the
system must be sufficient to educate the users on how to use the system without
any problem.
The
manager will also login with a different login requirement from that of the
customer and go direct to the database where he can view various details of the
customer for example the payment details, debt of a customer and other
contribution. Not only that but also the administrators will manage the
information about their customers, for example a description of the customer,
contact information and inheritors.
2.4 Operating environment
SUA
SACCOS management system is a web based system and will operate in all browsers
like Microsoft Internet Explorer versions 7.0, 8.0 and 9.0, with Flash Player 9
and JavaScript. Also the system will run in different operating system such as
windows, Unix and Linux and apache as webserver, MYSQL as a database.
2.5 Design and Implementation Constraints
The SUA SACCOS
management system is designed to store all the information of the users in a
database. From this database, each user will be able to access the information
they need. The system is constrained by the internet connection which needs a
person to be online both to request for registration as well as login.
This is because the system fetches data from
the database over the Internet, it is crucial that there is an Internet
connection for the registration and login to function.
Both activities
are constrained by the capacity of the database. Since the database is shared
between processes, it may be forced to queue incoming requests and therefore increase
the time it takes to fetch data.
2.6 User documentation
The User Manual
describes the use of the system to customers and managers. It describes the use
of the system on mobile systems. The user
manual should be available as a hard copy and also as online help. An installation document will be provided that includes
the installation instructions and configuration guidelines, which is important
to a full solution offering.
2.7 Assumptions and dependencies
One assumption
about the product is that it will involve SUA workers who must be connected
online to access the internet to perform all the functions they will need.
Since the system is designed to help the SUA workers, so the people who are not
workers of SUA will not be able to use and benefit from the system.
Also the system
allows members to borrow twice the amount they deposit which make the customers
of the system borrow a varying range of loan because each customer will borrow
the amount of money in accordance with the amount she/he will have deposited.
3. 3.0 External
Interface requirement
3.1 User Interfaces
3.1.1 Login Interface
This is the first interface which will allow user to
login into the system. If a user has an account already can login using the
username and the password. After pressing Login button a user will be able to
login in to the system. Also if a user has forgotten password, a user can
recover his or her password by clicking forgot password button.
3.1.2 Registration Interface
This is interface that will allow a person who is
not yet registered to the system to be registered where he or she is required to provide his
information such as names, department, guarantors, gender, emails and phone
number so that he or she can be registered to the system .
Registration interface can be constructed using HTML
form for web interface, Cascaded Style sheet (CSS) that used to provide the
visual layout styles of different HTML elements and Java Script functions that
used in validating users’ password that is checking and matching of two entered
password and give the appropriate message to user. After entering the required
information he or she clicks the register button where he or she becomes a
member of the system. Users will be warned for any mistakes made concerning on
the information that has entered. After that a user can login using the details
that has been inserted to the database.
3.1.3 User Profile view interface
This interface contains all the customer details
that is the information that customer has entered during his or her
registration This interface provide different options like changing user
profile picture, passwords .This interface will be constructed using PHP script
which validate the user session and fetch the data from the database and
display them and this script has a link to the HTML, JavaScript, codes together
with CSS for formatting the results from the output of PHP
Script execution.
Fig: user profile view
interface
3.2 Hardware Interfaces
The
system shall run on a Microsoft windows based system and will use the standard
input or output devices for personal computer or desktop computer .These
devices are such as Keyboard, Mouse, Monitor and Printers.
A
computer Keyboard
A
computer monitor
A
computer mouse
3.3 Software Interfaces
All
databases for the SUA SACCOS system will be configured using MySQL database.
These databases include the Customer information and System management
information .The system database will include the customer’s details like,
number of registered customers, entrance fees, payment details, balance,
borrower’s records, and fines
The
Customer database will contain the customer details like, customer names and
their guarantors, gender, address including their emails and phone number,
balance, and interest
3.4 Communication Interfaces
This system will use internet network and Hyper Text
Transfer Protocol (HTTP) as a communication standard that will be used in
sending and receiving data between a customer email and manager email and
sometimes mobile phone may be used in sending and receiving the information
between the customer and manager.
In this system users will be communicating one
another and system administrator using E-mail addresses that they will provide
during their registration to the system.
Also this system will use, a PHP function for
encryption of data when transfer data between a server and a customer web
browser. This will ensure the security of customer details while using the
system.
4. System features
The system of SUA
SACCOS management system has variety of features including security for user
details such as balance and other secret information that means these can be
seen by only authorized users, also it will allow the storage of user details
and as a result all the user details will be stored online thus the system will
ensure easy update and access of user information data nay time when these
information are needed, but also the system will be able to keep track of all
customer transactions that took place at a time. Thus the system will ensure
both security and access of the files at any time when these information are
needed.
5.0 Other Nonfunctional Requirements
5.1 Performance requirements
For
SUA SACCOS Management system to perform well there should be a good internet
connection which will helps in retrieving the information from the database. If
the internet connection is good the performance will be good and when the
internet connection is not good then the performance will not be good. Thus the
availability of a good internet is very important for the system to perform
well.
5.2 Safety requirements and security
Though
the system will perform well, the issue of safety is to be ensured. This
includes making the entire user information safe in a way that this information
cannot be lost. Also this can easily be done by storing user information in
different servers so as to ensure that these data are secured. Thus even when
one computer which contains user information has been destructed in any way the
user information is still available. Also the issue of making backup to the
files or documents which has been lost will ensure the availability of the
information stored in the system.
5.3 Software Quality Attributes
Availability:
This involves checking the information entered by the user and determine if
they match with these that has been stored in the database. As a result a
system will display the appropriate message to the user depending on the
information filled by the user. Example if user entered incorrect password a
system will tell the user that the password entered is incorrect.
Usability:
This ensures that the system checks the request of the user and ensures that
the user request is to be responded at a time without delay. In case there is
no information that relates to the user request an appropriate message will be
displayed to the user so as to ensure that a user is satisfied with the system.
Functionality:
This deals with the user especially when a user needs to edit some information
that can be edited according to the requirements of the system. By allowing
user to edit various information it will be easy to have some updates that user
has entered. Example if a user lost his or her phone and inserted a new line
and wants to update so as to have updates on his or her account a system must
allow a user to do so.
5.4 Business rules
In
SUA SACCOS System management there are variety of boundaries in terms of the
activities that can be performed by each user of the system. The Manger will be
able to enter customer details, to check the account balance for each customer
also manager can check the list of all customers and their details. Other users
they will be able to see their own details and edit some details that they can
edit according to the system.
Thus
each user of the system performs different functions depending on their
position in the system. This will ensure that every user knows their details
and be clear of these details.
6.
Other Requirements
The following are the definitions of all
terms, acronyms, and abbreviations required to properly interpret
Term
|
Definition
|
SACCOS
|
Savings
and Credit Cooperative Society
|
SUA
|
Sokoine university of agriculture
|
SAVE
|
Keep for future use
|
MySQL
|
Microsoft structured query language
|
HTTP
|
Hypertext transfer protocol
|
HTML
|
Hypertext markup language
|
CSS
|
Cascaded Style sheet
|
good job
ReplyDelete