DESIGN AND IMPLEMENTATION OF A MOBILE

APPLICATION

STUDENT ACTIVITIES PLANNER

BY

ADEDARA ADEGOKE OMOLAYO

12CG014259

A PROJECT SUBMITTED TO THE DEPARTMENT OF COMPUTER

AND INFORMATION SCIENCES, COLLEGE OF SCIENCE AND
TECHNOLOGY, COVENANT UNIVERSITY, OTA, OGUN STATE.

IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE

AWARD OF THE BACHELOR OF SCIENCE (HONOURS) DEGREE IN
COMPUTER SCIENCE

APRIL 2016

1
 CERTIFICATION

It is hereby certified that this project work titled, Development of a Mobile Application
Student Activities Planner written by Adedara Adegoke Omolayo was supervised by me and
submitted to the Department of Computer and Information Sciences, College of Science and
Technology, Covenant University, Ota.

1. Supervisor:

Dr Adewole Adewumi ………………………………………...

Signature and Date

2. Head of Department:

Professor Osamor V.C ………………………………………...

Signature and Date

2
 DEDICATION

This project is give all out thankfulness to God Almighty for His limitless effortlessness and
shrewdness upon my life, and for the quality and learning he presented to my life all through my
stay in Covenant University to guarantee the effective culmination of my B.Sc. program.

3
 ACKNOWLEDGEMENT

This undertaking work won't be finished today without some significant individuals, hence I
need to value my parents Mr. & Mrs. Kehinde Adedara for their nonstop backing and
consolation, additionally my supervisor Dr. Adewole Adewumi for his help and supervision in
accomplishing this project. I would also like to acknowledge my project partners Omoloja
Ayodeji & Obinnaya Loveth, for their efforts and commitment to bringing the project to
fruition.

4
 TABLE OF CONTENTS

CERTIFICATION-------------------------------------------------------------------------------------------------------- 2

DEDICATION----------------------------------------------------------------------------------------------------------- 3

ACKNOWLEDGEMENT----------------------------------------------------------------------------------------------- 4

CHAPTER ONE------------------------------------------------------------------------------------------------------- 10
1.1 BACKGROUND---------------------------------------------------------------------------------------- 10
1.2 STATEMENT OF THE PROBLEM----------------------------------------------------------------11
1.3 AIM AND OBJECTIVES---------------------------------------------------------------------------------12
METHODOLOGY---------------------------------------------------------------------------------------------- 12
1.5 SIGNIFICANCE OF THE STUDY---------------------------------------------------------------------14
1.6 PROJECT OUTLINE-------------------------------------------------------------------------------------- 14

CHAPTER TWO------------------------------------------------------------------------------------------------------- 15
2.1 INTRODUCTION-------------------------------------------------------------------------------------- 15
2.2 REVIEW OF EXISTING SYSTEMS--------------------------------------------------------------15
2.2.1 MY STUDY LIFE---------------------------------------------------------------------------------------- 15
2.2.2 MY HOMEWORK STUDENT PLANNER--------------------------------------------------------17
2.2.3 WEB BASED TIME SCHEDULE SYSTEM FOR MULTIPLE LMSS ON THE
SSO/PORTAL ENVIRONMENT.---------------------------------------------------------------------------- 17
FIGURE 2.4: DATA FLOW AND SSO CONNECTIONS BETWEEN THE TIME SCHEDULE SYSTEM ON
UNIVERSITY PORTAL, LMSS AND SIS------------------------------------------------------------------------19
2.2.4 STUDENT ORGANIZER------------------------------------------------------------------------------19
2.2.5 TIMETABLE---------------------------------------------------------------------------------------------- 20
2.3 COVENANT UNIVERSITY TIME TABLE SCHEDULING SYSTEM----------------------21
2.4 CONCLUSION---------------------------------------------------------------------------------------------- 23

CHAPTER THREE----------------------------------------------------------------------------------------------------- 24
3.1 INTRODUCTION------------------------------------------------------------------------------------------ 24

5
 3.2 SYSTEM ANALYSIS-------------------------------------------------------------------------------------- 24
3.2.1 SYSTEM---------------------------------------------------------------------------------------------------- 24
3.2.2 SYSTEM ANALYSIS----------------------------------------------------------------------------------- 24
3.2.3 PROPOSED SYSTEM----------------------------------------------------------------------------------25
3.3.1 UNIFIED MODELING LANGUAGE (UML)----------------------------------------------------25
3.3.2 USE CASE DIAGRAMS------------------------------------------------------------------------------- 26
3.3.3 SEQUENCE DIAGRAM-------------------------------------------------------------------------------28
3.3.4 ACTIVITY DIAGRAM--------------------------------------------------------------------------------- 29
3.3.5 CLASS DIAGRAM-------------------------------------------------------------------------------------- 31
3.4 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS-------------------------------31
3.4.1 DATABASE DESIGN----------------------------------------------------------------------------------- 32
3.4.2 DESCRIPTION OF THE TABLES------------------------------------------------------------------32

