TABLE OF CONTENT

1.0 Introduction
1.1 Background of organization.
1.2 Objective of organization.
1.3 Organizational chart.
2.0 System planning
2.1 Requirement analysis.
2.1.1 Objective of the system..
2.1.2 Scope of the system
2.2 System overview.....
2.3 Functional requirement
3.0 System analysis
3.1 Introduction
3.2 Description of the system/function.
4.0 System design
4.1 Introduction
4.2 System design.
4.3 Database design..
4.4 Entity relationship design (ERD)
4.5 User interface design..
5.0 Implementation
5.1 Introduction
5.2 Hardware
5.3 Software.
5.4 Coding phase..
5.5 Testing phase..
5.6 Unit testing.
6.0 Conclusion..
Appendix

2
3
4
5
5
6
7
8
9
10
11
12
13
15
17
17
17
18
19
19
20
21-28

1.0

INTRODUCTION

1.1

Introduction to organization background

The Academic Affairs Division is a Centre entrusted with the management of

all academic affairs of the university. It was established on 21st August 1969 as part
of the restructuring of UiTM's administration and was then headed by the Dean of
Academic Affairs. At its inception, The Academic Affairs Division managed only 9
schools (now known as faculties) that offered 42 programmes. By 1998, UiTM once
again underwent restructuring. Subsequently, the duties that came with the post of the
Dean of the Academic Affairs Division went to three Assistant Directors (Academic).
In 1996, amendments were made to the ITM Act of 1976 that led to further changes.

At present, the Division is placed under the office of the Deputy Vice
Chancellor (Academic and International), two Academic Heads who are headed by
the Director of Academic Development and the Director of Curriculum Affairs Unit
(UHEK), responsible for academic matters of 25 faculties and 3 learning centres, in
addition to 13 branch campuses all over the country.

1.2

Objective of the organization

The main objectives of The Academic Affairs Division (HEA) are :

To keep up with the current demands and standards of professionalism in

the world of academia.

To involve in various academic-related activities such as researches and

publications.

To manage academic processes and procedures.

To provide direction to academic developments.

To regulate academic systems and policies.

To observe the quality of academic assessments and monitor academic

standards.

1.3 organizational chart

2.0

SYSTEM PLANNING
System Development Life Cycle (SDLC) is an approach to build information
systems and refers to all the activities that go into producing an information system.
System planning is the first phase SDLC that include the investigation and data gathering
involving the problems, purpose, and the benefit of the project. This phase also is the
process of understanding why the system should be built and defines the requirement.
2.1

Requirement analysis
There are 2 requirements for doing system analysis. We have to define the

objective and the scope of the system.

2.1.1

Objective of the system

The objectives of the system are :

2.1.2

To insert and store all the class scheduling information.

To search any available class to fit the entire timetable.

To view the class timetable in a more proper way.

To check their balance of leave more easily.

Scope of the system

After understanding the problems, we define scope and content of the

project. The scopes are:

1.

Alternative system arrangements agreed by The Academics

Division of UiTM team to handle all the timetable and class.

2.

Updating the system of class scheduling system for the overall

semester.

3.

The system module should be able to show the class scheduling in

a timetable form following the criteria needed.

4.

Publish the information requirements online applicable for all user

view.

2.2

System overview

Class scheduling system is a system under HEA that build to arrange the
entire course in UiTM in a systematic way. This system help the user especially
student and lecturer to setting up the schedule for the teaching session. The system
will construct the database to keep and arrange all the class for each course that have
in UiTM. These systems basically have 5 subsystems. Firstly, login system, which is
need user/ lecturer (staff) to key in ID, faculty, and CSS details. By key all the
details the CSS will generate and build in two categories. The user have to choose
either enter to the new semester or the last semester for the CSS update the course
code system and report to display. Under the system its also have course code and
grouping system, user system, class booking system and report and viewing system.

