Group 3 Project Final 1-3 (Commented)

Samara University
College of Engineering and Technology
Department of Computer Science

Project Title: Web Based Final Project Management System for
College of Engineering and Technology
Prepared by:
Name ID
1 Eshetu Moges……………0032/08
2 Natnael kassu…………….0056/08
3 Asnakew Kasew…………...0018/08
4 kalab Yibelital ………….0046/08
5 Roble Odawa……………0060/08
Advisor: Mr. Welday G. Samara, Ethiopia
January, 2019
Final Project Management System for CET 2011
Table of Contents
Table of Contents..............................................................................................................................i
Acknowledgment............................................................................................................................iii
Abstract............................................................................................................................................1
List of Acronyms.............................................................................................................................2
List Of table.....................................................................................................................................3
Chapter One.....................................................................................................................................5
1 Introduction...................................................................................................................................5
1.1.1 Background about the Organization..............................................................................5
1.1.2 Introduction about the project.............................................................................................6
1.2 Statement of the Problem...........................................................................................................6
1.3 Objective....................................................................................................................................7
1.3.1 General objective................................................................................................................7
1.3.2 Specific Objective...............................................................................................................7
1.4 Scope of the Project and Limitation..........................................................................................7
1.4.1 Scope...................................................................................................................................7
1.4.2 Limitation...........................................................................................................................7
1.5 Significance of the Project.........................................................................................................7
1.6 Methodology for the Project......................................................................................................8
1.6.1 Data Gathering Technique..................................................................................................8
1.6.2 Design Methodology..........................................................................................................8
Table of Content Page i

1.6.4 Implementation Methodology............................................................................................9
1.6.5 Testing Methodology........................................................................................................10
Chapter two....................................................................................................................................11
2 Requirement elicitations...............................................................................................................7
2.1 The over view of the existing system........................................................................................7
2.1.1 Major activities in the existing system...............................................................................7
2.1.2 Problem of the existing system...........................................................................................8
2.1.3 Weakness and strength of the existing system...................................................................8
2.1.4 Business rules of the system...............................................................................................8
2.2 Overview of the proposed system..............................................................................................9
2.2.1 Functional requirements of the proposed system...............................................................9
2.2.2 Non-functional requirements of the proposed system......................................................10
2.2.3 System requirements of the proposed system....................................................................11
2.4 Constraints and Assumptions..................................................................................................11
2.4.1 Constraint..........................................................................................................................11
2.4.2 Assumption.......................................................................................................................11
Chapter Three................................................................................................................................13
System Model................................................................................................................................13
3.1 Use Case Specification............................................................................................................13
3.2 Use Case Diagram...................................................................................................................14
3.2.1 Actor Specification...........................................................................................................14
3.2.2 Use Case Description........................................................................................................16
3.3 Sequence Diagram...................................................................................................................26
3.4 Class diagram...........................................................................................................................31
Reference......................................................................................................................................33
Table of Content Page ii

List Of table
Table3. 1:- use case description for login......................................................................................16
Table3. 2:-use case description for create Account.......................................................................18
Table3. 3:- use case descriptions for manage project....................................................................19
Table3. 4:- use case descriptions for manage schedule.................................................................20
Table3. 5:-use case descriptions for register Project.....................................................................20
Table3. 6:- use case descriptions for give Comment.....................................................................21
Table3. 7:- use case descriptions for view comment....................................................................22
Table3. 8:- use case descriptions for register on project...............................................................23
Table3. 9:-use case descriptions for view schedule.......................................................................24
Table3. 10:- use case descriptions for view notification...............................................................24
Table3. 11:- use case descriptions for view result.........................................................................25
Table3. 12:- use case descriptions for logout................................................................................25
Table of Content Page iii

List of figure
Figure 1 :-use case diagram...........................................................................................................20
Figure 2:-Sequence Diagram for Login.........................................................................................31
Figure 3:-Sequence Diagram for Set Schedule..............................................................................32
Figure 4:-Sequence Diagram For create account...........................................................................33
Figure 5:-Sequence Diagram For Submit Result...........................................................................34
Figure 6:-Sequence Diagram view result......................................................................................35
Figure 7:- Sequence Diagram for Logout......................................................................................36
Figure 8:- Sequence diagram for register project..........................................................................37
Figure 9:-Class diagram for register..............................................................................................38
Figure 10:-Class diagram...............................................................................................................40
Table of Content Page iv