CHAPTER FOUR------------------------------------------------------------------------------------------------------ 38
4.1 INTRODUCTION------------------------------------------------------------------------------------------ 38
4.2 PLATFORM AND TOOLS FOR IMPLEMENTATION-------------------------------------------38
4.3 SYSTEM REQUIREMENTS----------------------------------------------------------------------------------- 39
4.3.1 SOFTWARE REQUIREMENTS-----------------------------------------------------------------------------39
4.3.2 HARDWARE REQUIREMENTS----------------------------------------------------------------------------40
4.4 PROGRAM MODULES AND INTERFACES------------------------------------------------------40
4.4.1 THE LOGIN PAGE------------------------------------------------------------------------------------------- 40
4.4.2 HOME PAGE------------------------------------------------------------------------------------------------- 41
4.4.3 LEVEL TIMETABLE---------------------------------------------------------------------------------------- 42
4.4.4 SCHOOL CALENDAR-------------------------------------------------------------------------------------- 43
4.4.5 REMINDER-------------------------------------------------------------------------------------------------- 44
4.4.6 VIEW TASK------------------------------------------------------------------------------------------------- 46
4.4.7 LOGOUT----------------------------------------------------------------------------------------------------- 47

CHAPTER FIVE-------------------------------------------------------------------------------------------------------- 48
5.1 SUMMARY-------------------------------------------------------------------------------------------------- 48
5.2 CONCLUSION---------------------------------------------------------------------------------------------- 48

6
REFERENCES---------------------------------------------------------------------------------------------------------- 49

7
 LIST OF TABLES

TABLE 3.1: STUDENT DATA TABLE-----------------------------------------------------------------------------33

TABLE 3.2: TIMETABLE DATA TABLE--------------------------------------------------------------------------34

TABLE 3.3: WEEKDAY DATA TABLE----------------------------------------------------------- 36

TABLE 4.1 THE SOFTWARE REQUIREMENTS---------------------------------------------------------------40

TABLE 4.2 SOFTWARE DEPLOYMENT REQUIREMENTS-------------------------------------------------40

8
 LIST OF FIGURES

FIGURE 2.1: SCREEN SHOT VIEWS OF MY STUDY LIFE APPLICATION ------------------15

FIGURE 2.2: SCREENSHOTS VIEWS OF THE MY HOMEWORK STUDENT PLANNER

APPLICATION----------------------------------------------------------------------------------------------16

FIGURE 2.5: A SCREENSHOT OF THE STUDENT ORGANIZER APPLICATION ----------18

FIGURE 2.6: SCREENSHOT VIEWS OF TIMETABLE MOBILE APPLICATION ------------19

FIGURE 2.7 SCREENSHOT SHOWING THE PRINTED COPY OF THE TIMETABLE FOR
MONDAY----------------------------------------------------------------------------------------------------21

FIGURE 3.1: USE CASE DIAGRAM FOR STUDENT ACTIVITY PLANNER-----------------27

FIGURE 3.2: SEQUENCE DIAGRAM FOR STUDENT ACTIVITY PLANNER----------------28

FIGURE 3.3: ACTIVITY DIAGRAM FOR STUDENT ACTIVITY PLANNER-----------------29

FIGURE 3.4: CLASS DIAGRAM FOR THE STUDENT ACTIVITY PLANNER---------------30

FIGURE 3.5: DATABASE FOR STUDENT DATA TABLE------------------------------------------32

FIGURE 3.6: DATABASE FOR TIMETABLE TABLE-----------------------------------------------33

FIGURE 3.7: DATABASE FOR WEEKDAY TABLE-------------------------------------------------34

FIGURE 3.8: DATABASE FOR SCHOOL CALENDAR TABLE-----------------------------------34

FIGURE 3.9: TIMETABLE TABLE WITH RECORDS-----------------------------------------------34

FIGURE 3.10: STUDENT TABLE WITH RECORDS------------------------------------------------35

FIGURE 4.1 SCREENSHOT OF LOGIN PAGE-------------------------------------------------------38

FIGURE 4.2 SCREENSHOT OF THE HOME PAGE-------------------------------------------------39

FIGURE 4.3SCREENSHOT OF THE LEVEL TIMETABLE----------------------------------------40

FIGURE 4.4SCREENSHOT OF THE SCHOOL CALENDAR--------------------------------------41

FIGURE 4.5 SCREENSHOT OF THE REMINDER MODULE-------------------------------------42

9
FIGURE 4.6 SCREENSHOT OF THE VIEW TASK PAGE------------------------------------------44

FIGURE 4.7 SHOWS THE SCREENSHOT OF THE LOGOUT PAGE----------------------------44

10
 CHAPTER ONE

INTRODUCTION

1.1 BACKGROUND