The CSS system has an ability to interact with other system (SIMS) to get all
the data from SIMS to match with the CSS system. Thus the users have to use the
same ID and password as they use in SIMS system. The systems also are allowed the
user to print out the class details using the format given by the system. The system
also can be access by student to view all the details based on their course that have
been registered in Student Portal.

2.3

Functional Requirement
The functional requirements for a system describe what the system should do,
how the system should react to particular inputs, and how the system should behave
7

in particular situation. These requirements depend on the type of software being

developed, the expected users of the software, and the general approach taken by the
organization when writing requirements.
The functional requirements for this system is :
1. All the students/lecturers should be able to search their timetable with
the class provided for each faculty and courses.
2. The system shall generate a report and update the any changes of data.
3. Each staff member using the system is uniquely identified by his or her
ID number.

3.0 SYSTEM ANALYSIS

3.1

Introduction of system analysis

System analysis is the process of investigating a system, identifying problems,
and using the information to recommend improvements to the system. This phase
make ease for the programmer to understand the purpose of the system for creating
the system.

3.2

Description of the system

The HEA departments are responsible to keep the staff and student details for the
system to update the data information. The main are checking the availability and
demanding for class booking. Once the student registered to the system by validating,
CSS will automatically update the data.
8

The HEA staff will key-in the data and build the CSS in two different ways either
using the last semester or new semester. Then the system will update the CSS
parameter and details to be made in group and will be display for user viewing. The
student can view all the details about classroom, course and group.

4.0 SYSTEM DESIGN

4.1

Introduction of System Design

System design is the third phase of System Development Life Cycle. In this
phase the physical model will provide the understanding on the flow of data for
output report design. The principle goal of system design approach that provide the
function describe in the system requirements document. This phase involved creating
the entity-relationship diagram, designing the user interface and creating output
report.

Data dictionary :
Data dictionary stores definitions of the data elements and their relationships.
Correct query is needed in producing output reports. The uses of data dictionary are to
look up for primary key of the table, the foreign key related to the table, the spelling
9

of the column and so on. The data dictionary can be viewed in Appendix A at the
back of the report.

4.2

System Design
CONTEXT DIAGRAM :

System
Login system

System

System

Course code &

generating group

Report & data viewing

system

System
Class Scheduling

System

System

Class booking system

User system

10

FLOW PROCESSING (DFD)

Below is the Data Flow Diagram (DFD) that is used in building a logical model .

Last semester

Css
parameter

Login
details

Generate CSS

Login into
the system +
key in data

Copy CSS last

semester

Update CSS and

made group

New semester

Login
details

Css
Update CSS
parameter
parameter

Choose a
semester &
course code
Information
details

Display
complete CSS

11

 Entity relationship design (ERD)

START
Start

Login System CSS

Use ID,
password and
faculty/campus
as registered at

Built CSS

CSS last semester?

Choose semester and
course code

SCC new semester?

Copy CSS last

semester

Update
the new
CSS
Campus,
faculty,
course
code
mode
of information
study, day,
time, programme
block, category
type, max student
can registred

Update CSS
parameter(lecturer, room,
date/slot)

Choose a semester and

course code
Campus, faculty,
mode of study, day,
time, programme
block, category
type, max student

12

Enter the information of

course code to be made a
group

Display/generate a
complete CSS

END

4.3

User interface design

User interface design is the physical model of developing a system. It
describes how user interact with the computer system and consist all hardware and
software, screen, menus, function, output and features that affect two-way
communication between the user and the computer. We take a screen shot of ICReSS
interfaces as the example. Below is the example of interface that has similar features
as CSS system.
Example of interface :

Figure 4.5 User Interface Design of ICReSS, key in the course or faculty

13

Figure 4.5 display the class, time, group of each course registered

5.0 IMPLEMENTATION
5.1

Introduction

14

Systems Implementation is the fourth of five phases in the systems

development life cycle (SDLC). These phases also include application development,
testing, installation, and evaluation.

5.2

Hardware & software

During the implementation of this system, below are the hardware and

software used in implementation phase of the class scheduling system (CSS).

5.3

1.

database development server

