Project Title: Student placement system according to new police

Names of project developer:

1, Zinaye Teshome

2, Yerosan Tafesse

Wachemo University

College of Engineering and Technology

Department of Software Engineering

Submitted to: Mesay A.

19 September
2022

Hossana, Ethiopia

1|Page
Table of Contents

CHAPTER ONE

1.1 Introduction…………………………………………………………………………………5

1.2 Background………………………………………………………………………………….5

1.3 Organizational Structure………….……………………………………………………6

1.4 Literature Review………………………………………………………………………….7

1.5 Statement of the Problem………………………………………………………………9

1.6 Objective of the project………………………………………………………………….9

1.6.1 General Objective…………………….……………………………………..………9

1.6.2 Specific Objective………………………………….…………………………………9

1.7 Feasibility of the Project………………………………………………………………….10

1.7.1 Technical Feasibility……………………………………………….………………..10

1.7.2 Operational Feasibility….………………………………………………………….12

1.7.3 Economical Feasibility…….…………….…………………………………………..11

1.7.3.1 Tangible……………………………………………….………………….…………….11

1.7.3.2 Intangible ………………………………………………………………………………11

1.8 Scope and Limitation…………………………………………….…………………………..12

2|Page
1.9 Methodology of the Project……………………………………………………………….13

1.9.1 Software Requirement Engineering Process Mod……..………….………13

1.9.2 Software Analysis and Design d…………………..………………………….…….14

1.9.3 Requirement collection methods………………….……………………………….14

1.9.4 Testing Method……………………………………………………………………………….15

1.9.5 Coding method…………………………………….………………………………………….16

1.10 Significance of the project……………………………………………………………………18

1.11 Team Composition of the project…………………………………………………………18

1.12 Project Schedule and Budget………………………………………………………………..19

CHAPTER TWO

2.1 Introduction…………………………………………………………………………………..…………22

2.2 Major function of existing system……………………………………………………………..22

2.3 Document used in existing system…………………………………………………………….23

2.4 User of current system……………………………………………………………………………..29

2.5 Drawback of existing system…………………………………………………………………....29

2.6 Business rules of domain………………………………………………………………………….29

2.7 Alternative solution………………………………………………………………………………….30

CHAPTER THREE

3|Page
3.1 Introduction…………………………………………………………………………………………….31

3.2 Functional Requirements………………………………………………………………………….31

3.3 Non-functional Requirements…………………………………………………………………33

3.3.1 User Interface………………………………………………………………………………………33

3.3.2 Performance…………………………………………………………………………………..34

3.3.3 Security………………………………………………………………………………………….34

3.3.4 Hardware Requirements…………………………………………………………………35

3.3.5 Error Handling…………………………………………………………………………………35

3.3.6 Documentation Requirements…………………………………………………………35

3.4 System Models……………………………………………………………………………………35

3.4.1 Use Case Model…………………………………………………………………………………35

3.4.1.1 Identify Candidate Actors………………………………………………………………36

3.4.1.2 Use Case Diagram………………………………………………………………………….37

3.5 Requirements Analysis………………………………………………………………………..39

3.5.1 Activity Diagram………………………………………………………………………………39

3.5.2 Sequence Diagram………………………………………………………………………….40

Reference……………………………………………………………………………………………..42

4|Page
1.1 Introduction

Currently in wachemo university students select departments according to their choice

and their result of the entrance exam and CGP of first semester. After the first semester,
students have to choose departments by ranking all departments and all disciplines
available on a piece of paper, which is obviously a manual process. In fact, students have
the ability to view their placement online but the site which is currently available is not
working efficiently and it is unsecure due to these causes many complaints are raised.
Generally, in the proposed system we would like to solve all the problems and better
educational placement. In the proposed system we change from manual to
computerized form. wachemo university students choice and placement their
department according to their choice and result of entrance exam and CGPA of first
semester online ways

1.2 Background
Department selection is one of major task for the campus. Our project is coming up with
the idea of department selection, because we found it sensitive area to deal with. Since
students finish their first semester and they want to know how this department look
like. This project takes a huge place. Firstly, it keeps students from random choice but in
Reality, department selection is totally automated for the lack of fairness and quality.
Since the major objective of department placement is to identify qualified professionals
before they complete their education. This project is going to make an impact on the
minds of the students by providing different department information and profile on the
site. By implementing all this it will provide a way of widening students’ awareness
about universities and fully automates the department selection and placement system.