The impact of information and communication technology (ICT) in the world’s development
cannot be over emphasized. In recent years, the university-learning environment is becoming
more and more conducive, convenient, effective and efficient by various ICT enhanced systems.
For example, the student portal, which aids course registration and results checking; the e-
learning platform, for getting lectures materials, submitting assignments and participating in tests
and examinations. These ICTs have greatly impacted on students’ performance in general
(Youssef and Dahmani,2008).This goes to show that the quality of education and university
management can be improved through appropriate ICT adoption. However, ICT can still be
leveraged further in solving some fundamental challenges that students face such as time
management and scheduling. This can be demonstrated with the following scenarios:

Scenario 1: Student A copied her exam timetable schedule from the notice board of her hall of
residence. The timetable schedule was a general one containing all courses offered in the
university. In the process of copying this, she copied a wrong time for one of the courses. On the
day of the course exam, she decided to do a few things before attending the exam thinking she
was still in time. She got to the exam hall and discovered that the exam was already rounding off
and thus she had missed the exam. How could ICT have helped to prevent this challenge?

Scenario 2: Student B was given an assignment to be submitted on a certain day. He does the
assignment and did not remember to bring it along on the day of submission. As a result, he was
unable to submit afterwards. Could this challenge have been addressed through some form of
reminder?

Clearly, ICT brings new technologies that help to reduce and possibly eliminate challenges that
accompany the manual method of copying timetable schedules and remembering important

11
dates. Prior to this time, students of Covenant University copy their timetable manually and this
is not efficient based on the results of a research embarked on prior to this project and which also
formed the motivation for this project. Student Activities Planner (SAP) for Covenant University
students will help each student generate their timetable automatically by simply signing into the
website and registering their courses for the semester. This system will be able to generate
timetable for each student and also for the lecturers. The timetable scheduling system shall be
able to address the problems stated in the aforementioned scenarios.

Firstly for the issue of bulky and confusing lecture/examination timetable: Every student should
have the application on their tablets and should be able to login with their matriculation number,
course and level.Every student would be required to input his or her registered courses for a
semester into the system. The student showing the time, venue and lecturer for each course
swould then automatically receive the timetable for those registered courses. The same procedure
will take place for both test and examination timetable for the student. This same procedure
could extend to the lecturers as well.

Secondly, on the issue of task and assignments: The application will contain a memo where
students are able to put down different assignments, topic of the assignments and due dates.
Students will also be able to set reminders for the assignments.

Thirdly, for extracurricular activities: The application already contains the extracurricular
activities for the semester and it shows the dates of all the activities.The student is left with the
choice of setting a reminder for any activity that is of importance to him/her.

In general, the Student Activities Planner shall be able to help students organize their lectures,
tasks, test and examination and also make their academic life much easier to manage.

1.2 STATEMENT OF THE PROBLEM

The problem of bulky, enormous and confusing timetable has been a challenge for a while now
in many universities (Nakano et al, 2010) and in Covenant University a survey was carried out in
the various halls of residence. The results showed that 63% of students surveyed do not copy
their timetable, while 17% of the few who copy the timetable, copy the wrong thing. Most often
students tend to forget tasks and assignments given to them because most times they have lots of

12
assignments from different lectures to do. This is in addition to other extracurricular activities.
Also, students are not aware of activities to be done during the semester well ahead of the event
occurrence. The idea behind this project is to address these challenges. The copying of timetable
problem usually arises at the beginning of every semester when the students need to copy their
lecture timetable, or during test and examination week when they students need to get their
timetable. On the other hand, the issue of assignments and task reminder occur often, as different
lecturers tend to give assignment at different times during the semester.

1.3 AIM AND OBJECTIVES

The aim of this project is to develop a mobile-based student activities planner.

The objectives of this project are as follows:

 To gather requirements for the proposed system.

 To design the proposed system based on the requirements gathered
 To implement and deploy the system as a mobile app

METHODOLOGY

In other to achieve the project we will adapt a descriptive conceptual approach whereby
designing a mobile application.

Objective 1: To gather requirements for the proposed system

A survey was carried out among the students in the ten different halls in Covenant University
using Survey Monkey. Survey Monkey is an online survey site that simplifies the survey process
considerably by sending out the survey to multiple people and keeping track of the respondent so
you can re-contact non-respondent.

13
Objective 2: To design the proposed system based on the requirements gathered

Unified Modeling Language (UML) was used to model the proposed system. The specific
diagrams used include: Use case models – which show the interaction between users and the
system; sequence diagrams – which show the flow of information within the proposed system;
and activity diagram - which show the flow of activities within the proposed system

Objective 3: To implement and deploy the system as a mobile app

The system will be developed for tablets running Android, The tools required include:

MySQL: This is the database software that helps to store the information from the student
activity planner and also helps to store the information from users and admin.

PHP: PHP is a server side scripting language designed for web development but also used as a
general purpose programming language. In this project, it will be used to create the web
application that will serve as support to the mobile application.

JSON: Java Script Object Notation is a readable format for structuring data that is used majorly
to pass data between a server and a web application; it is used as an alternative to XML. It is also
known as a lightweight data because it is easy for humans to read and write and also easy for
machines to parse and generate.

