SYSTEM ANALYSIS

DKB 3143 SYSTEM ANALYSIS AND DESIGN

 SUB TOPIK

• System Analysis Phase Overview

• Joint Application Development
• Rapid Application Development
• Agile Methods
• Modeling Tools and Techniques
• Functional Decomposition Diagrams
• Data Flow Diagram
• System Requirements Checklist
• Future Growth, Cost, and Benefits
• Scalability
• Total Cost of Ownership
 OBJEKTIF PEMBELAJARAN/LESSON OBJECTIVE

• MENGENALPASTI AKTIVITI DALAM FASA ANALISA

• MENJELASAKAN KONSEP JAD, RAD DAN AGILE
• MENJELASKAN KONSEP FDD DAN DFD.
• MENYENARAIKAN KEPERLUAN SISTEM TERMASUKLAH INPUT,OUTPUT,
PROSES, PRESTASI DAN KAWALAN
• MENJELASKAN KONSEP SKALABILITY DAN TCO (Total cost of ownership)
 OVERRALL OBJECTIVE

• TO UNDERSTAND THE PROPOSED PROJECT,

• ENSURE IT WILL SUPPORT BUSINESS REQUIREMENT
• BUILT SOLID FOUNDATION FOR SYSTEM DEVELOPMENTD

• WILL USE MODEL AND OTHE DOCUMENTATION TOOL TO VISUALIZE AND

DESCRIBE THE PROPOSED OF PROJECT THAT YOU WANT TO DEVELOP
SYSTEM ANALYSIS PHASES
ANALYTICAL SKILLS
INTERPERSONAL SKILLS
 JAD (JOINT APPLICATION DEVELOPMENT)

• Fact – finding technique that bring user into the

development process as active participants.
• Popular strategy for user involvement is JAD TEAM
APPROACH
• Which involve user, manager and it professional that
work together to gather information, discuss business
need and define new system requirement
• The end product of JAD is a REQUIREMENT MODEL.
JAD PARTICIPANTS AND ROLE
AGENDA OF A JAD
SESSION
ADVANTAGE AND DISADVANTAGE
(KELEBIHAN DAN KEKURANGAN)
 RAPID APPLICATION DEVELOPMENT
(PEMBANGUNAN APLIKASI RAPID)
• TEAM BASED TECHNIQUE that speed – up information system
development and produce functioning information system.
• End product of RAD is a new information system.
• Relies heavily on prototyping and user involvement.
• Allows users to examine a working model as early as possible
• Determine if it meet their need and suggest necessary changes.
• Uses cases tool - to build prototype and create continues stream of
documentation.
• Use to reduce cost and development time
• To increase the probability of success.
PHASES OF
RAD
 AGILE

• Attempt to develop a system incrementally by building a series of

prototype and constantly adjusting them to user requirement
• Scrum is other agile approach.

Team member prepare to lunge at each

Other to achieve their objectives.
PERBEZAAN RAD, JAD DAN AGILE
 MODELING TOOL AND
TECHNIQUES
(TEKNIK DAN ALAT MODEL)

FDD (FUNCTIONAL CASE TOOL

DECOMPOSITION DIAGRAM)
RAJAH PENGENDALIAN FUNGSI
DATA FLOW DIAGRAM
RAJAH ALIRAN DATA
 FDD
• Representation of function or process.
• Similar to draw an organization chart.
• Analysts use FDD to model business function and to show how they
organized into lower – level process

BUSINESS PROCESS MODELING

• Describe one or more process
• Analysts create model that uses standard language called business
process modeling notation (BPMN)
BUSINESS PROCESS MODELING NOTATION (BPMN)
• USING BPMN TERMINOLOGY AND INTEGRATED IT INTO CASE
DEVELOPMENT – TO GET FASTER RESULT, FEWER ERROR AND REDUCES
COST.
 DFD

• TO show the system

store, process and
transform data.
 UML (UNIFIED MODELING LANGUAGE)

• Uses object oriented design concept but it independent od any specific

programming language and use to describe business process and
requirement
• UML TOOL – USE CASE DIAGRAM AND SEQUENCE DIAGRAM
• TO representation the information system from a user view point.

USER CASE DIAGRAM

• Represent the
interaction between
user and the information
system
USE CASE DIAGRAM
 SEQUENCE DIAGRAM

• Show the timing d interaction

between object
• The interaction process from top
to bottom along a vertical
timeline while the horizontal
arrows represent message from
one object to another
 SYSTEM REQUIREMENT CHECKLIST

• A system requirement is a characteristic or feature that must be

• Included in an information system to satisfy business requirements and
be acceptable to users.
• System requirement checklist include:-
• OUTPUT
• INPUT
• PROCESS
• PERFORMANCE
• CONTROL
 FUTURE GROWTH, COST AND BENEFIT

• SCALABILITY
• System ability to handle increased business volume and transaction in the future.
• Need information about projected future volume for all output,input and process
• Need to project activity level for several year operation.
SCALABILITY FOR WEB DEVELOPMENT
TOTAL COST
OF
OWNERSHIP
(TCO)
EXERCISE TIME
 NEXT CHAPTER

HOW TO CREATE
• PERT CHART
• GANTT CHART
• DATA FLOW DIAGRAM