5|Page
1.3 Organizational Structure

An organizational structure is a system that outlines how certain activities are directed
in order to achieve the goals of an organization. These activities can include rules, roles,
and responsibilities.

6|Page
1.4 Literature Review

 Even though the web has enabled us to get information easily and it enables
people in the world to exchange information as if it is a small village managing
such information on the net in a way that is understandable and easily accessible
to all is a challenging task.
 For a service provider speed is one of the main factors that determine its
relationship with its clients. When we consider specifically the speed of a service
provider website, even though it provides all the necessary information to its
clients if there is problem on its Speed it will be one of the root causes for its dark
image. “There’s a time bomb on the web: user patience. It starts ticking each
time someone opens one of your pages. You only have a few seconds to get
Compelling content onto the screen. Fail and you can kiss your customers and
profits goodbye. You can't count on fast connections either. Most of your
customers are still sucking content through a 56K straw. You have to serve up
greased Lightning or they'll bail. ”
 One of the main challenges of web-based applications is the loading speed or the
Performance of its pages. “It is estimated that if a page doesn't load within 5-8
seconds you will lose 1/3 of your visitors. So if your website speed is slower than
that perhaps you should revise your design, site structure or just move to a faster
server.” So for web application developers it is a must to identify and understand
the root causes Of performance problems of web pages before going deep into
development.

7|Page
What affects site loading speed of a web page?

 web server speed (server resources, Internet connection speed)

 database usage (none, one or many)
 HTML code page size (20kb or larger)
 CSS file size (5kb or larger)
 Total image size (50kb or larger)
 Script usage (none, 10kb or larger)
 Amount of file requests (style sheets, Server Side Includes, images,
scripts, etc.)

According to [7] the solutions for these problems are listed as follows:

1) Web server speed

2) Databases

3) HTML code size

4) CSS file size

5) Total image size

6) Script files size

7) HTTP files requests

8|Page
1.5 Statement of the Problem

The current or existing system, which includes both manual and automated system, for
university selection and placement has many major problems. We realize the following
problems as indication to the problems of the existing system.
 In case of choosing each student will use papers to select universities that did not
include full information about the universities. Therefore, students will be
subjected to unwanted choices due to the inaccurate information.
 After selection there may be errors like the department the students choose may
be disordered without their knowledge, this is highly offensive for the students
when they check their placement.
 There is repetition of work like making students to select again if the order of
department is not correct or the filled papers are lost, it increases workload for
the agency as well as for the students.
 Students failed to change the department choice once they chose because the
authorized party to change their selection will not work after some specific time.

1.6 Objective of the project

1.6.1 General Objective

The main objective of this project is to develop reliable, preformat and fairer web-based
department allotment system for students by completely computerizing and improving
the existing system.

1.6.2 Specific Objective

To attain general objectives the following are specific objective.

 Studying the existing system.

9|Page
  Finding exact department information from the official website of each
department and other sources.
 Designing a user interface that is usable for most of the users which are in
fact from different areas of the country having different background.
 Designing a database which has the capability of holding this nationwide
student’s information and integrating with the existing one.
 To develop a system that performs department student placement based
on the placement criteria of the Ministry.
 To make student data available on the web for the respective colleges and
department so that they can access and use that information directly with
their web site by avoiding repeated data entry.

1.7 Feasibility of the Project

It is essential to evaluate the cost and benefits of the new system. On the basis of the
feasibility study decision is taken on whether to proceed or to cancel the project.

Need of the feasibility study:

 It determines the potential of the existing system.

 It used to determine/finds out the problem of the existing system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing system.

1.7.1 Technical Feasibility

Our group is a composition of dedicated and skilled full students who are well aware
how to analyse, design and develop the proposed system. Every group member has
their own responsibilities and task to perform and since the team is cooperative and
skilled, we can say this project is technically feasible.

10 | P a g e
1.7.2 Operational Feasibility
The system will bring phenomenon change on remedying the problems that we have
discussed so far. Most students in Wachemo University do not have information about
department and have a need to access the selection system by themselves so our
system will provide that important information about department and give capabilities
to select and check the department by the students themselves. Therefore, the system
is operationally feasible.

