G 3 Final Second

SPECIAL STUDENT SUPPORTING INFORMATION
MANAGEMENTSYSTEM FOR DEBERE BEREHAN

UNIVERSITY
A Senior Project Documentation Submitted to Debre Birhan

University.
In Partial Fulfilment of the Requirement for the Degree of Bachelor of
Science in Computer science.
By Group Three
GROUPMEMBER ID
1. YALEMWORK YESHANEH…………………………1454/08
2. CHILENEW BELACHEW…………………………….1296/08
3. WORKU GIRMA………………………………….......1452/08
4. BEKELECH ALIKO……………………………..……1275/08
5. SAMRAWIT LEMMA…………………………………2036/07
Supervised By “Ins.Eden.A”
Department of Computer Science.
College of Computing, Department of Computer Science

Debre Birhan University, Debre Birhan, Ethiopia
January 25, 2022

Approval letter
The Project is our own and original work which has not been presented for a degree in any other
university. Thus, our signature has duly acknowledged every piece of work that has carried
throughout the whole project.
Name Signature
1. YALEMWORK YESHANEH ……………………

2. CHILENEW BELACHEW ……………………
3. WORKU GIRMA ……………………
4. BEKELECH ALIKO ……………………
5. SAMRAWIT LEMMA ……………………
College: College of Computing
Program: Computer science
Project subject: special student supporting information management system for debere berehan
university
I certify that this project satisfies all the requirements as a project for the degree of Bachelor of
Science.
Name of program coordinator ……………………. Signature …………………….
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope
and quality, as a thesis for the degree of Bachelor of Science.
------------------------------------- -----------------------
Name of Advisor Signature
Examining committee members signature Date
1. Chairman ____________ ____________ __________
2. Examiner 1 ____________ ____________ __________
3. Examiner 2 ____________ ____________ ___________
4. Examiner 3 ____________ ____________ ___________
It approved that this project has been write in compliance with the formatting rules laid down by
the college of the university.
i
Acknowledgment
First, we would like to thank Almighty (omnipotent) GOD, for giving strength; he has given us
throughout our life and the project. Secondly, we would like to express our deepest gratitude to our
advisor Ins.Eden.A for her excellent guidance, caring, patience, and providing us with an excellent
atmosphere for doing this documentation. We would also like to express our gratitude to Debre Berhan
University special student supporting information management system for debere berehan university
Officials who gave enough information for our questionnaires with patience and full of voluntariness.
We would also like to acknowledge our teachers and our class meet student who are help us for unclear
part.
ii
Abstract
The system that we want to develop website for DBU special supported student information
management system. That will help the office to perform their task within few amount of time
and resource in case of data management, resource utilization, and security.
The system develops simple graphical user interface, so that users can use and interact with the
system in a simple way and user-friendly manner provides a file sharing to enable users to share
files to each other.
The implementation of our project will be using an appropriate programing language such PHP
and html is in such a way that a server responds for any connection request from clients and then
sending back to a list of recipients.
The development methodologies of our project using object oriented design methodology. The
reason why our project is conducted to solve: -
 The extravagance of offices resource and member’s time.
 The manually working style of the office worker.
 Communication system of office workers and student.
Contents
iii
Approval letter............................................................................................................................................i
Acknowledgment.......................................................................................................................................ii
List of table.................................................................................................................................................vi
List of figure...............................................................................................................................................vii
List of Acronyms.......................................................................................................................................viii
CHAPTER ONE........................................................................................................................................1
1. Background and Introduction about the Project................................................................................1
1. 1 Introduction........................................................................................................................................1
1.2 Background information of the organization..................................................................................1
1.2.1 Background of the project........................................................................................................1
1.3 Statement of the Problem....................................................................................................................2
1.4 Team Composition.............................................................................................................................3
1.5 objective of the project........................................................................................................................4
1.5.1 General objective of the project...............................................................................................4
1.5.2 Specific objective.......................................................................................................................4
1.6 Feasibility of the project......................................................................................................................4
1.6.1 Economic Feasibility.................................................................................................................4
1.6.2 Political Feasibility....................................................................................................................5
1.6.3 Technical Feasibility.................................................................................................................5
1.6.4 Schedule feasibility...................................................................................................................5
1.6.4.1 Tasks and schedule.........................................................................................................................5
1.7 Significance of the Project...................................................................................................................5
1.8 Target beneficiaries of the system......................................................................................................6
1.9 Methodology of the project.................................................................................................................6
1.9.1 Data Collection Methodology.................................................................................................6
1.9.2 System Analysis and Design Methodology............................................................................7
1.9.3 Case Tools...............................................................................................................................7
1.9.4 Requirements Specification Testing Procedure......................................................................8
1.10 Scope and Limitation of the Project.................................................................................................9
1.10.1 Scope of the Project................................................................................................................9
1.10.2 Limitation of the Project........................................................................................................9
1.11 Assumption and Constraint’s...........................................................................................................9
CHAPTER TWO.....................................................................................................................................11
iv
2. Description of Existing System...........................................................................................................11
2.1 Introduction of Existing system........................................................................................................11
2.1.1 Players in the existing system.................................................................................................11
2.2 Business Rules.....................................................................................................................................12
2.3 Forms and other documents of the existing system.........................................................................14
2.3.1 Report Generating in the Existing System............................................................................15
2.3.2 Major functions/activities in the existing system like inputs, processes &outputs.............15
2.4 Bottlenecks of the existing system (using for example PIECSS frame work)................................17
 Performance.................................................................................................................................17
 Service..........................................................................................................................................18
2.5 Practices to be preserved...................................................................................................................19
2.6 Proposed Solution for the New System............................................................................................19
2.7 Requirements of the Proposed System.............................................................................................19
2.7.1. Functional Requirements......................................................................................................19
2.7.2 Nonfunctional Requirement.................................................................................................21
CHAPTER THREE.................................................................................................................................23
System Analysis.......................................................................................................................................23
3.1 Introduction.......................................................................................................................................23
3.2 Scenarios............................................................................................................................................23
3.3 Use Case Model..................................................................................................................................25
3.4 Use case description.........................................................................................................................26
3.5 Analysis level class diagram (conceptual modeling)........................................................................36
3.6 Dynamic model..................................................................................................................................37
3.6.1 Sequence diagram...................................................................................................................37
3.7 Activity diagram................................................................................................................................44
3.8 State diagram.....................................................................................................................................49
3.9 User interface prototype....................................................................................................................51
3.10 Supplementary Specifications.........................................................................................................52
CHAPTER FOUR...................................................................................................................................53
System Design..........................................................................................................................................53
4.1 Introduction.......................................................................................................................................53
4.1.1 Purpose of the system.............................................................................................................53
4.1.2 Design goal..............................................................................................................................53
v
4.2 System architecture...........................................................................................................................56
4.2.1 Current software architecture...............................................................................................56
4.2.2 Proposed software architecture.............................................................................................56
4.3 Class modelling................................................................................................................................57
4.4 Component Diagram.........................................................................................................................58
4.5 Subsystem Decomposition.................................................................................................................59
4.5.1 Hardware/Software Mapping................................................................................................63
4.6 Deployment Diagram........................................................................................................................63
4.7 Database design.................................................................................................................................64
4.7.1 Persistent Data Management...............................................................................................64
4.7.2 Access Control and Security..................................................................................................65
References................................................................................................................................................68
List of table
Table 1 Team composition......................................................................................3
Table 2 tasks and schedule.....................................................................................5
vi
Table 3 Business rules-1........................................................................................12
Table 6 Use case Description for Login...............................................................26
Table 7 Use case Description for Assign Role.....................................................27
Table 8 Use case Description for Create User Account.....................................28
Table 9 Use case Description for Delete Account...............................................29
Table 10 Use case Description for online Registration.......................................30
Table 11 Use case Description for record material............................................31
Table 12 Use case Description for chat................................................................32
Table 13 Use case documentation of comment...................................................33
Table 14 Use case documentation of manages information...............................34
Table 15 Use case documentation of file transfer...............................................35
Table 16 Use case Description for speech recognition.......................................36
Table 17 Access control and security...................................................................67
List of figure
vii
Figure 1 student register form...............................................................................................................14
Figure 2use case diagram for WCYD........................................................................................................25
Figure 3 Diagram for Analysis label class diagram....................................................................................37
Figure 4 Sequence Diagram for Login.......................................................................................................38
Figure 5 Sequence Diagram for Delete Account.......................................................................................39
Figure 6 Sequence Diagram online registration for student......................................................................40
Figure 7Sequence Diagram for Change password.....................................................................................41
Figure 8 Sequence Diagram for manage information................................................................................42
Figure 9 Sequence Diagram for chatting...................................................................................................43
Figure 10 Sequence Diagram file share.....................................................................................................43
Figure 11 Activity Diagram for Login.......................................................................................................44
Figure 12 Activity Diagram for Create Account........................................................................................46
Figure 13 Activity Diagram for Change Password....................................................................................46
Figure 14 Activity Diagram for chatting...................................................................................................47
Figure 15 Activity Diagram for file management.....................................................................................48
Figure 16 Activity Diagram for speech recognition...................................................................................49
Figure 17 State chart Diagram for login...................................................................................................50
Figure 18 State Chart Diagram for online student Registration System.....................................................51
Figure 19 user interface prototype.............................................................................................................52
Figure 20 system architecture...................................................................................................................57
Figure 21 class modeling diagram.............................................................................................................58
Figure 22 component diagram...................................................................................................................59
Figure 23 Subsystem decomposition diagram...........................................................................................62
Figure 24 hardware software diagram.......................................................................................................63
Figure 25 deployment diagram..................................................................................................................64
Figure 26 database diagram.......................................................................................................................65
List of Acronyms
BR---------------------------------------------------Business Rule
CD----------------------------------------------------Compact Disc
viii
DB-------------------------------------------------Data Base.
DBU-------------------------------------------------Debre Berhan University.
DFD ------------------------------------------------Data Follow Diagram.
DVD-------------------------------------------------Digital Versatile Disc
FK-------------------------------------------------Foreign Key
HTML------------------------------------------------Hypertext Mark Up Language.
HTTP---------------------------------------------Hypertext Transfer Protocol.
HTTPS---------------------------------------------Hyper Text Transfer Protocol Secure
NGO------------------------------------------------ None Governmental Organization.
OOSA -------------------------------------------------Object Oriented System Analysis.
OOSD-------------------------------------------------Object Oriented System Design
OS----------------------------------------------------Operating System
PHP----------------------------------------------------Hypertext Pre Processor.
PIECSS--------------------------Performance, Input output Inaccurate, Efficiency, Service,
Security.
RAM-------------------------------------------------Random Access Memory.
SQL--------------------------------------------------Structural Query Language
UC--------------------------------------------------Use Case
UI----------------------------------------------------User Interface.
UML-------------------------------------------------Unified Modeling Language
PC------------------------------------------------ Personal Computer.
PK------------------------------------------------ Primary Key
SSSIMT. Special Student Supporting Information Management .
ix
CHAPTER ONE
1 Background and Introduction about the Project
1.1 Introduction
This chapter will introduce about the background of the study, and overview of the system that
developed which is the project aims and objectives, summary modules description, project scope,
project schedule, project team composition the outline of methodology, Fact Finding,
development environment, operational environment used, significant of the study, and testing
procedure.
The project is concerned web based system of SSSIMT. The current system does not have any
computerized way of communication. Therefore, our system is the first that intended to change
the manual operations into computerized system. This simplifies the workload of staff members.
1.2 Background information of the organization

