You are on page 1of 8

PROJECT TITTLE: ONLINE STUDENT RE- REGISTRATION SYSTEM

(UDOM -OSRS)

TABLE OF CONTENTS

1 CHAPTER 1:INTRODUCTION........................................................................1
1.1 Purpose..........................................................................................................1
1.2 Scope of Project..............................................................................................
1.3 Definitions,acronyms and abbreviations.......................................................3
1.4 goals..............................................................................................................4
1.5 References.....................................................................................................4
2 CHAPTER 2:GENERAL DESCRIPTION.........................................................5
2.1 Product perspectives.....................................................................................5
2.2 Product functions..........................................................................................5
2.3 User characteristics.......................................................................................6
2.4 General constraints........................................................................................6
2.5 Assumptions and dependencies....................................................................7
3 CHAPTER 3:GOALS OF IMPLEMENTATION...............................................7
4 CHAPTER 4:FUNCTIONAL REQUIREMENTS.............................................8
5 CHAPTER 5:NON-FUNCTIONAL REQUIREMENTS.................................12
6 Index......................................................................................................................

0
CHAPTER 1:
INTRODUCTION
1.1 Purpose
This document explains in details the requirements and specifications of the
system which is UDOM online Students Reregistration System(UDOM-OSRS) so as
to facilitate the implementation of the system. Also this document will enable the
system developers to make sure that they develop this system exactly as required
by its users.
Using this document the project managers can estimate the cost of the project
easily. The functionalities that will be explained later will help the
maintenance engineers to design and code as well as making modification
of this system.
1.2 Scope of project

The document aimed at specifying requirements of software to be developed .The


standard can be used to create software requirements specifications directly or
can be used as a model for defining a organization or project specific standard .It
does not identify any specific method ,nomenclature or tool for preparing an SRS.

1.3 Definitions ,acronyms and abbreviation

This part defines and explains the ambiguous terms that will be used to develop
the system so that to make them well understandable by any reader of this
document before reading the document.
UDOM-OSRS:UDOM Online Students Reregistration System, This is the name of
the system that is intended to be produced.
User: Someone who interact with the system

1
Database: is basically a collection of information organized in such a way that a
computerprogram can quickly select desired pieces of data.
Web browser: A program that used to access web pages on the internet.

1.4 Goals

The main goal of this document is to develop system that will allow users
(students ) to re-register themselves online so that to save time and
inconvenience of queuing while waiting for their re-registration.
The App will cover the following
i. Student registration

ii. Keeping the students records for future reference

The system will not cover the following


i. T he system will not allow signing online

CHAPTER 2:
2: general description of OSRS PROJECT:
2.1. Project perspectives
The UDOM-OSRS system shall provide the greater services which could not
available for the long period of time in our university as long as in our country
since we are still use manually system in registration.

2.2.System functions
The UDOM-OSRS (i.e. The university of Dodoma-online students re-
registration system)
Its an online system of re-registration for the continuous students especial for
the new academic year as well as the new semester.
The UDOM-OSRS system should be able to perform/provides one or more basic
operations(service).
2
The following are among the special purpose or tasks of the UDOM-OSRS
system:-
 The system should allow the prompt user/students to login in his/her account
using registration number as user name and surname as the password.
 The system should allow or enable students to submit bank pay-in-slip
number for the payment made either for the school fees or direct costs.
 The system as well should allow students to view the teaching Timetable
and university almanac.
2.3. User characteristics
- The user of the UDOM-OSRS may be one or more as it include the following:-
 Any continuous Students.(i.e. 2nd year,3rd year,4th year and 5th year)
 All university bursars
The following are the user characteristic:-
 The student must be a continuous students.
 The student should also have students registration number.
 The student should be the one who is not discontinued from the studies.
 The students should be aware of how to login to his/her account.

2.4 General constraints


-The UDOM-OSRS system would encounter a number of limit or restrictions in
the whole process of developing the system:-
 Lack of enough capital in order to come up with a complete system that