Acknowledgment
First of all, we would like to thank our God, who gives as love, patience, healthy,
wisdom and ability to walk through all the problems and obstacles during the period of
our study. Then we would like to acknowledge our advisor Ms. Welday G/kirstos very
Much, they was giving directions and leading how to work the project from every
beginning of the proposal writing up to prepare documentation. And we also want to
acknowledge to our department head Mr. Sisay Tigstu for the advice to work the
project effectively and timely based on the schedule planned and for their constructive
opinion and willingness to participate in each part of our project and their effective
direction, assistance and guidance for the accomplishing of our project. . Lastly we
would like to say thanks to all 4th year computer science department students.
Table of Content Page v

Abstract
This project is aimed at developing Web Based Final Year Project Management System for
Samara University College of engineering and technology. The general objective of the project
is to change the existing paper-based system into computerized system for samara University
College of engineering and technology project management activities. After the new
management system, the existing system is replaced by flexible, accurate, and fast access
strategy. Final Project Management System mainly consists of four types of users. The student
who update task status, register/submit their project, view and give comment, view schedule ,
view their mark , department head who invite manage all over the activity in project
management, manage project, Advisor view project status , give comment for student project
and view feedback, submit student result ,Examiner view schedule and submit student mark. To
give different services in the system this four users needed.
This document deals with the system analysis and design of web based final year project
management system for samara university CET. This is mostly used for the system users that we
have described in the different parts of this document. Computerized is the basic thing for the
office in every of its activity it must be changed in to computerized system software in order to
reduce the delay of work.
Basically this project major function is generating project Management (managing) and display
the result of students‟ online. This system is specifically focus on project management system.
So in the future it might good that perform all project activates online and student can get advice,
Show result, scheduling and comment on that system.
Table of Content Page vi

List of Acronyms
CET…………………………………..College of Engineering and technology
CSS ……………………………… Cascading style sheet
EC ………………………………..Ethiopian Colander
GB …………………………………….Giga Byte
HTML …………………. ……………hyper Text Markup Language
OOSAD…………………………….object oriented system analysis and design
PHP ……………………………………..Hypertext preprocessor
SQL.………………………………….Structured Query Language
UC………………………………………….usecas
List of acronyms Page vii

Chapter One
1 Introduction
1.1.1 Background about the Organization
Samara University is a newly established pioneer academic institution located in Ethiopia
specifically situated at “Samara” town which is the regional capital of the Afar National
Regional State. The region is endowed with considerable amount of natural resources
which are totally unavailable or rarely available in other parts of the country and even in
any part of the world. The University is located with a distance of 1.5kms farther from the
Ethio-Djibouti international high-way that connects Ethiopia with Djibouti.
The CET at Samara University was established on July 7th, 2011, we take pride in our
accomplishments and in the quality of our programs in, playing a prominent role in the
academic mission of our university towards the goal of growth and transformation plan of
the country. Currently the college of engineering and technology has undergraduate
programs in Chemical Engineering, civil engineering electrical engineering, computer
science, and information technology, mechanical engineering, construction technology and
management engineering. Today, the College of Engineering and Technology is the
largest college on Samara University with more than 1594 students in regular and
extension programs. The college is poised to play an important role to influence economic
development of Afar region by providing education, training, technology transfer, and
research opportunities in engineering and technology.
The mission of College of Engineering and Technology is dedicated in producing

competent Engineers and Technologists, to conducting and releasing problem solving
research outputs, and providing need based community services and transferring
technologies to foster the development aspiration of the nation and the vision is
Introduction Page 1
To be one of the top ten leading Institute of Technology in pastoral and agro-pastoral
community development in East Africa by 2025. [1]
?? what is the space here.
1.1.2 Introduction about the project

In Samara University for CET, student projects for college of engineering and technology
were managed mostly by manually. Later on project management techniques were
formalized to more professional and modern solutions. The development of different web
based system has provided enormous advantages for many organizations and institutions.
Due to these advantages of the organization our team members are interested to develop
web based Final Project Management System to college of engineering and technology for
Samara University. In the previous time the information of project was stored in manual
based. This makes the system tedious to work so many tasks. Since Web based final
project management systems are designed to manage and store project information that are
used in web-based applications.
1.2 Statement of the Problem

