UNIVERSITY OF DAR ES SALAAM

COLLEGE OF INFORMATION AND COMMUNICATION TECHNOLOGIES CoICT

PROJECT TITLE: ONLINE SIM CARD REGISTRATION SYSTEM (OSCRS) PROJECT SUPERVISOR: MR. MWASITA HENRICK PARTICIPANTS REG.NO 2011-04-00482 2011-04-00264 2010-04-02728 Software Requirements Specification For ONLINE SIM CARD REGISTRATION SYSTEM (OSCRS)

S/N 1 2 3

NAME Mshana, Edger A Kimomwe Malaika Msabika, Gaspar I

DEGREE PROGRAM BSC. WITH COMPUTER SCIENCE BSC. WITH COMPUTER SCIENCE BSC. IN COMPUTER SCIENCE

Table of Contents Definitions, Acronyms and Abbreviations ..........................................................................3 1 INTRODUCTION .............................................................................................................4 1.1 Scope ............................................................................................................................... 4 1.2 system workflow............................................................................................................ 4 2 GENERAL DESCRIPTION .............................................................................................. 4 2.1 Actors description......................................................................................................... 4 2.2 System requirements........................................................................................................5 2.3 General System Constraints ............................................................................................ 6 2.4 Operating Environment, Assumptions and Dependencies ............................................. 6 2.4.1 Operating Environment ................................................................................................ 6 2.4.2 Assumptions and Dependencies ..................................................................................6 2.5Deliverables: ................................................................................................................... 7 3 System Requirement Specification ....................................................................................7 3.1 Functional Requirement...................................................................................................7 3.1.1 User functional requirements .......................................................................................7 3.1.2 System functional requirement ....................................................................................7 3.2 Non-functional requirements ..........................................................................................8 3.2.1 Performance .................................................................................................................8 3.2.2 Security ........................................................................................................................8 3.2.3 Software quality attributes ...........................................................................................8 4.1 Use case .........................................................................................................................10 4.2.1 Class Diagram .....................................................................................................11 4.2.2 Actors Descriptions .....................................................................................................12 4.2.3 Use case description ...................................................................... .............................12 4.2.4 source Code generate.................................................................................................. 14

DEFINITIONS, ACRONYMS AND ABBREVIATIONS

PHP PHP: Hypertext Preprocessor CSS Cascading Style Sheet HTML Hypertext Markup Language DBMS Database Management System RAM Random Access Memory OSCRS-Online SIM Card Registration System

1 INTRODUCTION Traditionally registration of SIM CARD is paper based. Online SIM CARD Registration System is web based application software that will be used to register mobile phone numbers. This System has the following advantages over traditionally method of mobile phone number registration It simplifies the work. It is more secured. It reduce paper work It serve time
1.1 Scope of the System

The system will have three types of users, system administrator, system operator and normal user The System will enable system administrator to perform all the administrative tasks including view users, query reports etc. And system operator may perform the task of verifying and change user information /details Also the System will enable normal user to register new mobile phone number and check registration status
1.2 System Workflow

1. When the system is open, user will access the main menu and select the required service eg. register

mobile phone number, check registration status, query report etc 2. Then user will be prompted to fill his/her details on the corresponding form depending on the service chosen, and submit.
3. The details will be checked by the system to the database if they already exist. If not then will be saved. If

the details will be already in database then system has to return the error message.

4. If the details are sufficient as required by the system the user will be prompted two options either to attach

copy of identification card or to submit the copy of identification card physically. 5. After attaching copy of identification card or submit option of deliver copy of identification card physically, then the system has to display the complete status message.

2. GENERAL DESCRIPTION 2.1 Actor descriptions There are three types of users that will use this system
4

System Administrator: Will manage the system and all other users. He has unlimited access to the system functionalities and can perform all the administrative tasks including add user, view users, query report. System Operator: Will manage to verify and change user information/details. Normal user: This forms a group of users that have limited access to the system functionalities. Mainly they can register sim card and check registration status.

2.2 System requirements The system provides the system administrator, system operator and the normal user with the following functionalities into which authentication are necessary: Add user Verifying registration View users Add user details Check registration status Query report

2.3 General System Constraints i. PHP will be used as a server-scripting language for the web pages and it will be implemented using Object Oriented Model. ii. HTML and CSS will be used on the client side to format the interface. iii. The Web server is required to parse the PHP scripts and return the resulting HTML statement to the browser for presentation. iv. Database Server is required to handle the Database information. v. JavaScript is also used as a scripting language to control the inputs made in various forms. vi. The written program codes shall be well commented to enhance easy maintenance and evolution of the system.

2.4 Operating Environment, Assumptions and Dependencies 2.4.1 Operating Environment i. The user of the system must be connected to the network to be able to access and use the system. ii. A web browser: Mozilla Firefox, Internet Explorer, Safari, Opera, chrome etc. iii. Operating System: Windows or Linux
5