Java: Java is an object-oriented language and computing platform similar to C++, but simplified
to eliminate language features that cause common programming errors. Java is a general purpose
programming language that can be used to create applications that run on single computers or
maybe distributed among servers in a network. It can also be used to create small Java
applications, which are called applets.

Eclipse: Eclipse is an integrated development environment (IDE) that provides a platform which
is used to quickly set up new Android projects, create packages based on the Android Framework
API, design the application user interface and debug the application using the Android SDK
tools. It also allows import and export of application source codes.

Android SDK: It is an integrated development environment (IDE) that was used to develop the
mobile application.

14
1.5 SIGNIFICANCE OF THE STUDY

 Reduced scope for error: students will be able to get appropriate information rather than
relying on third parties who might not copy the correct timetable.
 Focus on the student: creates personalized electronic timetable for the students
 Ease of data viewing: it allows the students to focus on the data that is relevant to them
 Reminders: it also allows students to set remainders for due assignments and project.

1.6 PROJECT OUTLINE

The rest of this project is outlined as follows: Chapter 2 provides the literature review for the
project. In Chapter 3, the system analysis and design was performed. In Chapter 4 the
implementation of the system was presented and discussed. Chapter 5 rounds off the project by
providing a summary, recommendation and conclusion.

15
 CHAPTER TWO

LITERATURE REVIEW

2.1 INTRODUCTION

A survey conducted at the beginning of this study revealed that many of students find it difficult
to copy their timetable, organize their task and assignments and other extracurricular activities
for any given semester. Failure in this regard could result in a setback for the student. Therefore,
the student activity planner is a necessity for every student even thou it is not ubiquitous.

2.2 REVIEW OF EXISTING SYSTEMS

An automated system that provides both student timetables and organizers that enables them to
organize their assignments and extracurricular activities is not ubiquitous. However, applications
to perform each of these activities separately exist. Examples include: my study life (Jamie
Clark, 2015), and my homework student planner, student organizer (Miranda, 2013), timetable
which all enable students to plan their assignments, set reminders for them and other
extracurricular activities. There is also the web based time schedule system that enables students
to get their personal timetable (Nakano et al., 2007)

2.2.1 MY STUDY LIFE

My study life is both a web and mobile application developed by Jamie Clarke in 2010.Jamie got
tired of using paper planners to keep track of homework and coursework and in addressing this
drawback, he decided to create an application that he could use on a daily basis to keep track of
his classes and assignments. He expected that it would ultimately replace the need for a paper
planner. Thus he came up with the MY STUDY LIFE application which today works across all
popular platforms ensuring that students have a simple, easy to use solution to organize all of
their classes, tasks and examinations as well as add new functionality for teachers and schools.
Figure 2.1 gives an overview of the application.

16
Figure 2.1: Screen shot views of MY STUDY LIFE application (Jamie Clark, august 2015)

17
2.2.2 MY HOMEWORK STUDENT PLANNER

My Homework Student Planner is also an application that enables students keep track of
lectures, assignments, test and examinations, also enables them to set reminders for all necessary
activities. What make it even better is its simplicity, reliability and beauty. Figure 2.2 gives the
screenshot of the system.

Figure 2.2: Screenshots views of the My Homework Student Planner application

(My homework, 2015)

2.2.3 WEB BASED TIME SCHEDULE SYSTEM FOR MULTIPLE LMSs ON THE
SSO/PORTAL ENVIRONMENT.

It is a web based time schedule system that was developed by Kumamoto University in Japan to
meet their long-term plan. Along with their long-term goal they developed a single sign-on
(SSO) university portal for all students and staff since 2006 (Nakano et al., 2008) and once
authentication has been completed in the portal, each user gets personalized web pages including
information for each role, direct links to available systems without re-authentication. The web
based time schedule system was also included in the portal as a tab page, where students and
professors can get theirown course timetable depending on the registered courses of the student

18
information system (SIS). Each course name on the timetable is directly linked to the
corresponding course page on the LMS through the SSO. Figure 2.3 show the architecture of the
system while2.4depicts the Data flow and SSO connections between the time schedule system on
university portal, LMSs and SIS.

Figure 2.3: Architecture of the Web-based timetable system integrated with the portal and SSO
(http://www.ieec.uned.es/investigacion/educon2010/searchtool/EDUCON2010/papers/
2010S01D01.pdf)

19
Figure 2.4: Data flow and SSO connections between the time schedule system on university
portal, LMSs and SIS

(http://www.ieec.uned.es/investigacion/educon2010/searchtool/EDUCON2010/papers/
2010S01D01.pdf)

2.2.4 STUDENT ORGANIZER

This is a mobile application that allows students to create weekly schedule with great ease by
requiring them to enter the start and end time, the venue and the appropriate day of the week of a
particular course. From the planned schedule it is possible to access all the information on a
particular course (time, venue, and lecturer). It also enables them to keep track of test and
examination dates, and other academic activities using charts. Figure 2.5 shows a screenshot of a
view of the application.