The following are some of the problems faced with the current final year project management
system of college of engineering and technology.
 Lack of information can be occurred because submission date and other task is notified
manual based; the posted paper can be tearing out if students are not going to the notice
board.
 The data can loss and redundant.
Introduction Page 2
 It consumes time and resources.

 Lack of good time management
Generally, the manual way of data handling and running up of the activities is
tedious.
1.3 Objective
1.3.1 General objective
The general objective of the project is to develop Web Based Final Project Management
System for CET.
1.3.2 Specific Objective

In order to achieve the above general objective, the following specific objectives are required:
 To make easy and suitable user friendly system for users.

 Identifying the problem of the current system
 To analyze the existing system and design better system for the CET.
 Design and develop the system based on the requirements identified
 Implementation of the system
 Testing how the system works under a variety of conditions
1.4 Scope of the Project and Limitation

1.4.1 Scope
Scope of the project means the boundary that we are performing tasks in this project. This
project mainly focuses on the manipulation of final year project management system
starting from assigning of project title, advisor and management of account, project,
schedule, and comment up to showing the result of students. So our Project is to Develop
Web Based Final Project Management System for CET in the samara university.
1.4.2 Limitation
 The system does not support local language like Amharic
 The system couldn’t support to evaluate Students result in online.
Introduction Page 3
1.5 Significance of the Project

 To make the work of project coordinators simple.
 Reduce time and resource wastage on the progress of the project.
 Avoid redundancy of projects.
 Avoiding data lost
 Better and fast process scheduling
 Storing completed project to the data base.
1.6 Methodology for the Project

1.6.1 Data Gathering Technique
Observation
While finding facts, the team member intensely observed all the activities and transaction usage
of files and document through observation. Observation helped us in finding out the actual way
of functioning part from the ideal or desired. The team member tries to analyze by direct
observation from college of engineering and technology. Direct observation helps to know what,
how would be done and who would perform the activities in the project management system.
Document analysis
Using this method of gathering requirements, our team tried to analyze existing written
documents in college of engineering and technology.
Interview
Our project team members orally discussed and interviewed some staff members and
administrator of the engineering and technology departments to get necessary information about
our system. This information helps us to identify the project problems and also to understand the
current System. So, the team member analyzed the information of the project and obtained some
basic concepts on how the project is managed in the current system.
1.6.2 Design Methodology

In this system the team would use Object Oriented System Develop Iterative project
management system methodology. This is the phase that bridges the gap between problem
Introduction Page 4
domain and the existing system in a manageable way. This phase focuses on the solution
domain, i.e. “how to implement?”
It is the phase where the SRS document is converted into a format that can be implemented and
decides how the system will operate. [2]
1.6.3 Analysis methodology
In our project, we used object oriented system analysis and design (OOSAD) because OO
focuses on data rather than the procedures and it support reusability of code. Therefore, the
time and cost of development is inherently less. It includes essential use case diagram,
system use case diagram, use case descriptions (scenarios), sequence diagrams, activity
diagrams and class diagram.
1.6.4 Implementation Methodology

Software requirements
In this project the following system develops project management system tools will be used:
Activities Software Tools

Client side coding and user HTML
interface design
Client side scripting(for JavaScript
validation purpose)
Database server MySQL
Web server Wamp Server
Server-side scripting PHP
Browsers Mozilla Firefox ,chrome and torch
Editors(To write source Notepad++
code)
Introduction Page 5
Table 1 Software tools
Hard ware requirements
Name of hardware Model

Processor Intel core i3
RAM 4GB
System type 64 bit
Hard disk 400 GB
Introduction Page 6
Table 2:-Hardware tools
1.6.5 Testing Methodology

Before directly deploying this system, the team would perform different testing for its
functionality and users need. First the team tests each unit at each phase. So, if a problem is
encountered it would immediately fixed. Then the team would perform an integration testing to
check whether the system address all the functional requirements. System would be tested using
the following system testing procedures.
Alpha testing:-In this testing method, the system is tested by giving the correct input. It is tested
by user at the developer Site.
Beta testing:-In this testing method, team force the system to be tested for incorrect data input.
The System would be tested by the user at their actual work place.
If any failures occurred while testing the system in all the above testing methods, the team would
take immediate correction beginning where this fault occurred before jumping to next work so
that it would meet the goal. If all the above testing methods are carried out and find to be valid
the system would directly deployed.
Unit testing: - this unit testing will implement during deployment time. So, if the error will
occur, it will fix immediately
Integration Testing:-When a number of components are complete; it will make an integration