iv. DBMS: MySQL Server. v. Web Server: Apache server vi. Disk Space: 1 GB vii. RAM: 1 GB viii. Processor: 2 GHz 2.5.2 Assumptions and Dependencies i. It is assumed that a server is available on which the system will be installed for the many clients to connect and use the system. ii. A well established network infrastructure is required for the various users to be able to connect to the system. iii. The users should be able to use computers. 2.6 Deliverables: By the completion, the product will be given to the client together with the following attachments: i. User Manuals ii. A working system iii. Detailed technical report 3 SYSTEM REQUIREMENT SPECIFICATIONS 3.1 Functional Requirement 3.1.1 User functional requirements i. The system shall provide means for the system administrator to manage user informations including view user ii. The system shall provide a way of performing user authentication before access to the system functionalities is granted. iii. The system will be able to register system administrators and system operators iv. The system shall provide interface with limited functionalities based on user's privileges to control what tasks can be performed on the system. v. System administrator will be able to check list of system operators and normal users. vi. The system shall be able to generate reports. 3.1.2 System functional requirement i. The system shall group users into three categories (system administrator, system operators and normal user) based on their privileges. ii.For system administrators and system operators, the entered username and password shall be compared with the information in the system database for authentication. If there is a match, they shall be granted access to the system provided with an interface with respect to its group category otherwise they shall be denied access and be prompted to enter the username and password again.
6

iii. Forgotten password can be reset by the user by providing username to the system where the system will send an email to the user's email address with the username with the link which will allow him/her to set a new password. If the user-name doesn't exist the system will prompt the user to try again entering a correct username.

3.2 Non-functional requirements 3.2.1 Performance i.The software design should make use of web based applications (technologies). This will require the browsers and web servers application program ii.The software should be platform-independent, which implies that users working with all types of operating systems should be able to run the software on their respective Environments iii. The system shall be able to handle multiple requests from users and still respond to queries no longer than 5 seconds to load onto the screen after the user submits the query. iv. The system shall display confirmation messages (success or failure) to users within 2 seconds after users have submitted the form example when query report, check registration status, etc. v. All Web pages static or dynamic generated by the system shall be fully downloadable in no more than 4seconds over a normal LAN speed (100Kbps) connection. 3.2.2 Security i. System administrator and system operators will be required to log in using their username and password before having access to the system functionalities. The password should be stored in an encrypted format in the system database. 3.2.3 Software quality attributes The system will have several software quality attributes such as those mentioned below: i. Usability: the system shall be easy to use, providing all the required functionalities in assisting registration of sim cards. ii. Portability: the system shall be accessed from a variety of operating system platforms and with different versions of web browsers example Google Chrome, Mozilla, Internet explorer, safari and opera. iii. Maintainability: The system should be easily modifiable especially when in need of adding new system functionalities. For instance when a need to integrate it with another system that might be in place. iv. Reusability: The system components e.g. design diagrams and source code should be easy to use when implementing another system at little or no cost at all. 3. Domain requirement The OSCRS must be able to communicate with other systems.

4.Use case diagram

Figure 1: Use Case Diagrams

4.2 .1 Class Diagram

9

Figure 2: class Diagram

4.2.2 Use case Diagram description Use case 1: Login Login Elements Details Actor System Administrator, System Operator
10

Trigger Normal event flow

The actors want to use system functionalities/services that require identification and they are not being logged in. The actor fills in the login information and submits them. The system validates the information submitted. The system accepts an actor as a valid user, and provides the particular interface otherwise the system prompts the actor to reenter the login information.

Use case 2: Add user (System Operator) Add user Elements Details Actor System Administrator Trigger The actor submits the information of the System operator Normal event The actor fill the information of all System Operators so that they flow can be able to login Use case 3: Verify user registration Verify user registration Elements Details Actor System Administrator and System Operator Trigger The actor check, verify and submits the information of the normal user Normal event The system receives the information of the normal user. flow The system retrieve some data from the database Use case 4: Add user details Add user details Elements Details Actor Normal user Trigger The actor submits his/her information Normal event The actor fill his/her information and submit the form flow Use case 5: View users View users Elements Details Actor System Administrator and System Operator Trigger The actor has request for information of the users from the database Normal event The system checks the stored information about users Use case 6: Check registration status Check registration status Elements Details Actor System Administrator, System Operator and Normal user Trigger The actor fill and submit the form with information of the user Normal event The system checks the stored information about users
11

Use case 7: Query report Query report Elements Details Actor System Administrator and System Operator Trigger The actor has submitted the query for the type of report Normal event The system search the report information from its database flow The search hits are collected and presented in good format and returned as the reply. Use case 8: Logout Logout Elements Details Actor System Administrator and System Operator Trigger The actor is logged in the system and want to end session Normal event The system end the session flow

4.2.3 Class diagram description System Administrator Element Details Description A person in charge of managing and monitoring the Online Sim Card Registration System Example An administrator can add or delete user in the System System Operator Element Details Description A person with fewer privileges than the administrator who is responsible for performing several tasks associated with the system. Example System Operator can login into the system and verify user registration Normal user Element Details Description A person that is not involved in managing and operation but only access the system for getting service. Example Normal user check registration status

4.2.4. SOURCE CODE GENERATED BY THE CLASS DIAGRAM ABOVE

12