20
Figure 2.5: A screenshot of the student organizer application (Miranda, 2013)

2.2.5 TIMETABLE

It is a mobile application that helps to organize students’ classes, homework, reading

assignments, and schedule. The app has multiple views that allow a student to check his/her class
schedule and events for possible assignments, quizzes and exams. Timetable application takes all
of the great things about a paper student organizer and delivers it to an Android mobile device.
The application also makes it easy to keep track of public holidays; and check what assignments
are due. The app also supports Dash Clock Widget, so a student can see their events on the lock
screen, and comes with home screen widgets as well for a quick view of upcoming activities as
well as activities that ought to be taking place at the given time. Figure 2.6 shows a screenshot of
a view of the application.

21
Figure 2.6: Screenshot views of Timetable mobile application (Alan Henry, 10th February 2013)

2.3 COVENANT UNIVERSITY TIME TABLE SCHEDULING SYSTEM

The method used by students in Covenant University to retrieve their timetable is still manual
whereby each student has to go the nearest notice board either in the hall of residence or in the
college buildings to copy their table for lectures, test and examinations, sometimes these
timetables are changed and the student needs to copy the new timetable again. Figure 2.3 shows
what the printed timetable looks like.

22
Figure 2.7 Screenshot showing the printed copy of the timetable for Monday

23
The figure above shows a copy of the student timetable for Monday which is just a day out of the
five days of the week days, when all the timetable for the five weekdays are posted on the notice
board it is usually too bulky thus making it tedious and difficult to locate different courses, as
well as their venues and time.

2.4 CONCLUSION

This chapter has reviewed the existing student organizer applications as well as what currently
obtains in the Covenant University context. In order to improve on the current approach to
copying timetables, this study is proposing an automated and personalized student organizer. The
provision of Android tablets to all Covenant University undergraduate students also favors the
introduction of such an application which should be able to run on their devices. The application
will thus be similar to what obtains in the existing applications. In the next chapter, analysis of
the requirements for the proposed application is performed.

24
 CHAPTER THREE

SYSTEM ANALYSIS AND DESIGN

3.1 INTRODUCTION

In this chapter, the necessities for the student activity planner were accumulated by watching the
current procedures utilized as a part of various applications, for example, My Study Life
(Clark,2015), My Homework Planner, Timetable (Henry,2013) and Web Based Timetable
Schedule System (Nakano et al., 2007). The core operations relevant to the student activity
planner are modeled using the Unified Modeling Language (UML).

3.2 SYSTEM ANALYSIS

3.2.1 SYSTEM

There are basically three critical parts in every system and that fuses input, processing and
output.

3.2.2 SYSTEM ANALYSIS

System analysis is the process of seeking to understand the business processes of an organization
in order to be able to model it. It is also a term to collectively describe the early phases of system
development. There are many ways to go about system analysis, discovery prototyping,
information engineering and object-oriented analysis (Singh,2015). The object oriented analysis
methodology was received exclusively for this project. System analysis is an extremely crucial
part of system improvement since it opens ways to different other principal choices and
decisions. Amid the analysis, the system clients are indicated in light of the fact that the analysis
is driven by the business worries of the users. System analysis likewise figures out if a proposed
system is in fact, economically and operationally feasible.

25
3.2.3 PROPOSED SYSTEM

Student activity planner is a portable application based on the Android platform, which can be
effectively gotten to with any Android gadget. It takes every one of the benefits of the android
platform to give an effective user experience which incorporate simple user interface, security,
and access from anyplace and that's only the tip of the iceberg, you essentially simply require an
android gadget to utilize this application.

Features

Student activity planner provides features such as

 Keep record of assignments, tasks and keep record of the considerable number of
assignments given in class and when they ought to be submitted furthermore updates can
be set to remind them before the due date that there is a task to be submitted.
 Download individual timetable: This permits the user (student) to effectively download
their own tests, examination timetable for the semester and personal lecture timetable.
 Keep track of school occasion: This empowers the user to know about school exercises
and when they are to happen, this includes extracurricular activities such as trade fair,
concerts.
 Set updates for lectures, test and examination: This empowers the user to set updates for
every one of their lectures, test and exams to guarantee that they bear in mind.

3.3 REQUIREMENTS ANALYSIS AND MODELLING

3.3.1 UNIFIED MODELING LANGUAGE (UML)

UML is a standard documentation for the exhibiting of certifiable objects as an underlying stage
in building up an object-oriented outline methodology. Its documentation is gotten from and
brings together the documentations of three article arranged outline and examination techniques
(Margaret, 2010). It shows the overall system design that enables right decisions to be made
early in the process of developing the software. It empowers simplicity of upkeep by giving more
viable visual representations of the system (Thangaraj,2011).

26
UML is used primarily for software intensive systems like: systems software and business
processes. The following are the most commonly used UML diagrams (Schneider et al., 1998):

 Use Case Diagrams

 Behavioral Diagrams
- State chart diagrams
- Object diagrams
- Activity diagrams
- Interaction diagrams
 Sequence diagrams
 Collaboration diagrams
 Implementation Diagrams