testing to check whether the system meets all the functionality requirements or not.
Introduction Page 7
Chapter two
2 Requirement elicitations
2.1 The over view of the existing system

Currently in college of engineering and technology Final Project Management system is fully
manual system. All those activities are performed manually by using paper.
It is necessary to know the existing system of an organization to develop a better system. As
mentioned above existing system currently performs different activities includes managing
Advisor information, manage project, task schedule, Create process schedule, Update the task
schedule if it is necessary, record project and also Generate report in manual way. The target
Introduction Page 8
area of this proposed system is web-based Final Project Management system (i.e. change manual
system in to computerized system).
2.1.1 Major activities in the existing system

Final year project management are the projects that are expected to be done by department who
controls the overall activities of the project, Students who are the main actors of the project,
Advisors who advises Students to done their project effectively, Examiners who evaluate
students in the presentation day.
Process:
 First the department assign Advisors and group members, and perform scheduling
properly
 Advisor advises Students and follows up the progress of the project
 Students also select and submit three titles to the department and contact their advisor
and select one title, do their project if it is accepted, submit their project and view their
result.
 Finally Examiners also examinee Students and submit the result of Students to
department
2.1.2 Problem of the existing system

The overall activities of the college of engineering and technology final project
information management are under taken manually. Because of these manual activities
problems is face like: There are repetitive and bulky activities like task schedule, adding
new project and updating records periodically and Wastage of working materials (papers),
Loosing of data. Due to these the office is facing a lot of problems that need much
improvement in order to assist in realizing organizational objectives. The manual way of
data handling and running up of the activities is tedious.
2.1.3 Weakness and strength of the existing system

Strength
 Network: independent which can work without network connection.
Introduction Page 9
Weakness
 Time: consumes much more time to retrieve and to get the service
 Labor: the system requires many numbers of employee and energy.
 The data can loss and redundant.
2.1.4 Business rules of the system

The business rules related with the existing system are the following
 Advisors make correction for student project
 Advisor must properly advise in time
 Advisor give advice for their project
 Advisor and Examiner evaluate students
 Students must upload project information and document
 Receive and perform what the advisor say to them
 Student must respect their advisor and department
 Department Head Must assign advisor and group members
 Department Head must control advisors
 Department Head Must apply the rule for the project and must manage the task
properly
 Examiner must examine students in the presentation day and must give appropriate mark
2.2 Overview of the proposed system

After a thorough investigation of the currently working system, we need able to identify the
critical problems clearly observed (that was explained in the problems of existing system in the
above). Therefore, in order to solve these problems we have established a new system that would
benefit the organization. The new system works by taking the input from the user and store the
input in the database for the future use. Those input are Project schedule with related task,
Reports and comments from user and employee, advisor and student biography and current
project status
When this system is advanced for web based Final project Management system in order to
facilitate the activity for evaluation of project wisely.
The major purpose of proposed system is: -
Introduction Page 10
 To improve project time management

 To reduce paper work
 To reduce loss of data
 To facilitate the working system of college of engineering and technology.
2.2.1 Functional requirements of the proposed system

A functional requirement describes what a software system should do. The functional
requirements focus on requirements of the proposed system. It deals with what the system
should do or provide for users. The major functional requirement of the proposed system
includes:
 The system shall allow the department head to create account

 The system shall allow all authorized Students to register/submit their project
 The system shall allow authorized advisor view the student project
 The system shall also allow the advisor to give comment to students
 The system shall allow View comment and notice
 The system shall allow the department to set schedule (post, update and delete etc.)
 The system shall allow assign advisor
 The system shall allow to update schedule if it is necessary
 The system shall allow to update the data base when updating new project
 The system shall allow submit the student mark
 The system shall allow the Student to view result
 The system shall calculate result of students
 The system shall include a user authorization procedure where users must be identified