The SSSIMT office was approve under DBU is one of forty-five Universities, which were
established scince1999 E.C by the Ethiopian educational ministry of the government. It is
located in Amhara Region, North Showa Zone, in the town of Debre Berhan about 130
kilometers northeast of Addis Ababa.
The office of SSSIMT established because of lack of attitude among the university community
about special students and Physical disable students in DBU in many directions including
educational, material, financially and other services.
1.3 Background of the project

SSSIMT for DBU is the project that is concerned about the way of communication system for
member of SSSIMT in DBU and changes the existing manual system into computerized way. It
mainly focuses on the issue of special students such as disable student, economically supported
student in the university. It helps the office to give its information widely to the community of
the university. our main goal is to change the current Manuel system of work into computerized
form.
This website will be fun, educating and entertaining that will attract many students.
1
1.4 Statement of the Problem
In the existing system, there are a lot of disadvantage related to time, cost and other related
factors. In addition to that On the office, most works done manually, this increase the workload
of the employees for performing different activities.
The following are the most common problems related to current manual system: -
 The communication between sponsor and director, and also student and director is always
manual or paper based.
 Manual registration of student and sponsor makes the director tirades and loss of time.
 luck of information distribution.
 increase the workload of employees.
 Redundancy of data or information.

 Reports prepared manually that leads to inaccurate to be produced and time wastage.
 Difficult to manage the overall system.

 Loss of data.
 The paper kept for a long time becomes older can be damage, and even it can be lost
accidentally.
 There can be a number of papers accumulated each year in a store. This can consume a
large store size as new paper accumulated each year.
 Data affected by external environment such as fire, rain, and any other natural dangers.
 Records can easily be misplaced, damaged, and lost.
2
1.5 Team Composition
The project team is composed from five members as follows
No Member Name Responsibility Email
1 Yalemwork Yeshaneh System Designer and yalmdbu2010@gmail.com

analyzer
2 Chilelenew Belachew Programmer Chilenew.belachew@gmail.com
3 Worku Girma System Designer and analyzer Workugirm@gmail.com
4 Bekelech Aliko Testing bekelech@gmail.com
5 Samrawit Lemma Requirement Gatherer

Samir@gmail.com
Table 1 Team composition
1.6 objective of the project

1.6.1 General objective of the project
The General objective of this project is developing and designing web-based system for SSSIMS
for DBU.
1.6.2 Specific objective

To achieve the general objective, the proposed system, use the following specific objective
 To develop the online registration system module for student and NGO or sponsor.
 To develop various report generation module.
 To design a search module to find all information easily.
 To design a user-friendly user interface and interactive system.
 To develop manage information system module for student.
 Develop chatting rooms.
 Reviewing how the current system works and operates.
 Analyze the current system to design new data base system operated easily using web
based system.
 To develop file sharing system.
1.7 Feasibility of the project

The feasibility of the project is ensuring the new system, which we are going to implement is
efficient and the analysis begins once the goals are define. The project is feasible in different
3
aspects of feasibility. Some of these are Economic, Political, Technical feasible and schedule
feasibility.
1.7.1 Economic Feasibility

The proposed system will have more exceed benefit than expected cost. The deployment of our
project result will have the ultimate benefit to the office from an economic perspective. The
current system has more expenditure in a resource. The system solves this expenditure by a
substitute in a computerized manner.
Economic feasibility can be tangible and intangible benefits perspective.
Tangible benefits
Since this project is going to computerized system, there is reduction of cost for material that
used for manual operation, save time and make comfortable working environment for the users.
Intangible benefits
The intangible benefits we have pointed out the system development are the following: -
 Easily access information.

 Increased flexibility
 Increase speed of activity
 Improves the security mechanism.
1.7.2 Political Feasibility

When this project develops, it does not conflict with any political body and government
directives. Since this office controlled by the current government; the project is not out of the
government strategies and plans. This help to achieve the office plan in appropriate way.
Therefore, the project is political feasible.
1.7.3 Technical Feasibility

The project can easily have deployed by the office using the available technology. It did not
need a special knowledge to a user; it is enough if they know basic computer skill. When they
deploy, it need a computer and give a short training and system be upgraded in the future
technology, so it is technically feasible.
4
Tasks Months
No Steps Nov18- Nov Dec Dec Jan App16- App16-june5
28 30- 11- 26- 19- may15
Dec Dec25 Jan app
10 18 15
1 Proposal
2 Data collection
and
Requirement
3 System
analysis
4 System design
5 Implementatio
n
6 Testing
7 Documentation
Total Overall project
time
Table 2 tasks and schedule
1.8 Significance of the Project

The significance of SSSIMS for DBU system is as follows: -
 Facilities online communication and participation of users.

 Reduces wastage of Resources like, time, material, and cost.
 Give efficient and effective service to the user or the clients.
 To save the workloads of the organization.
 To increase the performance of the organization.
 Generate more secured information for each employee to use the system.
 Enhance office-to-office and other user communication.
 Users can access the system everywhere they can get different services at the same
time and hence the system saves time.
5
1.9 Target beneficiaries of the system
There are different bodies that will benefited from this system. The main beneficiary of these
systems is-
 The first beneficiary of this system is students and other customers and office workers.
 The system supports communication between users.
 How to interact with people around them
 Also sharing files and practicing safe and responsible use of information and
technology
 For director beneficiary
The director gets timely ways of generating report, easily data reporting and accessing
, and reduce the cost and to create easy change of information between college coordinator,
disability center coordinator and other.
 Team Members beneficiary
The project has initiated our team to get knowledge of how to develop the required application
system and the team members will get a comprehensive knowledge and experience in developing
and designing a new system. It also used to create team Spirit among the development team.
 The other beneficiaries of this system are all DBU societies.
1.10 Methodology of the project

1.10.1 Data Collection Method
In the data collection phase of our project, we use interview and Observation. For those methods,
we went to the office and we make an interview and observe.
 Interview: - is making the asking and answering the needed thing. We have made the
interview with the special student supporting office about how to the whole activity in the
special student supporting office management system look like in the DBU. In addition, we
make an interview with some students and employees that work related with issue about their
role and responsibility in the office.
6
 Observation: - in addition to the interview, we have observed many things when we went to
the office in the data collection time. We can analyze how the office prepares recording
information including by getting the form. Generally, we can observe what the current
system of these office look like. Moreover, it helps as to how we propose the next system.
1.10.2 System Analysis and Design Methodology

The project team uses the object oriented design methodology for the development of the system.
Because it is better way to construct and manage objects that are implemented in our system.
Object oriented design methodology has two phases:
Object Oriented System Analysis (OOSA): during this phase, the team will look at the
problem domain and with the aim of producing a conceptual model of the information that exists
in the area, which will have analyzed. Moreover, this model the functions of this system (use
case modeling), identifying the business objects, organize the objects and the relationship
between them and finally model the behavior of the objects.
Object Oriented System Design (OOSD): during this phase, the model interactions and
behaviors that support the use case scenario, and finally update object model to reflect the
implementation environment. Moreover, transforms the conceptual model produced in object
oriented analysis to take account of the constraints needed to our system, so that we will use this
phase to improve the use case model to reflect the implementation environment.
1.10.3 Case Tools

We use the following development tools in order to design our proposed system. Those tools
include hardware and software.
 Software requirement Tools: -

 Enterprise Arch architect: We will use this case tool for designing use case diagram,
class diagram, state chart diagram, activity diagram, sequence diagram and other
needed diagrams or UML diagrams.
 PHP: We will use this software to develop server side interface.
 SQL Server: web server we use.
 Window 10 operating system
7
 Microsoft Office Word 2013: We use this software for documentation preparation and
proposal preparation.
 Hardware requirement tools:
 Computer: We use any desktop computer for all project activities.
 RAM: We use 4GB RAM for our project preparation.
 Disks (CD, DVD); -necessary for the movement of relevant data and for backup and
recovery mechanism.
 Flash: We will use 16 GB Flash for managing our project proposal, documentation etc.
1.10.4 Requirements Specification Testing Procedure

Testing Procedures are the testing practices, processes and techniques used to ensure that the
software application is tested and validating before release or deployment.
We set two approaches to test the proposed system. These approaches are functionality testing of
the proposed system and implementation testing of the system. Each testing approaches use
different techniques. The examiners will test the functionality of the system. In order to test the
functionality of the system, testers will use Black-Box testing technique.
The developers using White-Box testing technique will test implementation of the proposed
system.
Black-Box Testing: - used by testers who do not know the design and structure of the code? The
tester in this case has a set of input values and respective desired outputs from the system. On
providing input, if the output is matches to the desired output the system is tested “OK”. In
addition, problematic otherwise.
White-Box Testing: -We use this testing technique to test the program and its implementation in
order to improve code efficiency and structure of our system.
Testing Levels
There are different testing levels for a system. However, we will use the following testing levels.
These are:
 Unit Testing
8
While coding, the project team performs some tests on that unit of program to know if it is error
free. This testing level helps us to decide that individual units of the program are working as per
requirement and are error free. We use white-box testing approach for this level of testing.
 Integration Testing
Even if the units of the system are working fine individually, there is a need to find out if the
units were integrating together would also work without errors. For example, we test argument
passing and data updating.
1.11 Scope and Limitation of the Project

1.11.1 Scope of the Project
The scope of this project is Developing Web based System for DBU special student supporting
office.
 It concerned about creating a website that makes special student supporting office
effective and efficient by creating text chat room in-group and private, file sharing,
uploading and download files on the website.
 It concerns about increase the participation of NGO (sponsor).
 To manage available information &generating reports for special student
supporting office.
1.11.2 Limitation of the Project

Due to time and budget constraint, our project does not include the whole management system of
the special student supporting office related work in DBU.
There are many constraints within our proposed system that limit their effectiveness of
performance. Our system is limited only in the process of web based SSSIM system of the Debre
university but does not include about hole management system, the system depends on electric
power and network connection. The above activities or subsystems are proposed system
limitations because of the following reason
 Time Is the main factor of limitation our proposed systems that limit its performance
because while we are developing the system it takes more time and we may not get
enough time to automate the system.
 The system does not support any payment system for students using bank.
9
1.12 Assumption and Constraint’s
1.12.1Assumptions
This section must include any assumptions if not true, would require changes to the
requirements.
 The system depends on the software components and operating system which are needed for
the system.
 The hardware used to interact with the system will be standard keyboard as required
 The users know how to start the program from the GUI, and can interact with a user interface
using a standard keyboard, mouse, and monitor.
1.12.2Constraint
 Unfortunate failure of system: To handle this problem we have some method to resist not
completely but partially by using back up mechanisms using flash disks, CD/DVD and by
storing the data in more than two computers.
 Virus attack: It is difficult to control data from virus but try to scan the data, installing and
updating antivirus software for any time.
 Time management problem: we solve this problem by working cooperatively, divide our
time by schedule for each phase of the project and we try to use this schedule effectively
Therefore, whatever situation happen or occurred that hinder during the progression of the
project the team try to do what expected and reform it continuously.
Generally, we will develop the project we encountered different problems like:

 Failures of the programming tools due to the overload of work to the PC.
 Lack of efficient documents provided from the organization.
 Lack of enough references from written books, or from the Internet due to connection
