63
3.3.1. Communication
In this stage, the writer has some activities such as: problem identification, initiating the project, proposed the new system, giving
the scope of the system and using the feasibility study.
3.3.1.1. Problem Identification
In this stage the writer tries to shrink the existing problem at Informatic Engineering Major Islamic
University Syarif Hidayatullah Jakarta.
3.3.1.2. Initiating the project
After the problem is known, the writer set out to design a project that is expected to resolve existing
problems. Before starting this project, the writer also has started to determine what software will be used.
3.3.1.3. Purposing the new system
The purpose of awakening to a new system to address existing problems.
3.3.1.4. The scope of the system
The writer defines the problem and determines what is included in the system.
64
3.3.1.5. Feasibility Study
Based on Easterbrook 2004, Feasibility has some objectives, they are: to find out if a system development
project can be done, to suggest possible alternative solutions and to provide management with enough information to
know. In the feasibility study there are several aspects that must be considered as: technical feasibility, economic
feasibility, organization feasibility and operational feasibility.
3.3.2. Planning
Based on the analyse problem at Informatic Engineering, the writer plan to make a lecturing scheduling system. In which the
system will make a staff who in charge in scheduling feels easier to input the data, to process the data and to maintain the data.
3.3.3. Modelling
In building the system, the writer needs to create a model to make better understanding. A model must be capable of representing
the information that software transform, the architecture and functions that enable the transformation to occur, the features that
user desire, and the behaviour of the system as the transformation is taking place.
65
In software engineering work, two classes of models can be created:
3.3.3.1. Requirement Models
It can be called as analysis model. It represents customer request by depicting the software in three different
domains : information domain, functional domain and behavioural domain.
The writer uses requirement models to translate what the user needs such as flow chart and data flow diagram.
Using them is very useful because the user can have well understanding in system’s flow and the writer can work
easier based on the data flow and flow chart.
3.3.3.2. Design Model
It represents characteristic of the software that help practitioners to construct it effectively: the architecture, the
user interface and component level detail. Design model is very helpful because it not only
could communicate information to user who will test the software and to other who may maintain the software in the
future but also it helps to simplify program flow.
66
In this writing thesis, the writer provides Entity Relationship Diagram ERD, Genetic Algorithm GA
model and the interface of the system.
3.3.4. Construction
Kategori