1.7.3 Economical Feasibility

The system to be developed is economically feasible and the benefit is reducing the
cost. Since this project will computerize the existing system, the reduction of cost for
materials used in manual operation becomes beneficiary to the organizations.

Generally, the system that we will develop has a number of tangible and intangible
benefits.

1.7.3.1 Tangible
 Cost reduction.
 Error reduction.
 Increase speed of activities and minimize workload.

1.7.3.2 Intangible
 Reduce resource consumptions
 Increase security
 Increase employee satisfaction.
 Increase management flexibility

11 | P a g e
1.8 Scope and Limitation

1.8.1 The scope of the project

Currently the department placement for Wachemo University performs its basic tasks
not fully automated. The scope of this project is to develop and implement a new web-
based department allotment system for Wachemo University, which will avoid the
problems associated with the manual processing and improve the limitations on the
currently automated part.

The followings are the scopes of our project:

 The system is functional for an administrator, stream directors and

students who have taken the wachemo University
 The system permits students and directors to be registered into the
system by filling the form for registration.
 The system allows students and directors to login into the system by using
their username and password.
 The system displays students’ results.
 It allows students to acquire information about colleges and disciplines of
their interest.
 It enables students to select and choose department.
 It allows the students to know the department where they are allotted
with helpful information.
 It enables each department to give their information to the directors of
the stream.

12 | P a g e
  The system enables the administrator to create and give accounts for
directors of the stream.
 The system enables the administrator to manage user accounts.
 The system allows the administrator activation and deactivation of the
registration and login period in order to restrict time schedule so that we
can save the system from getting busy.

1.8.2 The limitation of the project:

 The system does not provide full functionality in the condition of no

internet connection.
 The system doesn’t provide services for blind users.
 It heavily depends on the information provided by all departments.

1.9 Methodology of the Project

1.9.1 Software Requirement Engineering Process Model

In our project we use the agile system model. Agile model believes that every project
needs to be handled differently and the existing methods need to be tailored to best
suit the project requirements. In Agile, the tasks are divided to time boxes (small time
frames) to deliver specific features for a release.
Agile model is:-

 Promotes teamwork and cross training.

 Functionality can be developed rapidly and demonstrated.
 Resource requirements are minimums.
 Suitable for fixed or changing requirement.
 Easy to manage.
 Gives flexibility to developers.
13 | P a g e
1.9.2 Software Analysis and Design Method
In our project we will use object-oriented software engineering methodology
(approaches) to develop the system. Because it is a popular technical approach for
analysing, designing an application system, or business by applying the object-oriented
paradigm and visual modelling throughout the development life cycle. Object oriented
system analysis and design is selected since it has so many advantages and which can
make the system more effective.

Object oriented system analysis and design used to:-

 To simplify the design and implementation of complex program.

 We can inherit properties of the class that are defined in the super class.
 We can reuse methods for avoiding redundancy.
 Increased consistency among analysis, design and programming activities.
 The data and functions are encapsulated in the objects that help us for easily
debugging purpose.

1.9.3 Requirement collection methods

Data collection is the process of gathering and measuring information on targeted
variables in an established system, which then enables one to answer relevant questions
and evaluate outcomes. Data collection is a research component in all study fields.

Observation:
We observe the system: -

 We observe what limitations are there in the current website.

 We observe different links are difficult to open and still did not work correctly.
 We observe that the site really needed to be managed and modified.
 We observe data are not updated frequently on the site.

14 | P a g e
Interview:

 We have interviewed senior and fresh students of our university for their
comment on the problems they faced during department placement.
 We found almost all of them wish that they knew all department information
before they join university and that they select and check the placement by
themselves.
 We found out that they have experienced many problems during their
department selection and placement process

Document analysis:

 Reading the document available in the library.

 We will read different books from online sources to identify what we will do in
our project.
 Read and understand the sample document that can support us.

1.9.4 Testing Method

Unit testing:

 Our group members testing each functional requirement are done correctly.

 We examine our proposed system step by step.

Integration testing:

 We examine our system modules are integrated each other.

15 | P a g e
  We have examined how the different procedures work together to achieve
the goal of the subsystem.

