web security service application by using web service and ron
Post on 03-Feb-2022
2 Views
Preview:
TRANSCRIPT
1
THESIS REPORT
WEB SECURITY SERVICE APPLICATION BY USING WEB SERVICE
AND RON SHAMIR ADLEMAN DIGITAL SIGNATURE WITH
MESSAGE DIGEST 5 ALGORITHM (CASE STUDY: FINANCE
INFORMATION SYSTEM RANCANGAN KERJA DAN ANGGARAN –
SATUAN KERJA PERANGKAT DAERAH KOTA MALANG)
By:
Galih Nabihi
107091102733
INFORMATICS ENGINEERING STUDY PROGRAM
FACULTY OF SCIENCE AND TECHNOLOGY
STATE OF ISLAMIC UNIVERSITY SYARIF HIDAYATULLAH
JAKARTA
4
STATEMENT
I HEREBY DECLARE THAT THIS THESIS IS REALLY WORKS OF MINE
THAT HAVENOT YET MADE AS THESIS SCIENTIFIC WORKS IN ANY
UNIVERSITY OR INSTITUTION.
Jakarta, November 17, 2011
Galih Nabihi
107091102733
5
PREFACE
Alhamdulillah, all of praise and grateful given to Allah SWT who poured
mercy, guidance, and helpful till arranging the Thesis Report with the title “Web
Security Service Application by Using Web Service and Ron Shamir
Adleman Digital Signature with Message Digest 5 Algorithm (Case Study:
Finance Information System Rancangan Kerja dan Anggaran – Satuan
Kerja Perangkat Daerah Kota Malang)” can be finished without any obstacle.
This thesis almost talk about Web Service and digital signature to avoid
your data from being sabotage, this main purpose for this project is to develop the
information system of RKA-SKPD Kota Malang in security side.
After one month of developing a service with digital signature using PHP
and mysql, the researcher filling the increase of his knowledge, learning a lot of
PHP coding strategy and techniques make me enjoy the software engineering field
and for better future we need better basic knowledge.
In this moment, the writer would to thanks to all of structural person that
covering this program
1. Mr. Dr. Syopiansyah Jaya Putra, M.Sis, Dean of Science Technology Faculty.
2. Mr. Yusuf Durrachman, M.Sc, MIT, The Head of Informatics Engineering
3. Mrs. Ria Hari Gusmita, M.Kom, Technical Coordinator of International Class
and My Supervisor help me a lot for the thesis.
4. Mr. Dr. Syafedi Syafei, MSi. as a first supervisor that always spare time with
patience giving a guidance, a motivation, a suggestion, and a purpose to the
writer in arranging the report.
6
I would like to say special thanks for:
1. Ayu Kharisma Maharani she give me motivation help me where I got
problems.
2. My parent, my brothers, my sisters who always give support and never let me
down.
3. Mrs. Mamita D who always help me in administration problem.
Jakarta, November 2011
Galih Nabihi
107091102733
7
LIST OF CONTENT
TITLE PAGE …………………................................................................... i
EXAM VALIDATION …………………………………..…………… .... ii
PAGE VALIDATION ………………………………………………… ... iii
STATEMENT............................................................................................... iv
ABSTRACT................................................................................................... v
PREFACE...................................................................................... ............. vi - vii
LIST OF CONTENT..................................................................................... viii - x
LIST OF PICTURE..................................................................................... xi - xii
LIST OF TABLE.......................................................................................... xiii
GLOSARRY................................................................................................. xiv
CHAPTER I INTRODUCTION
1.1 Background…………….…………….................................................. 1
1.2 Problems Identification......................................................................... 4
1.3 Problem Limitation............................................................................... 4
1.4 Purpose of Research............................................................................. 5
1.5 Benefit of
Research................................................................................................... 5
1.5.1 Academic Parts.................................................................... 5
1.5.2 Object................................................................................. 5
8
1.5.3 Writer....................................................................................... 5
1.6 Research Methodology........................................................................... 6
1.6.1 The Method of Collection Data.......................................... 6
1.6.2 Method of Development System....................................... 6
1.7 Structure of Report............................................................................... 7
CHAPTER II LITERATURE REVIEW
2.1 Basic Concept of System............................................................……. 9
2.2 System Characteristic..................................................................................
9
2.3 Web Service………………….............................................................. 10
2.4 Authentication….................................................................................... 17
2.5 Cryptography ....................................................................................... 18
2.6 Encryption............................................................................................. 19
2.7 Element of Encryption…………………............................................. 20
2.8 Digital Signature………………………............................................. 21
2.9 RSA Algorithm……………………………………………………. 24
2.10 Research Methodology…………………………………………… 25
2.10.1 Collection the Data........................................................... 25
2.10.2 Object Oriented Analysis And Design.................................... 27
2.10.3 Basic principles of Object Oriented.................................... 27
2.10.4 Concept of Object Oriented Analysis and Design (OOAD) 29
2.10.5 Rich Picture.......................................................................... 29
9
2.10.6 Development Cycle with OOAD....................................... 30
2.10.7 Main Activity of OOAD.................................................... 30
2.11 Unified Modeling Language (UML)................................................ 40
2.12 PHP…………………………………………................................ 47
2.13 MYSQL............................................................................................. 48
2.14 XAMPP……………………………………...................................... 48
2.15 Related Works…………………….................................................. 49
CHAPTER III RESEARCH METHOD
3.1.1. Collection data.............................................................................. 52
3.1.2. System Development Methodology............................................... 53
CHAPTER IV ANALYSIS AND DESIGN SYSTEM
4.1 Problem Domain Analysis………………………………………...... 56
4.1.1 Profile RKA-SKPD Kota Malang......................................... 56
4.1.1.1 A Glance with Information System RKA-SKPD Kota Malang.
56
4.1.1.2 Scope Work RKA-SKPD Kota Malang……..……. 56
4.1.2 Analysis of the existing system (RKA-SKPD Kota Malang)...59
4.1.3 Analysis the proposed system (RKA-SKPD Kota Malang).... 60
4.2 Application Domain Analysis................................................................ 92
4.4 Architectural Design........................................................................... 110
4.5. Component Design............................................................................ 113
4.6. Programming......................................................................................... 133
4.7 Quality Assurance/testing…………....................................................... 115
10
CHAPTER V CONCLUSION
5.1 Conclusion..................................................................................……... 148
5.2 Recommendation................................................................................. 148
References................................................................................................ 149
11
LIST OF PICTURE
Figure 2.3.1 Example of WSDL................................................................... 12
Figure 2.3.2 Example of xml....................................................................... 14
Figure 2.7.1: Grouping of encryption along with examples...................... 20
Figure 2.8.1 Two Bob's Lock On............................................................... 21
Figure 2.8.2 Public Key Bob ..................................................................... 21
Figure 2.8.3 Encrypt and Decrypt Message.................................................. 22
Figure 2.8.4 Encrypt digital signature in document................................ 22
Figure 2.8.5 example digital signature in document.................................. 23
Figure 2.8.6 Digital Signature in document………………….................. 23
Figure 2.8.7 Digital Signature cerficate in document……................... 24
Figure 2.10.3.1 Example of Understanding Inheritance Kitchen Equipment and
Furniture is inherited from House wares ………………….…………….. 28
Figure 2.10.6.1 Development Cycle OOA&D…………............................ 30
Figure 2.11.5.1 Example of rich picture………………………..……… 32
Figure 2.10.7.1 Activities in Problem Domain Analysis.......................... 33
Figure 2.10.2 UML clasification diagram ................................................ 42
Figure 3.1 frames of mind......................................................................... 51
Figure 4.1.2.1 Rich Picture Existing system............................................. 59
Figure 4.1.3.1 Rich Picture Proposed System.......................................... 60
Figure 4.1.3.2.1 XML Request Login Format…………………………. 63
Figure 4.1.3.2.2 XML Response Login Format…………………………. 64
Figure 4.1.3.2.3 XML Request input Format……………………………. 66
12
Figure 4.1.3.2.4 XML Response input Format………………………… 69
Figure 4.1.3.2.5 XML Request view Format……..…………………..... 72
Figure 4.1.3.2.6 XML Response view Format……………………..……. 73
Figure 4.1.3.2.7 XML Request Delete Format…….………..……………. 74
Figure 4.1.3.2.8 XML Response Delete Format..………………….…... 75
Figure 4.1.3.2.9 XML Request Edit Format…………………………… 77
Figure 4.1.3.2.10 XML Request Edit Format………………………..... 80
Figure 4.1.3.1 Class Diagram………………………………………….. 86
Figure 4.1.3.6.1 Statechart Diagram of Login Page……………………. 87
Figure 4.1.3.6.4 Statechart Diagram Management Xml……. .......... 88
Figure 4.1.3.6.6 Statechart Diagram View RKA SKPD............ ............ 89
Figure 4.1.3.6.7 Statechart Diagram Input RKA SKPD....................... 90
Figure 4.1.3.6.8 Statechart Diagram Edit RKA SKPD.......................... 91
Figure 4.1 Use Case Model Diagram……………….................................... 93
Figure 4.2.2.1 Sequence Diagram Use Case Login.................................... 101
Figure 4.2.2.2 Sequence Diagram Use Case Management XML........ 102
Figure 4.2.2.3 Sequence Diagram Use Case view RKA........................... 102
Figure 4.2.2.4 Sequence Diagram Use Case input RKA……………….. 103
Figure 4.2.2.5 Sequence Diagram Use Case edit RKA ………………….. 104
Figure 4.2.2.6 Sequence Diagram Use Case Logout……………………. 104
Figure 4.3.2.1 Window Diagram Login Form……….………………. 106
Figure 4.3.2.2 Window Diagram Home Form……………………… 107
Figure 4.3.2.3 Window Diagram management XML……...…………….. 108
13
Figure 4.3.2.4 Window Diagram management RKA………………….. 108
Figure 4.3.2.5 Window Diagram input management RKA………...…. 109
Figure 4.3.2.6 Window Diagram management edit RKA…………………. 110
Figure 4.32 Deployment Diagram web secure system………………... 113
Figure4.33 Component Diagram web secure system…………………. 114
Figure 4.4.1.1 Home Page…………….……………………………….. 115
Figure 4.4.1.2 Management XML Page………………………………. 116
Figure 4.4.1.3 Management RKA View Page……………………... 116
Figure 4.4.1.3 Management RKA Input Page…………………………... 117
Figure 4.4.2.1 Simulation Input Page………………………………… 117
Figure 4.4.3.1 Generate Key Pair…………………………………….. 121
Figure 4.4.3.2 Generate Key Pair Password……………………….. 122
Figure 4.4.3.3 Generate Key Pair File……………………………… 122
Figure 4.4.3.4 Entering Data for Key Pair………………………………. 122
Figure 4.4.3.5 Entering Valid Day Key Pair…………………………. 122
Figure 4.4.3.5 Entering Valid Day Key Pair…………………………. 123
Figure 4.4.3.6 Creating Cer File……………………………………… 123
Figure 4.4.3.7 All Output File Key Pair……………………………… 123
14
LIST OF TABLE
Table 2.15 Summary of Related Work Chart……….……………….... 51
Table 2.11.1 UML Diagram type…………………………………….. 41
Table 4.1.3.2.1 Login request data description table…………............. 64
Table 4.1.3.2.2 Login response data description table.......................... 66
Table 4.1.3.2.3 input request data description table……............................ 70
Table 4.1.3.2.4 input response data description table………..................... 73
Table 4.1.3.2.5 view request data description table …............................. 75
Table 4.1.3.2.6 view response data description table……......................... 76
Table 4.1.3.2.7 delete request data description table ……...................... 78
Table 4.1.3.2.8 delete response data description table……....................... 79
Table 4.1.3.2.9 edit request data description table ……............................ 83
Table Table 4.1.3.2.10 edit response data description table……........... 86
Table 4.1.3.2.1 Entity Class Candidates on the Web Secure system............ 88
Table 4.2.1.1 Actor Identification……………………...................... 95
Table 4.2.1.2 Use Case identification…………..................................... 95
Table 4.2.1.3 Narratives Use Case Login…………................................. 97
Table 4.2.1.4 Narratives Use Case Management RKA……….................... 97
Table 4.2.1.5 Narratives Use Case Management XML...................... 98
Table 4.2.1.6 Narratives Use Case Logout……......................................... 100
Table 4.2.3 Function List in web secure system........................................ 105
Table 4.2.1 Criteria proposed system………….................................... 111
Table 4.5 Testing Table List………………………................................... 12
15
Define of General Term
OOAD : Object Oriented Analysis and Design
UML : Unified Modeling Language
User : End Users / User Management
Black box : A new type of software testing based on the inputs,
outputs user.
SQL : Database for storing data
HTML : HyperText Markup Language
RKA – SKPD : Rencana Kerja Dan Anggaran – Satuan Kerja Perangkat
Daerah
SYMBOL DEFINITION
: Terminator
: Process
: Action / include
: Exclude
16
CHAPTER I
INTRODUCTION
1.1. Background
Information technology developed very fast, now it gives a lot of
advantages for the efficiency and affectivity for the user. The Development
information system itself developed with their support technology.
For example in the system of weather forecast application, there are a
lot of application that will take the data and use from main server, those
application could have many different flat form, the different could be in the
language , operating system and devices. This condition of course give problem
to doing synchronize data in every system.
To solve that problem, so that web service was used. Web service allow
the different devices, operating system and different application to exchange
data and information with else (Lucky, 2008)
Another problem is when someone needs to increase protection for their
data from someone who want to stole or crash their data, they need to think
some method to improve defense of their web.
One of the methods to increase the protection of the system is by using
digital signature. Digital signature technology is used to protect the data by
verifying the data and encrypt using some algorithm. Some of them are very
popular in network security, such as DES, AES, RSA and MD5. First MD5,
which is algorithm that implements one-way Hash (cannot be decrypted) this
algorithm usually used to protect our password in system.
17
Second DES (Data Encryption Standard) is algorithm that used block
of key pair with a block size of 64-bit and 56-bit key size. Previously, there is
some research done with DES which is used in archives system in hospital, this
algorithm is quite fast to process but this algorithm has been determined no
longer safe in recent years. The main cause of the problem is the key size is very
short (56-bit), and if it is compare with technology in this era it has possibility to
break it.
Third is AES (Advanced Encryption Standard) this algorithm is, AES
that related with key size become block size of 128 bits and a key size of 128,
192, or 256 bits. Literally this algorithm already fixed the weakness of DES
which related with key size that has only 56 bits max. This algorithm used in
research to become algorithm that used in digital signature to verify card of
identity republic of Indonesia. But AES is the one group of symmetric algorithm
which is only has one key of encryption that means if it still compare with RSA
which have two key encryption AES have higher possibility than RSA to be
cracked. So that way in this research writer used RSA AND MD5 algorithm to
be implemented in system.
RSA was found by Ron (R)ivert, (S)hamir and Leonard (A)dleman so
this algorithm called RSA. The security of RSA algorithm exist in the difficulty
of factoring all of big numbers become prime factor, as long the factor of prime
number still not found for factorized, the security of RSA algorithm will secure.
Bank is one company that used this method and also the consultant company
and so on used it for protect originality data of their company. So in conclusion
18
the researcher decided to used RSA and MD5 to become digital signature
algorithm in this research because RSA is the better algorithm instead of the
other algorithm that researcher already explained before and MD5 to improve
the security of the RSA algorithm.
As we know internet become the biggest place to do criminal. In this
era, it is possible that someone suddenly access to the system and crash
everything. The same condition with the finance information system of RKA –
SKPD Kota Malang, there a lot of people who interact or used the system. So
they need a new system that can authenticate the originality of the data
especially finance data in finance division.
The researcher want to minimize the possibility of the system to be
targeted for by hacker and to be sabotaged by implemented digital signature and
web service inside the system, base on previously explanation above the writer
chose the title “WEB SECURITY SERVICE APPLICATION BY USING
WEB SERVICE AND RON SHAMIR ADLEMAN DIGITAL SIGNATURE
WITH MESSAGE DIGEST 5 ALGORITHM (CASE STUDY: FINANCE
INFORMATION SYSTEM RANCANGAN KERJA DAN ANGGARAN –
SATUAN KERJA PERANGKAT DAERAH MALANG)”
19
1.2 PROBLEM IDENTIFICATION
In this research the problem identification are:
1. How to create a service (in this case web service) to interface (see, edit
and verify) the data in private network ( in this case skpd – malang
information system ) which used intranet for their security so that only
people that involved in their institution can access the databases.
2. How to implemented digital signature inside the web service instead
to verify the data from manipulation data.
3. How to Create and use two key pair to lock and open the encryption,
private (to lock the data put in server side) and public key (to decrypt
the data put in client) and also the opposite. This key pair used to take
data from intranet of SKPD malang.
1.3 PROBLEM LIMITATION
In this research Problem limitations are:
1. Digital signature only focus on MD5 and RSA algorithm to encrypt
and produce hashing code in system
2. RSA algorithm used certified as public key (.cer) in this case used
certified X509 and PKCS12 to produce public key.
3. The data which encrypted is the data that contains in the database at
archives finance system of SKPD malang.
20
1.4 PURPOSE OF RESEARCH
The purpose of this project is to create the web security service by using
web service and RSA digital signature with MD5 algorithm.
1.5 BENEFIT OF RESEARCH
1. ACCADEMIC PARTS
- To help another researcher as reference to implement and to do the same
research with another method in security to protect data.
2. Finance archives information system RKA-SKPD (Rencana Kerja Dan
Anggaran - Satuan Kerja Perangkat Daerah) malang city
- For the object itself will help to minimize the risk of system hacked.
- Establish cooperation between the Agencies and work education for
writer, so that could be used as reference to prepare workforce of more
advanced and competitive.
3. THE WRITER
- For writer will help to give knowledge in digital signature, web service
and cryptography.
- To meet one of the requirements of graduation degree (S1), Informatics
Engineering, Faculty of Science and Technology State Islamic University
Syarif Hidayatullah Jakarta.
- To introduce corporate overview required of students who will enter the
world of work according to their field and as a work experience.
21
1.6 RESEARCH METODOLOGY
Writer research methodology is divided into two steps, first gathering the
data and develops system.
1.6.1 Gathering the data
For gathering the data the writer use 3 methods as listed below:
1. Observation
Observation (observe) is a technique or approach to obtain primary data by
observing directly the object data In this Observation one researcher directly
involved with object of research (finance archives information system skpd
malang).
1. Interview
Interview is two way communications to get data from respondents. Do some
interview with stakeholder that involved in system which can give the needed
data.
3. Study Literature
In this method, the authors collected data and information by searching and
reading reference books and internet sites that can be used as a reference the
discussion in this issue (Gulo, 2002).
1.6.2 Method of Development System
Writers decided to use object-oriented systems development methods by using
(OOAD) Object Oriented Analysis Design as a method of system. Development
in this research six types of diagrams used in this study were: Statechart Diagram,
22
UseCase Diagram, Rich Diagram, Class Diagram, Sequence Diagram and
Window Diagram. OOAD consists of several main stages, there are:
1. Problem Domain Analysis.
2. Application Domain Analysis.
3. Architecture Design.
4. Component Design.
5. Programming.
6. Quality Assurance.
1.7 STRUCTURE OF REPORT
Systematic of writing is structured on 5 (five) chapters, organized as follows:
CHAPTER I: INTRODUCTION
This chapter contains background, problem identification, problem limitation,
advantages of research, research methodology and systematic of research.
CHAPTER II: LITERATURE REVIEW
This chapter contains a whole theory and concept of this research such as web
service, digital signature, cryptography and so on.
CHAPTER III: RESEARCH METOHOLOGY
This chapter contains data for analysis and steps to create the application.
CHAPTER IV: RESULT AND EXPLANATION
This chapter contains result and discussion based on research.
CHAPTER V: CONCULTION AND RECOMMENDATION
This chapter contains conclusion and suggestion based on research.
23
CHAPTER II
LITERATURE REVIEW
2.1 Definition System
The system is an interconnected group of components and works together
to achieve a common goal by accepting inputs and producing outputs in an orderly
process of transformation (O'Brien, 2005).
2.2 System Characteristics
A good system has the following characteristics (Mcleod and Schell, 2001):
1. Flexible
Although an effective system is a system that structured and well
organized, but should be flexible enough to be more easily adapted to the
circumstances that change frequently.
2. Easily Adapted
A good system should also be quickly and easily adapted to new
conditions without changing the old system and interfere with its primary
function.
3. Systematic
In order to function effectively, the existing system should be logical and
systematic, that is, the system created will not complicate the work
activities that already exist.
4. Functional
An effective system must be able to help achieve its intended purpose.
5. Simple
24
A system should be simpler so it is more easily understood and
implemented.
6. Optimal resource utilization
Well-designed system will make use of the resources of the organization
can be optimized utilization.
2.3 Web Service
Web service is a method of communication between two electronic
devices over a network.
The W3C defines a "Web service" as "a software system designed to
support interoperable machine-to-machine interaction over a network. It has an
interface described in a machine – process able format (specifically Web Services
Description Language WSDL). Other systems interact with the Web service in a
manner prescribed by its description using SOAP messages, typically conveyed
using HTTP with an XML serialization in conjunction with other Web-related
standards[6].
The Web Services Description Language (WSDL, pronounced 'wiz-del')
is an XML-based language that provides a model for describing Web services.
The WSDL defines services as collections of network endpoints, or ports. The
WSDL specification provides an XML format for documents for this purpose. The
abstract definitions of ports and messages are separated from their concrete use or
instance, allowing the reuse of these definitions [6].
A port is defined by associating a network address with a reusable binding,
and a collection of ports defines a service. Messages are abstract descriptions of
25
the data being exchanged, and port types are abstract collections of supported
operations. The concrete protocol and data format specifications for a particular
port type constitutes a reusable binding, where the operations and messages are
then bound to a concrete network protocol and message format. In this way,
WSDL describes the public interface to the Web service.
Figure 2.3.1 Example of WSDL
Service/Service: The service can be thought of as a container for a set of system
functions that have been exposed to the Web-based protocols.
Port/Endpoint: The port/endpoint does nothing more than define the address or
connection point to a Web service. It is typically represented by a simple HTTP
URL string.
26
Binding/Binding: The binding specifies the interface as well as defining the
SOAP binding style (RPC/Document) and transport (SOAP Protocol). The
binding section also defines the operations.
PortType/Interface: The <portType> element, renamed to <interface> in WSDL
2.0, defines a Web service, the operations that can be performed, and the
messages that are used to perform the operation.
Operation/Operation: Each operation can be compared to a method or function
call in a traditional programming language. Here the SOAP actions are defined
and the way the message is encoded, for example, "literal."
Message/N.A.: Typically, a message corresponds to an operation. The message
contains the information needed to perform the operation. Each message consists
of one or more logical parts. Each part is associated with a message-typing
attribute. The message name attribute provides a unique name among all
messages. The part name attribute provides a unique name among all the parts of
the enclosing message. Parts are a description of the logical content of a message.
In RPC binding, a binding may reference the name of a part in order to specify
binding-specific information about the part. A part may represent a parameter in
the message; the bindings define the actual meaning of the part. Messages were
removed in WSDL 2.0, in which XML schema types for defining bodies of inputs,
outputs and faults are referred to simply and directly.
Extensible Markup Language (XML) is a set of rules for encoding documents
in machine-readable form. It is defined in the XML 1.0 Specification produced by
the W3C, and several other related specifications, all gratis open standards [6].
27
XML's design goals emphasize simplicity, generality, and usability over the
Internet. It is a textual data format with strong support via Unicode for the
languages of the world. Although the design of XML focuses on documents, it is
widely used for the representation of arbitrary data structures, for example in web
services.
Figure 2.3.2 Example of xml
The material in this section is based on the XML Specification. This is not an
exhaustive list of all the constructs which appear in XML; it provides an
introduction to the key constructs most often encountered in day-to-day use.
(Unicode) Character
By definition, an XML document is a string of characters. Almost every legal
Unicode character may appear in an XML document.
Processor and Application
The processor analyzes the markup and passes structured information to an
application. The specification places requirements on what an XML processor
28
must do and not do, but the application is outside its scope. The processor (as the
specification calls it) is often referred to colloquially as an XML parser [6].
Markup and Content
The characters which make up an XML document are divided into markup and
content. Markup and content may be distinguished by the application of simple
syntactic rules. All strings which constitute markup either begin with the character
"<" and end with a ">", or begin with the character "&" and end with a ";". Strings
of characters which are not markup are content.
Tag
A markup construct that begins with "<" and ends with ">. Tags come in three
flavors: start-tags, for example <section>, end-tags, for example </section>, and
empty-element tags, for example <line-break />.
Element
Element is a logical component of a document which either begins with a start-tag
and ends with a matching end-tag, or consists only of an empty-element tag. The
characters between the start- and end-tags, if any, are the element's content, and
may contain markup, including other elements, which are called child elements.
An example of an element is <Greeting>Hello, world.</Greeting> (see hello
world). Another is <line-break />.
Attribute
A markup construct consisting of a name/value pair that exists within a start-tag or
empty-element tag. In the example (below) the element img has two attributes, src
and alt: <img src="madonna.jpg" alt='Foligno Madonna, by Raphael' />. Another
29
example would be <step number="3">Connect A to B.</step> where the name of
the attribute is "number" and the value is "3".
SOAP, originally defined as Simple Object Access Protocol, is a protocol
specification for exchanging structured information in the implementation of Web
Services in computer networks. It relies on Extensible Markup Language (XML)
for its message format, and usually relies on other Application Layer protocols,
most notably Remote Procedure Call (RPC) and Hypertext Transfer Protocol
(HTTP), for message negotiation and transmission. SOAP can form the
foundation layer of a web services protocol stack, providing a basic messaging
framework upon which web services can be built. This XML based protocol
consists of three parts: an envelope, which defines what is in the message and how
to process it, a set of encoding rules for expressing instances of application-
defined data types, and a convention for representing procedure calls and
responses [6].
2.4 Authentication
Authentication derived from the Greek, authentes = author, namely an action to
set something or someone is genuine. Proving originality an object is to establish
the place of origin, while to prove the authenticity of a person is with their identity
[4].
Authentication in humans depends on several factors:
A. Something the user is
An example is DNA, retina patterns, fingerprints, voice patterns,
biometrics, bio-electric signals produced by the body.
30
B. Something the user has
An example is the ID card, security token, software token and cell
phone.
C. Something the user know
Examples include passwords, PINs etc.
The first problem, prove the authenticity of documents, can be done with
watermarking and digital signature technology. Watermarking can also be used to
protect intellectual property, namely by marking the documents or the work of the
maker's signature.
The second problem is access control. A computer system is expected to can be
used only by that given the right, so that the computer system should be able to
detect and reject a user who does not have rights.
Sample access control which Authentication include :
² Using the internet banking system
² controlling the remote computer with internet
2.5 Cryptography
Cryptography derived from the Greek word which consists of Kryptos, which
means graft hidden and meaningful writing. Cryptography in general is the
science and art to maintain the confidentiality of news. In addition to these terms
as well cryptography is a science that studies mathematical techniques
31
related with aspects of information security such as data confidentiality, validity
of data, integrity bag data, and authentication data. [4]
There are four fundamental goals of science cryptography which is the security
aspect:
A. Confidentiality
It is a service used to keep the contents of the information from
anyone except the one with the authority or the secret key to unlock
or peel the information that has been encoded.
B. Data Integrity
Associated with the maintenance of the data changes illegally, for
maintaining data integrity, the system must have the ability to detect
manipulation of data by parties who are not eligible, including
insertion,
removal, and other data into the data. [4]
C. Authentication
Associated with the recognition, either in whole system as well as the
information itself, the two parties must communicate with each
other introduced themselves. Information sent through the canal
should authenticated authenticity, data content, delivery time, and
others.
D. Non- Repudiation
Efforts to prevent the denial of the transfer or creation of an
information by which to send or make
32
The process of randomization or the process being undertaken to secure a
message (called plaintext) into a hidden message (called a cipher
text) is encrypted (encryption). According to ISO 7498-2, terminology opposite
process, to convert ciphertext into plaintext, called de
descriptions (decryption). According to ISO 7498-2, more precise terminology
for this process is to decipher.
2.6 Encryption
Encryption used to compare the data or information so they cannot read by people
who don’t have permission. With data encryption your data will be encrypted with
a key. For opened the chipper text (decrypt) used another key. The key can be the
same like key that used for encryption or different. [4]
Mathematically, the process for encryption (E) can be written as:
E (M) = C
Where M is the plaintext (message) and C is the ciphertext (Encrypted message).
The process of decryption (D) can be written as:
D(C) = M
2.7 Elements of Encryption
Modern cryptographic techniques that available today can be classified as
shown in Figure [4]:
33
Figure 2.7.1: Grouping of encryption along with examples
2.8 Digital Signature
What is digital signature?
Here is an overview of the digital signature. Bob has been given 2 keys, one called
the public key and one called the private key (David Youd, 1996).
Figure 2.8.1 Two Bob's Lock On
34
Figure 2.8.2 Public Key Bob
Bob's public key available to everyone who needs it the private key saved for
himself, where that key used for lock of the data. Susan can encrypt a
message using the public key of Bob and Bob use, his private key to decrypt the
message (Figure 2.2). Anyone from bob co-worker may have access to the
massage that susan encrypt before, but without bob public key the data is not
valuable(David Youd, 1996).
Figure 2.8.3 Encrypt and decrypt message
In another case bob with his private key and the right software, Bob can
put digital signatures on documents and other data. A digital signature is a
"stamp" Bob places on the data which is unique to Bob, and is very difficult to
forge. In addition, the signature assures that any changes made to the data that has
been signed can not go undetected.
35
To sign a document, Bob's software will crunch down the data into just a
few lines by a process called "hashing". These few lines are called a message
digest. (It is not possible to change a message digest back into the original data
from which it was created.) (David Youd , 1996).
Figure 2.8.4 Encrypt digital signature in document
So Bob's software then encrypts the message digest with his private key. The
result is the digital signature.
Figure 2.8.5 example digital signature in document
Finally, Bob's software appends the digital signature to document. All of the data
that was hashed has been signed.
36
Figure 2.8.6 Digital Signature in document
So it just so happens that Susan works at the company's certificate authority
center. Susan can create a digital certificate for Bob simply by signing Bob's
public key as well as some information about Bob.
Bob Info:
Name
Department
Cubical Number
Certificate Info:
Expiration Date
Serial Number
Bob's Public Key:
Figure 2.8.7 Digital Signature cerficate in document
2.9 Ron Shamir Adleman (RSA) Algorithms
RSA is an algorithm for public-key cryptography that is based on the presumed
difficulty of factoring large integers, the factoring problem. RSA stands for Ron
37
Rivest, Adi Shamir and Leonard Adleman, who first publicly described it in
1978(Menezes, 1998).
Key Generation
Finding the large primes p and q is usually done by testing random numbers of the
right size with probabilistic primality tests which quickly eliminate virtually all
non-primes.
Numbers p and q should not be 'too close', lest the Fermat factorization for n be
successful, if p − q, for instance is less than 2n1/4
(which for even small 1024-bit
values of n is 3×1077
) solving for p and q is trivial. Furthermore, if either p − 1
or q − 1 has only small prime factors, n can be factored quickly by Pollard's p − 1
algorithm, and these values of p or q should therefore be discarded as well.
It is important that the private key d be large enough. Michael J.
Wiener showed that if p is between q and 2q (which is quite typical) andd < n1/4
/3,
then d can be computed efficiently from n and e(Menezes, 1998).
Adaptive chosen ciphertext attacks
In 1998, Daniel Bleichenbacher described the first practical adaptive chosen
ciphertext attack, against RSA-encrypted messages using the PKCS #1
v1 padding scheme (a padding scheme randomizes and adds structure to an RSA-
encrypted message, so it is possible to determine whether a decrypted message is
valid.) Due to flaws with the PKCS #1 scheme, Bleichenbacher was able to mount
a practical attack against RSA implementations of the Secure Socket
Layer protocol, and to recover session keys. As a result of this work,
cryptographers now recommend the use of provably secure padding schemes such
38
as Optimal Asymmetric Encryption Padding, and RSA Laboratories has released
new versions of PKCS #1 that are not vulnerable to these attacks(Menezes, 1998).
Magnitude scale used in the RSA algorithm:
1. p dan q Prime Number (Secret)
2. r = p * q (public)
3. m = (p – 1)(q – 1) (Secret)
4. PK (encryption key) (public)
5. SK (descryption key) (Secret)
6. X (plainteks) (Secret)
7. Y (cipherteks) (public)
Example:
p = 3 looking for e
dan q = 11 (both prime). gcd(e, 20)=1
n= p ⋅ q = 33 e= 3
m = (p – 1)(q – 1) = 20
count d public key : e, n privte key : d, n
e*d = 1 mod (m) Private key : (7, 33 )
3 * d = 1 mod 20 Public key : (3, 33 )
3 * d mod 20 = 1
= 7
X (text) = 2
Encryption (C) = 2*3(mod 33) = 8
Decryption (M) = 8*7(mod 33) = 2.
39
2.10 Message Digest 5 (MD5)
The MD5 Message-Digest Algorithm is a widely used cryptographic hash
function that produces a 128-bit (16-byte) hash value. MD5 was designed by Ron
Rivest in 1991 to replace an earlier hash function, MD4. In 1996, a flaw was
found with the design of MD5. While it was not a clearly fatal weakness,
cryptographers began recommending the use of other algorithms, such as SHA-
1 (which has since been found also to be vulnerable). In 2004, more serious flaws
were discovered, making further use of the algorithm for security purposes
questionable; specifically, a group of researchers described how to create a pair of
files that share the same MD5 checksum. Further advances were made in breaking
MD5 in 2005, 2006, and 2007. In an attack on MD5 published in December 2008,
a group of researchers used this technique to fake SSL certificate validity
(Thomas A, 1992).
ALGORITHM
MD5 processes a variable-length message into a fixed-length output of 128 bits.
The input message is broken up into chunks of 512-bit blocks (sixteen 32-bit little
endianintegers); the message is padded so that its length is divisible by 512. The
padding works as follows: first a single bit, 1, is appended to the end of the
message. This is followed by as many zeros as are required to bring the length of
the message up to 64 bits fewer than a multiple of 512. The remaining bits are
40
filled up with a 64-bit little endian integer representing the length of the original
message, in bits.
The main MD5 algorithm operates on a 128-bit state, divided into four 32-bit
words, denoted A, B, C and D. These are initialized to certain fixed constants. The
main algorithm then operates on each 512-bit message block in turn, each block
modifying the state. The processing of a message block consists of four similar
stages, termed rounds; each round is composed of 16 similar operations based on
a non-linear function F, modular addition, and left rotation. Figure 1 illustrates
one operation within a round(Thomas A, 1992).
MD5 HASHES
The 128-bit (16-byte) MD5 hashes (also termed message digests) are typically
represented as a sequence of 32 hexadecimal digits. The following demonstrates a
43-byte ASCII input and the corresponding MD5 hash:
Example:
MD5 ("The quick brown fox jumps over the lazy dog.") =
e4d909c290d0fb1ca068ffaddf22cbd0
MD5 ("")
= d41d8cd98f00b204e9800998ecf8427e
2.11 Research Methodology
41
2.11.1 Gathering The data
1. Observation
Observations are the fact-gathering technique in which systems analysts
participating or watching someone who is doing an activity to learn the system.
Observation is one of many effective data collection techniques for studying a
system (Whitten et al, 2004).
bservation has its advantages and disadvantages, the following advantages and
disadvantages of observation according to (Whitten et al, 2004):
1. Advantages of observation:
- Data are collected based on observations can be very reliable.
Sometimes observation done by verified validity of the data which
can directly see individually.
- Analysis can see what actually happened. The Complex tasks
sometimes difficult to explain with words. Through the
observation, system analyst can identify tasks that are missing or
not described accurately by the other fact-finding techniques.
Analysts can also find data describing the physical environment of
a task.
- Observations are relatively inexpensive compared to other fact-
finding techniques. Another fact-finding technique usually requires
a special time of labor and a lot of money.
2. Disadvantages of observation
42
- People usually feel uncomfortable when being watched (observed)
they may apply differently when observed.
2. Interview
Is a two-way communication to get data from respondents (Jogiyanto, 2008).
1. Advantages of interview (Jogiyanto, 2008):
- Good corporate from respondent can be happened.
- Special visual aid or other assessment tool can be done.
- Respondents who had no knowledge can be identified.
- The interviewer can filter the respondents as required.
2. Disadvantages of interview (Jogiyanto, 2008):
- Requires trained interviewer.
- Long data collection time.
- Some of respondent did not want to talk with strangers.
3. Study Literature
Is a written record of events or occasions in the past and journals in a particular
scientific field; including important documents is a reference for researchers in
understanding the object of his research. Even the literature, relevant literature is
also included in documents that support the research. All documents relating to
the research in question should be noted as a source of information (Gulo, 2002).
2.11.2 Object Oriented Concept
Object is something that always exists around us, both concrete and
conceptual. An object has a state and behavior. State an object is the object
43
conditions stated in the attribute, while the behavior of an object defines how an
object to act and react. Behavior of an object expressed in the operation.
2.11.3 Basic principles of Object Oriented
Here are some basic principles of Object-Oriented concepts (Munawar, 2005: 29):
1. Inheritance
As described above, the object is an example of a class. This has important
consequences as an instance of a class; an object has all the characteristics of
its class. This is called inheritance. Thus, the object will have any attribute
and operation derived from its class.
Figure 2.11.3.1 Example of Understanding Inheritance Kitchen
Equipment and Furniture is inherited from House wares (Munawar,
2005:29).
2. Encapsulation
The term encapsulation is often used interchangeably with
information hiding. Not all agree on the distinctions between the
two though; one may think of information hiding as being the
principle and encapsulation being the technique. A software module
House wares
Furniture Kitchen
appliance
44
hides information by encapsulating the information into a module or
other construct which presents an interface.
3. Message Sending
In object oriented systems, objects are mutually communicated
each other by sending messages. An object sends a message to
another object to perform an operation and the object that receive
will give the response to run the operation.
4. Association
Association is the relationship between objects that need each other.
This relationship can be one-way or multiple ways.
5. Aggregation
Aggregation is a special form of association that describes all parts
of an object is part of another object.
2.10.4 The Concept of Object Oriented Analysis and Design (OOAD)
Object Oriented Analysis and Design or OOA&D is a collection of general
guidelines for carrying out analysis and design. It must therefore be tailored to
your organization and project. To make our method more usable, we designed it
so that adaptations, improvements, and part substitutions would be easy to
implement.
OOA&D reflects four central perspectives on a system and its context: the
system’s information contents, how the system will be used, the system as a
whole, and the system’s components. The perspectives are connected to OOA&D
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 OOA&D (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)
UML (Unified Modeling Language) is one tools that very reliable in the
world of object-oriented system development. This is because UML provides a
visual modeling language that enable for the developer to a blue print for their
vision in the form of a standardized, easily understood and quipped with effective
mechanisms for sharing and communicate their design with others.
Table 2.11.1 UML Diagram type
Diagram Goal
Activity Procedural and parallel behavior
Class Interaction between Object. More
emphasis to the link
Component The sructure and the connection of
the component
Composite
Structure
Decomposition of a class when
runtime
Deployment Deployment / installation to the
client
Interaction
Overview
The combination of activity and
sequence diagram
55
Object Example of instance configuration
Package Hierarchical structure when
compiling
Sequence Interaction between Object. More
emphasis on the order
State
Machine
How does event change an object
Timing Intercation between object. More
emphasis on time
Use case How user interact with the system
(Resource: Munawar, 2005)
Component Diagram
Artructure Diagram
Component Diagram
Composite Structure
Diagram
Deployment Diagram
Object Diagram
Package Diagram
Diagram
Behaviour Diagram
Activity Diagram
Use Case Diagram
State Machine
Diagram
Interaction Diagram
Sequence Diagram
Communication
Diagram
Interaction Diagram
Timing Diagram
Figure 2.11.2 UML clasification diagram
56
(Resource: Munawar, 2005)
2.11.1 Use Case Diagram
Usecase diagram is a description of a system from a user perspective. Use
cases work by describing a typical interactionbetween the user of a system with its
own system through a story of how a system is used. Sequence of steps that
describe theuser with a system called a scenario. Each scenario describes the
sequence of events. Each sequence is initialized by the people, the other system,
hardware or time sequence. Three components in theuse case diagram are
actors, associations and use-case line.
Actors are the abstraction of people and system that actives the function of
the target system. Person or system can appear in multiple roles. Actors interact
with the use case but have no control over the use case. Actors usually can be user
who interacts with software or information system. But actors can be other
computer system that interacts with the software Interaction is indicated by a
straight line from one component to another component. While
the ellipse represents a use case that isan abstraction of the interaction between the
system with the actor.Use case is based on the purposes of the actor. Use
cases should be the "what" is done the software application, not the "how"
ofsoftware applications to do it. Each use case should be given aname that
says what it achieved from the interaction with theactors. Name of use
case may consist of several words and there should be no use case has the same
name.
57
Stereotype is a special model is limited to certain conditions. To realize the
stereotypes used the symbol "<<" diawalnya and closed under the symbol ">>" an
end. <<extend>> Used to show that one use case is a functional addition of
another use case if certain conditions or requirements are met. While <<include>>
used to describe the use case that was entirely the functionality of another use
case. Usually <<include>> is used to prevent copying of a use case because it is
often used.
Each use case should be described in a document called the document flow
of event. This document defines what should be done by the system when the
actors to enable the use case. The structure of the document use case can very, but
generally this description should at least contain ( Munawar , 2005);
- Brief Description
- Actor who involved
- Precondition the importance thing for the use case to start
- Detail description of the flow event that include:
o Main flow of the event specified can be divided into:
- Sub Flow
o Alternative Flow
- Post condition which describes the state of the system after the use case ends.
2.11.2 Class Diagram
Class diagrams describe the static interaction between classes that occur in
the system. The main component in the class diagram is the class itself. Class
diagrams are helpful in visualizing the class structure of a system. This is because
58
the class is a description of the structure of an object with properties, behavior and
the same relation. Besides class diagrams can provided a global view of a system.
This is reflected in the classes that have relationship with one another.
2.11.3 Activity Diagram
Activity diagrams model the workflow a business process and sequence of
activities in a process. This diagram is very similar to the flow chart because we
can model the logic procedures, business processes and workflow. The main
deference is the flow chart created to describe the workflow of the system, while
the activity diagram is made to describe the activity of the actor. As already
discussed in the first part of this case study, by modeling the activity diagram in
advance would be very helpful in understanding the overall business process.
Activity diagram are also very useful in describing the behavior of parallel or
explain how the behavior of the various use cases interact.
2.11.4 Sequence Diagram
Sequence diagrams are used to describe the behavior in a scenario. This
diagram shows a number of object instances and message (the message) that is
placed between these objects in a use case. The main component sequence
diagrams consist of objects specified with rectangular boxes called. Message is
represented by lines with arrows and the time indicated by vertical progress.
2.11 .5 Collaboration Diagram
Collaboration diagram is an extension of the object diagram collaboration
diagrams show the object-message sent to one another. This type of diagram
emphasizes the relationship between object, while the sequence diagram
59
emphasize the sequence of the event. In the collaboration diagram there are
several object links and message. Collaboration diagrams are used as a tool to
describe interaction that reveals the decision regarding the behavior of the system
2.11.6 Statechart Diagram
Statechart diagrams show the possible state-state of an object, an
event that can detect and respond to these events. In general, the detection of an
event can cause an object moves from one state to another state. This is called
a transition.
2.11.7 Component Diagram
Component diagrams illustrate the allocation of all classes and object into
components in the physical design of the system software. This diagram shows
the arrangement and dependencies between software and components, such as
source, code, binary code, and executable components. We can create one or more
component diagrams to describe or explain the component and the package
contents of the package component.
2.11.8 Deployment Diagram
Deployment diagrams show the layout of a physical system,
exposing parts of the software running on hardware parts. The main part
of hardware / hardware is a node, which is the common name for all types
of computing resources. There are two types of nodes are possible. Processor is a
node that can execute a component, while the device is not. Device is a hardware
device ( such as printer or monitor) typically becomes an interface with the
outside world. Node containing the artiface where the artifact is a physical
60
manifestation of the software, usually files. These files are usually executable
(such as EXE file , binner , JAR , assembly or script), or data files, configuration
files , HTML document and others.
2.12 PHP
PHP stands for Hypertext Preprocessor is server side scripting
programming language, programming language used by the web server to
generate HTML documents on-the-fly. PHP is an interpreter that can be executed
as a program Common Gateway Interface (CGI) for web server or used as a
module of the web server. PHP is a widely-used general-purpose scripting
language that is especially suited for Web development and can be embedded into
HTML.
PHP is already available on almost any network operating system that
provides web server, especially apache web server. Non apache windows based
has also been supported, such as IIS, PWS or Xitami, from windows 98/ME to
Windows NT 4 / 2000 and XP. Portability of applications developed using PHP is
easier, and requires no changes to application source code. Portability is one of the
key of php. Portability is the software codebase feature to be able to reuse the
existing code instead of creating new code when moving software from an
environment to another. The pre requirement for portability is the generalized
abstraction between the application logic and system interfaces. When one is
targeting several platforms with the same application, portability is the key issue
for development cost reduction, for instance, from windows to linux or vice versa.
61
This is because of convenience portability PHP on all platforms (Sidik, 2005:323-
325).
PHP is a server-side scripting language that allows your Web site to be
truly dynamic (Elizabeth, et.al, 2005).
There are four kinds of couples PHP tags that can be used to mark blocks
of PHP scripts, namely (Peranginangin, 2006):
1. <?php…?>
2. <script language = “PHP”>…</script>
3. <?...?>
4. <%...%>
2.13 MYSQL
MySQL is a database management system that is open source. MySQL is
a couple of PHP. MySQL created and developed by MySQL AB in Sweden.
MySQL can be used to create and manage a database and its contents. MySQL
can be used to add, modify, and delete data that resides in the database. MySQL is
a database management system that is relational. This means that data is managed
in the database will be placed on separate tables so that some data manipulation
will be faster. MySQL can be used to manage databases ranging from small to
large. MySQL can also run commands Structured Query Language (SQL) to
manage relational databases in it (Ramadan, 2006).
2.14 XAMPP
XAMPP is software which is used to run a website based on PHP and
using MYSQL data processing on the local computer. XAMPP act as a web server
62
on the computer. XAMPP can also be called a virtual server Control Panel which
helps us to do a preview so that it can modify the web site without having to
online accessible to the internet (Wicaksono, 2008).
2.15 Related Works
There are many studies has been done in related to this topics in adition to
support this research there are:
Rahmawati(2007), title of her research Aplikasi Digital Signature Sebagai
Autentikasi Pada Kartu Tanda Penduduk , finding the system that will autenticate
the identity card for manipulated, used java and used SDLC strutured,
recommendation try to used web based system that will improved the performance
the system.
Other researher is Adharawati (2010), titled Penerapan web service
sebagai alat pengendalian biaya, finding manipulating budget trough different
platform as web based system, used qualitative approaches method,
recommendation can have function for upload the phical file.
Other researcher is Ramadan (2009), titled Aplikasi digital signature
sebagai sistem pengarsipan rumah sakit, finding autentication system to hospital
file that will keep the data in original version, recommendation used web base to
support system better.
Other researcher is Hartono (2009), title of research Penerapan teknologi
web services pada prototype layanan informasi lowongan pekerjaan secara online,
,finding intergrated with multi platform data, remocemdation used password to
improve the web service.
63
Other researcher is Rianto (2007), Implementasi Web Service Untuk
Menambah dan Mengurangi Service Pada Web Service Lain, finding intergrated
with multi platform data system can give effect to anther syetm via web service,
recommendation used simple algorithm to encrypt data that send via xml.
Other researcher is Pratama (2008), Implementasi Digital Signature Pada
Sistem Keamanan Mobile Banking, finding intergrated with multi platform data in
moble divice, recommendation used simple algorithm to encrypt data that send via
xml.
Table 2.15 Summary of Related Work Chart
No Literatur Metode Tools Weakness System offered
1 Aplikasi Digital
Signature Sebagai
Autentikasi Pada Katu
Tanda Penduduk (Desi
Ramayanti, 2007)
Terstruktur/
Waterfall
Java Use AES Algorithm
because in this eras
technology develop
very well we
actually we can use
better algorithm to
protect it
in terms of features, the
proposed
system provides a report in
the form of graphs that
can show the
event rate difference in the
number of variance or a
larger budget than the
budgeted cost.
2 Penerapan web service
sebagai Alat
Research usin
g qualitative a
PHP,MYSQ
L
Results of
the study is
Was applied by
utilizing information tech
64
Pengendalian Biaya
(Athena Adharawati,
2010)
pproaches only a theory
of how the
F maliputi budget b
ut not
yet implemented by
utilizing informatio
n technology
nology by using the
tools ofxampp, Dreamwe
aver
8, Star UML and Ms.Visi
o. With the PHP
programming language.
3 Aplikasi Digital
signature sebagai
autentikasi system
pengarsipan rumah
sakit ( Ramadan , 2009
)
SDLC PHP
MYSQL
Still used old
algorithm DES that
can be creaked now
System that will
intergrated even they
have different platform.
4. Penerapan teknologi
web services pada
prototype layanan
informasi lowongan
pekerjaan
secara online(HARTO
NO,2009)
SDLC C#, SQL
SERVER
System tranfer data
via xml and it is not
encrypted
System that will
intergrated even they
have different platform.
5. Implementasi Web
Service Untuk
Prototyping VB Data that transfer
via xml not
System can effect
another service in
65
Based on all related work above researcher want to make a system that integrated
between web service and digital signature, so beside the system can integrated
with multi platform application they can also can authenticated data that need to
be checked in this case RKA – SKPD Kota Malang.
Menambah dan
Mengurangi Service
Pada Web Service
Lain(Andi
Rianto,2007)
encrypted different system
6. Implementasi Digital
Signature Pada Sistem
Keamanan Mobile
Banking (Ramadani
Pratama ,2008)
Prototyping JAVA Still used AES
algorithm
Moblie banking system
66
CHAPTER III
RESEARCH METHOD
In conducting the research, researchers used two steps of research,
gathering the data and methods of systems development. Each step fulfilled by
particular methods. Those methods are described in figure 3.1.
Gathering The Data
Development
System
Result
Field Research
Observation
Interview
Object Oriented Analysis And
Design (Mathiassen, et.al, 2000)
Problem Domain
Analysis
Profile of RKA-
SKPD Kota Malang
Analysis The
System that already
runing
Analysis The
proposed system
Application
Domain Analysis
Usecase Diagram, Sequence
Diagram, Function list, Windo
Diagram
Architectural
Design
Criteria design and deployment
diagram
Component
Design
Programing
Quality Assurance
Component
Diagram
Spesification hardware and
sofware , testing system
Recomendation
End
Start
Create core
digital
signature
Databases
and
aplication
Web
service
Figure 3.1 frames of mind
3.1 Gathering the data
Gathering the data is a stage in the research process is important, because
only by getting the right data then the research process will continue until
67
investigators get answers from the formulation of a problem that has been
determined.
For gathering the data researcher used tree methods observation, literature study
and interview.
3.1.1 Literature Study
Working on literature review and study by reading books as listed bellow:
1. Systems Analysis and Design (Mathiassen, et.al., 2000) and (wiritern, baley
2009) and writer get an overview about OOAD (object oriented analysis and
design).
2. Human Resources Development book for suitable interface for customer.
3. Programming books about php and mysql integration
4. Software Engineering books and books that support the discussed topics in the
preparation of this research.
5. Websites rosihanari related to php programming and mysql integration with
web service.
6. http://library.nu there a lot of e-book that related to RSA algorithm and
cryptography
3.1.1 Observation Method
The purpose of this observation is to know the weakness and requirement that
current system needed in this case (RKA-SKPD MALANG). The observation
68
was done by 1 mei – 30 mei 2011. The researcher observed the system of RKA-
SKPD Kota Malang and sees the function one by one.
3.1.2 Interview
This method of collecting data involves presentation or oral-verbal stimuli and
reply in terms of oral-verbal responses. The purpose of this interview is to know
more detail about current system. There are two interviews in general as follows:
1) Personal Interviews with the developer of this project related to
finance archives system RKA-SKPD Kota Malang in this case Mr
syafedi syafei.
2) Writeable document from the system that includes more technically
aspects from finance archives system RKA-SKPD Kota Malang.
3.2 System Development Methodology
There are four main OOAD activities that are using in this research
1. Problem Domain Analysis
At this stage, writer gives explanation about previous system that
already running, the system is archives system RKA-SKPD Kota Malang,
analysis behavior and characteristic of the system that already running in a
rich picture, also described is a system proposed in the form of rich
picture, class diagrams, database structure, CRUD matrix and State chart
diagrams.
2. Application Domain Analysis
At this stage describes how the system that researcher purposed to
RKA-SKPD Kota Malang (secure web system) will be used, including
69
usage. And also determine how the system interacts with people (actors)
and other systems in the function. And explain how the designs of the
system can verify the data from network.
Stages of the Application Domain Analysis are described in the
form of use case diagrams, sequence diagrams, function list and diagram
window.
3. Architectural Design
At this stage will be explained the. Architecture Design In the
design criteria contained in the web secure system (proposed system) in
table of criteria and will be described web secure system in the layout of a
physical system, exposing parts of the software that runs on parts of the
hardware components of what is required in the that data will be show in
deployment diagrams.
4. Component Design
Purpose of this phase is to determine an implementation of requirements
within an architectureal framework of web secure that offered. Build a
model compnenet and function component from existing class diagram.
5. Programming
At this stage will be included coding of the programs that has been design.
Coding was made in the PHP programming language and integrated it
with mysql
70
6. Quality Assurance
At this stage it is described on the specifications of the hardware
and software needed. In Addition, system testing also done with black-box
testing method, where the authors perform data input the system and sees
its output as expected. The black-box testing focusing on user oriented
71
CHAPTER IV
ANALYSIS AND DESIGN SYSTEM
4.1 Problem Domain Analysis
4.1.1 Profile RKA-SKPD Kota Malang
4.1.1.1 A Glance with Information System RKA-SKPD Kota Malang
Local government finance system is part of the public sector’s financial
system, which records and report all financial transaction relating to area. Called
regional financial is all the rights and obligations in the area of local government
framework that can be valued in money, including all forms of property-related
right and obligations of the area.
The scope of state finances are managed directly by Central Government is
Revenue and Expenditure Government Budget (APBN), and directly managed by
Regional Government is Revenue and Expenditure Regional Budget (APBD).
Both the Government and Regional Budget is a basic of government financial
accounting. Therefore, the position of government and regional budget in the
financial administration and accounting of government is essential.
Government and regional budget is a plan of government activity that
expressed in units of money and includes spending plans.
After released package of state finance law no. 17-2003 on government
finance, law no. 1 of 2004 on government treasury, law no 15 of 2004 on audit of
the management and financial responsibility of government, then government of
financial information that including Central and regional Government is equipped
72
with balance sheet information, statement of cash flows, notes to the financial
statement, along with information about the realization report APBN/APBD.
Government financial reporting should refer to the government accounting
standards as set out in regulation 24 of 2005.
Furthermore, in the PP. 58 of 2005 on Financial Management, the
Government should set up an accounting system that is regulated by the Regional
Head. Local government financial accounting system is a system of accounting to
record, classify, analyze, summarize and report financial transactions undertaken
by the Government in implementation of the budget.
4.1.1.2 Scope of work RKA-SKPD Kota Malang
At the Regional Finance Unit Malang there are two financial systems that
have been used, namely the first application system to produce local budget and
the budget, and the second application system called SIKPD (Regional Financial
Management Information System) that serves to process financial data on the
stages of implementation, administration, accountability and supervision.
At the planning stage, application system has been applied to RAPBD and
APBD, but the previous manufacturing process of SKPD RKA-implemented
system using excel, RKA-SKPD the data is then manually re-entry by the Finance
Department.
Furthermore, the task force agreed that the PROV-SUM SIMKEU SCBD
Financial Information System (SIMKEU) is implementing manufacturing
information systems RKA-SKPD. RKA-SKPD system where there are also
systems SAB as a reference in determining the cost components.
73
This in order to better understand and apply the ASB as one of the principal
instruments of performance-based budgeting as required by various rules and
regulations concerning the Regional Financial Management Guidelines (PKD),
like the PP. 105 of 2000 on Regional Financial Management and accountability,
PP. 58 of 2005, Permendagri No. 13 of 2006 which improved to No. Permendagri.
59 2007 on PKD.
4.1.2 Analysis the existing system (RKA-SKPD Kota Malang)
Financial SKPD application system can be described as follows:
Input rekening
Budget Input
Input, edit, delete RKA
Display Report and print
VPN (Virtual Private
Network)
provisions of the budget
plan sheet
Figure 4.1.2.1 Rich Picture Existing system
Base on Analysis system of RKA –SKPD Malang above there are some
aspects that still can be improved, there are:
1. Their application still work in vpn(virtual private network)
,means the application only can be accessed internal only. The
researcher want to improve for accessed from public network.
74
2. for the developer want to improve their security of this
program
Researcher want to used web service and digital signature to
increase security of their web.
Web service used for bridge the data from vpn (intranet system RKA
malang) and public network, in this case our system. And also add digital
signature the system of RKA – Malang can be accessed more secure in
public.
4.1.3 Analysis the proposed system.
Based on the problems that arise, the system is still in development stage
and still needs improvement on a system that already running, to improve the
security of the system itself.
Input rekening
Budget Input
Input, edit, delete RKA
Display Report and print
VPN (Virtual Private
Network)
provisions of the budget
plan sheet
Web ServiceWeb Secure
Applicationrequest request
response response
Figure 4.1.3.1 Rich Picture Proposed System
4.1.3.1 Three main parts in this system.
1. Web service page (in this case server for services).
75
Web service page provide service for all function which connected with
internal database RKA SKPD Kota Malang, and as explained above, this
module can bridge between intranet RKA SKPD Kota Malang and public
network.
2. XML
The Way to communicate or exchange the data between server (web service)
and client is a XML (Extensible Markup Language).
There some response code in XML that represents process in system there are:
1. SS, description Success (No error and valid signature)
2. IS, description Invalid Signature (if signature have problem)
3. IP, description Invalid Password/username (work in login form if
password/ username invalid).
4. LG, description Length Problem (if there is problem in inputting length
parameter).
5. IE, description Insufficient Element (if you forget to input mandatory
parameter in system).
In client Side XML file that generate is request XML and in server side XML file
that generate in response XML, The example of those XML can see bellow:
4.1.3.2 XML FORMAT
In example of XML request we can see their 3 main parts, there are:
1. Method ID
Show and called which function in web service that we want to used.
2. Content
76
Contain with all data that we want to transfer.
3. Signature
Contain Data that already encrypt in system.
In example of XML response we can see their 4 main parts, there are:
1. Method ID
Show and called which function are in web service that we want to use.
2. Content
Contain with all data that we want to transfer.
3. Response
Contain code and description that represent the result of executing
function.
3. Signature
Contain Data that already encrypt in system.
1. XML Login Request Format:
77
<? Xml version="1.0"?>
<MethodCall>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Username>username</Username>
<Pass>password</Pass>
</Content>
<Signature>
<Data>Data</Data>
</Signature>
</MethodCall>
Figure 4.1.3.2.1 XML Request Login Format
2. XML Login Data Description:
No Name Type Status Description
Method ID
1. Name String Mandatory Method Name ( used to
which function called in
service)
Content
78
2. Username String Mandatory Username Format :Md5
Length : 30 (max)
3. Password String Mandatory Password Format : Md5
Length : 30 (max)
Signature
4. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.1 Login request data description table
3. XML Response Login Format:
79
<? Xml version="1.0"?>
<ResponseMethod>
<Content>
<Username>username</username>
<Pass>password</pass>
</Content>
<Response>
<Code>Code</Code>
<Description>Description</
Description>
</Response>
<Signature>
<Data>Data</Data>
</Signature>
</ResponseMethod>
Figure 4.1.3.2.2 XML Response Login Format
4. XML Login Response Data Description:
No Name Type Status Description
Content
1. Username String Mandatory Username from request
XML sender
2. Password String Mandatory Password from request
XML sender
Response
3. Code String Mandatory Response Code
Length : 2 (Fixed)
80
4. Description String Mandatory Response Description
Length : 50 (max)
Signature
5. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.2 Login response data description table
5. XML Request Input Format:
81
Figure 4.1.3.2.3 XML Request Input Format
6. XML Input Request Data Description:
No Name Type Status Description
Method ID
1. Input String Mandatory Method Name ( used to
which function called in
service)
Content
2. Urusan String Mandatory Purpose the activity
Length : 30 (max)
3. Organisasi String Mandatory Organisation which
82
involved with the
activity
Length : 30 (max)
4. Program String Mandatory Activity that will be
done
Length : 30(max)
5. Kegiatan String mandatory List of activity
Length : 30(max)
6. Tahun Numeric Mandatory Year of program being
held
Length : 4(fix)
7. Lokasi
Kegiatan
String Mandatory Location of program
being held
Length : 30(max)
8. N-1 Numeric Mandatory Budget previous year
(year -1 )
Length: 12(max)
9. N Numeric Mandatory Budget in current year
Length: 12(Max)
10. N+1 Numeric Mandatory Budget in next year
Length: 12(Max)
11. Capaian
Program
String Mandatory Target of Program
Length : 30 (Max)
83
12. Capaian
Program 2
String Mandatory Target of Program
detail
Length: 30 (Max)
13. Masukan 2 Numeric Mandatory Incoming budgeting for
program being held
Length: 12(max)
14. Masukan String Mandatory Description incoming
budgeting
Length : 30(max)
15. Keluaran String Mandatory Description out coming
budgeting
Length: 30(max)
16. Keluaran 2 String Mandatory Detail Description out
coming budgeting
Length: 30(max)
17. Hasil String Mandatory Result of activity
Length: 30(max)
18. Hasil 2 String Mandatory Detail result of activity
Length: 30(max)
Signature
19. Data String Mandatory Data signature create by
sender system to
identify that the
84
massage is valid
Table 4.1.3.2.3 input request data description table
7. XML Response Input Format:
Figure 4.1.3.2.4 XML Response Input Format
8. XML Input Response Data Description:
No Name Type Status Description
Content
1. Urusan String Mandatory Purpose the activity
Length : 30 (max)
2. Organisasi String Mandatory Organisation which
involved with the
85
activity
Length : 30 (max)
3. Program String Mandatory Activity that will be
done
Length : 30(max)
4. Kegiatan String mandatory List of activity
Length : 30(max)
5. Tahun Numeric Mandatory Year of program being
held
Length : 4(fix)
6. Lokasi
Kegiatan
String Mandatory Location of program
being held
Length : 30(max)
7. N-1 Numeric Mandatory Budget previous year
(year -1 )
Length: 12(max)
8. N Numeric Mandatory Budget in current year
Length: 12(Max)
9. N+1 Numeric Mandatory Budget in next year
Length: 12(Max)
10. Capaian
Program
String Mandatory Target of Program
Length : 30 (Max)
11. Capaian String Mandatory Target of Program
86
Program 2 detail
Length: 30 (Max)
12. Masukan 2 Numeric Mandatory Incoming budgeting for
program being held
Length: 12(max)
13. Masukan String Mandatory Description incoming
budgeting
Length : 30(max)
14. Keluaran String Mandatory Description out coming
budgeting
Length: 30(max)
15. Keluaran 2 String Mandatory Detail Description out
coming budgeting
Length: 30(max)
16. Hasil String Mandatory Result of activity
Length: 30(max)
17. Hasil 2 String Mandatory Detail result of activity
Length: 30(max)
Response
18. Code String Mandatory Response Code
Length: 2(fix)
19. Description String Mandatory Response Description
Length: 50 (max)
87
Signature
20. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.4 input response data description table
9. XML View Request Data Format:
Figure 4.1.3.2.5 XML Request View Format
10. XML View Request Data Description:
No Name Type Status Description
Method ID
88
1. Name String Mandatory Method Name ( used to
which function called in
service)
Content
2. Page Numeric Mandatory Page of the data
Length : 5 (max)
Signature
4. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.5 view request data description table
11. XML View Response Data Format:
Figure 4.1.3.2.6 XML Response View Format
12. XML View Response Data Description:
89
No Name Type Status Description
Content
1. Numpage Numeric Mandatory Number page of data
Length : 5 (max)
2. Page Numeric Mandatory Page of data
Length : 5 (max)
3. Id Alfa
Numeric
Mandatory Id skpd
Length : 30(max)
4. Skpd String mandatory Detial activity of skpd
Length : 30(max)
5. Program Numeric Mandatory Program of skpd
Length : 4(fix)
6. Kegiatan String Mandatory Activity being held
Length : 30(max)
Response
18. Code String Mandatory Response Code
Length: 2(fix)
19. Description String Mandatory Response Description
Length: 50 (max)
Signature
20. Data String Mandatory Data signature create by
sender system to
identify that the
90
massage is valid
Table 4.1.3.2.6 view response data description table
13. XML Delete Request Data Format:
Figure 4.1.3.2.7 XML Request Delete Format
14. XML Delete Request Data Description:
No Name Type Status Description
Method ID
1. Name String Mandatory Method Name ( used to
which function called in
service)
Content
91
2. Idrka Numeric Mandatory Number of id rka
Length : 5 (max)
Signature
4. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.7 delete request data description table
15. XML Delete Response Data Format:
Figure 4.1.3.2.8 XML Response Delete Format
16. XML Delete Response Data Description:
No Name Type Status Description
Method ID
1. Name String Mandatory Method Name ( used to
which function called in
service)
Content
92
2. Idrka Numeric Mandatory Number of id rka
Length : 5 (max)
Response
3. Code String Mandatory Response Code
Length: 5(max)
4. Description String Mandatory Response Description
Length: 50(Max)
Signature
5. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.8 delete response data description table
93
17. XML Request Edit Format:
Figure 4.1.3.2.9 XML Request Input Format
18. XML Input Request Data Description:
No Name Type Status Description
Method ID
1. Edit String Mandatory Method Name ( used to
which function called in
service)
Content
2. Urusan String Mandatory Purpose the activity
Length : 30 (max)
94
3. Organisasi String Mandatory Organisation which
involved with the
activity
Length : 30 (max)
4. Program String Mandatory Activity that will be
done
Length : 30(max)
5. Kegiatan String mandatory List of activity
Length : 30(max)
6. Tahun Numeric Mandatory Year of program being
held
Length : 4(fix)
7. Lokasi
Kegiatan
String Mandatory Location of program
being held
Length : 30(max)
8. N-1 Numeric Mandatory Budget previous year
(year -1 )
Length: 12(max)
9. N Numeric Mandatory Budget in current year
Length: 12(Max)
10. N+1 Numeric Mandatory Budget in next year
Length: 12(Max)
11. Capaian String Mandatory Target of Program
95
Program Length : 30 (Max)
12. Capaian
Program 2
String Mandatory Target of Program
detail
Length: 30 (Max)
13. Masukan 2 Numeric Mandatory Incoming budgeting for
program being held
Length: 12(max)
14. Masukan String Mandatory Description incoming
budgeting
Length : 30(max)
15. Keluaran String Mandatory Description out coming
budgeting
Length: 30(max)
16. Keluaran 2 String Mandatory Detail Description out
coming budgeting
Length: 30(max)
17. Hasil String Mandatory Result of activity
Length: 30(max)
18. Hasil 2 String Mandatory Detail result of activity
Length: 30(max)
Signature
19. Data String Mandatory Data signature create by
sender system to
96
identify that the
massage is valid
Table 4.1.3.2.9 edit request data description table
19. XML Response Input Format:
Figure 4.1.3.2.10 XML Response Edit Format
20. XML Edit Response Data Description:
No Name Type Status Description
Content
1. Urusan String Mandatory Purpose the activity
Length : 30 (max)
2. Organisasi String Mandatory Organisation which
involved with the
97
activity
Length : 30 (max)
3. Program String Mandatory Activity that will be
done
Length : 30(max)
4. Kegiatan String mandatory List of activity
Length : 30(max)
5. Tahun Numeric Mandatory Year of program being
held
Length : 4(fix)
6. Lokasi
Kegiatan
String Mandatory Location of program
being held
Length : 30(max)
7. N-1 Numeric Mandatory Budget previous year
(year -1 )
Length: 12(max)
8. N Numeric Mandatory Budget in current year
Length: 12(Max)
9. N+1 Numeric Mandatory Budget in next year
Length: 12(Max)
10. Capaian
Program
String Mandatory Target of Program
Length : 30 (Max)
11. Capaian String Mandatory Target of Program
98
Program 2 detail
Length: 30 (Max)
12. Masukan 2 Numeric Mandatory Incoming budgeting for
program being held
Length: 12(max)
13. Masukan String Mandatory Description incoming
budgeting
Length : 30(max)
14. Keluaran String Mandatory Description out coming
budgeting
Length: 30(max)
15. Keluaran 2 String Mandatory Detail Description out
coming budgeting
Length: 30(max)
16. Hasil String Mandatory Result of activity
Length: 30(max)
17. Hasil 2 String Mandatory Detail result of activity
Length: 30(max)
Response
18. Code String Mandatory Response Code
Length: 2(fix)
19. Description String Mandatory Response Description
Length: 50 (max)
99
Signature
20. Data String Mandatory Data signature create by
sender system to
identify that the
massage is valid
Table 4.1.3.2.10 edit response data description table
3. Digital Signature
Digital Signature usually adds inside XML file format that already want
to send. With this system can be more secure. In this case Researcher
using RSA algorithm to protect their data. Researcher used two key in
encrypting the system there are:
1. .key (private key, used to encrypt the massage that wants to transfer).
2. .cer (public key, used to decrypt the massage that already sends).
4.1.3.1 Basic Needs System
Here are the basic needs that must be met by the system to be designed:
- User Needs
In a secure web system users can log in and have the authority in running
the system. Therefore that user can do, including the following:
1. Input Data
In this case user can input the data to database in server with form input.
2. View Data
In this case user can view data which needed in server.
3. Edit Data
100
In this case user can update the data from server database.
4. Management XML
In this case user can see the log XML that processed in system.
4.1.3.2 Modeling the clasess
This class modeling shows that there are classes in the web secure
system. Here are the candidates who obtained the entity classes based on needs of
analysis RKA-SKPD Kota Malang:
Table 4.1.3.2.1 Entity Class Candidates on the Web Secure system
No Needs Class Entity
1. User can perform data
management RKA such as add,
view and modify data.
user,RKA
2. User can perform converting
data into XML file
user, xml
3. User can add digital signature
inside XML file.
user , signature
4. User can perform searching data User, search
5. User can perform to see log of
xml
User, log
101
4.1.3.3 Class Diagram
Class diagrams describe classes of objects that make up a system and
also the relationship between object classes that occur in web secure system.
Figure 4.1.3.1 Class Diagram
4.1.3.6 Statechart Diagram for the Proposed System
Statechart diagrams describe the specification of sequences of state caused by the
sequence of events that exist in secure web system.
102
1. Statechart Diagram Login Page Web Secure system
Start
Display the login page
Display Error
Message
Verify in Server
Open The Aplication
Input username and password
Invalid Signature / Error Happend
Repeat Login
End
Generate Digital
Signature & XML file
Display The Home
Page
Send XML file to server
Signature True/No error
Figure 4.1.3.6.1 Statechart Diagram Login Page
In Statechart Diagram Figure 4.1.3.6.1 users make the event open the application,
and then the state will display the login page. Then the user logs in by entering
your username and password correctly in order to go to the page Web secure. If
the username or password is entered incorrectly, the state would display an error
message and asks the user to repeat the login. If the username and password is
103
entered correctly, then the state will display the user's home page in according to
the authentication.
4. Statcechart Diagram Management Xml
Start
Display Super
Admin Home
Page
Display Xml
Process
Display Logout
Menu
Login As Super Admin
Chose Logout Menu
End
Display Management
Xml Module
Chose Management Xml Module
Xml Show in text
Figure 4.1.3.6.4 Statechart Diagram Management Xml
In Statechart Diargam Figure 4.1.3.6.4 user perform event, login,then the state
will display the home page for the Super Admin. The Super Admin select event
management xml menu and the state will display xml process log in system.
5. Statcechart Diagram View RKA-SKPD
104
Start
Display Home
Page
Display View RKA
Form
Verify in Server
Display data in
table
Display logout
End
Login
Chose View RKA
Generate Digital Signature And XML
Valid Signature
Chose Logout Menu
Display Error
Page
Repeat View
Invalid Signature
Figure 4.1.3.6.6 Statechart Diagram View RKA SKPD
In Figure 4.1.3.6.6 Statechart Diagram user performs event login, and then the
state will display the user's home page. To perform a view command, then state
will process the data and generate the signature from data that already prepare to
send and go to next step convert it into XML file Event select the logout menu
made to exit the state system and the system will display the message out.
6. Statcechart Diagram Input RKA-SKPD
105
Start
Display Home
Page
Display View RKA
Form
Verify in Server
Display data in
table
Display logout
End
Login
Chose View RKA
Generate Digital Signature And XML
Valid Signature
Chose Logout Menu
Display Error
Page
Repeat Input
Invalid Signature
Display Input RKA
Form
Chose Input RKA Menu
Figure 4.1.3.6.7 Statechart Diagram Input RKA SKPD
In Figure 4.1.3.6.7 Statechart Diagram user performs event login, and then the
state will display the user's home page. To perform a input command, then state
display the input page and user input the data , then state will process the data and
generate the signature from data that already prepare to send and go to next step
convert it into XML file Event select the logout menu made to exit the state
system and the system will display the message out.
7. Statcechart Diagram Edit RKA-SKPD
106
Start
Display Home
Page
Display View RKA
Form
Verify in Server
Display data in
table
Display logout
End
Login
Chose View RKA
Generate Digital Signature And XML
Valid Signature
Chose Logout Menu
Display Error
Page
Repeat Edit
Invalid Signature
Display Edit RKA
Form
Chose Edit RKA Menu
Figure 4.1.3.6.8 Statechart Diagram Edit RKA SKPD
In Figure 4.1.3.6.8 Statechart Diagram user performs event login, and then the
state will display the user's home page. To perform a edit command, then state
display the edit page and user updated the data, then state will process the data
and generate the signature from data that already prepare to send and go to next
step convert it into XML file Event select the logout menu made to exit the state
system and the system will display the message out.
4.1 3.7Application Domain Analysis
4.2.1 Use Case Diagram
1. Stakeholder Identification
107
Table 4.2.1.1 Actor Identification
No Actor Description
2 User The person responsible for overseeing the
performance to operate and receives reports.
2. Use Case Identification
Table 4.2.1.2 Use Case identification
No Use Case Description Actor
1. Login Use Case describes the activities of
entering your username and
password to access the system.
user, Login
2. Management XML Use Case describes the activities to
manage and view the processes that
occur in the system xml
user, XML
3. Management RKA Use Case describes activities of
operator / super admin instead
view, edit and delete the data of
RKA
User, RKA
4. Logout Use Case Describes when operator
/super admin want to end their
season.
User, logout
108
3. Use Case Model Diagram
Gambar 4.1 Use Case Model Diagram
4. Narrative Use Case
In this Use Case narratives described the sequence of activities performed by the
system and actors, there are:
1. Login
Table 4.2.1.3 Narratives Use Case Login
Use Case Name Login
Brief Description Actors must login to be able to open the
application. Login is done by entering a username
and user password.
Actor User
109
Precondition User Already have Username and I Password
Main Flow 1. Open the web secure application
2. Enter User name and password
3. Login
Alternative Flow If the username or password, the system will give
warning that the username or password is entered
incorrectly and the system will ask for repeat
logins.
Post Condition Displaying page corresponding to the
authentication.
2. Management RKA
Table 4.2.1.4 Narratives Use Case Management RKA
Use Case Name Management RKA
Brief Description Use Case describes activity instead in list input,
edit and delete budgeting planning but though the
network with xml and digital signature
Actor User
Precondition User Login As Super Admin and Operator
Main Flow 1. User Chose view RKA menu
2. The Data display in table cluster with year RKA
3. For Add the new RKA press the add button
4. System will display the add new data RKA
110
form
5. User can input the data and press the save
button
6. System will display the new data in table
7. User can edit the data by choosing them and
press edit menu
8. System will display edit data RKA
9. User can edit the RKA data and change it by
pressing edit
10. System will display the changes.
11. User can delete RKA data by pressing delete
button
12. System will delete the data from database.
Alternative Flow If Signature invalid system will display error
message
Post Condition System will put all data in xml with digital
signature and trow it to server to verify.
3. Management XML
Table 4.2.1.5 Narratives Use Case Management XML
Use Case Name Management XML
Brief Description Use Case describes activities of Super Admin to
monitoring the log of XML that send and recive
111
from server.
Actor User
Precondition User Login as Super Admin
Main Flow 1. User chose the management XML menu
2. System will display the log of XML
Alternative Flow -
Post Condition Sistem Display The XML file
4. Logout
Table 4.2.1.6 Narratives Use Case Logout
Use Case Name Logout
Brief Description Use Case describes activities the Super Admin and
Operator out from the system
Actor User
Precondition User login as Super Admin or Operator
Main Flow 1. User chose logout menu
Alternative Flow -
Post Condition System will display ”Sucess to Logout ”
[LOGOUT]”.
112
4.2.2 Sequence Diagram
Sequence diagrams describe interactions among the objects of the message in the
time series occurring in the application.
1. Sequence Diagram Use Case Login
User
Form Login
Input Username and password
User
Display Home Page
Repeat Login
Check User
Access from login
Display Error Message
Figure 4.2.2.1 Sequence Diagram Use Case Login
In the Sequence Diagram Use Case Log, users who want to use the system to
access the login form and then send the message input username and password
login form on the object. If the username and password is entered incorrectly,
it will display an error message. If the username and password are entered
113
correctly then it will display the user's home page in accordance with the user
level.
2. Sequence Diagram Use Case Management XML
Super Admin
XML
Chose management XML Menu
Display XML Log Process
Figure 4.2.2.2 Sequence Diagram Use Case Management XML
In sequence diagrams management XML use case, actor super admin to send a
message select management XML menu. Then the object displays the log XML of
the system.
3. Sequence Diagram Use case view RKA
114
View RKA
User
Chose management RKA Menu
Display RKA Form
Digital
Signature core Server form
Verify and Send response to display data
Verify process
Chose view data
XML core
Generate SignatureGenerate XML
Send to Server
Figure 4.2.2.3 Sequence Diagram Use Case view RKA
In sequence diagrams management RKA use case, actor super admin and operator
select view RKA then the object display the RKA form, and actor press view data,
the system response to create the xml file with digital signature send parameter to
request the data from server. The server verifies the data by checking their digital
signature and send respond with all data needed.
4. Sequence Diagram Use case input RKA
Input
User
Chose management RKA Menu
Display RKA Form
Digital
Signature core Server form
Verify and Send response to display data
Verify process
Chose Input data
XML core
Generate SignatureGenerate XML
Send to Server
Figure 4.2.2.4 Sequence Diagram Use Case input RKA
115
In sequence diagrams management RKA use case, user select view RKA then the
object display the RKA form, and actor press input data, the system response to
create the xml file with digital signature send parameter to request the data from
server. The server verifies the data by checking their digital signature and send
respond with process value.
5. Sequence Diagram Use case edit RKA
Edit
User
Chose management RKA Menu
Display RKA Form
Digital
Signature core Server form
Verify and Send response to display data
Verify process
Chose Edit data
XML core
Generate SignatureGenerate XML
Send to Server
Figure 4.2.2.5 Sequence Diagram Use Case edit RKA
In sequence diagrams management RKA use case, user select view RKA then the
object display the RKA form, and actor press edit data, the system response to
create the xml file with digital signature send parameter to request the data from
server. The server verifies the data by checking their digital signature and send
respond with all data needed.
116
6. Sequence Diagram Use Case Logout
User
Logout
Chose Logout Menu
Display Logout Form
Figure 4.2.2.6 Sequence Diagram Use Case Logout
In sequence diagrams logout use case, actor operator or super admin to send a
message select the menu page the user logged onto the object. Then the object
displays the message out of the system.
4.2.3 Function List
Is a list that describes the actions detailed specification for understanding
the needs of the system. In the Function List is to determine the level of desire in
achieving the objectives of the system designed, so it becomes more clear function
for the user. Function List the following table on the web secure system.
Table 4.2.3 Function List in web secure system
Function Complexity Type
1. Login
Input username and password Medium Read
2. Management XML
Chose management XML menu Simple Read
117
3. Management RKA
Chose Management RKA-SKPD Simple Read
Create, update, delete RKA-SKPD - Update
4. Search data
Chose Search data menu Simple Read
Chose data type Simple Read
Input data Simple Create , Read
Display and print result Simple Read
5. Logout
Chose menu logout Simple Read
From table above describes some of the functions of the Use Case that has been
made. And it can be concluded that the results from the function or use made of
some of the activities undertaken are fairly consistent and in accordance with the
required design.
Window Diagram
Window diagram aims to illustrate the design of the display or user interface of
the application to be made. The design of web secure system is consisting of two
menu pages of the operator and the super user admin. The following diagram
window for the web secure system.
a. Window diagram
1. Window Diagram Login From
118
LOGOHEADER
FOOTER
Process Cancel
Username :
Password :
Figure 4.3.2.1 Window Diagram Login Form
Login page is the start page to open a secure web system. In this case each user
either Super Admin or operators are required to enter the correct username and
password to enter the main page of the user.
2. Window Diagram Home form
LOGOHEADER
FOOTER
Home
Management XML
Management RKA
Search
Logout
Home Page
Figure 4.3.2.2 Window Diagram Home Form
Super admin-level home page will appear first when they successfully login in
system.
119
3. Window Diagram Management XML from
LOGOHEADER
FOOTER
Home
Management XML
Management RKA
Search
Logout Log XML
XML Log System
Figure 4.3.2.3 Window Diagram management XML
Super admin-level XML page will appear first when they successfully login in
system List of all XML log will appear here.
4. Window Diagram Management RKA
120
LOGOHEADER
FOOTER
Home
Management RKA
Logout
Data Bound + - ?
Data Bound
Data Bound
Data Bound
Data Bound
Data Bound
Back
+
+
+
+
+
-
-
-
-
-
?
?
?
?
?
Search
Management XML
Figure 4.3.2.4 Window Diagram management RKA
This page displays the user edit form that can allow a user to update delete and
add data.
5. Window Diagram Management Input RKA
LOGOHEADER
FOOTER
Home
Management XML
Management RKA
Search
Logout
Save Cancel
Government Business
Organisation
Program
Activity
Year
Location
Sum (n-1)
Sum (n)
Sum (n+1)
Program Goal
input
Output
Result
Sugestion
Figure 4.3.2.5 Window Diagram input management RKA
This page displays the user input form that can allow a user to insert data.
121
6. Window Diagram Management Edit RKA
LOGOHEADER
FOOTER
Home
Management XML
Management RKA
Search
Logout
Update Cancel
Data Bound
DB
Data Bound
Data Bound
Data Bound
Government Business
Organisation
Program
Activity
Year
Location Data Bound
Sum (n-1) Data Bound
Data Bound
Data Bound
Sum (n)
Sum (n+1)
Program Goal
input
Output
Result
Sugestion
Data Bound
Data Bound
Data Bound
Data Bound
Data Bound
Data Bound
Data Bound
Data Bound
Data Bound
Figure 4.3.2.6 Window Diagram management edit RKA
This page displays the user edit form that can allow a user to update data.
4.2 Architecture Design
4.2.1. Design Criteria.
In an architectural design is necessary to determ mine criteria to set priorities in
the design of applications that will be displayed in tabular form, it aims to produce
122
high quality applications and to help prioritize system development strategy,
support the evaluation and assist in assessing the completeness of the proposed
system. Design criteria in designing web secure system can be seen in Figure
4.21.
Table 4.2.1 Criteria proposed system
Criteria
Very
Importan
t
Importan
t
Less
Important
Irrelevan
t
Easily
Fullfield
Usable √
Secure √
Efficient √
Correct √
Reliable √
Maintainable √
Testable √
Flexible √
Comprehensib
le
√
Reuseable √
Portable √
123
Explanation:
1. Usable : Usefulness of the proposed system in accordance with the
requirements
2. Secure : Secure access from people who do not have right
3. Efficient : Efficiarncy of the system
4. Correct : Fulfill requirement with needed
5. Reliable : Fulfillment of the results from the execution of existing
functions.
6. Maintainable : Pengalokasian biaya dan perbaikan sistem yang rusak
7. Testable : system which delevopled match with the function
8. Flexible : esiest to modify system .
9. Comprehensible :Effort required to gain an understanding
clear from the system.
10. Reusable : Potensial used in another system
11. Portable : Transfer to another platform
4.3.2 Deployment Diagram
Deployment diagram provides an overview of how the system as a physical and
visible. The system consists of nodes where each node is represented by a symbol
or a cube. In this system uses the client and server programs using the Internet
network since the system is used in one area. Therefore in the application of this
system is used in the form of an application server XAMPP also called CPanel
virtual server that can serve to make the application accessible offline.
124
Information can be accessed using a web browser internally. The system is web
secure system can retrieve data from the previous system from the outside safely.
Webservice Aplication Server
Database ServerPublic Internet
PC Client Websecure
MYSQL
RKA SKPD
Browser Firefox, Internet
Explorer dll.
Figure 4.32 Deployment Diagram web secure system
4.3 Component Design
4.1.Component Diagram
Component diagram illustrates the allocation of all classes and objects into the
physical components in a system designed. In this system, an application based on
PHP with MySQL data processing on the local computer. In this system the
business logic can be placed on a server or the client. To run the system, the first
time the user must enter the address of the system using a web browser
application, after which the display will show the secure web system. For more
details can be seen in Figure 4.83.
125
Mysql
Webservice
Firefox
Websecure system
RKA SKPD
Figure4.33 Component Diagram web secure system
As we can be seen in Figure 4.33. That component on a secure web system in
general this is the "firefox.exe" component is a multiplatform browser.
Component "XAMPP" is software that is used as a web server in which consists
of the Apache web server, PHP, MySQL, and phpMyAdmin. and for component
"secure web system" is an application that is built. While MySQL is a database
that is used in applications.
Hardware Specification
Requirement specifications of the hardware used to support this system are as
follows:
1. Processor pentium atom with speed 1,8 GHz
2. Memori RAM capacity 512 MB.
3. Hard Disk capacity 180 GB.
4. VGA Card 32 MB
5. Monitor SVGA 15”.
6. Mouse, Keyboard.
126
7. CD R/RW 52 x.
8. LAN Card.
Software Specification
Software needs to support in running a web secure system are as follows:
1. Operating system Microsoft Windows XP Service Pack 2
2. XAMPP Version 1.6.4
3. Mozila Firefox 3.0
4. Adobe Flash Player Plugin Installer versi 10.0
5. Adobe Reader 8.
6. Microsoft office 2003 / 2007.
4.4 Programming
4.4.1. Screenshot system
Home Page
Figure 4.4.1.1 Home Page
XML Page
127
Figure 4.4.1.2 Management XML Page
Management RKA (view)
Figure 4.4.1.3 Management RKA View Page
Management RKA (Input)
128
Figure 4.4.1.3 Management RKA Input Page
4.4.2. Signature Process
There are several steps the signature created:
1. First data input in form and user click process button
Figure 4.4.2.1 Simulation Input Page
2. The data form to xml core and convert to the xml format
<?xml version="1.0"?>
129
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>0</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
130
</Content>
3. All of content padded into one sentence
<urusan>1.01</urusan><organisasi>1.20</organisasi><Program>0</Program><
Kegiatan>1.01.1.01.01.01.01</Kegiatan><Tahun>2012</Tahun><LokasiKegiata
n>Malang</LokasiKegiatan><nmin1>0</nmin1><n>1000000000</n><nplus1>0
</nplus1><CapaianProgram>Terwujudnya rumah
jabatan</CapaianProgram><CapaianProgram_2>1
ton</CapaianProgram_2><Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2><Keluaran>Terlaksananya
rumah jabatan</Keluaran><Keluaran_2>1
paket</Keluaran_2><Hasil>Terwujudnya rumah jabatan</Hasil <Hasil_2>1
paket</Hasil_2><SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
4. All content that padded before encrypted with MD5 first
8b927aa88d024f0559a39389f73ff3ad0bd399f672caa8f2f1e055a6d445e19358471
ed9a12d0868ba340866b4c46c448742c7747d0e6be9bbda78bc407aeca909c30261
8922ecb8d0218c622669b816ddc199a34684fb38b885bb6212c443926f454ec0f935
04140f21bc01dbd557cdf8c26425ab1ab474ea414df3cafa6f42
131
5. Encrypted again with RSA
8b927aa88d024f0559a39389f73ff3ad0bd399f672caa8f2f1e055a6d445e19358471
ed9a12d0868ba340866b4c46c448742c7747d0e6be9bbda78bc407aeca909c30261
8922ecb8d0218c622669b816ddc199a34684fb38b885bb6212c443926f454ec0f935
04140f21bc01dbd557cdf8c26425ab1ab474ea414df3cafa6f42
6. Added the signature in XML
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>0</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2011</Tahun>
<LokasiKegiatan>jakarta</LokasiKegiatan>
<nmin1>0</nmin1>
132
<n>200000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Urusan Field insufficient element</Description>
</Response>
<Signature>
<Data>2f6c2e29b51b74f1b673bca3496db07c690745469def1711e2f0807a06c
4ef31e460220a87d3348fb405f084c391ae1184722acda60cf05e7a3ab2d8ec469
6cf456b66e4243d4657d8c94c2715425fd3b9497bf6c08e4a4d9613eb2d5c28bd
71e28c6e095a923a3fed017a45245bce7852c3da599dfcf7e6a265b4aa3a87a6e7
</Data>
</Signature>
133
</ResponseMethod>
4.4.3. Make Key Pair
The Step by Step describe with the figure bellow :
Figure 4.4.3.1 Generate Key Pair
Figure 4.4.3.2 Generate Key Pair Password
Figure 4.4.3.3 Generate Key Pair File
134
Figure 4.4.3.4 Entering Data for Key Pair
Figure 4.4.3.5 Entering Valid Day Key Pair
Figure 4.4.3.6 Creating Cer File
Figure 4.4.3.7 All Output File Key Pair
135
4.5 Testing System
At this stage explain testing of secure web system. The test used is a black
box testing (external). External testing is done by checking one by one existing
output, whether those output are correct as expected or not.
Table 4.5 Testing Table List
No Scenario Process Result Expected Result
Login
1. Enter right username and
password (with valid
signature)
show the display home page OK
Application screenshot
Xml
2011-12-12 12:35:55,063 [DEBUG] Response XML History
2011-12-12 12:35:55,063 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
136
<MethodID>
<Name>Login</Name>
</MethodID>
<Content>
<Username>admin</Username>
<Pass>21232f297a57a5a743894a0e4a801fc3</Pass>
</Content>
<Response>
<Code>SS</Code>
<Description>Sucess</Description>
</Response>
<Signature>
<Data>8b927aa88d024f0559a39389f73ff3ad0bd399f672caa8f2f1e055a6d445
e19358471ed9a12d0868ba340866b4c46c448742c7747d0e6be9bbda78bc407a
eca909c302618922ecb8d0218c622669b816ddc199a34684fb38b885bb6212c4
43926f454ec0f93504140f21bc01dbd557cdf8c26425ab1ab474ea414df3cafa6f
42</Data>
</Signature>
</ResponseMethod>
2. Enter right username and
password (with Invalid
signature)
Redirect to again Login page OK
Application screenshot
137
XML
2011-12-12 12:49:57,000 [DEBUG] Response XML History
2011-12-12 12:49:57,000 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Login</Name>
</MethodID>
<Content>
<Username>admin</Username>
<Pass>21232f297a57a5a743894a0e4a801fc3</Pass>
</Content>
<Response>
<Code>IS</Code>
<Description>Invalid Signature</Description>
</Response>
138
<Signature>
<Data>8b927aa88d024f0559a39389f73ff3ad0bd399f672caa8f2f1e055a6d445
e19358471ed9a12d0868ba340866b4c46c448742c7747d0e6be9bbda78bc407a
eca909c302618922ecb8d0218c622669b816ddc199a34684fb38b885bb6212c4
43926f454ec0f93504140f21bc01dbd557cdf8c26425ab1ab474ea414df3cafa6f
42</Data>
</Signature>
</ResponseMethod>
3. Enter Invalid username
and password
Redirect to again Login page OK
Application screenshot
XML
2011-12-12 12:44:00,406 [DEBUG] Response XML History
2011-12-12 12:44:00,406 [DEBUG]
<?xml version="1.0"?>
139
<ResponseMethod>
<MethodID>
<Name>Login</Name>
</MethodID>
<Content>
<Username>admin</Username>
<Pass>74b87337454200d4d33f80c4663dc5e5</Pass>
</Content>
<Response>
<Code>IP</Code>
<Description>Invalid Username/Password</Description>
</Response>
<Signature>
<Data>36f65b6e0df03c9a6952f532f3ddadc852a1376dd1114a2f79f74d5ad90
cba1ce050dc7a690a34df19f9ab9cd89233dcbe7305c3926f671f2bf527a89e36
95547a775169fedeff0e20f7f7c5a04fa74b2c18486ec8bde96464e43ae5f67802
0bd87545100a0300a1f0fecba789cd01ea7b4efac40ed3aa4c996b30adb0d996a
b</Data>
</Signature>
</ResponseMethod>
Management XML
4. Chose Management XML Show The XML Log File OK
140
Management RKA (
Input )
5. Urusan Pemerintahan
(with value null)
Back to input form and display
the Insufficient Element error
OK
Application screenshot
XML
2011-12-12 12:57:24,953 [DEBUG] Response XML History
2011-12-12 12:57:24,953 [DEBUG]
<?xml version="1.0"?>
141
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>0</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2011</Tahun>
<LokasiKegiatan>jakarta</LokasiKegiatan>
<nmin1>0</nmin1>
<n>200000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
142
</Content>
<Response>
<Code>IE</Code>
<Description>Urusan Field insufficient element</Description>
</Response>
<Signature>
<Data>2f6c2e29b51b74f1b673bca3496db07c690745469def1711e2f0807a06c
4ef31e460220a87d3348fb405f084c391ae1184722acda60cf05e7a3ab2d8ec46
96cf456b66e4243d4657d8c94c2715425fd3b9497bf6c08e4a4d9613eb2d5c28
bd71e28c6e095a923a3fed017a45245bce7852c3da599dfcf7e6a265b4aa3a87a
6e7</Data>
</Signature>
</ResponseMethod>
6. Organisasi (with value
null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
143
XML
2011-12-12 13:12:32,844 [DEBUG] Response XML History
2011-12-12 13:12:32,844 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>0</Organisasi>
<Program>1.04.1.04.01.16</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
144
<n>200000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 ton</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Organisasi Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
145
</Signature>
</ResponseMethod>
7. Program (with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 13:15:53,313 [DEBUG] Response XML History
2011-12-12 13:15:53,313 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>0</Program>
146
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Program Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
147
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
8. Kegiatan (with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 13:27:19,641 [DEBUG] Response XML History
2011-12-12 13:27:19,641 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
148
<Content>
<Urusan>1.02</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>0</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Kegiatan Field insufficient element</Description>
149
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
9. Tahun (with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 13:31:07,719 [DEBUG] Response XML History
2011-12-12 13:31:07,719 [DEBUG]
150
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun/>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
151
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Tahun Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
10. Tahun ( with wrong value
ex: 20121 )
Back to input form and display
the length error
OK
Application Screenshot
152
XML
2011-12-12 13:35:39,719 [DEBUG] Response XML History
2011-12-12 13:35:39,719 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>20121</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
153
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 ton</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Tahun Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
154
</Signature>
</ResponseMethod>
11. Lokasi kegiatan (with
value null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 13:40:52,203 [DEBUG] Response XML History
2011-12-12 13:40:52,203 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
155
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.02.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan/>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Lokasi_Kegiatan Field insufficient element</Description>
</Response>
<Signature>
156
<Data>03cefd2cc9daca9110751b48ef010bfecfb2930ed22b87a26f3e99d9780f
3775cf172494595a42ccabab84696aa4be7a497ecfebea438a9db4e810db512f1
3876a994da50225b4e92f5f213ce50b3a37966e2fd862eafc1733417900127c09
985c93582dc3aad5b8b37fdb2a4bcec4044403ff4560bbb9dd1196773f3ae27ab
1</Data>
</Signature>
</ResponseMethod>
12. Lokasi Kegiatan ( with
value more than 30
Length )
Back to input form and display
the length error
OK
Application Sreen Shot
XML
2011-12-12 13:44:53,078 [DEBUG] Response XML History
2011-12-12 13:44:53,078 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
157
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>1234567890asdfghjklqwertyuiopmnb</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
158
<Response>
<Code>LG</Code>
<Description>Lokasi Kegiatan Length Error</Description>
</Response>
<Signature>
<Data>83cedbeea92c9cc1dd72e363b25338ffff093625ae5965bf69842dc89e9
a9ffec61564115ea6095fccf6e31e493b52d4021ba40f34156b13d512932e3b55
d25c558b6007e56045e1113b533b8ce8f7f170b0dd16d61289c0d8a511b5ede5
bbd5081899fa35f97cea337e14e2bc278dfd12c3a5c2e34b31a346bf524edf14f4
6a</Data>
</Signature>
</ResponseMethod>
13. n-1 (with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
159
XML
2011-12-12 13:53:01,875 [DEBUG] Response XML History
2011-12-12 13:53:01,875 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.04.1.04.01.16</Program>
<Kegiatan>1.04.1.04.01.16.24</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1/>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
160
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 ton</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>N-1 Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
14. n-1 ( with value more than
30 Length )
Back to input form and display
the length error
OK
Application Screenshot
161
XML
2011-12-12 14:01:08,234 [DEBUG] Response XML History
2011-12-12 14:01:08,234 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>1234567890asdfghjklqwertyuiopmnb</LokasiKegiatan>
<nmin1>0</nmin1>
162
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Lokasi Kegiatan Length Error</Description>
</Response>
<Signature>
<Data>83cedbeea92c9cc1dd72e363b25338ffff093625ae5965bf69842dc89e9
a9ffec61564115ea6095fccf6e31e493b52d4021ba40f34156b13d512932e3b55
d25c558b6007e56045e1113b533b8ce8f7f170b0dd16d61289c0d8a511b5ede5
bbd5081899fa35f97cea337e14e2bc278dfd12c3a5c2e34b31a346bf524edf14f4
6a</Data>
163
</Signature>
</ResponseMethod>
15. n (with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 19:41:09,625 [DEBUG] Response XML History
2011-12-12 19:41:09,625 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
164
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n><n/>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 ton</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>N Field insufficient element</Description>
</Response>
<Signature>
165
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
16. Capaian Program (with
value null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 19:50:45,891 [DEBUG] Response XML History
2011-12-12 19:50:45,891 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
166
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram/>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>test</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
167
<Response>
<Code>IE</Code>
<Description>Capaian Program Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
17. Capaian Program ( with
value more than 30
Length )
Back to input form and display
the length error
OK
Application Screenshot
168
XML
2011-12-12 19:57:43,109 [DEBUG] Response XML History
2011-12-12 19:57:43,109 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
169
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>1234567890asdfghjklqwertyuiopjlkj</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Capaian Program Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
170
c94</Data>
</Signature>
</ResponseMethod>
18. Capaian Program TK(with
value null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 20:06:09,484 [DEBUG] Response XML History
2011-12-12 20:06:09,484 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
171
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2/>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 ton</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Capaian Program Target Kinerja Field insufficient
element</Description>
</Response>
<Signature>
172
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
19. Capaian Program TK (
with value more than 30
Length )
Back to input form and display
the length error
OK
Application Screenshot
XML
2011-12-12 20:04:00,406 [DEBUG] Response XML History
2011-12-12 20:04:00,406 [DEBUG]
<?xml version="1.0"?>
173
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1234567890asdfghjklqwertyuioplkjhg</CapaianProgra
m_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
174
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Capaian Program TK Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
20. Masukan(with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
175
XML
2011-12-12 20:37:37,719 [DEBUG] Response XML History
2011-12-12 20:37:37,719 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
176
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan/>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Masukan Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
177
</Signature>
</ResponseMethod>
21. Masukan ( with value
more than 30 Length )
Back to input form and display
the length error
OK
Application Screenshot
XML
2011-12-12 21:47:55,063 [DEBUG] Response XML History
2011-12-12 21:47:55,063 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
178
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2011</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>1234567890asdfghjklpoiuytrewqasdf</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Masukan Length Error</Description>
</Response>
<Signature>
179
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
22. masukan TK(with value
null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 21:51:52,297 [DEBUG] Response XML History
2011-12-12 21:51:52,297 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
180
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2/>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
181
<Code>IE</Code>
<Description>Masukan Target Kinerja Field insufficient
element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
23. masukan TK ( with value
more than 30 Length )
Back to input form and display
the length error
OK
Application Screenshot
182
XML
2011-12-12 21:55:13,359 [DEBUG] Response XML History
2011-12-12 21:55:13,359 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>1234567890asdfghjklpoiuytrewqasd</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
183
<Keluaran_2>1 ton</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Masukan TK Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
24. Keluaran (with value
null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
184
XML
2011-12-12 21:57:40,438 [DEBUG] Response XML History
2011-12-12 21:57:40,438 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
185
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran/>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Keluaran Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
186
</Signature>
</ResponseMethod>
25. Keluaran ( with value
more than 30 Length )
Back to input form and display
the length error
OK
Application Screenshot
XML
2011-12-12 22:00:14,484 [DEBUG] Response XML History
2011-12-12 22:00:14,484 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
187
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>1234567890asdfghjklpqwertyuiomnbvcx</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Keluaran Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
188
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
26. Keluaran TK(with value
null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 22:03:23,297 [DEBUG] Response XML History
2011-12-12 22:03:23,297 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
189
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 ton</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2/>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Keluaran Target Kinerja Field insufficient
190
element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
27. Keluaran TK ( with value
more than 30 Length )
Back to input form and display
the length error
OK
Application Screenshot
XML
2011-12-12 22:07:56,375 [DEBUG] Response XML History
2011-12-12 22:07:56,375 [DEBUG]
191
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1234567890asdfghjklpqwertyuiolkjhn</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
192
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Keluaran TK Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
28. Hasil (with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
193
XML
2011-12-12 22:09:56,125 [DEBUG] Response XML History
2011-12-12 22:09:56,125 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
194
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil/>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Hasil Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
195
</ResponseMethod>
29. Hasil ( with value more
than 30 Length )
Back to input form and display
the length error
OK
Application Screenshot
XML
2011-12-12 22:21:55,141 [DEBUG] Response XML History
2011-12-12 22:21:55,141 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
196
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>1234567890asdfghjklpqwertyuiomnbvc</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Hasil Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
197
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
30. Hasil TK(with value null) Back to input form and display
the Insufficient Element error
OK
Application Screenshot
XML
2011-12-12 22:24:12,250 [DEBUG] Response XML History
2011-12-12 22:24:12,250 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
198
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2/>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IE</Code>
<Description>Hasil Target Kinerja Field insufficient
199
element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
31. Hasil TK ( with value
more than 30 Length )
Back to input form and display
the length error
OK
Application Screenshot
XML
2011-12-12 22:26:23,813 [DEBUG] Response XML History
2011-12-12 22:26:23,813 [DEBUG]
200
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1234567890asdfghjklpqwertyuiomnbvc</Hasil_2>
201
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Hasil TK Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
32. Kelompok sasaran
kegiatan(with value null)
Back to input form and display
the Insufficient Element error
OK
Application Screenshot
202
XML
2011-12-12 22:29:33,719 [DEBUG] Response XML History
2011-12-12 22:29:33,719 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
203
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan/>
</Content>
<Response>
<Code>IE</Code>
<Description>Sasaran Kegiatan Field insufficient element</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
204
</ResponseMethod>
33. Input data with Invalid
signature as response from
server
Back to input form and display
the invalid signature error
OK
Application Screenshot
XML
2011-12-12 22:36:56,844 [DEBUG] Response XML History
2011-12-12 22:36:56,844 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Input</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
205
<Kegiatan>1.04.1.04.01.16.24</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1 paket</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>IS</Code>
<Description>Invalid Signature</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
206
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
</ResponseMethod>
Management RKA (
Edit )
34. User can edit data of RKA Data Updated in Database of
RKA SKPD
OK
Application Screenshot
XML
2011-12-14 12:13:45,422 [DEBUG] Response XML History
2011-12-14 12:13:45,422 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
207
<MethodID>
<Name>edit</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2011</Tahun>
<LokasiKegiatan>jogjakarta</LokasiKegiatan>
<nmin1>0</nmin1>
<n>200000</n>
<nplus1>0</nplus1>
<CapaianProgram>test</CapaianProgram>
<CapaianProgram_2>test</CapaianProgram_2>
<Masukan>test</Masukan>
<Masukan_2>test</Masukan_2>
<Keluaran>test</Keluaran>
<Keluaran_2>test</Keluaran_2>
<Hasil>test</Hasil>
<Hasil_2>test</Hasil_2>
<SasaranKegiatan>test</SasaranKegiatan>
</Content>
208
<Response>
<Code>SS</Code>
<Description>Sucess</Description>
</Response>
<Signature>
<Data>0c0b2ba73511309280c2728b9b14d2eb68367f9719e4046026a2068d7
a7d11196268e67607365e8bc0341462d67e586ff2af3e8cf1b112c01118fd19e6
58c0a9bb9411e6d0226d602d96242fff79af5fb6dcb58c8be9cc61b69d61e5d44
e6ea6b8f3c8073017349b083f2b09d716f1b226630724123ac4f945488cb4ca93
0d30</Data>
</Signature>
</ResponseMethod>
35. Edit data with invalid
signature as response from
server
Back to edit form and display the
invalid signature error
OK
Application Screenshot
209
XML
2011-12-14 12:13:45,422 [DEBUG] Response XML History
2011-12-14 12:13:45,422 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>edit</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2011</Tahun>
<LokasiKegiatan>jogjakarta</LokasiKegiatan>
<nmin1>0</nmin1>
<n>200000</n>
<nplus1>0</nplus1>
<CapaianProgram>test</CapaianProgram>
<CapaianProgram_2>test</CapaianProgram_2>
<Masukan>test</Masukan>
<Masukan_2>test</Masukan_2>
<Keluaran>test</Keluaran>
210
<Keluaran_2>test</Keluaran_2>
<Hasil>test</Hasil>
<Hasil_2>test</Hasil_2>
<SasaranKegiatan>test</SasaranKegiatan>
</Content>
<Response>
<Code>IS</Code>
<Description>Invalid Signature</Description>
</Response>
<Signature>
<Data>0c0b2ba73511309280c2728b9b14d2eb68367f9719e4046026a2068d7
a7d11196268e67607365e8bc0341462d67e586ff2af3e8cf1b112c01118fd19e6
58c0a9bb9411e6d0226d602d96242fff79af5fb6dcb58c8be9cc61b69d61e5d44
e6ea6b8f3c8073017349b083f2b09d716f1b226630724123ac4f945488cb4ca93
0d30</Data>
</Signature>
</ResponseMethod>
36. Edit data with length
character more than
specification
Back to edit form and display the
length error
OK
Application Screenshot
211
XML
2011-12-12 22:26:23,813 [DEBUG] Response XML History
2011-12-12 22:26:23,813 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>Edit</Name>
</MethodID>
<Content>
<Urusan>1.01</Urusan>
<Organisasi>1.01.01</Organisasi>
<Program>1.01.1.01.01.01</Program>
<Kegiatan>1.01.1.01.01.01.01</Kegiatan>
<Tahun>2012</Tahun>
<LokasiKegiatan>Malang</LokasiKegiatan>
<nmin1>0</nmin1>
<n>1000000000</n>
212
<nplus1>0</nplus1>
<CapaianProgram>Terwujudnya rumah jabatan</CapaianProgram>
<CapaianProgram_2>1 paket</CapaianProgram_2>
<Masukan>Dana yang tersedia</Masukan>
<Masukan_2>Rp. 1.000.000.000,-</Masukan_2>
<Keluaran>Terlaksananya rumah jabatan</Keluaran>
<Keluaran_2>1 paket</Keluaran_2>
<Hasil>Terwujudnya rumah jabatan</Hasil>
<Hasil_2>1234567890asdfghjklpqwertyuiomnbvc</Hasil_2>
<SasaranKegiatan>Rumah rumah pejabat</SasaranKegiatan>
</Content>
<Response>
<Code>LG</Code>
<Description>Hasil TK Length Error</Description>
</Response>
<Signature>
<Data>149ea6ffa3c7c25b0ee0c376e140cd5b4a061cbd36e6720ea5bb9d26a7c
c12eacd04b547a6762605b90bf4977557cde0ed7f9016fb84d87f46948c972e22
13e2f15922e38721c1aafccb0716047019723645d903c8586f8b6177ef247a645
aa34296f78e615d0071741c3e241a77b0681e46d0606b62bf228004b0bb5b9fc
c94</Data>
</Signature>
213
</ResponseMethod>
Management RKA
(View)
37. User can see list of table
RKA
Data showed in table OK
Application Screenshot
XML
2011-12-12 22:41:05,906 [DEBUG] Response XML History
2011-12-12 22:41:05,906 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>view</Name>
</MethodID>
<Content>
214
<Numpage>1</Numpage>
<Page>1</Page>
<HasilQuery>
<id>6</id>
<skpd>1.04.01. Dinas Perumahan</skpd>
<program>1.04.1.04.01.16. Program Lingkungan Sehat
Perumahan</program>
<kegiatan>1.04.1.04.01.16.24. Pemeliharaan Insidentil Sarana dan
Prasarana Permukiman</kegiatan>
</HasilQuery>
<HasilQuery2>
<id>7</id>
<skpd>1.04.01. Dinas Perumahan</skpd>
<program>1.01.1.01.01.02. Program peningkatan sarana dan prasarana
aparatur</program>
<kegiatan>1.01.1.01.01.02.01. Pembangunan rumah jabatan</kegiatan>
</HasilQuery2>
<HasilQuery3>
<id>9</id>
<skpd>1.04.01. Dinas Perumahan</skpd>
<program>1.04.1.04.01.18. Program perbaikan perumahan akibat bencana
alam/sosial</program>
<kegiatan>1.04.1.04.01.18.01. Fasilitasi dan stimulasi rahabilitasi rumah
215
akibat bencana alam</kegiatan>
</HasilQuery3>
<HasilQuery4>
<id>10</id>
<skpd>1.01.01. Dinas Pendidikan</skpd>
<program>1.01.1.01.01.03. Program peningkatan disiplin
aparatur</program>
<kegiatan>1.01.1.01.01.03.09. Pengadaan pakaian Paskibra</kegiatan>
</HasilQuery4>
<HasilQuery5>
<id>23</id>
<skpd>1.01.01. Dinas Pendidikan</skpd>
<program>1.01.1.01.01.01. Program Pelayanan Administrasi
Perkantoran</program>
<kegiatan>1.01.1.01.01.01.01. Penyediaan jasa surat
menyurat</kegiatan>
</HasilQuery5>
</Content>
<Response>
<Code>SS</Code>
<Description>Sucess</Description>
</Response>
<Signature>
216
<Data>13b29a565a3e7e80ff6504f70f0026d181f24fd009d495037751a745fd7
5e994c9f7e795efddd7724827d64a65580ca937e4c1178a0fcc956657713c107b
3413c0980faba7f4b9185e41a80bba4181d7396f19653b0d959312afb91f36d45
1ed2b6deebdb3ca874297ee03118d7fd6d8880a1b2a83f48291c23da9235c0f28
f7</Data>
</Signature>
</ResponseMethod>
38. View RKA with invalid
signature as Response
from server
Display Invalid signature error OK
Application Screenshot
XML
2011-10-07 11:08:10,766 [DEBUG] Response XML History
2011-10-07 11:08:10,766 [DEBUG]
<?xml version="1.0"?>
217
<ResponseMethod>
<MethodID>
<Name>view</Name>
</MethodID>
<Content>
<Numpage>1</Numpage>
<Page>1</Page>
<HasilQuery>
<id>6</id>
<skpd>1.04.01. Dinas Perumahan</skpd>
<program>1.04.1.04.01.16. Program Lingkungan Sehat
Perumahan</program>
<kegiatan>1.04.1.04.01.16.24. Pemeliharaan Insidentil Sarana dan
Prasarana Permukiman</kegiatan>
</HasilQuery>
<HasilQuery2>
<id>7</id>
<skpd>1.04.01. Dinas Perumahan</skpd>
<program>1.01.1.01.01.02. Program peningkatan sarana dan prasarana
aparatur</program>
<kegiatan>1.01.1.01.01.02.01. Pembangunan rumah jabatan</kegiatan>
</HasilQuery2>
<HasilQuery3>
218
<id>9</id>
<skpd>1.04.01. Dinas Perumahan</skpd>
<program>1.04.1.04.01.18. Program perbaikan perumahan akibat bencana
alam/sosial</program>
<kegiatan>1.04.1.04.01.18.01. Fasilitasi dan stimulasi rahabilitasi rumah
akibat bencana alam</kegiatan>
</HasilQuery3>
<HasilQuery4>
<id>10</id>
<skpd>1.01.01. Dinas Pendidikan</skpd>
<program>1.01.1.01.01.03. Program peningkatan disiplin
aparatur</program>
<kegiatan>1.01.1.01.01.03.09. Pengadaan pakaian Paskibra</kegiatan>
</HasilQuery4>
<HasilQuery5>
<id>13</id>
<skpd>1.01.01. Dinas Pendidikan</skpd>
<program>1.01.1.01.01.01. Program Pelayanan Administrasi
Perkantoran</program>
<kegiatan>1.01.1.01.01.01.01. Penyediaan jasa surat
menyurat</kegiatan>
</HasilQuery5>
</Content>
219
<Response>
<Code>IS</Code>
<Description>Invalid Signature</Description>
</Response>
<Signature>
<Data>13b29a565a3e7e80ff6504f70f0026d181f24fd009d495037751a745fd7
5e994c9f7e795efddd7724827d64a65580ca937e4c1178a0fcc956657713c107b
3413c0980faba7f4b9185e41a80bba4181d7396f19653b0d959312afb91f36d45
1ed2b6deebdb3ca874297ee03118d7fd6d8880a1b2a83f48291c23da9235c0f28
f7</Data>
</Signature>
</ResponseMethod>
Management RKA
(delete)
39. User can delete data of
RKA SKPD
Data deleted in database of RKA
SKPD
OK
XML
2011-12-12 22:44:35,172 [DEBUG] Response XML History
2011-12-12 22:44:35,172 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
220
<MethodID>
<Name>delete</Name>
</MethodID>
<Content>
<id_rka>40</id_rka>
</Content>
<Response>
<Code>SS</Code>
<Description>Sucess</Description>
</Response>
<Signature>
<Data>45d716ca221447879c1c1796ed8459100434370eff511b6e745f04e895
d874d8c4e2b76ab268bb322c8605ba340c2813b8c2c766c1d8f8ae2002950af2
b6357dddbc2b6b5122eb8208b94d09167fd8d465d119e94a5bf03a1647d0bfa9
c71b159ae8242514974e8d84214469798893ef50997be7c76896bd1e5585ebdb
a18141</Data>
</Signature>
</ResponseMethod>
40. Delete data with invalid
signature as response in
rka skpd
Display invalid signature error OK
Application Screenshot
221
XML
2011-12-12 22:44:35,172 [DEBUG] Response XML History
2011-12-12 22:44:35,172 [DEBUG]
<?xml version="1.0"?>
<ResponseMethod>
<MethodID>
<Name>delete</Name>
</MethodID>
<Content>
<id_rka>40</id_rka>
</Content>
<Response>
<Code>IS</Code>
<Description>Invalid Signature</Description>
</Response>
<Signature>
222
<Data>45d716ca221447879c1c1796ed8459100434370eff511b6e745f04e895
d874d8c4e2b76ab268bb322c8605ba340c2813b8c2c766c1d8f8ae2002950af2
b6357dddbc2b6b5122eb8208b94d09167fd8d465d119e94a5bf03a1647d0bfa9
c71b159ae8242514974e8d84214469798893ef50997be7c76896bd1e5585ebdb
a18141</Data>
</Signature>
</ResponseMethod>
41. Logout Display Logout OK
Application Screenshot
42. Digital Signature inside file
with valid signature
Give the data inside file OK
224
CHAPTER V
CONCLUSION
5.1 Conclusion
Based on the research, it can be concluded that:
1. The service generated with openssl library in php and also array to
XML library to generate the XML core. In fact the service which
developed now can synchronize and interface the different
platform application (in this case RKA SKPD application used
linux operating system) and the web secure (The developed
system) used windows operating system. More detail explanation
can be viewed in Table 4.5
2. The best way to implement Digital Signature in this system is by
adding the Digital Signature in XML file that used to transfer the
data. And also the digital signatures can be used as one method to
avoid or prevent the sabotage of data.
3. The key pair generated with openssl library in php which used
1024 bit encryption instead of the key pair. For more detail can be
viewed from figure 4.4.3.1 until Figure 4.4.3.7
5.2 Recommandation
Based on the limitations in the manufacture of this system,
recommendations for the future development are:
225
1. Because the researcher used another password inside the public
key(.cer) in which is used in encryption and decryption process ,
researcher suggest to develop module to handle the forgotten
password for the ssl mode (key) service .
2. The researcher suggest to another researcher to evaluate the different
combination of asymmetric algorithm as comparison for better
system.
226
REFERENCES [1] Aghus Sofwan, Agung Budi P, Toni Susanto,(2006),Aplikasi Kriptogra
Dengan Algoritma Message Digest 5 (MD5),Transmisi, Vol. 11, No. 1, Juni 2006
:
[2] Budi Raharjo, (2005),Keamanan Sistem Informasi Berbasis Internet, PT Insan
Indonesia Bandung dan PT INDOCISC Jakarta
[3] http://www.cs.eku.edu/faculty/styer/460/Encrypt opened 1 juni 2011,time
21:00
[4] Schneier Bruce, (1996), Applied Cryptography Second Edition: Protocols,
Algo-rthms, and Source Code in C (cloth), John Wiley Sons, Inc.
[5] Lucky, 2008, XML Web Service Aplikasi Desktop, Internet & Handphone,
Jakarta:Jasakom
[6] Siswoutomo, Wiwit, 2004, Membangun Web Service Open Source
Menggunakan PHP, Jakarta : Penerbit PT Elex Media Komputindo.
[7] Kadir, Abdul, 2008, Dasar Pemrograman Web Dinamis Menggunakan
PHP,Yogyakarta : Penerbit Andi
[8] Roger S.Pressman, Software Engineering: A Practitioner's Approach 6th
edition [chapter 7] 2005
[9] Lars Mathiassen, Object-oriented Analysis & Design [Paperback] 2000
[10] John Wiley.2009.[online].Avalible.http://en.wikipedia.org/wiki/Unit_testing
opened 3 june 2011, time 20:00
[11] John Lewis.2007.[online].Avalible.http://en.wikipedia.org/wiki/Black_box
opened 3 june 2011, time 21:00
[13] Online source from official website of TouchScreen
(http://www.touchscreens.com/) 2011
[14] Lucky, 2008, XML Web Service Aplikasi Desktop, Internet & Handphone,
Jakarta: Jasakom
[15] Ari, Rosihan, 2009, Script PHP Untuk Updating Data Secara
Simultan.[online].Avalibe. http://blog.rosihanari.net/script-php-updating-data-
secara-simultan-studikasus-
update-nilai-kuliah-mahasiswa , 20 june 2011, Jam 20.05
[16] Daniel, Roy, 2003, Pengenalan Konsep XML Web Services,[online].Avalibe.
http://ikc.cbn.net.id/populer/roy-webservices.php , 20 june 2011, Jam 09.45
top related