using a login name and password
 Generate report from the database.
2.2.2 Non-functional requirements of the proposed system

The Non-functional requirements of our proposed system include
Performance requirements:
 The proposed system is fast to process data.
 No wastage of time to organize and integrate file

 It has the ability to processed data efficiently and effectively.
Security requirements
 The system doesn’t allow unauthorized users to log into it.
 No one can modify and give comment for student.
 The proposed system is more secured
Availability
The system is available at any time in the presence of intranet connection.

The system can be accessed by the user to be used.
Reliability
The system should handle invalid inputs and displays error message to users
Maintainability
The system can be easily maintained.
The user interface is user friendly and interactive so it is easy to fix while errors occur.
Portability
This system supports easily portable, since it runs on a different platforms.
Access permission
Consideration of the security of the system has a great advantage for this system, because the
database should be secured from the unauthorized users. Only those who have access permission
are authorized to access the database. To prevent from the unauthorized user, the user should
have user name and password is used privatized only for who has access rights.
End user criteria
The system should have simple and understandable graphical user Interface such as forms and
buttons which have descriptive names. It should give reliable response for each user comment.
All the interface forms and buttons are written or designed in a simple language or common
language so that the user can access simply without any difficulty
2.2.3 System requirements of the proposed system

Hardware requirement
 Client computer (desktop or laptop any type brand).

 Server computer with wamp server installed.
 Network cable (IPV4)
Software requirement
 Web browser (Mozilla Firefox, Google chrome, …)
 Wamp server
2.4 Constraints and Assumptions

2.4.1 Constraint
 Insufficient connection
 Unable to contact with advisors regularly.
 Have insufficient material.
2.4.2 Assumption
 Student would upload their project for their advisor
 Advisor would make advice for his/her student in take web based
 Student would follow in online with their advisor
 Student would view project schedule & project profile.
 Student obtains information about project for the future to be corrected
 Accuracy and security can be maintained easily.
 It is web-based system so Users use it anywhere and anytime.
 Department can easily change data or information; also it enters and appends the data
any time.
Chapter Three
System Model
3.1 Use Case Specification
A use case is an interaction between users and a system. It captures the goal of the users
and the responsibility the system to its users. It is the functionality of the system or the
service provided by the system. A use case is a sequence of action that provides a
measurable value to an actor.
A use case describes a sequence of action that provides a measurable value to an actor and
draw as a horizontal ellipse. Each Use Case describes the functionality to be built in the
proposed system. The most important and basic use cases of this system are the following:-
 Login
 Manage account.
 Manage Project
 Upload project
 Download the Project
 Upload comment
 Download comment
 View and Add notification
 Set Schedule and Update Schedule
 Show, submit and view Result
3.2 Use Case Diagram

Use case diagrams:-are diagrams used for capturing for functional requirements
of the system. Each use case diagram describes a behaviorally related sequence of
transaction in a dialogue between the user and the system. A use case diagram is a
collection of actors, use cases, and their communications.
3.2.1 Actor Specification

In the use cases an actor interact with the system to perform a piece of meaningful work
that helps them to achieve a goal and has access to define their overall role in the system
and the scope of their action. The following are the actors involved in Final Year Project
Management System for CET.
 Department Head:- A person that control all activity like login to the system, create and
delete account for all users, set notice to the student, assign advisor to student, set and
update schedule ,manage project which means approve if it is not done before and
reject/delete if it is done before .
 Advisor: - Advisor is a person who guides students when they do their project. Perform
activity like login to the system, register to the project by selecting the project, view
schedule, give comment to student and view feedback that given by student, and submit
student result to department head.
 Student: - a person who attends his/her lesson in one of programs found in the
department. Perform activity like login to the system, register their project, view
notification, view schedule, view their mark out of hundred and give feedback to advisor
and view comment.
 Examiner: - a person who examine the student. Perform activity like view schedule and
submit student result.
Figure 1 :-use case diagram
3.2.2 Use Case Description
1. Use case name Login
2. Identifier UC1
3. Description To Authenticate the user
4. Actor Department, Advisor, Student and Examiner
5. Pre-condition The User must have an account
6. Basic Course of 6.1 The user open the system