System testing:

 We have examined how the whole subsystems came together to achieve the
desired goal (user’s requirements of the system).

 The goals of system testing are to detect the problem that can only be
exposed by testing the entire integrated system or some major part of it.

User acceptance testing:

 Where the system is test for acceptability. The processes whereby actual users are
test a completed system, so in our case our system will be tested by academic staff
members for acceptability.

1.9.5 Coding method

1.9.5.1 Software development tools

The following requirement software tools are used to implement our project work

Front end: HTML, CSS, JavaScript

1. HTML: HTML is used to create and save web document. E.g., Notepad/Notepad+
+,
1. Sublime.
2. CSS: (Cascading Style Sheets) Create attractive Layout
3. JavaScript: it is a programming language, commonly use with web browsers.

16 | P a g e
Browser: -

 IE (Internet Explorer)
 Mozilla Firefox
 Opera &
 Google Chrome

Back end: PHP, MySQL

1. PHP/XAMPP: server side scripting Hypertext Pre-processor (PHP) is a

technology that allows software developers to create dynamically generated web
pages, in HTML, XML, or other document types, as per client request. PHP is
open source software.

2. MYSQL/PHP MYAdmin/XAMPP is a database server, widely used for accessing

Querying, updating, and managing data in databases

1.9.5.2 Documentation and modelling tools or software tools

Modelling tool

Visual paradigm: for designing UML diagrams.

Documentation tool

 Text editor: a software tool sublime text, notepad++ for typing the code.
 Microsoft word 2016: to prepare documentation
 MS PowerPoint 2016/MS Office: for preparation of power point

Deployment tools

 Lap top computer

 Desktop compute

17 | P a g e
1.10 Significance of the project

Computer based information system are designed to improve existing system. Whatever
the information, Placement Officer pass it to the student via E-mail notification. It has
user friendly interface having quick authenticated access to documents. It provides the
facility of maintaining the details of the students. It will reduce the paper work and
utilize the maximum capabilities of the Setup and organization as well as it will save time
and money which are spending in making reports and collecting data. It can be accessed
throughout the organization with proper login provided. This system can be used as an
application for college to manage the student information with regards to placement.

1.11 Team Composition of the project

Team composition table:

No Name Id Email Task

1 Yerosan 12D0823 Alsan12@gmail.com  Planning,

Tafesse gathering
requirement and
2 Zinaye 12D0945 bobzinaye11@gmail.com
implementation
Teshome
of proposed
system.
 Designing and
analysis
requirement
 Testing,
18 | P a g e
documentation
and deployment
1.12 Project Schedule and Budget

1.12.1 Project Budget

The following is budget of project

19 | P a g e
 NO Item need Quantity Cost Total price
for our team

1 Laptop 2 2*20,000 40,000 birr

computer

2 Flash disk 8 1 1*300 300 birr

GB

3 Pen and 100 birr

paper

4 Other 3000 birr

withdraw

Total birr 43,400 birr

1.12.2 Project Schedule

The following is schedule of project

20 | P a g e
 NO Task Duration Starting Ending

1 Planning 3 days 20/8/2014 21/8/2014 E.C

E.C

2 Gathering data 4 days 22/8/2014 28/8/2014 E.C

and collection E.C

3 Analysis 3 days 29/8/2014 4/9/2014 E.C

E.C

4 Designing 4 days 5/9/2014 7/9/2014 E.C

E.C

5 Implementation 2 days 8/9/2014 10/9/2014 E.C

E.C

6 Integration 1 days 11/9/2014 12/9/2014 E.C

E.C

7 Testing 1 days 12/9/2014 14/9/2014 E.C

E.C

8 Documentation 2 days 15/9/2014 16/9/2014 E.C

E.C

21 | P a g e
9 Deployment 2 days 17/9/2014 18/9/2014 E.C
E.C
 CHAPTER TWO

DESCRIPTION OF EXISTING SYSTEM

2.1 Introduction

The Existing system is a computerized system but which is maintained at individual

