ANALYSIS AND SYSTEM DESIGN
Requirements analysis software is based
on the formulation of the problems that exist in this article.
From the results of the analysis is then on
software design that can meet all
functional requirements. The design of this software
using object oriented design approach
which is represented by UML (Unified Modeling
Language).
A. Software Analysis
The analysis done in this article includes descriptions
in general against the software built,
specifications of what needs are required
Figure 1. Diagram of use cases
the software, the actor's analysis becomes
software users up to case analysis
use.
In this article, built a collection app
iOS-based interactive folklore named
Tales. This app is a digital folklore book
which contains 5 pieces of local folklore. The purpose of
making this final task is to design and
build an application including digital book category
iOS-based interactive that can be a means of entertainment and
promotion of practical Indonesian folklore.
List of functional requirements of the built system
described by the use case diagram in Fig
1 and details of use cases.
Use of "Interactive Folk Story Reading"
The use case of "Reading the Interactive Folk Story"
is a use case that is accessed directly
by user (children).
Use Case "Getting New People's Stories
with IAP
The use case of "Getting a New People's Story
with IAP "is an access case used
directly by the user (parent).
Use case "Gain Achievements
from Game Center
Case use "Getting Achievements from
Game Center "is a use case that is accessed
directly by the user (children).
B. System Architecture
Here is an architecture used for
build apps Tales. Overall system
which overshadowed the Tale divided into six layers
main. The Layer is the Interface Layer
(Presentation Layer), Data Model Layer (Model Data
Layer), Business Logic Layer (Bussines Logic Layer), and
Core Services Layer. In Figure 2 shows how
connectivity between layers.
C. Class Diagram Design
This layer serves as a regulator of the running process
application. This layer also contains the functions to be
called by the interface layer. The business logic
used here is one controller for one view
MVC ;)