- Component diagram
- Deployment diagram
 Class Diagrams

3.3.2 USE CASE DIAGRAMS

A use case is a methodology used as a part of a system examination to recognize, illustrate, and
form system necessities. In this setting, the expression "system" implies something being made
or worked, for instance, a mail-ask for thing arrangements and organization Web website page.
Use case charts are used in UML (Unified Modeling Language), a standard documentation for
the showing of true objects and systems (Project management, 2015). A use case model is a point
of view of a system that underscores the behavior of a framework as it appears to outside clients.
A use case model fragments system helpfulness into trades (use cases) that are critical to clients
(actors). It addresses an essential piece of value that is finished through and through. It gets a far-
reaching point of view of a key helpfulness of the structure in a way that can be easily
understood by a non-specific client.

The sections of a use case diagram consolidate: actors, use cases, affiliations and the framework
boundary.

27
  Actors:an Actor is a user of the system. This incorporates both human users and other PC
systems. An Actor uses a Use Case to perform some bit of work, which is of quality to
the business. The arrangement of Use Cases an actor has admittance to characterizes their
general part in the system and the extent of their activity. .
 Use Cases is a complete undertaking of a system that gives a quantifiable aftereffect of
worth for an actor. All the more formally, a use case characterizes an arrangement of
utilization case cases or situations.
 Associations area relationship be-tween an actor and a use case that shows that the actor
communicates with the system by method for the use case.
 System Boundary addresses the degree of the framework the performing actor is
teaming up with.

There are additionally two sorts of connections between use cases namely:

 Includes: The «include» relationship allows us to include the steps from one Use Case
into another. This is valuable when the included steps occur as a recognizable sequence
in many different contexts. Example we need to capture the client’s details, after further
analysis, we may find that there are other Use Cases where we also need to record the
clients’ details. Furthermore, we will find that there are a number of ways of doing this,
for example, we may need to capture them as a new client or recall them as an existing
client.

 Extends: The «extend» relationship allows us to modify the behavior of the base Use
Case. Suppose we want to add courses or test that requires a degree of client
specification. For these additions we will need to record the clients additional
requirements, such as venue and time. In this case we are adding something extra to the
flow of the base Use Case.

28
. Figure 3.1: Use case diagram for Student Activity Planner

Figure 3.1 shows the actor and the activities s/he performs. The outline shows two actors. The
first actor (student) signs into the system get their timetable and can set reminder for lectures and
assignments if necessary. The second actor updates the timetable and student calendar whatever
point there is a change or another activity has been included.

3.3.3 SEQUENCE DIAGRAM

The Sequence Diagram models the cooperation of objects considering a period progression. It
shows how the objects interface with others in a particular circumstance of a use case