database i.e., in excel sheets; it is a time delay process. And maintaining all the records
in Excel sheets is difficult. The management and all the departments that have been
carrying out this job using manually makes the job more complicated and tedious most
of the times. So, the best way is computerize computerization of the current
environment. For example, in the earlier system placement officer has to collect student
details for placements. Approving those student details takes lot of time. Placement
officer and students have to consult each other directly if any information is needed. If
any new student come for placements, placement officer and his staff has to search the
student details and they have to find the eligible candidates for that particular student
placement. Here searching for eligible candidates takes lots of time. And sometimes
some candidates’ details may be missed. By this process the student can view his details
and if there is any correction to make in data, the student should send request to the
placement officer, since the student cannot change the details.

2.2 Major function of existing system

One of the major functions of existing system is:

 Place student to their college.

 Place student to their department.
 Transfer students from natural stream to social stream.
 Transfer students from one college to another.
 Transfer students from department to department.

22 | P a g e
2.3 Document used in existing system

The existing system uses forms and number that are used to perform different
operations such as placement forms, department transfer form and use number to
select department. The documents used in the system are shown as follows.

School of Law form

23 | P a g e
 Social science college form

24 | P a g e
 Business and Economics College form

25 | P a g e
 Engineering and Technology form

26 | P a g e
Health department form

27 | P a g e
College form

28 | P a g e
2.4 User of current system

 Registrar: register student to their stream.

 College dean: place student to their department according to their choice and grade.
 Coordinator: place student to department according their choice.
 Student: fill the form to select college and department.

2.5 drawback of existing system

The drawback of the student placement system for Wachemo University is that the
process is done manually due to absence of automated system. So the existing system
has the following draw backs:

 It takes so much time for a placement officer to collect students’ details and
approving the details provided by them.
 Poor communication between students and placement officer, so here intimating
about new placements is a hard task.
 Student may not know about department details. Here also poor communication
provide a problem
 Candidate may not get required information if concerned TPO is not at the desk.
 The system is not an online system.

2.6 Business rules of domain

Business rules of existing system:

BR1. Student should be placed to Wachemo University.

BR2. Student should be registered to their stream.

BR3. Student should have identification number/ID.

29 | P a g e
2.7 Alternative solution

There are different alternative systems of a possible solution for the student placement
system such as:

 Web-based student placement system

 Android-based student placement system
 SMS based student placement system

We select web based online student placement system. We have reasons for selecting
web based student placement system for Wachemo University. Although the web based
system can be functional to the users with internet connection and use personal
computers to access the system without encountering any difficulty.

The SMS based system cannot be relevant for the student placement system, because
this system involves sending letters which contain forms to be filled by different user.

The android based system has its own benefits and drawbacks, for example, developing
the system is very effective by addressing mobile phone users, but the system becomes
complex for the users and would be difficult to retrieve data from the system through
mobile easily than using computers. But if we use Web-based system, it is fastest to
retrieve data and becomes more relevant for the following reasons:

 Easily Accessible
 Easy to retrieve data
 Cross platform usability
 Cost effective

CHAPTER 3
30 | P a g e
 PROPOSED SYSTEM

3.1 Introduction

System analysis is an essential activity that must be taken in any project in order to have
a clear idea of a proposed system. In other word, it means the process of analysing a
task to develop a conceptual model that can be used to complete our task. This implies
finding and describing the object or the problem domain of the system.

This chapter describes an overall description of the project which is mainly to the
constraint of the system, functional and non-functional requirements will be included.
Then use case modelling with their description and the development of activity
diagrams and sequence diagrams are performed. Lastly, Requirement validation and
verification will be explained

The analysis phase defines the requirement of the system independent of how this
requirement will be accomplished. This phase defines the problem that we will try to
solve and explores about the new system of our project ideally the chapter states in a
clear and precise fashion what is to be built.

We used an object oriented system development methodology which incorporates two

principal phases. These principal phases are Object-Oriented Analysis and Object-
oriented Design. In this chapter, what the team will do is the object oriented System
analysis (OOSA).

3.2 Functional requirements

The functional requirement of the student placement system is concerned with the
functionality that the system should provide to users. This functional requirement
specification for the student placement system helps the system to perform correctly

31 | P a g e
and reliably its intended functionality and most of them have a very good idea of the
changes they would like to see. We as a requirement engineers used interviews because
it is easily capable of collecting wide range of information from a small numbers of
respondents or stake holders.

The developed system is expected to provide the following functionalities:

1.1, the system should allow the student login with ID number and last name.