problem.
CHAPTER TWO
2 Description of Existing System
2.1 Introduction of Existing system
This chapter describes what the existing system looks like and how the special student
supporting office of DBU work. The current system on special student supporting office is the
Manuel system.
10
This activity includes generating report mechanism, student and sponsor registration, file
sharing, communication system and other related activities.
The existing system uses Microsoft offices like an excels for its day to day activities that include
storing data’s and other operations and office have no its own website.
2.2 Players in the existing system

An existing system compromises different players with their own responsibilities, and carry out
their own job. The most player of the existing system is mentioned below; -
 The Director of the office: the highest responsible body of the office who controls all over
activities of the employees of the office and others sub office is that found in special student
supporting offices.
 The role of Director in the existing system firstly every plan of the office is preparing
by her.
 The other duty of the director is preparing reports for NGO (sponsor) that support the
SSSIMS office financially and materially.
 The third role for the directories views disability care support reports.
 The fourth role for the director in the existing system includes participating in different
kinds of meetings with stakeholders with in the university and outside of the
University.
 Disability center coordinator:

 This sector will give material, financial and economic support for physically disable
and economic weak student.
 Preparing reports for the SSSIMS office directorate. He also plans and proposed
activities performed in the center.
 Students: those uses the system to get different service online and by direct contacting from the
system
 College coordinator: are those uses the system in order performs office task like: - give
Photocopy service for students and send student grade to director.
The role is providing psychological support for the students and the whole DBU society
11
 Sponsor (NGO): an organization (persons) give service for students by the help of SSSIMS
office.
 Admin: a person who manages and assign the roles of each sector officials
2.2 Business Rules

SSSIMS office is not a business organization but it has certain rules to select the students to
support. The rules are the following: -
Let us look an example on table: -
Identifier BRULE-001
Name Application Requirement
Description Student should have a support letter from their respective residence
Keeble/woreda/ preparatory school to apply firstly.
Disability Students should identify by using whether physically observe

or using hospital evidence.
Example Student who has a support letter from its residential Keble can apply for
the SSSIMS office regarding educational and pocket money support.
Source SSSIMS office policy and procedure.
Table 3 Business rules-1
Name Approve student information
Description Approve student whether the application letter is valid or not.
Example
Source SSSIMS office rules and regulation

Figure 4-business role 2
12
Name Student selection(screen out)
Description Students selected based on the criteria.
Example
Student whom applied firstly in the application process and this process
approved by student union and college coordinators (approved) by directorate
based on the criteria set by the SSSIMS office.
Name Support students
Description material and money support for selected students

Example Material and money support for selected students, based on their status.

2.3 Forms and other documents of the existing system

The following are the major forms and documents used in the existing system: -
13
Registration application forms: - this form used to register the students whom need to apply for
the SSSIMS office firstly.
Screen selection forms: - this form used to screen out the registered students.
Figure 1 student register form
2.3.1 Report Generating in the Existing System

In the existing system, reports are generating for different purpose. For example, the director
writes the monthly and annual report what does they do. This report helps them to announce the
president and for NGO to know how many students involved. The disability center coordinator
also writes reports that disability student information. All these reports are generated manually
using paper.
2.3.2 Major functions/activities in the existing system like inputs, processes &outputs
The current system has the following major function that includes-
 Preparing reports for NGO’

 Providing financial support for DBU special supported students
 Providing material support for DBU special supported students
 Preparing reports SSSIMS office
14
A. Preparing reports for NGO’s
Input
 Year of the report

 Major functions and activities on that quarter and annual year
 Additional financial support proposal
Process
By combining both its quarter and annual year functions and activities, the office of SSSIMS
prepares both reports for its financial donor is which Non-governmental organizations are.
Output
 Report documents
B, providing financial support for DBU students
Input
 Preparing certain criteria’s for selecting financially weak students

 Selecting financially weak students of DBU.
Process
Based on the criteria, the SSSIMS office will select those whom are financially weak students of
DBU.
Output
 Pocket money
C, providing material support for DBU students
Input
 Preparing criteria for those students whom need educational material

 Selecting the students based on that criteria
15
Process
After selecting based on the criteria, the office of SSSIMS provides different kinds of
educational materials for each student whom passed those criteria for support.
Output
 Educational materials like books, pens, pencil and other

 To support disability students of material like photocopy service brain paper, brain
book etc.
D, Preparing quarter term and annual reports SSSIMS office
Input
 year of the report
 major activities on that year done by the center coordinator for disability
Process
In every single year the office of disable student prepares its quarter and annual year
report to the SSSIMS office based on activate done by the sub office.
Output
 Report documents
2.4 Bottlenecks of the existing system (using for PIECSS frame work)
PIECSS framework is a checklist for identifying problems with an existing SSSIMS office
services information system. We classify the problem according to PIECES framework as
follows: -
 Performance
We can measure the performance of the system from two perspectives
 Throughput: the amount of work a system can do on a specified period.

This is not relevant in the existing system because the system not totally automated and it
takes longer time to do one specific job. The existing system only uses Microsoft Word
and Excel when it comes to automated way.
16
 Response time: the time a system takes to react to a given input.
This is not also relevant in the existing system because for example a student may not get a
support from the SSSIMS office at necessary time because of longer time taken for selecting
and screening out the students.
Input and output Inaccurate/redundant
 Input Inaccurate
The existing system is poor in managing the students’ data. Student’s data is capture redundantly
because of poor handling of data’s on the computer system. This happen because of the workload
on the employees of the SSSIMS office, there is no enough skilled IT professional on that office.
There is inaccuracy on the data, because the data contains errors because of the existing system
is not fully automate and it may be subject to human errors.
 Output (inaccurate)
 Irrelevant and redundant information because of the above problem occurred by the
stored data.
 Information that is not accurate because there is a probability to capture wrong input
information so the output is also wrong.
 There is also loss of data’s because of the malicious attacks like viruses on the
computer system, that may cause partial or full loss of data’s.
 Security and control

Due to poor handling of information and data on the SSSIMS office, the computer security
system is vulnerable for human and malicious attacks. To control the system from damage
the office must hire skilled individual with the knowledge of information technology and
implement the security system. However, in current situation the office is very vulnerable on
the security and control measure.
 Efficiency
 Needs skilled professional with database and information technology.
 Wastage of time because data is stored redundantly and incorrectly.
17
 Service
The quality of service in the existing system is poor due to certain factors that were citied on
the above. To improve the current system and to satisfy its user the office should be fully
automate.Generally, the following problems are existing in the current system.
 Most of the time uses manual ways to operate their tasks
 It takes more time and effort.
 Difficult for getting feedbacks.
 Problems of data loss and data redundancy
2.5 Practices to be preserved from the existing system

Even if the existing system is manual and has weakness, there are important an activity we
should preserve to the proposed system that means that there is no required to change. These
practices are-
 Generate report timely.

 Registering students and sponsors(NGO)
 Provide information for its sub part.
 Approved registered students and sponsor.
2.6 Proposed Solution for the New System

From the description of the existing problem, the project team identifies the above problems.
Therefore, the team decides to solve the problems found in the existing system by designing
user-friendly web based application systems in order to solve the current problems. Hence, we
try to solve the problems by the following alternatives:
 Automating the system using computer software application.

 Designing the appropriate data base system in order to store data for a long time
 Designing a user-friendly user interface.
 Information exchange will be easy and takes less time.
 Can address all user requirements.
 More students to know about the services of the SSSIMS office.
2.7 System requirements of the new System

The requirements of the proposed system can contain both the functional and non-functional
requirements of the system. Those are -
18
2.7.1 Functional Requirements
User requirement
It is requirements of the system, director, disability center coordinator, college coordinator and
managers of the system that needs the system to perform. To uniquely identify our user
requirements, we used “REQ #” Where: -
REQ requirement and
# unique number to identify.
REQ 1. Login: director, disability center coordinator, sponsor/NGO, student and college
coordinator login to website by using his or her own username and password to access the web
site.
REQ 2. Create account: The administrator can create the account for each sector in order to use
the website.
REQ 3. Manage account: The administrator can manage user account
REQ 4. Online registration: student and NGO/sponsor can register online in order to perform
their task.
REQ5: Approve Registration: The director can have approved the profiles of the registered
student and sponsor
REQ 6: delete User Account: The administrator can delete user accounts.
REQ 7: Assign Role: The administrator assigns role to each sector.
REQ8: View Report: director and NGO/sponsor can View the report that generated by the
system.
REQ9: Update Information: directors and disability center coordinator can update student
information.
REQ10: Uploading and download necessary information about SSSIMS office related file.
REQ11: Allowing communicate through group and private chat between student and office
worker.
19
REQ12: disability center coordinator registers material that gives for disable students any other
special students.
System requirement
The proposed system has the following functional requirements: -
 Provide user account management capability. the system shall allow an authorized use to
inactive, active, create, and change password.
 Provide manage information capability. the system enables manage information capability.
 Generating report. The system can be generating a report from disability center office and
director office.
2.7.2 Nonfunctional Requirement

Non-functional requirements are requirements that are not directly concerned with the specific
services delivered by the system to its users.
Non-functional requirement usually specifies characteristics of the system as a whole. In other

words, how well some behavioral or structural aspect of the system should have accomplished.
It describes aspects of the system that are concerned with how the system provides the functional
requirements.
 Usability: The system allows users to access and operate on it, because the user interfaces are
easily understandable and user guideline will have prepared to help users to access the system so
the interface is user friendly.
Usability includes viewing, capturing, and stating requirements based around user interface
issues, e.g. accessibility, interface aesthetics and consistency within the user interface
 Reliability: Reliability includes aspects such as availability, accuracy, and recoverability for
example, from shutdown failure. The system is effective and consistent in that integrity of
information maintain and supply to the system. The new system shall be 90% reliable.
 Performance: Performance involves issues such as transition of information, system response
time (which also relates to usability), recovery time and start-up time. Therefore, our system
should be fast in order to access the required information and services of the SSSIMS office. The
proposed system is expected to be response to queries, making updates and generating different
20
reports with short period of time no more than 15 seconds for a single response. It shall also
avoid redundant works, errors and other functions. It shall also avoid redundant works by using
keys. Such as primary key and foreign keys and avoid errors by using validation mechanism and
other functions.
 Supportability: This is a summation of requirements, which address supporting the software;
for example, adaptability, maintainability, compatibility, configurability, install-ability,
scalability and localizability.
 Security and Access permissions: - The subsystem should provide a better level of security and
integrity of the data held by the system as compared to the current system, only authorized
person of the system can gain access to the organization secured page on the system; and only
users with valid password and username can login to view user’s page.
The system must confidentially be control from being access by unauthorized Students or people.
It must protect the SSSIMS offices confidential information and data’s. Encryption is the mean to best
diminish the access exposure of privacy information. It helps in ensuring the confidentiality of
information transferring across networks. User access the confidential information over network protected
by encryption techniques. Therefore, our system will use this encryption method when users enter their
password.
CHAPTER THREE
3 System Analysis
3.1 Introduction
System modeling is the process of developing abstract models of a system, with each model
presenting a different view or perspective of that system and in this section, the functionalities of
the system describes and modeled using UML models and describes the interaction between the
user and the system. This section also used to identify the actors of the system who interacts to
the system and who is use on what function.
3.2 Scenarios of the use case

