45 main
activities: problem-domain
analysis, application-domain
analysis, architectural design, and component design, respectively. Each activity leads to
specific results, which are subsequently included in the analysis and design documentation Mathiassen, et.al. 2000:12.
2.11.5 Rich picture
Rich picture is an informal drawing that presents the illustrator’s understanding of a situation. A rich picture focuses on important aspects of the
situation, which are determined by the illustrator. However, the rich picture should give a broad description of the situation that enables several alternative
interpretations Mathiassen, et.al. 2000:27.
Kepala Seksi Operator
General Branch Administration GBA Lembar ketetapan rencana
anggaran biaya Memo tagihan
Computer
Input anggaran Input tagihan, cetak SPM,update status SPM
Menampilkan SPM dan laporan siap dicetak Lihat laporan
yang diperlukan
Input realisasi Input COA dan kategori COA
sesuai standar kebutuhan BTN syariah Menampilkan laporan
- pencatatan tidak lagi menggunakan aplikasi spreadsheet yang hanya
memungkinkan dipegang oleh satu pengguna.
- pada SIA pengendalian anggaran, kepala seksi operator dapat langsung
mengakses sistem untuk melihat laporan dan memvalidasi Surat
Perintah Membayar SPM. - dalam proses pencatatan no.COA
dan pembuatan SPM tidak lagi dilakukan secara manual.
- pada SIA pengendalian anggaran disertai laporan dalam bentuk grafik
yang berfungsi untuk membandingkan tingkat realisasi anggaran perbulan.
cetak laporan Validasi SPM
Figure 2.11.5.1 Example of rich picture
2.11.6 Development Cycle with OOAD
The development cycle in OOAD consist of four main steps there are:
46 1. Problem Domain analysis which analysis the current system and their
weakness 2. Application Domain Analysis which analysis the actor of the purpose system
3. Architecture design which is design the architecture 4. And last thing is component design which is allocated the design of the
system
Figure 2.11.6.1 Development Cycle OOAD Mathiassen, et.al, 2000:15
2.11.7 Main Activity of OOAD
There are four main activities that are used in Unified Software Deployment methods for OOAD Object Oriented Analysis and Design and 2
activity Mathiassen implementation based on the usual approach is also called A Traditional Top-Down Approach Based on OOAD namely Mathiassen, 2000:
1. Problem Domain Analysis 2. Application Domain Analysis
3. Architecture Design 4. Component Design
Implementation activities are: 1. Programming.
47 2. Quality Assurance
2.10.7.1 Problem Domain Analysis
Problem domain analysis is part of a context in which administered, monitored or controlled by a system. In this stage system is designed according to
the information needs from users, this step determines the overall outcome of the analysis and design activities.
The problem domain consists of: 1. Classes
Class is a description of a collection of objects that have a behavior pattern and structure of the same attributes. Abstraction, classification, and
selection is a major task in classroom activities. Class is the main objective in defining and limiting the problem domain. Class consists of class
names, attributes and operations. The name of the class is defines the class itself.
2. Structure Structure activity focused on the relationship between classless and
objects. 3. Events
Event is an instantaneous event that involves one or more objects. Event table make easier to analyze the system so that no event is overlooked in
creating a class diagram. 4. Behavior Pattern
48 Behavior pattern is a description of the event trace is possible for all
objects in the class. Event trace is a sequence of events of a particular object.
State diagrams describe the general behavior of all objects of a certain class, which consists of the parts and the transitions among them and may also explain
the usecase. Statechart diagrams describe the transition and changes the state of an object on the system as a result of stimulation received. Notation on the
behavioral pattern consists of three kinds, namely, sequence selection and iteration. Sequence is the events that occurred only once. Selection is something
that comes out of events occurring. Iteration is the events that occur zero or more.
Figure 2.11.7.1 Problem Domain Analysis Mathiassen, 2000
2.11.7.2 Application Domain Analysis
This stage focuses on how the system will be used by the user. This stage and earlier stage can be started in turn, depends on the condition of the user.
Application Domain is the organization that manages, monitor or control the problem domain. Application Domain consists of:
1. Usage
49 a. Usecase
Usage describes how the system interacts with people and systems in context. Usage consists of sequence diagrams and use case diagrams. Use
case diagram is a diagram illustrating the interaction between system and actors within the application domain. Actor is an abstraction of the user or
other systems that interact with the target system. Actor is abstraction of people and other systems that are active on the system function. A use case
is abstraction of interaction with the target system. Use cases can be activated by the actor or the target system. Complete use case that
determines all uses of the target system in the application domain. b. Sequence
Sequence diagram is an apparatus for communication interaction diagrams. An interaction between objects or systems designed to
participate in collaboration. The interaction is described by the messages placed on a time or more than two messages to be sent at the same time.
Interaction is an important communication role that fact. Some concepts can be applied in varying contexts. Sequence diagrams describe
interactions between objects with regularly according to the time. Sequence diagrams can be described in some detail levels and for different
purposes in several steps developed lifecycle. When a message is sent on an object will require an operation of the object. Message name is usually
in accordance with the operation to be requested. A message is received, the operation had been asked to carry the message. at some stage during
50 the operation carried out is referred to as activation. Activation period in
the period, including some period of time during the operation waiting for a response from the other operations that are requested will begin
immediately. 2. Function
Function is a facility to create a useful model for the actor. Function consists of complete function list. There are several types of functions include:
1. Update Function is activated by an event from the problem domain and the result is a change in the model state.
2. Signal Function is activated by a change in the model state and the result of a reaction on the context. This reaction may be a display of
the actor in the model domain. 3. Read Function is activated by a need for information on a work
assignment at the actors and the result display system associated with the model.
4. Compute function is activated by a need for information on a work assignment on the actor and consists of a calculation involving
information provided by the actor or model. The result is a display of calculation results.
3. Interface Interface is the facilities that make the models and functions available to
the actor. Results of the interfaces are user interfaces and system interfaces. The user interface is the style of dialogue and other forms of presentation, a list of
51 elements of a complete user interface, windows are selected diagrams and
diagram navigation. System interface is a class diagram for the external devices and protocols for interaction with other systems. Navigation charts are all the
windows of the user interface and dynamic relationship.
2.11.7.3 Architectural Design
In this step architectural relationship between the client and server are sufficient for the system to run correctly. The design of this stage
determines how the structure of the physical system will be created and how the distribution of the information system on the physical design. The resulting report
is a Deployment Diagram. According to Mathiassen, 2000, Activities in architectural design consist of:
a. Criteria
Criterion Measure of
Usable
Secure
Efficient Correct
Reliable The system’s adaptability to the
organizational, work-relative,
and technical contexts.
The precautions against unauthorized access to data and facilities.
The economical exploitation of the technical platform’s facilities.
The fulfillment of requirements. The fulfillment of the required precisions
in function execution.
52 Maintainable
Testable
Flexible
Comprehensible
Reusable
Portable
Interoperable The cost of locating and fixing system
defects. The cost of locating and fixing system
defects. The cost of modifying the deployed
system. The effort needed to obtain a coherent
understanding of the system.
The potential for using system parts in other related systems.
The cost of moving the system to another technical platform.
The cost of coupling the system to other systems.
b. Components Good component architecture makes a system easier to understand,
organizing the design work and reflecting the stability of the system’s
context. A class diagram describes the component architecture’s core.
53 UML’s diagram contains packages denoting components, and
dependencies between packages denoting component connection. c. Process
The process architecture brings us closer to the system’s physical level. We focus on distribution and execution, and work with processes and
objects as opposed to components and classes. We also deal with the physical devices that the system will be executed on and consider whether
we need to coordinate shared resources.
2.11.7.4 Component Design
The starting point for component design is the architectural specification and the system requirements. The result of this activity is specification of the
connected components. The component design builds on two general principles. The first is respect the component architecture; the second is adapting component
designs to the technical possibilities.
2.11.7.5 Programming
At this stage the activities undertaken already entered the stage of the design program to design a system that has been in its design.
2.11.7.6 Quality Assurance
At this stage there are two activities involved Mathiassen, 2000: 1. System testing
Testing is the process of executing an intensive program to find errors. This definition is very important because it will affect the manner of testing. Testing
54 not only to obtain the correct program, but also ensure that the program is free
of errors for all conditions.
2. Software release
At this stage of its activities is to apply the system to the end user.
2.11 Unified Modeling Language UML