1.2, the system should allow the admin and coordinator login with user name and
password.

1.3, the system should enable the user’s logout.

1.4, the system should allow the student fill placement form.

1.5, the system should enable the student viewed placed department.

1.6, the system should generate placement report.

1.7, the system should enable admin to register student with their grade.

1.8, the system should notify the student register successfully or not.

1.9, the system should allow the coordinator to view student GPA to place
department.

1.10, the system should allow the coordinator to view student filled placement
form.

1.11, the system shall enable the coordinator to place student in their
department according in their choice and grade.

1.12, the system shall enable the Admin to delete old account

32 | P a g e
 1.13, the system should enable user to create new account.

1.14, the system should register student information with grade to place
department.

1.15, the system should display student’s placement and GPA.

3.3 Non-Functional Requirements

Non-functional requirements define system attributes such as security, reliability,

performance, maintainability, scalability, and usability. They serve as constraints or
restrictions on the design of the system across the different backlogs. This constraints
does not have direct impact on the functionality of the system but, for example if the
user interface is not attractive and doesn’t provide options to navigate easily, users will
be frustrated to do their jobs using this system, which may lead to poor quality service
delivery. In case of performance if the system does not respond within a reasonable
response time and provide accurate results, users will not have confidence on their jobs.
In addition if the system is not well secured, users may not be willing and confident to
put their information into the system and they will not trust the service provided by the
system.

3.3.1 User interface

The user interface will be simple and consistent, using terminology commonly
understood by the intended users of the system.

 The user interface should be user friendly and attractive

 The navigation facility must be flexible
 Interaction of users with the system should be through graphical user
interface

33 | P a g e
  The user interface should be consistent in terms of format of page,
background colour ,font, and size

3.3.2 Performance

 For login in to the system password and user name should be matched to the
password and name respectively.
 Since the system is web based the performance of the system can be directly
affected by the quality of the hardware, robustness of the software and
network traffic. So the response time should be minimal.
 Reasonable number of concurrent access should be granted.
 There shall take less time in various ways of retrieving and processing data.
 The data system shall load as quickly as comparable productivity tools on
whatever environment it is running in.

3.3.3 Security

 The system shall provide high level of security by blocking unauthorized user
to view secured system page.
 Student placement system will follow best practices for authentication.
Authentication addresses security requirements to ensure those using system
are who they say they are. This is of greatest concern when data are being
changed or updated. This is primarily done through user name and
passwords.
 Confidentiality security requirements describe the need to protect the data
appropriately. IMS will use the user classes to define boundaries of
information sharing to ensure confidentiality as appropriate. Any data that
should be viewed by a restricted audience must be protected with
appropriate security features.

34 | P a g e
  The system should allow the student login with ID number as password and
last name as user name.

3.3.4 Hardware Requirements

Hardware consideration refers to the physical parts of a computer and related devices.

 Processor: Minimum 1 GHz; Recommended 2GHz or more.

 Hard Drive: Minimum 32 GB; Recommended 64 GB or more.
 Ethernet connection (LAN) OR a wireless adapter (Wi-Fi)
 Memory (RAM): Minimum 1 GB; Recommended 4 GB or above.

3.3.5 Error Handling

 The system must be able to validate all input to their assigned value and
display informative message to the user
 Well-structured client side validation should be implemented for ease of
functionality

3.3.6 Documentation Requirements

 The overall development process should be documented including the

requirement analysis, system design and implementation details

3.4 System Models

3.4.1 Use Case Model

In its simplest form, a use case can be described as a specific way of using the system
from a user’s (actor’s) perspective. Use cases provide a means to capture system
requirements, communicate with the end users and domain experts, and test the

35 | P a g e
system. Use cases are best discovered by examining the actors and defining what the
actor will be able to do with the system.

The following use cases have been identified from the system specification

UC-01:- Login
UC-02:- Register
UC-03:-fill placement form
UC-04:- Place student
UC-05:- delete placement
UC-06:-view placement
UC-07:- manage account
UC-08:- manage placement
UC-09:- change password
UC-010:- modify account
UC-011:- generate placement report
UC-012:- delete account
UC-013:-view student placement filled form
UC-014:- Logout

3.4.1.1. Identify Candidate Actors