action 6.2 Display the home page
6.3 Select the Login link
6.4 The system display the Login page
6.5 Fill user name and password
6.6 Validate user name and password
6.7 The system would display the appropriate information
6.8 Use case ends.
7. Alternative course 7.1 If the user name and password is incorrect the system
of action display incorrect user name and password
7.2 The system redirect to go to step 6.4 i.e. enter user name
and password
7.3 Use case ends.
8. Post condition The Authenticated person get the target page
Table3. 1:- use case description for login
1 .Use case name Create account

2. Identifier UC2
3. Description It describes the process of creating
a new account for the user

4. Actor Department head
5. Pre-condition The Department head must login in
to the system.
6. Basic Course of action 6.1 The Department head clicks
manage accounts
6.2 The system display manage
accounts menu.
6.3 The Department head click
create account from manage
accounts menu.
6.4 The system displays create user
account page
6.5 The department head fills the
required information and click the
create button.
6.6 The system saves the user and
display successful message
6.7 The use case end
7. Alternative course of action 7.1 If the user miss required

information
7.2 The system displays the
message “missed field! “
7.3 The use case return back to
basic flow event 6.4
8. Post condition The Department head successfully
create the user account
Table3. 2:-use case description for create Account
1. Use case name Manage project

2. Identifier UC3
3. Description Use Case to add /delete and to view project
information consequently.
4. Actor Department head
5. Pre-condition The Department Head must be login to perform
those activities.
6. Post condition System has successfully add/delete and display
project information to the Department Head
7. Basic course of 7.1 Department Head clicks add new project /delete project.
action 7.2 The system displays project registration form/enter
project Id to delete/enter project Id to view
consequently.
7.3 Department Head fills project data/enter project Id.
7.4 When Department Head click “submit/delete/view
“button the Added/deleted/search stored in systems
database/deleted from the data base/save to data base
and display from the database consequently.
7.5 Use case ends.
8. Alternative course 8.1 When there is not filled the project data correctly
of action “please fill project data correctly” message would be
displayed.
8.2 When the Department Head fills the form incorrect
manner, the message “Invalid data Entered please fill in
appropriate format” would be displayed.
Table3. 3:- use case descriptions for manage project
1.Use case name Manage Schedule

2.Identifier UC4
3.Description Use Case to add /delete and update schedule
information consequently.
4.Actor Department Head
5.Precondition The Department Head must be login to perform those
activities.
6.Post condition System has successfully add/delete/update/ and
display task schedule to the Department Head
7.Basic course of 7.1 Department Head clicks the set new task schedule /update
action link.
7.2 The system displays task schedule form to create enter task
id and starting and ending date/enter task Id to update c.
7.3 Department Head fills starting and ending date of task the .
7.4 When Department Head click “save/d/update/ “button the
Added/updated stored in systems database/deleted from the
data base.
7.5 Use case ends.
8. Alternative 8.1 When there is not filled the task schedule data correctly
course of action “please fill schedule data correctly” message would be
displayed.
8.2 When the Department Head fills the form incorrect manner,
the message “Invalid data Entered please fill in appropriate
format” would be displayed.
Table3. 4:- use case descriptions for manage schedule
1. Use Case Register Project

Name
2. Use Case Id UC5
3. Description register project in order to approve their project
4. Actor Students
5. Preconditio The Students have full privilege.
n
6. Basic 6.1 The Students must log to his/her page
course of action 6.2 The Students select register link.
6.3 The system display the project registration form
6.4 The student fill the form and click the register project link
6.5 The system displays the information successfully register
6.6 Use case ends
1 Alternative The system verify information is not correctly

course of action 7.1 The system displays
7.2 Go to step 6.4
7.3 Use case ends
8 Post condition The Project would be shown to the advisor and Department Head.
Table3. 5:-use case descriptions for register Project
1.Use Case Give Comment

Name
2.Use Case Id UC6
3.Description give Comment for Student
4.Actor Advisor
5.Precondition The Advisor has full privilege.
6.Basic course 6.1The Advisor must log to his/her page
of action 6.2 The Advisor select give Comment link.
6.3 The system displays the give comment page
6.4 The Advisor click give comment

6.5 The system display the space
6.6 The advisor write the comment in the space and click the give
comment
6.7 The system display successfully message
6.8 Use case ends
7.Alternative 7.1The system displays error message for in valid selection