A scenario is a sequence of steps that represents a single use case execution. It made up of a
number of simple, discrete steps that designated as performed by either the “System” or a
“User”.
21
The following are describing scenario of how the user uses the systems to perform operations.
Scenario Name: Online registration of students
Actor: students
Flow of Event: the students
first activates the system and enter to the homepage by searching student’s id the
system displays the registration form and the student fills the form according to
their requirements. After finishing the form, they submit the form in the SSSIMS
office approved the form which is correct or much to their original profile.
Scenario Name: create account

Actor: admin
Flow of Event: At first, the administrator will make active the system. He /She
browse so that a home page will be display. He /She clicks login link and display
login a form. The administrator fills the valid user name, password, and then click
on the button ‘login’. An admin page, which consist the different task of the
administrator including, create delete account, change account and assign role.
When the user select the account create menu item an account create form will be
displayed which ask the user to fill the required information and the create button
that make the user to create account. System will save the information into the
database and display a message saying, “a user account is successfully created”.
Finally, administrator acknowledges the message.
Scenario Name: delete account
Actor: admin
Flow of Event: administrator first activates the system, then he enters the home
page, he presses the login link from the homepage in order to enter login page he
must fill the exact user name and password. The administrator page is display
from the different categories he should select on the link ‘delete account ‘pressing
this link the user is expected to enter the id of the user to be delete then clicks on
the search button. Therefore, the system will display the required account with its
details including a button saying ‘delete account’ at the bottom of the retrieved
22
account detail. Administrator views all the available information is of the account
since it is necessary to delete he press the delete button. System will save the
information in the database and display a message with “account is delete
successfully”.
Scenario Name: view report
Actor: director of special student supporting office and sponsor
Flow of Event: - SSSIMS office first activates the system, and then he enters the home page.
After entering to the page he logins to the system and inter his user name and password then after
he clicks the report generating button and he/ she can view the report as required.
Scenario Name: manage student information
Actor: director of SSSIMS office
Flow of Event: -director of SSSIMS office first activates the system, then he enters the home
page, then login by its user name and password the presses the manage information link from
the page in order to enter manage student information he must select the exact updated
information. The director of SSSIMS office page is display from the different categories like
update, search information. He should select on the link ‘manage information ‘pressing this link
the user is expected to enter required updated information. Therefore, the system will display the
required information with its details including a button saying ‘manage information’ at the
bottom of the retrieved information detail. Director of SSSIMS office views all the available
information’s of the manage information since it is necessary to update, and search he press the
manage information. System will save the information in the database and display a message
with “manage information is successful”.
23
3.3 Use Case Model
uc Use Case for WCYD
Usecase diagram for SSSIMS
ManageFile
Another sub system
Assign role
USERS Update
«extend» Manage Admin
Manage File Account «extend» Account
«extend» View
Create «extend» Comment
«extend» Account Inactive
«extend» Account
Student
Download Manage Director
Director Approve
College File Student Information
«extend»
Coordinator Upload File Information
Disablity Center «extend»
«extend»
Coordinator Update generate
Sponsor Information Aproved report
Sponsor
Information
Record
Material View Report
Sponsor
Register
Comment
Chat
Disability Center
Coordinator «extend»
«extend»
Private Chat
Group Chat Student
Send request
Information
College Coordinator
Figure 2use case diagram for SSSIMS
3.4 Use case description
Use case NO UC-1

Use Case Login
Name:
Participating All users
Actor(s)
Description: All Users Login to system in order to have privileges for performing their own
different tasks.
24
Trigger When user want to start their work
Typical Actor Action System response