Candidate actors include groups of users who will require help from the system to
perform their tasks and run the system to perform their tasks and run the system’s
primary or secondary functions, as well as external hardware, software, and other
systems. Define each actor by naming it and writing a brief description. Include the
actor’s area of responsibility and the goals that the actor will attempt to accomplish
when attempt to accomplish when using the system. Eliminate actors candidate who do
not have any goals

36 | P a g e
The identified actors that will be participating in the system are:

 Coordinator: - a person, who is responsible for creating account, modifies

account, view placement and communicate with admin and students
 Admin: - a person who is responsible for administer system, Create account,
Modify account, view placement, add placement, delete placement and
communicate with other actors
 Student: - a person who is responsible for creates account, change password,
view placement and communicate with Coordinator and admin.

3.4.1.2. Use Case Diagram

Use case diagrams graphically depict system behaviour (use cases). These diagrams
present a high level view of how the system is used as viewed from an outsider’s
(actor’s) perspective. From the identified use cases and actors the use case diagram of
the system is shown in Fig 3.1.

Fig 4.1 Use Case diagram of student placement processing & retrieval system

37 | P a g e
As we can see from the use case diagram data clerk of the Ministry can register
students’ personal information; register student’s score, chosen field of study and
chosen institution; process placement, and export the processed data to XML. A student
is another user of the system and he/she can see his/her placement information.
Representative of a school can get from the system placement report of all students
from that school and similarly personnel of the respective higher institution can get list
of newly assigned student together with students’ personal data from the system.

3.5. Requirement Analysis

To produce a model of the system which is correct, complete and consistent we need to
construct .The analysis model which focuses on structuring and formalizing the
requirements of the system.

3.5.1. Activity Diagram

The activity diagram is another important diagram in UML to describe the dynamic
aspect of the system. It a follow chart to represent the flow of information one activity
to another activity but it is not exactly a flow chart as they have some additional
capabilities. These additional capabilities include branching, parallel flow, etc. An activity
represents an operation on some class in the system that results in a change the state of
the system. Typically, activity diagrams are used to model workflow or business
processes and internal operation. Because an activity diagram is a special kind of state
chart diagram, it uses some of the same modelling conventions. These additional
capabilities include branching, parallel flow, etc.

38 | P a g e
Activity diagram for login

Figure 3.2 Activity diagram for login

39 | P a g e
Activity diagram for placement

Figure 3.3 Activity diagram for login

3.5.2. Sequence Diagram

A sequence diagram is an interaction diagram that shows how objects operate with one
another and in what order. It is a construct of a message sequence chart. A sequence
diagram shows object interactions arranged in time sequence. It depicts the objects and
classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario.

40 | P a g e
Sequence diagram for student login

Figure 3.4 Sequence diagram for login

Sequence diagram for student logout

Figure 3.5 Sequence diagram for student logout

41 | P a g e
Reference

1. George Koch, Kevin Loney, “Oracle – The Complete Reference”, Tata McGraw Hill,

2. Herbert Schildt& Patrick Naughton, “Java2 Complete Reference”, Tmh 3/e, 1999.

3. James Jawroski, “Mastering Java Script”, Tmh 3/e, 2000.

4. D.J. Abadi, “Data Management: Limitations and Opportunities,” IEEE Data Eng.

Bull., vol. 32, no. 1, pp. 3-12, Mar. 2009.

5. Roger S Pressman, “Software Engineering – A Practitioner’s approach” McGraw –

Hill International Editions, Fifth Edition, 2001.

6. Roger S Pressman, “Software Engineering – A Practitioner’s approach” McGraw –

Hill International Editions, Fifth Edition, 2001.

7. Henry F Korth, S. Sudharshan, “Database System Concepts” McGraw – Hill

International Editions, Fourth Edition, 2002.

8. George Koch, Kevin Loney, “Oracle – The Complete Reference”, Tata McGraw Hill,

Third Edition, 2001.

9. Herbert Schildt& Patrick Naughton, “Java2 Complete Reference”, Tmh 3/e, 1999.

10. James Jawroski, “Mastering Java Script”, Tmh 3/e, 2000.

11. D.J. Abadi, “Data Management : Limitations and Opportunities,” IEEE Data Eng.

42 | P a g e