CHAPTER THREE
SYSTEM ANALYSIS AND DESIGN
3.1 Analysis of the Existing System
The existing project topic information management system is manual in Ignatius Ajuru University
of Education, Computer Science Department in particular. The project leader or guide manually
gives the student mission. Students complete the work done by the coordinator or guide and apply
manually, all work is manually done in this method, allowing more time to work in connection
with the project. The project coordinator or guide needs attention when students finish the job, so
it is hard for the project coordinator or guide to whom and when the student finished the research.
In the current framework, users cannot get the right details at the right time, and users cannot
easily handle project progress to achieve their principal objective.
3.1.1 Architecture of the Existing System
Fig. 3.1: Architecture of the Existing System
3.1.2 Constraints of the Existing System
a. Inability to achieve student attendance status quickly.
b. Modify student/staff information is a broad process which can lead to confusion and
mistakes.
c. Incompatibility and inaccuracy in data maintenance
d. It is very difficult to understand system by a layman and, if a naive person is to be used
by the student information system, adequate instruction must be provided on the
operation of the system and the overall system becomes extremely inefficient.
e. The final process takes a great deal of time.
f. The right information at the right time is not recovered.
g. The rest of the team cannot see any changes to the data by team members or the Project
Leader or Guide immediately.
3.2 Analysis of the Proposed System
The proposed system is an Online Project Topic and Author Information Management System. It
is a system based application. The system helps in seeking opinions from users. In this proposed
framework we will develop a system to manage the project that recognizes all work done by the
organizer or guide of the project. The coordinator updates the project details, views a student and
views the progress chart of the student's work, develops a progress chart using WBS (Work
Breakdown Structure). Students have been able to obtain updates on the work details and
complete this work at times and report to the project management system making the details to
be reliable and data replication will not occur.
3.2.1 Architecture of the Proposed System
Fig 3.2: Architecture of the Proposed System
3.2.2 Justification of the Proposed System
The new system is designed to solve problems affecting the manual system in use. It is designed
to be used online thereby relieving both the students and staff from much stress as experienced in
the manual system.
This system will do the analyzing and storing of information either automatically or interactively
as it is online (i.e. having access to the Internet).
The following are some of the interfaces that is been used and their functionality and importance.
a. Password Recovery Page: This page would be used by the student in- case she/he
forgets his/her password. The new password would be sent to the email address
provided.
b. Home Page: This is the first page the user/visitor sees when visits the site.
c. Admin Setup Page: This page is used strictly by the administrator to set up his/her
parameters so as to enable him/her have total control over the system.
d. Admin Search Page: The admin uses this page to search for student details which
he/she wants to edit, delete or blacklist.
e. Database View: This is the view of how the database looks like. This view is created
with PhpmyadminPanel.
3.3 Method Adopted in the Proposed System
The design methodology adopted in implementing the proposed system is an incremental
development model. An incremental model enables development of initial implementation,
allowing user feedback and evolving it through several versions until a final version of the system
has been developed. Use case diagram, activity diagram, and database design were adopted as
system designs.
3.4 Design of the proposed System
The system mainly contains several modules which includes:
Login:
The main index of the application is login page where we need to provide credentials such as ID,
Password and type of login (Coordinator / Supervisor / Student).
Once inputs are authenticated, the user will be redirected to the dashboard page from where the
header menu options will be available to navigate to the required page.
Coordinator Login:
Coordinator login is handled by a single person who is the top level management of all logins
Add Student:
From this screen, Coordinator can able to create new student by providing the details of ID,
Password, Name, etc.
Search Student:
Coordinator can also able to view the details of specific student by choosing the student ID from
the list in dropdown box.
Add Supervisor:
The next menu option for the coordinator is to create supervisor by filling out the form.
Search Supervisor:
This page consists of searching the existing supervisor to check and update their details by
Supervisor ID.
Share Document:
The screen has the option to upload general / Project related documents to share with students
and can be available in the respective student's login.
Allocate:
To allocate the supervisor for student projects this screen helps to choose the user to assign and
the assigned students can be listed in supervisor’s login
Reviews:
Reviews table contains the details of upcoming and completed project reviews which were
created by the supervisors.
3.4.1 Input Design of the Proposed System
The input to this system consists of the various forms through information inputted or supplied to
the system, which includes the login interface, the password recovery interface, the admin set up
interface, the admin search interface, interface where students can input the opinion regarding
voting and other matters relating academics.
3.4.2 Output Design of the Proposed System
After the student must have supplied the information required by the system, the output produced
by the system includes information put together display, which is the career that matches the
information provided by the student.
3.4.3 Process Design of the Proposed System
Based on the information collected from the students, an analysis is carried out.
Fig 3.4: Process Design of the Proposed System
3.5 Database Design
A database is a gathering of data that is sorted out so it can without much of a stretch be
accessed, managed, and updated.
Student’s Information Table
Table 3.1 displays the specification of the information in the individual table
Table 3.1: individual information table
Field Data Type Null Key
Name Varchar NO
Title Varchar NO
Username Varchar NO YES
Dob Date NO
Location Varchar NO
Personal_information Text NO
Video Varchar NO
Job_category Varchar NO
Skills Varchar NO
Number Varchar NO
Date_created Timestamp NO
Date_modified Timestamp NO
School Information Table
Table 3.2 displays the specification of the information in the company table
Table 3.2 Company Information Table
Field Data Type Null Key
Email Varchar NO YES
Company_name Varchar NO
Brief Text NO
Address Varchar NO
State Varchar NO
Country Varchar NO
Number Varchar NO
Logo Varchar NO
Date_modified Timestamp NO
Date_created Timestamp NO
Topic Scheduling Table
Table 3.3 displays the specification of the information in the job posting table
Table 3.3: Job posting table
Field Data Type Null Key
Student_id Int NO YES
Email Varchar NO
Title Varchar NO
Region Varchar NO
Location Varchar NO
Job_type Varchar NO
Job_category Varchar NO
Description Text NO
Job_url Varchar NO
Company_name Varchar NO
Logo Varchar NO
Amount Varchar NO
Slogan Varchar NO
Date_modified Timestamp NO
Date_created Timestamp NO
Fig 3.5: Schemas of the Proposed System
3.6 Security Design of the Proposed System
The proposed system is open to all the students that want to vote but it has some security features
such Administrator ID and password. This helps the system to restrict access to unauthorized
users who may want to manipulate the system to their advantage. Fig. 3.5 below shows security
design;
Fig. 3.5: Security Design