1.Users launch the system 1. The system displays “Home
Course
3.Users click on Login link Page”.
of event
5.Users enter user name and password 4 The system Display the “Login
6. click on login button Form”.
7. If username or password is valid,
the corresponding page for each user
is display. (A7: if user name or
password in correct
8.Use case ends
Alternative 1. A7. If the username and password is incorrect, the system prompt the message,
Course of event
as his /her password is incorrect and try again.
Pre-condition All Users must have user account.

Post User can successfully logged in to the system and Appropriate Page for Each Actor is
condition Display.
Table 6 Use case Description for Login
Use case No: UC-2

Use case Name: Assign Role
Participating Admin
Actor (s):
Description: The “Assign Role” use case enables the Administrator of the system to
assign the privileges of each users.
Trigger When a new request is arrived.

Actor Action System Response
1. Open Assign Role form. 2. Display Assign Role
3. Give Assign for Each individual users form.
Typical course
4. Click assign Role button. 5. Show successful
of events
message. (A5: if filled
25
privilege is not valid).
6. The use case ends.
Alternative A5: if the privilege is not valid, the
course: system displays error message and allows
back to choose the correct privilege for
the user.
Preconditions The administrator should logged into the system and identify the role of
the users.
Post condition Assigned Role that related to the privilege.
Table 7 Use case Description for Assign Role
Use case No: UC-3

Use case Name: Create Account
Participating Actor Admin
(s):
Description: The “Create Account” use case enables the administrator to create user account for
each users.
Trigger When Users need their own user account.
26
1. 1. The Administrator Clicks “Create 2. The system display “Create new Account
new Account Link”. Form”.
1. 3. Admin fills information to create new 4. The system Validate data, and Save (A4:
Basic Course of account, Clicks “Create New Account” If data is invalid).
action. button. 5. The system Display “Account Created
2. 6. The admin confirms the “success Successfully” message.
message”.
3. 7. The use case end.
Alternative course: A4: If data is invalid:

1. System displays error message.
2. The use case resumes to step3.
Preconditions User must be registered

Post condition Account Created for Users.
Table 8 Use case Description for Create User Account
Use case No: UC-4
Use case Delete Account

Name:
Participating The Administrator
Actor (s):
Description: The “Delete User Account” use case enables the Administrator to remove user
accounts.
Trigger When The user account is nonfunctional or have no user.
27
1. Clicks on manage account 2. The system displays “account information
link. form”.
3. Clicks on “View” button. 4. The system displays “account list”.
Typical 5. The Admin select account to delete, 6. The system removes the selected user
course of click “Delete” button. account.
events 8. The Admin confirms “success 7. The system displays “successful
message”. message”.
9. The use case ends.
Alternative Has no alternative conditions.

Precondition There must accounts available.
s
Post Account removed from the user account list.
condition
Table 9 Use case Description for Delete Account
Use case No: UC-5
Use case Online Registration

Name:
Participating Students and NGO/sponsor
Actor (s):
Description: The “Online Registration” use case enables the students and NGO to be register in
the system.
Trigger When Student and sponsor wants to register.

Typical 1. Clicks on online registration link. 2. The system displays “Online
course of 3. The user fills required information Registration form”.
events into the Registration form and click 4. The system return “Success
save button. messages” and (A4 if invalid input
28
5. Use case end. format.
Alternative A4 if invalid input format.

course: “System display error message”.
3. The use case resumes to step3.
Precondition The student and NGO/sponsor should have logged in the system.
s
Post The student and sponsor can registered successfully
condition
Table 10 Use case Description for online Registration
Use case No: UC-6
Use case Record material

Name:
Participating Disability center coordinator
Actor (s):
Description: The “Record material” use case enables for disability center coordinator in the system
Trigger Disability center coordinators and the officer wants to record materials.

1. Click on record material link. 2. The system displays “Record material
3. The user fills to the record form and form”.
click submit button. 4. The system Displays record
Typical 5. Use case end. “Successfully messages” and(A4”the
29
course of input is invalid”
events
Alternative A4 “please input the correct format”.
course: The use case resumes to step3.
Precondition The Disability center coordinator should logged in the system.

s
Post Material is record successfully.
condition
Table 11 Use case Description for record material
Use case No: UC-7
Use case Chat

Name:
Participating All Users
Actor (s):
Description: The User to share their ideas and communicate each other.
Trigger When Users wants to share ideas.
30
Actors action: Step2. The system displays the chatting home
1. Click on the chat link. page.
3. User select receiver. 4. The system connects sender with receiver.
5. Sender write message 7. The system return success message and (A7
6. Send the written message to the receiver.
if message is not send.)
Typical 8. Use case end.
course of
events
Alternative 6.If the text is not sent the system displays” message is not sent”
course: 4. The use case resumes to Step 6.
Precondition The users must logged in the system.

s
Post The user can communicate each other through chatting.
condition
Table 12 Use case Description for chat
Use case No: UC-8
Use case Feedback (comment)

Name:
Participating Student and Sponsor
Actor (s):
Description: Student and sponsor write comments for director office about their weakness’ strength and
other work related information.
Trigger When The student and sponsor want to give comment.
31
Typical Actor Action System Response
course of 1. User must open the home page. 2. System displays comment box.
events 3. Type comment in comment box 5. The system Displays “Successfully

form messages”
4. Click submit button.
Precondition User must browse the system.

s
Post Users can sent and receive text messages.
condition
Table 13 Use case documentation of comment.
Use case No: UC-9
Use case Manage information

Name:
Participating Director.
Actor (s):
Description: Director manage students’ information.
Trigger When the director wants to manage student information.

course of 1 the actor clicks manage 2. Displays form.
events information link 4 The system displays fully personal

3. Enters unique personal information information
to be manage. 7. return success message and (A7
32
5. Actor may Approve, delete or If Submitted is not correct.)
modify information.
6. click Submit button
Alternative 7.If the user enters incorrect information system back step5
course:
Precondition Any user should be login first.
s
Post Student information is manage successfully.
condition
Table 14 Use case documentation of manages information.
Use case No: UC-10
Use case File management

Name:
Participating All user
Actor (s):
Description: Users can upload and download files.
Trigger Information needed distributed among all users.

course of 1. The users click on File management. 2. The system display File upload page.
events 3. The system users select or browse. and download page

5. The system users Browse file or 4 The system selects file (A4)
generate its own file then upload 6.Or The system user also download file.
Alternative 4. If file is not selected the system display select the file message.
course: 2. Prompt the user to select the file from the folder.
33
Precondition The system users should be login to the system.
s
Post The users must upload or download the file.
condition
Table 15 Use case documentation of file transfer.
3.5 Analysis level class diagram (conceptual modeling)
A class diagram in the Unified Modeling Language(UML) is a type of static structure diagram

that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.
The class diagram is the main building block of object-oriented modeling. It is used both for
general conceptual modeling of the systematic of the application, and for detailed modeling
translating the models into programming code. Class diagrams can also use for data
modeling. The classes in a class diagram represent both the main objects, interactions in the
application and the classes to be programmed.
In the diagram, classes are representing with boxes, which contain three parts:
 The top part contains the name of the class

 The middle part contains the attributes of the class.
 The bottom part gives the methods or operations the class can take or undertake
In the design of a system, a number of classes are identifying and grouped together in a class
diagram, which helps to determine the static relations between those objects. With detailed
modeling, the classes of the conceptual design often split into a number of subclasses.
This section discusses classes and their variations, including templates and instantiated classes,
and the relationships between classes association and the contents of classes (attributes and
operations). Class diagrams show the static structure of the model, in particular, the things that
exist (such as classes and types), their internal structure, and their relationships to other things.
34
class analysis class diagram
USER
chat User Account
+ age: int
- Chat content: string has - password: varchar(30)
+ email: varchar(50)
- message time: date - user id: varchar(25)
+ Father Name: varchar(25) 1 1
send/recive - user name: varchar(30)
- reciepant: string + First Name: varchar(25)
- user name: int 1..* 1..* - user role: varchar(30)
+ Grandfather Name: varchar(25)
+ group chat() + personal id: varchar(30) + login()
+ private chat() + phone: varchar(13) + manage account()
+ sex: varchar(6)
+ Chatting()
should login Login
Manages
+ File Managment()
1..* - Password: Varchar(50)
- User Name: Varchar(20) manages
1..* + login()
ISA
+ Logout()
File
- adate: date
Report
- flie name: string Sponsor Admin
- location: string - Date: Varchar
- address: varchar(30) Views - Type: Varchar
+ dowload file() + Assign Role()
- job: string - Generate()
+ upload file() 1..* 1..* + Create Account()
- View(): short
+ Comment() + Delete Account()
+ Registration() + Update Account()
1..*
+ View Report() Approve Disability Center
1 Coordinator
Student
Director
+ record material()
- account number: int
Officers
- deparetement: varchar(25) Approve 1
- Family status: varchar(25) + aprove student infor()
- Photo: file 1..*
1 + search student information()
+ Comment() + update student information()
1..*
+ registration()
College coordinator 1
ISA add
+ Send Report()
disable student
1..*
gets
- type of injured: varchar(30)
Matrerial
1..*
- amount: double add
- material id: varchar(30)
1..*
- Name: varchar(50)
- type: varchar(30)
Figure 3 Diagram for Analysis label class diagram
3.6 Dynamic model

A dynamic model represents the behavior of an object over time. It used where the object's
behavior best described as a set of states that occur in a defined sequence.
35
3.6.1 Sequence diagram
Sequence diagram shows interaction between objects over a specific period time and describe the
flow of messages, events, and actions between objects. We show concurrent processes,
activations and time sequences to these are not depict easily in other diagrams.
sd sequence diagram for login
Terminate
user
WCYD hompage login form controller login database
1.initate()
Director
Student
College 2.click login button()
coordinator
3.activ ate login form()
Disability center
coordinator
Sponsor 4.diplay login form()
5.1 fill user name ()
Officer
5.2 fill passw ord()
6.click login button()
7.submit(use rname , passw ord)
8. request to database()
9.response()
check()
10.if incorrect(use name, passw ord )
10.if v alid(user name , passw ord )
11.sucsses to login()
12.sucsses message display()
Terminate Terminate Terminate Terminate Terminate
Figure 4 Sequence Diagram for Login
36
sd sequence diagram for delete account
Admin Adimin
delete account user account delete account user account user account
form controller list database
1. initate()
2. create()
3 popup user account list()
4.return user account list()
5. show user account list()
6. select user account list()
7. click delete button()

8. click delete function()
9. send request()
10 .response()
11.check()
[if not]:11.1.try again
()
[if deleted]:11.2. remov e user account()
11.return sucsess message()

12. account sucsessful deleted()
13.confirm()
14. close()
Terminate
Terminate Terminate
Terminate Terminate
Figure 5 Sequence Diagram for Delete Account
37
sd sequence diagram for online register
student
home page registration registration register database
form controller
1. open home page()
student
registration
2.click registration link()
3. send request to activate the form()
4 display registration form()

5.fill the form()
6.click sav e button()
7.submit data()
8.request to database()
9.response()
10. check()
[if invalid]:10.1.try again()
11.registration succsse()
12. registration sucsessful()
Terminate Terminate Terminate Terminate

Terminate
Figure 6 Sequence Diagram online registration for student
38
sd sequence diagram for change passw ord
Admin
home page Change passw ord Controller Database
form
1. log in to home page()
2.click change password link()
3 activate the form()
4.display the form()
5.fill the form()
6.click comfirm button()

7. submit()
8.validate()
[if not mach]:9.try agin()
[if mached]:9.change password()
10.confirm()
password apdation is succesefully()
Figure 7Sequence Diagram for Change password
39
sd squence diagram for manage information
diractor
home page manage Controller Database
1.login the home page()

information
form
2.select manage user link()
manage
information 3. dislay manage information from the option()
4. make any change()
5. submit()
6.check()
[if no any change]:7.try again()
[if changed]:8.continue
()
10. display updated()
manage your data is succese fully()
Figure 8 Sequence Diagram for manage information
40
sd squence diagram for chat
Terminate
user
login page controller home page chat page chat database
Student
user name and passw ord()
Director
Sponsor
Officer
v alidate()
College
coordinator
Disability center v alidate()
coordinator
initate()
open()
chating()
submit()
sav e()
chating sucsess()

Terminate
Figure 9 Sequence Diagram for chatting

sd sequence diaram for manage file
user
home page controller database web page file transfer
1. click login()
2. display login form()
Student
3.fill user name and password()
Sponsor
4.check()
Director
Officer
Disability center
coordinator 5.invalid()
6.invalid user information()
College coordinator 7.display()
8.select upload or download file()
9.upload or download file()
10.end of file management()
11.logout()
T erminate Terminate T erminate T erminate T erminate

T erminate
Figure 10 Sequence Diagram file share
41
3.6.2 Activity diagram
Activity diagram used to document the logic of a single operation/method, a single use case,
or flow of logic of business operation. In many ways activity diagram is the object-oriented
equivalent of flow charts and data flow diagrams (DFD) from structured development to
represent the flow from one activity to another activity. It is one of the components of UML
and highlights the activities performed in the system activity. The processing with in an
activity goes to completion and then an automatic transition to the next activity occurs an
arrow represents the transition from one activity to the next. A filled-in circle and an end
represent the starting point of an activity diagram.
act Activ ity diagram for login
Open home Page Click On Login link
Inti al
LOgin Page Displayed
Login
Fill User Name And

Passw ord
If Incoorect
Check User Nam e And Password
Correct
Display Aproporiate
Page
End
Figure 11 Activity Diagram for Login
42
act activ ity diagram for create account
Initate admin page
click create account link
create account form

display
enter user id
click search button
if user id does not exist

check the user is rgister
user detail display
enter user name and

passw ord
confirm passw ord
if user name and password invalid

check valid created
user name
and id
if the password and user name is created
succsessfully created
43
Figure 12 Activity Diagram for Create Account
act Changepassw ord activ ity Diagram
Click ChangePassword
Displaye Change
password form
Change Password Enter old password and

new password
[if not Valid] : Try again

Confirm new Password
Click Change
Check
[if Correct]
Change successfuly
Figure 13 Activity Diagram for Change Password
44
act activ ity diagram for chating
Open Home Page
Ini ti al
Click On Chat link
chat
Display Chat login

page
user name and

passw ord
i nval i d
is valid?
val i d
Chat Page
Displayed
Start Chatting
recive
send message
message
exit
ActivityFinal
Figure 14 Activity Diagram for chatting
45
act activ ity diagram for manage information
open home page
click manage link
chcose or brow ese files
if uploaded file is not found
check if a file exists?
valid
file
displayed
dow nload
file upload file
FlowFinal
Figure 15 Activity Diagram for file management

3.6.3 State diagram
State-chart diagram describes the flow of control from one state to another state. States defined
as a condition in which an object exists and it changes when some event is trigger. Therefore, the
46
most important purpose of State-chart diagram is to model lifetime of an object from creation to
termination. The main purpose of using state -chart includes to model dynamic aspects of a
system, to model lifetime of an object, and to describe different states of an object during
lifetime.
stm state diagramfor login
Waiting User Name and

[Idel] Waiting Login Information [Enter User Name and Passw ord] Password Validatuion
start
[Valid User Name and Passw ord]
[Action Completed]
Login Sucsess
Final [User Name Or Passw ord Inv alid]
State Diagram For Login [abnormal termination]
Failed Login
Figure 16 State chart Diagram for login
47
stm State Diagram sponsor Registration
Registration Failed
[ReturnRegistration Information]
[Additional Information Required]
Sponsor Registration
[Idel]
[fill Sponsor Information] validate
Initial Information
Required
[Sponsor information Filled]
Cancle Registration
Success
[Create User Accunt]
Waiting for User

Account
Information
[Enter User Account Information]
Validate User
Account
Information
[Valid Account Information]
Account Created
[abnormal termination]
Login Sponsor
Page
Final
Figure 17 State Chart Diagram for online student Registration System
3.7 User interface prototype

User interface design is the overall process of designing how a user will be able to interact with a
system. The goal of user interface design is to make the user's interaction as simple and efficient
as possible, in terms of accomplishing user goals. When designing the home page, we use master
Page to each activity in module that is admins activity must be modularized in one master page.
48
The style sheet is used to design each form and in this style sheet we use header, menu and aside
Static part and section that is everything is on it.
Home page
Home Login Contact us Comment register Group chat Rules
Account Sponsor student employee file chat report
Create Account View report Register bank account Upload file

Post text
Send letter Download file

Manage account Read text
Assign role
View report
Manage information View report
49
Figure 18 User interface prototype
3.8 Supplementary Specifications

There are certain rules and regulation the new system that is SSSIMS for DBU will brought and
the existing system also provide that.
 Mostly the members are student of DBU.
 Unregistered persons have no permission to the whole application.
 Validate the form: -When user of the system fill details in the form the system validates
the form.
 The member can be in other room but in one intranet.
 Any meeting participant cannot use if and only if it activated by administrator
 Any member of the meeting or activated person can use the whole applications
provided.
 Determine eligibility to enter to the system: -Users of the system should have a unique
username and password to enter to the SSSIMS site.
50
CHAPTER FOUR
4 System Design
4.1 Introduction
In this chapter, we have discussed in detail about the design goals, system architecture (current
software architecture) and proposed software architecture, Subsystem description, Subsystem
services, Component diagram and Deployment diagram in detail.
System design is the transformation of the analysis model into a system design model. The main
objective of designing a system is to show how the system is build and obtain clear and enough
information needed to drive the actual implementation of the system.
4.1.1 Purpose of the system

The main purpose of the proposed system is to change the manual system, which is so bulky and
annoying system into computerized, and make a simple communication way to make the
working environment good and modernized. Additionally, to minimize the security problems,
and speed up the entire activity/operation of the system. In addition, the new system addresses
the problem of the existing system by providing well-organized, flexible and effective means of
activities.
4.1.2 Design goal

Design goals derived from the nonfunctional requirement of the system, which are the
description of the feature characteristics and attribute of the system as well as any constraints
that may limit the boundary of the proposed solution. Design goals describe the qualities of the
system that developers should optimize. In addition, to design the model with high qualities.
The goals of the system are identifying from the following four major quality perspective.
 Performance
 Dependability
 Maintainability
 End User Criteria
51
Performance Criteria
This include the speed and the space requirement imposed on the system. According to
the following three performances criterion are identifies.
 Response Time
As the system is a web-based application, the acknowledgement of remote user should be

optimizing.
 Throughput
The resources upload by the SSSIMS office will be access by different users and hence it is
required to accomplish several users request.
 Memory
The proposed system will require any size of storage space that fits within the size of the
resources to be stored.
Dependability Criteria
This criterion determines the effort that will be expend in minimizing system crushes and their
consequences. The following are identifying as the main dependability criteria.
 Robustness
The system should have the ability to withstand invalid user input by validating all the user
inputs.
 Availability
The resources uploaded by the SSSIMS offices should be able to be available to the
perspective users of the system as long as users are connecting to the internet. It takes few
seconds to fetch a single data from the server. Since the user can access the required
resources in a short fractions of time.
 Reliability
52
The system should behave in a way, which is reliable. It should have the ability to
authenticate all users, and validate each, and every user inputs, and other operations to
ensure reliability.
 Fault Tolerance
To ensure fault tolerance of the system backup services of both the application and
database server will be maintaining, and hence will be switched to, whenever the primary
servers experience a failure
 Security
Because of, the system is access over a public network; the system is likely to be expose
to vulnerabilities unless appropriate security measures are takes. To withstand intrusions
and hacking of the system firewall and other appropriate security measures shall be in
place. Moreover, the system is expected to compromise a security policy to protect
sensitive areas of the operation like Admin registration and other user registration from
malicious users.
Maintenance Criteria
Maintenance criteria determines how difficult it is to change the system after deployment. It also
determines how easily new functionalities can be added. The following are identified as
maintenance criteria.
 Extensibility
Since the proposed system uses Object Oriented Design approach, new functionalities and
new classes can be easily added.
 Modifiability
The new SSSIMS offices system should be well documented which will make it easily
modifiable after deployment without hampering the current working system.
End User Criteria

End user criteria include qualities that are desirable from user’s point of view that have not yet
been cover under the performance and dependability criteria. The following is identified as end
user criteria;
53
 Usability
The system should be user-friendly system so that users can easily learn and use it easily
without convenience.
4.2 System architecture

4.2.1 Current software architecture
This is a brief description of the current software architecture of SSSIMS offices in DBU. As it
has been stated during the requirement analysis and mentioned in the analysis document,
currently SSSIMS office in DBU uses a manually dominated system supported by a small scale
micro soft office applications that run on some standalone computers, to manage, and facilitate
the day to day routines of the bureau.
4.2.2 Proposed software architecture

Overview
The proposed system is developed in order to replace the current manual based system into a
computerized way. In this case, it uses three tires architecture were the client use the local area
network of the university. Three tiers architecture is an architecture in which the functional
process logic, data access, computer data storage and user interface are developed and
maintained as independent modules on separate platforms. Those thee tire are the presentation
layer (UI), Service/application tier or business logic (BL) and data tier (DB).
The presentation layer (UI): -this layer is the top-level part and displays information related to
services available on the server. This is the user interface displayed when the user opens the
application.
The Service/application tier or business logic (BL) is the middle tier, which is pull from the
user interface. It performs controlling the application functionalities by performing detailed
processing. The main responsibility of this tier is connecting the user interface and the database.
The data tier (DB) is a house for database servers where information is store
54
deployment deployement diagram for SSSIMS
«device» Applecation Serv er DataBase Layer

Personal Computer(client)
«device»
HTTP response
personal SQL Serv er
w eb serv er
computer mysql
brow ser
HTTPS Rquest
Figure 19 system architecture
4.3 Class modelling
55
Figure 20 class modeling diagram
4.4 Component Diagram

In the unified modeling language, a component diagram depicts how components are wired
together to form large components or software systems. They used to illustrate the structure of
arbitrarily complex systems. Show how the physical components of a system are organized, and
shows which component or objects will be accessed by whom and what type of security
infrastructures it is using. The diagram simulated as follows.
56
cmp COMPONENT DIAGRAM FOR SSSIMS
admin
manage account
subsystem
director
manage
information
subsystem
system security
disabilty center
v iew report
coordinator
chat subsystem
college
coordinator
file management
sponsor
DataBase
registration
subsystem
student
Figure 21 component diagram
4.5 Subsystem Decomposition

Subsystem a replaceable part of the system with well-defined interfaces that encapsulates the
state and behavior of its contained classes. By decomposing the system into relatively
independent subsystems, concurrent teams can work on individual subsystems with minimal
communication overhead.
Subsystem decomposition constitutes the bulk of system design. In order to reduce the
complexity of application domain smaller parts called classes are identified, and organized in to
packages. Similarly, to reduce the complexity of the solution domain, a system is decomposed
into simpler parts, called subsystems, which are made of a number of solution domain classes.
Normally each subsystem is realizing independently.
57
During system decomposition, different system-wide issues need to be address. The initial
subsystem should be drive from the functional requirements. The next step in subsystem
decomposition is to keep functionally related objects together using use case.
Generally, the following heuristics use in grouping the objects in to the subsystems.
 Assign objects identified in one use case in to the same subsystem.

 Create a dedicated subsystem for objects used for moving data among subsystems.
 Minimizing the number of associations crossing subsystem boundaries.
 All objects in the same subsystem should functionally related.
1. User Account management subsystem
This subsystem has the following functional requirements.
REQ 1: Create user account.
REQ 2: Delete user account
REQ 3: update account
REQ 4: Assign role
2. View report Subsystem

REQ 1: View daily, monthly, and annually report.
REQ 2: send request information.
3. Registration Subsystem
REQ 1: register supported student.
REQ 2: register sponsor.
REQ 3: record material
4. File management subsystem
58
REQ 1: upload files
REQ 2: download files.
5. Manage information
REQ 1: approved student information.
REQ 2: approved sponsor information.
REQ 3: update information.
REQ 4: Search information.
REQ 5: Delete information.
6. Chatting Subsystem
REQ 1: private chat.
REQ 2: group chat.
7. Comment Subsystem
REQ 1: Send Comment
REQ 2: View Comment
The diagram simulated as follows.
59
cmp SubSystem Decomposition
Registration Sub System Chat Sub System

Manage Account Sub System
Priv ate Chat
Register Student Create Account
Group Chat
Register Delete Account
Sponsor
Update Account
Register
Material
Asign Role
SSSIMS
inactiv e account
View Report Generation
Manage Registration Information

View Report
Delete information
Search Information
Manage File Sub System

Comment Sub System Approv ed Student Information
UPload File
View Comment
Dow nLoad Approv ed Sponsor Information
Send Comment
Update Information
Figure 22 Subsystem decomposition diagram
4.5.1 Hardware/Software Mapping

The system decomposition is one of issues that need to be addressed is the Hardware/Software
mapping. It describes information like hardware configuration of the system. The
Hardware/Software Mapping of SSSIMS office in DBU is describes below.
60
deployment Hard w are Soft w are Mapping
T CPAP
Application Serv er
«devi ce»
Personal Computer «devi ce»
Manage Account Mobile
HT T PS
HTT PS
Web
Brow ser Mobile
Brow ser
View Report
HT T PS
HT T PS
HT T PS
Registration HT TPS
HTT PS
HTT PS
File Managment
HTT PS
HT T PS
HT T PS Chat HTT PS
Manage
Information
sql
DataBase Serv er
DBMS (sql
serv er)
Figure 23 hardware software diagram
4.6 Deployment Diagram

Our system will deploy on the application server that is Apaches server, and clients can access
the system with HTTPS request to this application server. The application server accesses the
database with HTTP.
Figure 24 deployment diagram
61
deployment deployement diagram for SSSIMS
w eb Serv er
«device»
Personal Computer(client)
https appache http

serv er
WebBrow ser
https
php
tcp/i p
DataBase
my sql
4.7 Database design

4.7.1 Persistent Data Management
Persistent data management is an issue, which needs to be addresses during system
decomposition. Persistent data outlive a single execution of the system; and this allows all the
subsystem to run consistently. It describes data that need to be stored persistently where it should
be stored and how it should access. For this reason, the mapping of objects to tables are display
as follows: -
62
UserAccount * FileManagement *
UserId FileManageUser *
FileId
UserName FileUseId
FileType
FiledId
Status FileSize
User_id User_id
Location
FileName
User_id
Student * StudentMaterial *
StumatId
Role * StudId
RoleId
Employee * MaterialId
Year
EmpId
StudId
Name USER * Deparetement
User_id
UserId Email User_id
Qualification
Discription Name AccountNumber
FatherName Familystatus DisableStudent *
StudId
GrandfatherName EmpId
TypeOfInjured
Sex photo
Material Age
MaterialId Phone
MatName [User id]
Quantity
Comment CommUser
Type CommId StuId
EmpId CommentDescribition
CommId
Sponsor * StudId SpoId
User_id SpoId ComUseId
SpoId
Adress
Job
ChatUser * Type
ChatUserId EmpId
ChatId
Chat *
User_id ChatId
MessageTime
MessageContent
User_id
Figure 25 database diagram
4.7.2 Access Control and Security

Here clearly describe the way we will use to secure our system and the issues associated with
access control within our system; we should also specify which actions is given to which user
under what condition. Access to the system must controlled by creating different authentication
levels and using password for login purposes. Any people who have the authentication to use the
system have to provide a username and password in order to perform what it supposed to do. .
Systems are required to be abide by access control policies (security policies) to protect the
system and data from -
 Unauthorized access
 Malicious modification of data or destruction
 Accidental introduction of inconsistency
63
. Each user has a security access level and each document has a sensitivity level.
Admin Director Sponsor Student Disable College Officer

center coordinator
Login       
Update account       
Delete account       
Create account       
Assign role       
Send report       
Download files       
Upload files       
Record materials       
Private chat       
Group chat       
Online register       
Comment       
View report       
Approved student       
information
Update student       
information
Register support       
student
Approve a       
sponsor
information
Logout       
Table 16 Access control and security
64
CHAPTER FIVE
5 IMPLEMENTATION AND TESTING

5.1 Introduction
Implementation is the phase where objectives of physical operations of the application turned
into reality i.e. real working model. The crucial phase in the system development life cycle is the
successful implementation of the new application design. The process of converting as new
system into an operational one is known as system implementation. This includes all those
activities that take place to convert from a previous system to a new system. The focus of our test
strategy was simply prototyping testing on our system. The system developers are in a position
of converting all documents gathered and designed into the code so that the system will be
implemented for the user to be used for the purpose it developed. Implementation refers to the
coding of the all documents gathered starting from requirement analysis to Design phase. For the
implementation of this system, the user must have a computer and browser on it and search the
link of server where the SSSIMS software is deployed.
5.2 Hardware software acquisition

Hardware software acquisitions determine the system resource requirements, its capability with
other systems and networks, its interface requirements to existing systems if any, its security
capability, deficiencies and vulnerability and to make sure there are not already existing
software/system that provide equivalent functionality. For the project implementation the
following Software and hardware are used.
For the proper functioning of the system the following hardware and software are required
 Hardware’s: -
 Any Desktop Computer: for running the system
 RAM
 Laptop
 Flash disk 8GB
 Network cable
 Printer: For printing Document
 Software: -
 Microsoft word 2013
 Microsoft PowerPoint 2013
 Wamp Server
 MySQL database server
 Notepad++
 Enterprise architect
 Browsers (Mozilla Firefox, Google chrome)
65
5.3 language specification and selection strategy
To implementation (developing) this project we will have used PHP for front end (developing
Graphic user interface). Because PHP works great with html, interactive features and easy to
learn and My SQL for back end (for database).
5.4 Sample code

Coding is the process whereby the programmer turns in the physical design specification created
by the designers to working computer code.
E.g1 To give material
<?php
include("../connection.php");
session_start();
if(isset($_SESSION['UserName'])){
$UserName=$_SESSION['UserName'];
$sql="select UerName from useraccount where UserUame='$UserName'";
$ret=@mysql_query($sql);
$db_field=@mysql_fetch_assoc($ret);
$fname=$db_field['UserName'];
}else{
66
?>
<script>
alert('You Are Not Logged In !! Please Login to access this page');
alert(window.location='../login.php');
</script>
<?php
?>
<HTML>

<html lang="en-US" xml:lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>wcyd dbu</title>
<link rel="icon" type="image/ico" href="images/Picture1.ico"/>
<link rel="stylesheet" type="text/css" href="css/setting.css">
<script type="text/javascript" src="javascript/date_time.js"></script>
<script type="text/javascript">
</script>
<link rel="stylesheet" type="text/css" href="index's_file/globcss.css" />
</head>
<body background="images/bac.PNG" style='margin:0' onLoad="timeimgs('1');">
<center>
<table class="container" style="width:1310px;height:350px; background-color:#cococo >
<?php
require("header.php");
?>
<table width="1310px" border="0"height="350px"cellpadding="0" cellspacing="0" style="background-

color:#606060">
<?php
67
require("menudcc.php");
?>
</table>
<table width="1310px" border="0" cellpadding="0" cellspacing="0"
style="margin-top:0px;height:166px;background:url(index's_file/)">
</table>
<table style="margin-top:-300px" width="1310px"height="350px" border="0" cellpadding="0"

cellspacing="0">
<tr>
<td class="left_container" width="200px" valign="top" style="background-color:#919191">
<table width="100%" cellpadding="0" cellspacing="0" style="background-color:#919191">
</tr>
<tr>
<td class="left" align="left" >
</td></tr>
<tr>
<?php
require("left.php");
?>
</tr>
</table>
</td>
<td valign="top" align="left">

<td width="6px"> </td>

<form method="post">
68
<table align="center" border="0"cellpadding="4px"cellpadding="4px" style="margin-top:100px">
<?php
$d_program = @mysql_query("SELECT user_id FROM

useraccount where UserName='$UserName'");
while($getDprog = @mysql_fetch_array($d_program)){
$id = $getDprog['user_id'];
?>
<?php
} ?>
<tr><td>material type:</td><td>
<select name="matid" id="matid" data-rel="chosen" required>
<option selected="selected" value="">material type</option>
<?php
$result = mysql_query("select * from material")or die(mysql_error());
while ($row=mysql_fetch_array($result)){ ?>
<option value="<?php echo $row['matid']; ?>"><?php echo $row['type']; ?></option>
<?php } ?>
</select></td></tr>
<tr><td>taker id:</td><td>
<select name="studid" id="studid" data-rel="chosen" required>
<option selected="selected" value="">student list</option>
<?php
$result = mysql_query("select * from student where

action='approve'")or die(mysql_error());
while ($row=mysql_fetch_array($result)){ ?>
<option value="<?php echo $row['studid']; ?>"><?php echo $row['fname']." ".

$row['mname']; ?></option>
<?php } ?>
</select></td></tr>
69
<tr><td>quantity </td><td><input type="text"id="quantity"pattern="([0-9]{1,30})"name="quantity"
required /></td></tr>
<?php
$today=date('y-m-d',time());
$new=date('y-m-d',strtotime($today));
//echo $new;
?>
<tr><td> </td><td><input type="submit" name="submit" value="taken" /></td>
</tr></table>
<?php
if (isset($_POST['submit']))
//$user_id=$_POST['user_id'];
$borrowe_id=$_POST['studid'] ;
$quantity=$_POST['quantity'] ;
//$mattype=$_POST['mattype'] ;
$matid=$_POST['matid'] ;
$db = @mysql_connect("localhost","root","") or die ("Error connecting to database.");
if(!$db)
echo"no connection established";
mysql_select_db("final_project",$db) or die("Couldn't select the database.");
$sql=mysql_query("SELECT quantity FROM material where matid='$matid'");
while($row= mysql_fetch_array ($sql) )
$quantit=$row['quantity'];
$total = $quantit - $quantity;
70
if($total<0){
echo"qunitity is low to get";
else{
$sql1="SELECT * from studentmaterial where (date!='' AND borrowe_id='$borrowe_id')||date='' ORDER

BY date DESC LIMIT 1";
$qury1 = @mysql_query($sql1);
$row1=@mysql_fetch_array($qury1);
//$date=date('y-m-d',time());
//$st=$_GET['st'];
$prev=$row1['date'];
$dbtime=date('y-m-d',strtotime($prev));
$x=$new-$dbtime;
echo"$x";
if($prev==0)
$ins = "INSERT INTO `studentmaterial` (`borrowe_id`, `mattid`,`quantity`,ùser_id`) VALUES

('$borrowe_id', '$matid', '$quantity', '$id')";
$result_set1=@mysql_query($ins,$conn);
if(!$result_set1)
die("Query faill".mysql_error());
else{
echo "<script>alert('Successfully taken' )</script>";
mysql_query("UPDATE material SET quantity='$total' WHERE matid='$matid'");
71
else if(($x/(60*60*24)>90))
mysql_query("UPDATE student SET date='$new'and quantity='$quantity' WHERE

studid='$borrowe_id'");
mysql_query("UPDATE material SET quantity='$total' WHERE matid='$matid'");
} else if($x/(60*60*24)<90){
echo "<script>alert('not working time' )</script>";
} }}?>

<td>
<div id="siderightindexphoto11">
Calander
</div>
<?php
require("../date.php");
?>
</div>
<div id="siderightindexadational">
<div id="siderightindexadational1">
Social link
</div>
<table >
<tr><td><div id="twitter"></div></td><td><p><a href="https://www.twitter.com/" style="text-

decoration: none;">   Twitter</a></p></td></tr>
<tr><td><div id="facebook"></div></td><td>
<p><a href="https://www.facebook.com/" style="text-decoration:

none;">   Facebook</a><p></td></tr>
72
<tr><td><div id="you"></div></td><td><p><a href="https://www.youtube.com/" style="text-
decoration: none;">   Youtube</a></p></td></tr>
<tr><td><div id="googleplus"></div></td><td><p><a href="https://plus.google.com/"

style="text-decoration: none;">   Google++</a></p></td></tr></table>
</div>
</td>
</table>
</td>
</tr></table>
<table width="1310px"
style="margin-bottom:4px;margin-top:6px;background:#C3C3FF; ;border:1px solid :#C3C3FF;"

border="0" cellpadding="10" cellspacing="0">
<tr>
<?php
include("../footer.php");
?>
</td></tr></table>
</td></tr></table>
</center>
</body>
</html>
e.g. 2. Register sponsor source code
73
<?php
include("config/config.php");
session_start();
if(isset($_SESSION['']))
$mail=$_SESSION[''];
?>
<HTML>
<html lang="en-US" xml:lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>wcyd for dbu</title>
<link rel="stylesheet" type="text/css" href="index's_file/globcss.css" />
<link rel="stylesheet" type="text/css" href="setting.css">
74
<SCRIPT language='Javascript'>

</SCRIPT>
<link rel="icon" type="image/ico" href="images/Picture1.ico"/>
<script type="text/javascript" src="javascript\date_time.js"></script>
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.js"></script>
</head>
<body>
<center>
<table class="container" style="width:1310px;height:350px; background-color:#cococo >
<?php
require("header.php");
?>
<table width="1310px" border="0"height="350px"cellpadding="0" cellspacing="0"

style="background-color:#606060">
<?php
require("menuindex.php");
?>
75
</table>
<table width="1310px" border="0" cellpadding="0" cellspacing="0"
style="margin-top:0px;height:166px;background:url(index's_file/)">
</table>
<table style="margin-top:-300px" width="1310px"height="350px" border="0" cellpadding="0"

cellspacing="0">
<tr>
<td class="left_container" width="200px" valign="top" style="background-color:#919191">
<table width="100%" cellpadding="0" cellspacing="0" style="background-color:#919191">
</tr>
<tr>
<td class="left" align="left" >
</td></tr>
<tr>
<td>
<?php
require("left.php");
?></td>
</tr>
</table>
</td>

<script type='text/javascript'>
function validate(){
var firstname=document.getElementById('fname');
var middlename= document.getElementById('mname');
76
var lastname= document.getElementById('lname');
var job = document.getElementById('job');
var phone = document.getElementById('phone');
var city = document.getElementById('city');
var email = document.getElementById('email');
var sex = document.getElementById('sex');
var spoid = document.getElementById('spoid');
var age = document.getElementById('age');
if(isAlphabet(firstname, "please enter Your First name in letters only")){
if(lengthRestriction(firstname, 3, 30,"for your First name")){
if(isAlphabet(middlename, "please enter Your Middle name in letters only")){
if(lengthRestriction(middlename, 3, 30,"for your Middle name")){
if(isAlphabet(lastname, "please enter Your Last name in letters only")){
if(lengthRestriction(lastname, 3, 30,"for your Last name")){
if(isAlphabet(city, "please enter Your city in letters only")){
if(lengthRestriction(city, 3, 30,"for your city")){
if(isAlphanumeric(spoid,"Please Enter the Correct ID No (!@#$%^&*()*+=~`) Not allowed")){
if(lengthRestriction(spoid, 3, 15,"for your ID No")){
if(isNumeric(phone, "please enter Number only For Phone Number")){
if(emailValidator(email,"check your e-mail format")){
if(lengthRestriction(phone, 10, 10,"for your Phone number")){
return true;
}}}}}}}}}}}}}
return false;
function isAlphabet(elem, helperMsg){
var alphaExp = /^[a-zA-Z]+$/;
if(elem.value.match(alphaExp)){
77
return true;
}else{
alert(helperMsg);
elem.focus();
return false; }}
function emailValidator(elem, helperMsg){
var emailExp = /^[\w\-\.\+]+\@[a-zA-Z0-9\.\-]+\.[a-zA-z0-9]{2,4}$/;
if(elem.value.match(emailExp)){
return true;
}else{
alert(helperMsg);
elem.focus();
return false;
}}
function isNumeric(elem, helperMsg){
var numericExpression = /^[0-9]+$/;
if(elem.value.match(numericExpression)){
return true;
}else{
alert(helperMsg);
elem.focus();
return false;
}}
function lengthRestriction(elem, min, max, helperMsg){
var uInput = elem.value;
if(uInput.length >= min && uInput.length <= max){
return true;
}else{
alert("Please enter between " +min+ " and " +max+ " characters" +helperMsg);
78
elem.focus();
return false;
}}
function isAlphanumeric(elem, helperMsg){
var alphaExp = /^[0-9a-zA-Z\/]+$/;
return true;
}else{
alert(helperMsg);
elem.focus();
return false;
}}
function isAlphabet(elem, helperMsg){
var alphaExp = /^[a-zA-Z]+$/;
return true;
}else{
alert(helperMsg);
elem.focus();
return false;
}}
</script>
<form action="addsponsor.php" method="post" name="insert" onsubmit="return validate()">
<table bgcolor="#AFAFDB" cellpadding="0" align="center"border="0"style="margin-top:5px>
<tr><td colspan="2" ><center><h2><b>sponsors Information Registration

Form</b></h2></center></td></tr>
<tr><td>spoid:</td><td><input type="text" name="spoid" id="spoid" style="height: 30px;width:

200px;" required placeholder="Enter sponsor id"/>
79
</td></tr>
<tr><td>FirstName:</td><td><input type="text" name="fname" id="fname"

style="height: 30px;width: 200px;" required="required" placeholder="first_name" />
</td></tr>
<tr><td>MiddleName:</td><td><input type="text" name="mname" id="mname"

style="height: 30px;width: 200px;" required="required" placeholder="first_name" />
</td></tr>
</td></tr>
<tr><td>Last Name:</td><td><input type="text" name="lname" id="lname" style="height:

30px;width: 200px;" required="required" placeholder="last_name" />
</td></tr>
<tr><td>job:</td><td><input type="text" name="job" id="job" style="height: 30px;width: 200px;"

required="required" placeholder="last_name" />
</td></tr>
</td></tr>
<tr><td>address:</td><td><input type="text" name="address" id="city" style="height: 30px;width:

200px;" required="required" placeholder="adress" />
</td></tr>
<tr><td>Sex:</td><td><select name="sex" id="sex" style="height: 30px;width: 200px;"

required>
<option value="">--Please Select---</option>
<option value="male">Male</option>
<option value="female">Female</option>
</select>
</td></tr>
<tr><td>Email:</td><td><input type="email" name="email"

id="email"pattern="(\w[-._\w]*\w@\w[-._\w]*\w\.\w{2,3})" style="height: 30px;width: 200px;"
required="required" placeholder="Enter Email" />
function ValidateEmail(inputText)
80
{
var mailformat = /^\w+([\.-]?\w+)*@\w+([\.-]?\w+)*(\.\w{2,3})+$/;
if(inputText.value.match(mailformat))
form1.email.focus();
return true;
else
alert("You have entered an invalid email address!");
form1.email.focus();
return false;
}}
</script>
</td></tr>
<tr><td>phone_no:</td><td><input type="tel" name="phone_no" id="phone"p

style="height: 30px;width: 200px;" required="required" placeholder="phone_no" />
</td></tr>
<tr><td>age:</td><td><input type="text" name="age" id="age" style="height: 30px;width:

200px;" required="required" placeholder="age" />
$(function () {
$("#submit").on("click", function () {
if ($('#age').val() > 100 || $('#age').val()<18) {
alert("Please enter a number between 18 - 100 ");
return false
81
});
return true
});
</script>
</td></tr>
</tr>
<tr><td></td><td><input type="submit" id="submit" name="submit" style="height: 30px;

width: 100px;" value="REGISTER">
<input type="reset" id=id="m" name="validation" style="height: 30px; width: 100px;"

value="CANCEL"size="20" >
</td></tr>
</table>
</form>
<?php
if (isset($_POST['submit']))
$spoid=$_POST['spoid'];
$fname=$_POST['fname'];
$mname=$_POST['mname'];
$lname=$_POST['lname'];
$job=$_POST['job'];
$address=$_POST['address'];
$phone_no=$_POST['phone_no'];
$email=$_POST['email'];
$age=$_POST['age'];
$sex=$_POST['sex'];
$inu="INSERT INTO ùser` (ùser_id`, `fname`, `mname`, `lastname`, èmail`, `sex`, àge`,
`phone_no`,`Role`)VALUES
('$spoid', '$fname', '$mname', '$lname', '$email','$sex','$age', '$phone_no','sponsor')";
$result_set=@mysql_query($inu,$conn);
82
$ins="INSERT INTO sponsor(`spoid`, `fname`, `mname`, `lname`, `job`, àdress`, `phone_no`, èmail`,
àge`,`sex`,àction`) VALUES
('$spoid', '$fname', '$mname', '$lname', '$job', '$address', '$phone_no', '$email', '$age','$sex','waiting

to approve')";
$result_set1=@mysql_query($ins,$conn);
if(!$result_set1&&!$result_set)
die("Query faill".mysql_error());
else{
echo "<script>alert('Successfully registored' )</script>";
echo "<script>windows: location='addsponsor.php'</script>";
}}
?>
</h2>
</font>
</td>


<td>
83
Calander
</div>
<?php
require("date.php");
?>
</div>
<div id="siderightindexadational">
<div id="siderightindexadational1">
Social link
</div>
<table >
<tr><td><div id="facebook"></div></td><td>
<p><a href="https://www.facebook.com/" style="text-decoration:

none;">   Facebook</a><p></td></tr>
<tr><td><div id="twitter"></div></td><td><p><a href="https://www.twitter.com/"

style="text-decoration: none;">   Twitter</a></p></td></tr>
<tr><td><div id="you"></div></td><td><p><a href="https://www.youtube.com/" style="text-

decoration: none;">   Youtube</a></p></td></tr>
<tr><td><div id="googleplus"></div></td><td><p><a href="https://plus.google.com/"

style="text-decoration: none;">   Google++</a></p></td></tr></table>
</div> </td></table></td>
</tr></table>
<table width="1310px"
style="margin-bottom:4px;margin-top:6px;background:#C3C3FF; ;border:1px solid :#C3C3FF;"

border="0" cellpadding="10" cellspacing="0">
<tr><?phpinclude("footer.php");?></td></tr></table></td></tr></table></center></body></html>
84
5.5 Final Testing of the system
Once code has begun, the testing process can begin and proceed in parallel. As each program module is
produced, it can be tested individually, as part of the larger program, and then as part of larger system.
The following are different testing strategies. We will perform following testing techniques for checking
functionality of our proposed system.
 Unit testing: - First we will test each unit at each system. Each module of the system can be
tested check the working of each classes, methods and attributes of the system. For
immediately maintain at which the problem is occurred.
 Integrated testing: - In this testing part, all the modules will be combined together and
tested for their combinability with each other and with the systems functionality. If error
occurs in combining them, the module with problem will be identified and re combined. All
team members perform both units testing and integrated testing during development. Here
users cannot involve.
 System testing: - In this testing, the team performs over all functional testing by checking
whether it meets the required target or not.
5.6 User manual preparation

Since the system is web based system everything we expect important for the user will be
explained using Help menu in some basic activity of the system and implemented while
preparation of short training document when the system is deployed.
5.7 Training
Training manuals serve the important purpose of providing a consistent way to communicate
instructions to users about how to perform essential functions of their action by using the system.
The administer office is responsible to give training for the SSIMS user. And the project
developer gives full training to the administrator of the system.
To be effective, training manuals is based on functionalities and instructional objectives.

Information should be provided about the processes and procedures users are required to follow
as well as tasks that form the basis of the jobs they are charged with performing.
5.8 Installation Process

This project is now completed and ready for use. It can’t be installed to the desired destination
and it provides all the functionalities it is intended for because it is web-based. This is done by
85
creating all the data bases and tables that helps to store the purpose of reuse the data and to
validate the new data with the old data.
Required items to request an agent installation:
To request a web based installation, we need to provide the following information:
 Name of organization requesting the installation
 Ip address of the server being protected
 Host name of the servers
 URL being protected
 Operating system of the web application server being protected. Give the specific version
of windows, Linux, or Unix, specify whether 32/64 bit
 Type of web application server (Apache)
5.9 Startup strategy

The start-up strategy will be:
 Buying a domain name

 Hosting the system
 Finally, available internet connection
86
CHAPTER SIX
6 Conclusions and recommendations

6.1 Conclusions
This project which has two phases; the first phase concerned with the analysis phase of the
lifecycle, the design phase and the next phase is about implementation. As the end of the first
phase, we review that we have covered in accordance with what we have planned at the
beginning. We began our work by identifying the significance of web based system for the
on SSSIMS and the overall techniques to be used in the development process. This involved
defining the system development methodology, identifying resource and cost
requirements, and setting the deliverable and scheduled for the project.
The analysis helps our team to understand the major functional areas and processes of the
system. Through this method we evaluate the existing system that is manual system weakness.
After that, we performed requirements elicitation to discover user and system requirements. This
phase consisted of drawing the functional as well as non-functional requirements of the system.
Then we have undertaken a major phase in system development process: object oriented
Analysis. Here, we tried to model the new system we proposed using UML diagrams: Use case,
sequence, and activity and class diagrams Also, we designed the new system user interface
prototyping and implementation.
This new project is aimed to give the opportunity for DBU the opportunity student to use this
technology. The developed website has a more advantage for the society, organization and the
member of the university.
6.2 Recommendations
While doing this project the team has faced different challenges. According to the scope of our
project, the team develops web based system which may lack some functionalities. Because of
the time constraints, we cannot do full functionality of the systems, but in the future the team
believes that this system can be fully operational by having enough time and full information.
Next, the team would recommend that further work should be done on the system in order to
make the system improvement. Generally, for the next programmer or system developer, our
project team members recommend to add additional languages (e.g. Amharic and other
languages), speech recognition, speech synthesis, student give money on line system and video
group and private chat.
87
Appendix
Appendix A: diagram used during development
Symbol Definition
Actor
Use case
Package
Component
Node
Device
88
References
Timothy C.Lethbridge and Robert Lananiere. (n.d.). Object-Oriented Software Engineering
(Second edition ed.). (K. Mosman, Ed.) London: McGraw-Hill Education.
Grady Booch and Robert A.marksimchuk. ((2007)). Object Oriented Analaysis and Design with
Application (Third Edition ed.).
Malan Ruth. (n.d.). Functional Requirement and Use Case. Hewelett-Packard Company.
Satzinger, Jackson, and Burd. (n.d.). System Analysis and Design ( Fifth Edition ed.). In a
Changing World.
89

G 3 Final Second

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

G 3 Final Second

Uploaded by

Copyright:

Available Formats

SPECIAL STUDENT SUPPORTING INFORMATION

MANAGEMENTSYSTEM FOR DEBERE BEREHAN

A Senior Project Documentation Submitted to Debre Birhan

Department of Computer Science.

College of Computing, Department of Computer Science

January 25, 2022

1. YALEMWORK YESHANEH ……………………

1.2 Background information of the organization

1.3 Background of the project

 Redundancy of data or information.

 Difficult to manage the overall system.

No Member Name Responsibility Email

1 Yalemwork Yeshaneh System Designer and yalmdbu2010@gmail.com

3 Worku Girma System Designer and analyzer Workugirm@gmail.com

4 Bekelech Aliko Testing bekelech@gmail.com

5 Samrawit Lemma Requirement Gatherer

1.6 objective of the project

1.6.2 Specific objective

1.7 Feasibility of the project

1.7.1 Economic Feasibility

Economic feasibility can be tangible and intangible benefits perspective.

 Easily access information.

1.7.2 Political Feasibility

1.7.3 Technical Feasibility

Table 2 tasks and schedule

1.8 Significance of the Project

 Facilities online communication and participation of users.

 Team Members beneficiary

 The other beneficiaries of this system are all DBU societies.

1.10 Methodology of the project

1.10.2 System Analysis and Design Methodology

1.10.3 Case Tools

 Software requirement Tools: -

1.10.4 Requirements Specification Testing Procedure

1.11 Scope and Limitation of the Project

1.11.2 Limitation of the Project

Generally, we will develop the project we encountered different problems like:

2.2 Players in the existing system

 Disability center coordinator:

2.2 Business Rules

Let us look an example on table: -

Disability Students should identify by using whether physically observe

Source SSSIMS office rules and regulation

Table 4 Business rules-3

Description material and money support for selected students

Source SSSIMS office rules and regulation

2.3 Forms and other documents of the existing system

Figure 1 student register form

2.3.1 Report Generating in the Existing System

 Preparing reports for NGO’

 Year of the report

B, providing financial support for DBU students

 Preparing certain criteria’s for selecting financially weak students

C, providing material support for DBU students

 Preparing criteria for those students whom need educational material

 Educational materials like books, pens, pencil and other

We can measure the performance of the system from two perspectives

 Throughput: the amount of work a system can do on a specified period.

 Security and control

 Needs skilled professional with database and information technology.

 Wastage of time because data is stored redundantly and incorrectly.

2.5 Practices to be preserved from the existing system

 Generate report timely.