2.

Application development server

3.

Oracle 11gR2 DBMS

4.

Coldfusion 8

5.

Adobe Dreamweaver 3 as the development tool

Coding
Coding is the process of assigning a code to something for the purposes of
classification or identification of turning from program logic into specific
instructions that the computer system can execute and the system work properly.
The coding involve are:
15

1.

SQL Query

2.

XML programming language

3.

SQL Adapter programming language

4.

ASP.NET programming language

In designing reports and statistics, correct SQL Query is needed so that the
will produce. False query will cause inaccurate data produced in the report and the
output might view the error or might not appear at all. ( Attached of a sample
code of part of the system in Appendix B).

5.4

Testing phase
Testing is intended to show that a program does what it is intended to do
and to discover program defects before it is put into use. In testing phase, the
system have been through into two test, which is :
1. Unit test - to test functionality per function - usually done at
programmer level
2. Integrated test - to test functionality of whole system when all
components are put together.

16

Here we can see the whether the inter-related modules really work with each
other based on the data input. Any bugs/error will be noted and programmer in
charge will take action,

5.5

Unit testing
Unit testing is the process testing program components, such as method or
object classes. Individual functions or methods are the simplest type of
component. During the unit testing, we should :
Test all operations associated with the object
Set and check the value of all attributes associated with the object
Put the object into all possible states.

6.0 CONCLUSION
After the completed the CSS system analysis, we know how the flow to create a system
and contribute with the ideas and skills in order to fill the user requirements. Creating a new

complete system is not an easy task. Most of times taken are on planning the system and
implementing the programming coding. Designing can put it a lot of time and efforts too
because sometimes it may not display the same like what the design have been made.
From this project documentation, we also get to know how to make a good analysis and
know how the system is work. The good feedback from the staff department makes the
job easier. This memorial experience will give good benefit for student to be like real
worker in their field.

17

Appendix A

Data Entiti:

Pensyarah

Keterangan:

Maklumat Pensyarah

Atribut

Penerangan

Jenis

Panjang

Catitan

StaffID

Nombor Pekerja
Pensyarah

CHAR

Integrasi data
dari Sistem
STARS

Nama

Nama Pensyarah

VARCHAR

50

Integrasi data
dari Sistem
STARS

Jenis Staf

Staf UiTM / Staf

Luar UiTM

CHAR

20

Kod Kampus

Kod kampus
pensyarah
mengajar

VARCHAR

10

Data diambil
dari schema
SECURITY
table USERS

Nama Kampus

Nama kampus
pensyarah
mengajar

VARCHAR

80

Data diambil
dari schema
UITM table

18

Atribut

Penerangan

Jenis

Panjang

Catitan
CAMPUS

Kod Fakulti

Kod fakulti
pensyarah
mengajar

VARCHAR

10

Data diambil
dari schema
SECURITY
table USERS

Nama Fakulti

Nama fakulti
pensyarah
mengajar

VARCHAR

70

Data diambil
dari schema
UITM table
CAMPUS

Kod Jabatan
Hakiki

CHAR

Nama Jabatan
Hakiki

CHAR

40

Kod Jabatan
Sekarang

CHAR

Nama Jabatan
Sekarang

CHAR

40

Kod Jenis
Jawatan

A / P (Akademik /
Pentadbiran)

CHAR

Kod Status

Status terkini staf

CHAR

Status

Status terkini staf

CHAR

40

Data Entiti:

Bilik_Kuliah

Keterangan:

Maklumat Bilik Kuliah/Makmal

Atribut

Penerangan

Jenis

Panjang

Kod Bilik

VARCHAR

15

Nama Bilik

VARCHAR

80

Integrasi data
dari Sistem
STARS

Catitan
Integrasi data
dari Sistem
FMS

19

Atribut

Penerangan

Lokasi
Kapasiti

Jenis

Panjang

VARCHAR

80

CHAR

10

Data Entiti:

Tarikh/Slot

Keterangan:

Maklumat Tarikh/Slot Jadual Waktu Kuliah