course of 7.2Go to step 6.5
action
7.3Use case ends
8.Post The comment is shown to the student

condition
Table3. 6:- use case descriptions for give Comment
1.Use Case View comment
Name
2.Use case Id UC7
3.Description get comment from Advisor
4.Actor Students
5.Precondition The Students have full privilege
6.Basic course a. The user must log to his/her page

of action b. The user select view comment link
c. The system display the page
d. The student view the comment
e. Use case ends
7.Alternative
course of
action
7 Post condition When there is comment, the Students would get it.
Table3. 7:- use case descriptions for view comment
1. Use case name Register on project
2. Identifier UC8
3. Description The advisor and student register to the system to participate on the
project activities
4. Actor Student and Advisor
5. Precondition The Student and Advisor must be login to perform those activities
6. Post condition System has successfully display registration form to the Student and Advisor
7. Basic course of 1.1 Student and Advisor click the “register” link.
action 1.2 The system displays the required forms “submit” button consequently Student
and Advisor register on specific project.
1.3 When Student and Advisor click “submit information” button the “submit” save
to the systems database display comment consequently.
1.4 Use case ends.
2 Alternative course 2.1 When there is not filled the user type “please select user type” message
of action would be displayed.

2.2 When the Student and/or advisor fill the form incorrect manner, the
message “Invalid data Entered please fill in appropriate format” would be
displayed.
Table3. 8:- use case descriptions for register on project
1. Use Case Name View schedule
2. Use case Id UC9
3. Description get schedule from Department
4. Actor Students Advisors, and Examiner
5. Precondition The Students, advisor Examiner must have full privilege
6. Basic course of 6.1 The user must log to his/her page
action 6.2 The user select show view Schedule link

6.3 The system displays the information to the user
6.4 Use case ends
7 Alternative course The system verify information is not correctly
of action 7.1 The system displays error message as invalid selection

7.2 Go to step 6.2
7.3Use case ends
8 Post condition When there is schedule, the Students and/or advisor and also the Examiner
would get it.
Table3. 9:-use case descriptions for view schedule
1. Use Case Name View notice

2. Use case Id UC10
3. Description get notification from system
4. Actor Students
5. Precondition The Students must have full privilege
6. Basic course of 6.1 The user must open the system
action 6.2 The user select notice link
6.3 The system displays the notice form
6.4 The user view if there is new notice on the system
6.5 The system displays the information to the user
6.6 Use case ends

7. Alternative course The system verify information is not correctly
of action 7.1 The system displays error message as invalid selection
7.2 Go to step 4
7.3 Use case ends
8 Post condition When there is notification, the Students would get it.
Table3. 10:- use case descriptions for view notification
1.Use Case View result

Name
2.Use Case UC11
ID
3.Description View result of his/her project which is submitted
by advisor and examiners
4. Actor Student
5.Pre- Students must be login to view their results
Condition
Alternative 6.1 Students must be login to their page
course of 6.2 Students select view result link
action 6.3 The system displays the result page
6.3 Students can enter their ID and click on view
button
6.4 The system displays the result of students
6.5 Use case ends
Post 7.1 The system displays error message if you enter

condition incorrect ID
7.2 Go to step 6.3
7.3 Use case ends
Table3. 11:- use case descriptions for view result
1.Use Case Logout

Name
2.Use Case UC12
ID
3.Description To authenticate the user
4. Actor Department head, Advisor, Student and Examiner
5.Pre- The user is already login
Condition
Alternative 6.1.The user clicks the logout button
course of 6.2.The system then logs the user out
action 6.3.The system displays the login page
6.4.Use case ends
Post The user ends to login next time
condition
Table3. 12:- use case descriptions for logout
3.3 Sequence Diagram
The sequence diagram is used primarily to show the interactions between objects in the
sequential order that those interactions occur in our system. Most sequence diagrams will
communicate what messages are sent between a system's objects as well as the order in which
they occur. It shows the interaction between participating objects in a given use case. We see as
follows:
Figure 2:-Sequence Diagram for Login
Figure 3:-Sequence Diagram for Set Schedule
Figure 4:-Sequence Diagram For create account
Figure 5:-Sequence Diagram For Submit Result
Figure 6:-Sequence Diagram view result
Figure 7:- Sequence Diagram for Logout
Figure 8:- Sequence diagram for register project
Figure 9:-Class diagram for register
3.4 Class diagram