handle out the problem of queuing in the bursar office especial during the re-
opening of new academic year.
 The system may takes a long time in developing it.
 Lack of skilled professionals in developing the system
 Failure of the system to ensure how the user are identified when are using
the system.
 Failure of the system to recognize some of the intruders/attackers trying to
modify/update the information.
3
2.5 Assumption and dependences.
The UDOM-OSRS system would work properly and said to meet the needs of the
system’s user if and only if the following ASSUMPTION are said to be
implemented:-
 Identification requirement (i.e. the system should be able to identify
different user using the UDOM-OSRS system before interacting with them.)
 Integrity requirement (i.e The UDOM-OSRS system should be able to
protect itself against intruder or any attacker that may try to edit/modify
some information/data in the database of the system.)
-Also the system should specify how data corruption can be avoided
 Authentication requirement (i.e the system should specify how users are
identified)
 Immunity requirements (i.e specify how a system protect itself against
viruses, worms and similar threats.)
 Non-repudiation requirements specify that a party in a transaction cannot
deny its involvements in transaction.
 Risk detection and removal where the system is made in such away that
risks are detected and neutralized before they result in corrupted
information.
 Damage limitation, the should be designed in such away that the
consequences of damages/accident are minimized.

CHAPTER 3:
3.GOALS OF IMPLEMENTATION
We believe that after finishing our project the resulting system will be
capable to solve the different problems and will be of benefits in the university
and students at large. Due to the problems and limitations faced by students using
the current system (Manually), so there is a growing need to develop and use a new
system that not only eliminates all the problems and limitations caused by the
current system but also increase efficiency.
The following are objectives of the system implementation:

4
 To have the system that will save time since the students will re-register
themselves while they are at home during their holiday.
 To have the system that will give the student the details of their fees and
other costs paid and unpaid so they know what must be paid before
coming at the university
 Provides a convenient solution of Maintaining payment records of students
who are enrolled.
 To help the students at the university of Dodoma provide and confirm the
necessary information Needed when starting a new semester mainly
financial details using the internet as the main medium so as to solve the
troubles of queuing at the bursar’s office during class hours while missing
periods at the same time.
 To have the system that will display accommodation allocation for the
registered students
 To have the system that will that will provide a class time table for the
registered student
CHAPTER 4:
4.Functional Requirements

4.1 introduction
Here in the functional requirements we will try to define the internal workings of
the software(system)-UDOM Online Students Reregistration System(UDOM-
OSRS): that is, the calculations, technical details, data manipulation and
processing, and other specific functionality that shows how the use cases are to be
satisfied. Of course the system will allow the users to interrupt with it in different
approach with different identification.

R.1:Access information
Description: The Access of information function will first determine the type of
address that the user has and the address number from which the user wish to
interrupt with the system(UDOM-OSRS) access different information’s that are
authorized to him/her. It checks the account of the user to determine whether the
requested information are available in the system. If enough information are
available ,it outputs the required information, otherwise it generates an error
message.

R.2:Input

5
The system will give the user the authority to click the option “Online
registration” after being permitted to interact with the system either by entering
his/her password sometimes username if required by the system.
5.NON FUNCTIONAL REQUIREMENTS
External interface
This part gives a detailed description of the inputs into and the outputs from the
system. It also gives a description of the hardware, software and communication
interfaces and provides basic prototypes of the user interface
User interface
A first-time user of the UDOM-OSRS should see the log-in page when he/she
opens the web application.
If the user is registered, he/she should be able to see the application front page
of the system directly when the application is launched. Here the user chooses
the type of service he/she wants.
Hardware interface
Since UDOM-OSRS is a web based application it does not have any specific
hardware, it does not have any direct hardware interfaces. The hardware
connection to the database server is managed by the underlying operating system
of the device and the web server.
Software interface
The system communicates with the database in order to get the required
information about the student. The communication between the database and the
web application consists of operation concerning both reading and modifying
the data.
Communication interface
The communication between the different parts of the system is important
because they depend on each other. However, in what way the communication is
achieved is not important for the system and is therefore handled by the
underlying operating systems.

6
7

You might also like