Atribut

Penerangan

Jenis

Panjang

Minggu

CHAR

Hari

CHAR

20

Slot Masa
Mula

CHAR

20

Slot Masa
Tamat

CHAR

20

Tempoh

CHAR

20

Data Entiti:

Kursus

Keterangan:

Maklumat Kursus aktif

Atribut

Penerangan

Catitan

Catitan

Jenis

Panjang

Kod Kursus

VARCHAR

15

Nama Kursus

VARCHAR

200

Catitan

20

Atribut

Penerangan

Jenis

Panjang

Jam Kredit

NUMBER

OwnerID

VARCHAR

15

VARCHAR

15

Status

Active / Not Active

Data Entiti:

Data Jadual Waktu

Keterangan:

Maklumat Jadual Waktu

Atribut

Penerangan

Kategori JWK

Repeating Week /
Custom Week

CHAR

Semester

Semester semasa

VARCHAR

Kod Kampus

VARCHAR

Nama Kampus

VARCHAR

80

Kod Fakulti

VARCHAR

Nama Fakulti

VARCHAR

70

Blok Program

VARCHAR

80

Mod Pengajian

VARCHAR

10

CHAR

Kod Kursus

VARCHAR

10

Nama Kumpulan

VARCHAR

50

CHAR

Kategori Kelas

IDPensyarah

Both, Repeater, BOTH

No staff pensyarah
yang mengajar

Jenis

Catitan

Panjang

Catitan

21

Atribut

Penerangan

Bilangan
Maksimum
Pelajar

Bilangan maksimum
pelajar dalam 1
kumpulan

Jenis

Panjang

NUMBER

Kod Bilik

CHAR

Hari

CHAR

20

Minggu

CHAR

Slot Masa Mula

CHAR

20

Slot Masa Tamat

CHAR

20

Jam Mengajar

CHAR

Jenis Kumpulan Blended / none (-)

CHAR

VARCHAR

100

CHAR

40

Keterangan

Penerangan mengenai
kumpulan (jika ada)

Status

Aktif / Tidak aktif

Data Entiti:

Jejak Audit

Keterangan:

Maklumat Jejak Audit

Atribut
StaffID

Penerangan

Catitan

Jenis

Panjang

CHAR

Semester
process

VARCHAR

10

Kod Kursus

VARCHAR

15

Kumpulan

VARCHAR

50

Value New

VARCHAR

500

Catitan

22

Atribut

Penerangan

Jenis

Value Old

VARCHAR

Date Process

Panjang

Catitan

200

DATE

User PC Name

VARCHAR

150

User PC IP

VARCHAR

80

ScreenID

VARCHAR

50

Remarks

VARCHAR

500

Data Entiti:

Pentadbir

Keterangan:

Maklumat Pentadbir yang memegang jawatan di dalam Pentadbiran

Atribut

Penerangan

Kod Pentadbir

Jenis

Panjang

VARCHAR

15

Catitan

Kod Jawatan
Pentadbir

Kod jawatan
pentadbiran

VARCHAR

20

Integrasi data dari Sistem

STARS

Nama Jawatan
Pentadbir

Nama
jawatan
pentadbiran

VARCHAR

100

Integrasi data dari Sistem

STARS

Jabatan/Bahagia Penempatan VARCHAR

n/Unit/Pusat
pentadbir

100

Integrasi data dari Sistem

STARS

Jam Kredit

Nilai jawatan
pentadbir

CHAR

10

Status

Status kod
pentadbir

VARCHAR

23

Data Entiti:

Akses pengguna

Keterangan:

Maklumat akses yang diberikan bagi sistem JWK

Atribut

Penerangan

StaffID

Jenis

Panjang

VARCHAR

15

RoleID

Jenis Akses yang

diperolehi

VARCHAR

100

Status

Status Akses

VARCHAR

App ID

Jenis Aplikasi
yang diberi

VARCHAR

10

Catitan

24

Appendix B

25

Appendix C

26