Class diagrams are used to describe the structure of the system. It describe the structure of
the system in terms of classes and objects. Classes are abstractions that specify the
attributes and behavior of a set of objects whereas object are entities that encapsulate state
3.4 Class diagram

Class diagrams are used to describe the structure of the system. It describe the structure of
the system in terms of classes and objects. Classes are abstractions that specify the
attributes and behavior of a set of objects whereas object are entities that encapsulate
stateand behavior. In the below figure the class diagram for the system shows the classes
with their potential attributes and methods.
Figure 10:-Class diagram
Reference
[1] https://www.su.edu.et/about-college-engineering-and-technology
[2] https://www.tutorialspoint.com/system_analysis_and_design/system_design.htm
[3] Modern system analysis and design third edition by Jeffery A.Hoffer, Joeyf.George, and
Joseph S.Valaclch (Show to design sequence diagram with example.)
4) Object-Oriented Software Development with UML, By Zhiming Liu,
5) The Unified Modeling Language User Guide - Second Edition,By Grady Book, James Rum
Baugh, Ivar Jacobson,
6) www.tutorialspoint.com/object_oreinted_analysis_design/oosad_functional _modeling.html
7) http://en.wikipedia.org/wiki/deployement_daigram

Group 3 Project Final 1-3 (Commented)

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

Group 3 Project Final 1-3 (Commented)

Uploaded by

Copyright:

Available Formats

Samara University

College of Engineering and Technology

Department of Computer Science

4 kalab Yibelital ………….0046/08

Advisor: Mr. Welday G. Samara, Ethiopia

1.1.1 Background about the Organization..............................................................................5

1.1.2 Introduction about the project.............................................................................................6

1.2 Statement of the Problem...........................................................................................................6

1.3.1 General objective................................................................................................................7

1.3.2 Specific Objective...............................................................................................................7

1.4 Scope of the Project and Limitation..........................................................................................7

1.5 Significance of the Project.........................................................................................................7

1.6 Methodology for the Project......................................................................................................8

1.6.1 Data Gathering Technique..................................................................................................8

1.6.2 Design Methodology..........................................................................................................8

Table of Content Page i

1.6.4 Implementation Methodology............................................................................................9

1.6.5 Testing Methodology........................................................................................................10

2.1 The over view of the existing system........................................................................................7

2.1.1 Major activities in the existing system...............................................................................7

2.1.2 Problem of the existing system...........................................................................................8

2.1.3 Weakness and strength of the existing system...................................................................8

2.1.4 Business rules of the system...............................................................................................8

2.2 Overview of the proposed system..............................................................................................9

2.2.1 Functional requirements of the proposed system...............................................................9

2.2.2 Non-functional requirements of the proposed system......................................................10

2.2.3 System requirements of the proposed system....................................................................11

2.4 Constraints and Assumptions..................................................................................................11

3.1 Use Case Specification............................................................................................................13

3.2 Use Case Diagram...................................................................................................................14

3.2.1 Actor Specification...........................................................................................................14

3.2.2 Use Case Description........................................................................................................16

3.3 Sequence Diagram...................................................................................................................26

3.4 Class diagram...........................................................................................................................31

Table of Content Page ii

Table of Content Page iii

Table of Content Page iv

Table of Content Page v

Table of Content Page vi

CSS ……………………………… Cascading style sheet

HTML …………………. ……………hyper Text Markup Language

OOSAD…………………………….object oriented system analysis and design

PHP ……………………………………..Hypertext preprocessor

SQL.………………………………….Structured Query Language

List of acronyms Page vii

The mission of College of Engineering and Technology is dedicated in producing

?? what is the space here.

1.1.2 Introduction about the project

1.2 Statement of the Problem

 It consumes time and resources.

1.3.2 Specific Objective

 To make easy and suitable user friendly system for users.

1.4 Scope of the Project and Limitation

1.5 Significance of the Project

1.6 Methodology for the Project

1.6.2 Design Methodology

1.6.3 Analysis methodology

1.6.4 Implementation Methodology

Activities Software Tools

Table 1 Software tools

Hard ware requirements

Name of hardware Model

Table 2:-Hardware tools