CHAPTER III

RESEARCH METODOLOGY

This chapter discusses the research methodology used in the case study,
this research methodology contains problem formulation, data collection, analysis,
and conclusion.

3.1. Problem Formulation

The formulation of the problem in this case study is as follows:

1. How is the concept and basic technique of OOA/D ?
2. How is the concept of UML?
3. How to identify actor and use case, design use case diagram, and activity
diagram, sequence diagram, class diagram, and deployment diagram of
information system development planning?

3.2. Data Collection

Based on the results of practicum on M3, design use case diagrams and
activity diagrams based on business process models and DFDs. In the design of
the use case diagram there are 4 actors who play a role, namely members,
accounting departments, payroll departments, and membership departments. In the
model process there are stages in the accounting system, where the membership
department receives application forms and membership application registers,
payroll departments make payroll reports and send presentation checks,
accounting departments develop and run accounting systems in terms of payments
and issue payment receipts and members receive payment receipts and ID
numbers.
3.3. Analysis

Analysis is done on the data that has been collected. The content of the
analysis will lay out the scope of the system and the functionality between the
actor and the use case. Tools that can be used in analysis are to identify actors and
use cases, design using case diagrams, design using case descriptions and design
activity diagrams, sequence diagrams, class diagrams, and deployment diagrams.
The analysis contains the relationship of the use case with other use cases, actors
and use cases as well as dependencies, where dependency indicates there are
activities to be done before the system is accessed.

3.4. Conclusion

Conclusions contain data and analysis that has been done on the
completion of case studies. Conclusion answers from the formulation of the
problem, which helps in the development of information systems, especially
UML diagrams aimed at modeling agma accounting system into a diagram and
explaining the relationship between actors and use cases and use cases with other
use cases.. This process is developed in the accounting system program, then
will be developed in use case diagrams, activity diagrams, sequence diagrams,
class diagrams, deployment diagrams that will later describe the activities and
stages that run on the system as a whole.

3.5. Flowchart Research Methodology

The research methodology uses flowcharts that show the stages in solving
case study problems, which give the following stage points.
 Start
 Study literature
 Problem Identification studi kasus
 Problem Formulation studi kasus
 Data Collection
 Result
 Analysis
  Conclusion
 End

Figure 3.1 is the flow chart methodology analysis of information system

design module 3.
Figure 3.1 Flowchart Research Methodology
4.2 Context diagram

Figure 4.2 Use Case Diagram

5.2 Analysis

The use case diagram describes the relationship between the actor and the functions
running on the system in the diagram and the use case explains what the user wants to do that
can be seen in Figure 4.2. In the development of projects in the AGMA accounting system there
are 4 actors who play a role, namely members, payroll departments, membership departments,
and accounting departments. The creation of a use case diagram is done based on a pre-made
business process model. In the accounting department, the activities of obtaining an ID receipt,
entering a payment invoice, receiving a copy form, craete payment invoice, showing receipt ID,
determining payment compensation, payment of basic fees. Furthermore, the payroll department
conducts payroll reports and sends dues presentation activities. In the membership department
perform approved membership application activities and members receive payment invoices and
obtain member IDs. The direction of the use case arrow leads to another use case that is login by
using the include direction which means all use cases that want to access the AGMA accounting
system must login first. Each actor performs a task in accordance with the business process
model designed in the previous practicum after accessing the login system which describes all
use cases must login first to run the AGMA accounting system. The direction of the extend
arrow describes the use case requires another use case or the existence of functionality between
actors, namely the accounting department with members, where the functionality between get
receipt ID and receive receipt ID with member actors depends on the accounting department,
when receipt ID has been attached, then members need and accept use cases as a requirement in
the new membership of AGMA.