29
(http://www.visual-paradigm.com/VPGallery/diagrams/Sequence.html). It shows a course of
action of objects and the messages sent and got by those objects. A sequence diagram is also a
significant part used as a piece of methodology related to analysis, configuration and
documentation. A sequence diagram is otherwise called a timing diagram; event diagram and
event scenario Figure 3.2 shows the outline for the student activity planner application.

Figure 3.2: Sequence diagram for student activity planner

3.3.4 ACTIVITY DIAGRAM

Activity diagram is basically a flow chart to represent to the stream structure of one activity to
another activity. The activity can be delineated as an operation of the system
(http://www.tutorialspoint.com/uml/uml_activity_diagram.htm). Activity diagrams are graphical

30
representations of work procedures of stepwise activities and activities with sponsorship for
choice, cycle and concurrence. In UML, activity charts are proposed to indicate both
computational and various leveled techniques (i.e. workflows). Activity charts show the general
stream of control. Figure 3.3 shows the activity chart for the student activity planner.

Figure 3.3: Activity diagram for student activity planner

31
3.3.5 CLASS DIAGRAM

The class diagram is a static diagram. It speaks to the static viewpoint of an application. Class
diagram is not simply used for envisioning, delineating and chronicling assorted parts of a
system moreover to build executable code of the software application
(http://www.tutorialspoint.com/uml/uml_class_diagram.htm). A class is a depiction of a course
of action of objects that have the same qualities, operations, associations, and semantics.
Graphically, a class is rendered as a rectangle, ordinarily including its name, properties, and
operations in discrete, doled out compartments. It likewise shows the classes inside of a
particular model with each of the classes having their own unmistakable traits, name and
operations that can be completed on them and class charts can likewise relate with different
classes in a model.

Figure 3.4: Class Diagram for the Student Activity Planner

3.4 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS

Functional requirements include:

 Academic department will provide courses offered by each course and level in the
department.

32
  College of study will provide a cumulative timetable of all departments in the college.

Non-functional requirements include:

 The system should be easy to understand

 The system should be user friendly
 The system should have a quick response time
 The system should be able to retrieve each student’s timetable based on courses
registered

3.4.1 DATABASE DESIGN

A database is a collection of information organized to provide efficient retrieval. It provides an

organized mechanism for storing, managing and retrieving information (Ojo, 2009). The system
has an integrated database that allows data to be inputted and retrieved from the database.

3.4.2 DESCRIPTION OF THE TABLES

A relational database is made up of tables, each of which is an organized arrangement of records

and fields.

Table 3.1: Student data table

COLUMN DESCRIPTION

User Id

Username Name of student

Matric no Matriculation number of student

Password Student registration number

33
 Course Student course

Class name Student level

Figure 3.5: Database for student data table

Table 3.2: Timetable data table

COLUMN DESCRIPTION

Time Id

Class name Student Level

Course Student course

Time Time for each lecture

Monday

Tuesday

Wednesday

34
Thursday

Friday

Venue1 Lecture venue for Monday

Venue2 Lecture venue for Tuesday

Venue3 Lecture venue for Wednesday

Venue4 Lecture venue for Thursday

Venue5 Lecture venue for Friday

Figure 3.6: Database for timetable Table

35
Table 3.3 weekday data table

COLUMN DESCRIPTION

TIME Lecture time

MONDAY First day of the week

TUESDAY Second day of the week

WEDNESDAY Third day of the week

THURSDAY Fourth day of the week

FRIDAY Fifth day of the week

36
Figure 3.7: Database for weekday table

Figure 3.8: Database for school calendar table

Figure 3.9: Timetable table with records

37
Figure 3.10: Student table with records

38
 CHAPTER FOUR

SYSTEM IMPLEMENTATION

4.1 INTRODUCTION

This chapter discusses the implementation of the student activities planner providing an
overview on the choice of programming language and platform that was used in the
implementation of the system. It also discusses the various features of the system.

4.2 PLATFORM AND TOOLS FOR IMPLEMENTATION

The tools discussed below were used in the implementation of the proposed student activities.

 Android SDK: It is a software development kit that enables developers to create

applications for the Android platform. It also separates the Android SDK manager into
platforms, SDK tools and other components into their different packages for easy
management and use. The Android SDK includes sample projects with their source code,
development tools, an emulator, and necessary libraries to build Android applications.
Applications are written using the Java programming language.
 Eclipse: Eclipse is an integrated development environment (IDE) that provides a platform
which is used to quickly set up new Android projects, create packages based on the
Android Framework API, design the application user interface and debug the application
using the Android SDK tools. It also allows import and export of application source
codes.
 Structured Query Language (SQL): It is a standard language that is used to
communicate with a database by retrieving information from the database and updating
the database.
 Java: Java is an object-oriented language and computing platform similar to C++, but
simplified to eliminate language features that cause common programming errors. Java is
a general purpose programming language that can be used to create applications that run
on single computers or maybe distributed among servers in a network. It can also be used
to create small Java applications, which are called applets.
 PHP: Hypertext preprocessor is a very common and widely used open source scripting
language that can be used alone or embedded in HTML for web development. In this
39
 project it will serve as a server side script that will enable us to retrieve information from
the database.
 JSON: Java Script Object Notation is a readable format for structuring data that is used
majorly to pass data between a server and a web application; it is used as an alternative to
XML. It is also known as a lightweight data because it is easy for humans to read and
write and also easy for machines to parse and generate.

4.3 System Requirements

4.3.1 Software requirements

Table 4.1 The Software Requirements

Requirements Software

Operating system Android

Database management system MYSQL

Programming language Java, PHP, JSON

Web server WAMP server

Table 4.2 Software Deployment Requirements

Requirements Software

Operating system Android

Internet browser Firefox, internet explorer, chrome

40
4.3.2 Hardware requirements

An android powered device is needed for the application to run effectively.

4.4 PROGRAM MODULES AND INTERFACES

This section contains screenshots that show the different interfaces and their functionalities.

4.4.1 The login page

The login page is the first page of the application it is visible to everyone but only accessible by
the authorized users (students), the students put in their matriculation number as the username
and registration number as the password. This is depicted in Figure 4.1.

41
Figure 4.1 Screenshot of Login Page

4.4.2 Home page

The home page is the next page that appears when a user logs in successfully. It shows the date,
time and the activities of that day and also has two major icons: the user’s timetable and school
calendar. This is depicted in Figure 4.2.

42
Figure 4.2 Screenshot of the Home Page

4.4.3 Level Timetable

This page displays the timetable of each specific user that logs into the application. It displays
the day of the week, the courses and the time for each course and their venue as depicted in
Figure 4.3.

43
Figure 4.3Screenshot of the Level Timetable

4.4.4 School Calendar

The school calendar shows all the activities that are taking place in the current semester and it
shows the dates for all the events as depicted in Figure 4.4.

44
Figure 4.4Screenshot of the School Calendar

4.4.5 Reminder

The reminder enables each user to set alarm for important activities they will like to remember.
They can also set reminders for lecture attendance, assignment submission due dates as well as
other school activities of interest. This is depicted in Figure 4.5

45
Figure 4.5 Screenshot of the Reminder Module

46
4.4.6 View Task

In the view task it shows all the activities that the user has set a reminder for and their due dates,
it enables the user keep track of all important activities as depicted in Figure 4.6.

Figure 4.6 Screenshot of the View Task Page

47
4.4.7 Logout

The logout page is where the user returns to when they are done using the application and the
logout button takes them back to the login page as depicted in Figure 4.7.

Figure 4.7 shows the screenshot of the logout page

48
 CHAPTER FIVE

SUMMARY AND CONCLUSION

5.1 SUMMARY

This study provides an easier and more understanding method for student to be able to retrieve
their timetable, tests, keep track of assignments and other academic and non-academic school
activities. It provides user-friendly interface that makes it easy for the student to interact with. In
order to build this application a critical, extensive and in depth knowledge of the system
requirements which include information about existing systems their lacking areas, what is to be
done and customers wants were to put together and a desired design was developed to meet the
stated objectives based on the system requirements. The development of this system is relevant
to all students in various universities to provide for them easy the universities should consider
academic life, as such, its deployment and maintenance.

5.2 CONCLUSION

From the survey carried out towards the implementation of this project, it is clearly seen that the
student activities planner is an essential application for all students, the introduction of other
activities planner has made it easier for students to plan and keep track of school activities and
the deployment of this application pushes it up in the competitive market of activities planner
providing companies.

49
 REFERENCES
1. Youssef, A. B., & Dahmani, M. (2008). The impact of ICT on student performance in
higher education: direct effects, indirect effects and organizational change. RUSC.
Universities and Knowledge Society Journal, 5(1).
2. Nakano, H., Sugitani, K., Nagai, T., Kubota S., Migita M., Musashi Y., Iriguchi N.,
Usagawa T., (2010) Web based time schedule system for multiple lmss on the SSO/portal
environment.
3. H. Nakano, T. Kita, K. Sugitani, J. Nemoto, S. Kitamura, K. Suzuki, R.Matsuba, M.
Migita, Y. Musashi, N. Iriguchi and T. Usagawa, “The Learning Portal for Improving the
e-Learning Environment”, Proc. 5thInternational Conference on Emerging
Telecommunications Technologies and Applications (ICETA2007), The High Tatras,
Slovakia, 2007.
4. H. Nakano, K. Sugitani, T. Kita, R. Matsuba, S. Kubota, M. Migita, Y.Musashi, N.
Iriguchi, T. Kida, K. Tsuji, M. Shimamoto, T. Shimura andT. Usagawa, “Developing the
Web-based Timetable System Cooperatedwith LMS and SSO”, IPSJ SIG Technical
Reports (Japanese, Englishabstract), No. 9, pp.79-82, 2008.
5. Jamie Clark “My study life” August 21st 2015.
6. Nuno Miranda “Student organizer”17th July 2013
7. Timetable “timetable is a personal organizer designed for students” by Alan Henry 10 th
February 2013.
8. My homework accessed at https://myhomeworkapp.com/ on 28th October 2015
9. H. Nakano, K. Sugitani, T. Kita, R. Matsuba, S. Kubota, M. Migita, Y.Musashi, N.
Iriguchi, T. Kida, K. Tsuji, M. Shimamoto, T. Shimura andT. Usagawa, “Developing the
Web-based Timetable System Cooperatedwith LMS and SSO”, IPSJ SIG Technical
Reports (Japanese, Englishabstract), No. 9, pp.79-82, 2008.
10. Jamie Clark “My study life” August 21st 2015.
11. Nuno Miranda “Student organizer” 17th July 2013
12. Timetable “timetable is a personal organizer designed for students” by Alan Henry 10 th
February 2013.

50
13. My homework accessed at https://myhomeworkapp.com/ on 28th October 2015.
14. Hermant Raj Singh “system analysis methods”, Aug 25th 2015.
15. Schneider G., Winters J.P. (1998): Applying use Cases, Addison –Wesley.
16. Ojo T.O., (2009): Design and implementation of Online University Information System
(UIS),B.Sc Project submitted in the Department of Computer and Information Sciences,
Covenant University, Ota.
17. Margaret Rouse “Unified Modeling Language” 2010.
18. Project Management “use case Diagram” January 2015.
19. Sequence Diagram accessed at
http://www.visual-paradigm.com/VPGallery/diagrams/Sequence.html on the 20th of
February 2016.
20. http://www.tutorialspoint.com/uml/uml_activity_diagram.htm “Activity Diagram”
accessed on the 20th February 2016.
21. http://www.tutorialspoint.com/uml/uml_class_diagram.htm “class Diagram” accessed on
the 20th of February 2016.
22. http://web.simmons.edu/~benoit/lis486/SystemsImplementation accessed at System
implementation on the 5th of March 2016.
23. http://learnsad.com/SDLCImplementation.html accessed at “learn system analysis and
design” on the 5th of March 2016.
24. What can PHP do? http://php.net/manual/en/intro-whatcando.php accessed on the March
21, 2016

51