ORDER
0:M
CONTAINS
Relasi Data
Entitas Data
1:M
PRODUCT
Disampaikan Oleh
PROF . DR. SRI MULYANI NS,
SE, MS, AK
ADHI ALFIAN, SE.
System Analyst
(Multiple Job
levels)
RESPONSIBILITIES
EVALUATE PROJECTS FOR FEASIBILITY
ESTIMATES PERSONEL REQUIREMENTS,
BUDGETS, AND SCHEDULES FOR SYSTEM
DEVELOPMENT AND MAINTENANCE
PROJECTS.
PERFORM INTERVIEWS AND OTHER FACT
GATHERING.
DOCUMENT AND ANALYZES CURRENT
SYSTEM OPERATIONS.
5
EXTERNAL CONTACTS
ASSIGNED END USERS OF MAINFRAME COMPUTER AND
APPLICATIONS.
ASSIGNED OWNERS MAINFRAME COMPUTER AND
APPLICATIONS.
DATA ADMINISTRATION CENTRE PERSONNEL.
NETWORK ADMINISTRATION CENTER PERSONNEL.
INFORMATION CENTER PERSONNELS.
OPERATIONS CENTER PERSONNELS.
8
MINIMUM QUALIFICATIONS
BACHELOR OR MASTER DEGREE
IN COMPUTER INFORMATION
SYSTEMS OR RELATED FIELD.
PROGRAMMING EXPERINCE
PREFERRED.
PRIOR EXPERIENCE WITH
BUSINESS APPLICATIONS
CONSIDERED HELPFUL.
PRIOR TRAINING OR
EXPERIENCING IN SYSTEM
ANALYSIS AND DESIGN,
PREFERABLY STRUCTURED
METHODS, PREFERRED.
GOOD COMMUNICATIONS
SKILLS - ORAL AND WRITEN ARE
MANDATORY.
10
TRAINING REQUIREMENTS
ANALYST MUST COMPLETE OR DEMONSTRATE
EQUIVALENT BACKGROUNDS IN THE FOLLOWING HOURS COURSES ; STRADIS METHODOLOGY AND
STANDARDS, JOINT APPLICATION DESIGN (JAD)
TECHNIQUES, SYSTEM APPLICATION
ARCHITECTURE (SAA) STANDARDS,
FUNDAMENTALS, DDB DATABASE DESIGN
TECHNIQUES, CSP PROTOTYPING TECHNIQUES,
EXCELERATOR/IS CAD TECHNIQUES, PROJECT
MANAGEMENT TECHNIQUES, MICROCOMPUTER
SOFTWARE TOOLS, AND INTERPERSONAL
COMMUNICATIONS SKILLS FOR SYSTEMS
ANALYSIS.
11
JOB LEVEL
INITIAL ASSIGMENTS ARE BASED ON PROGRAMMING
EXPERIENCING AND TRAINING RESULTS. THE FOLLOWING
JOB LEVELS ARE DEFINED;
PROGRAMMER/ANALYST ; 30% ANALYSIS 70%PROGRAMMING.
ANALYST/PROGRAMMER; 50% ANALYSIS 50%PROGRAMMING.
ANALYST; 70% ANALYSIS 30% PROGRAMMING.
SENIOR ANALYS/DESIGN; 30% MANAGEMENT
60%ANALYSIS/DESIGN & 10% PROGRAMMING.
LEAD ANALYST ; 100% ANALYSIS/DESIGN OR
CONSULTING.
12
Computer
Programming
Experince and
Expertise
Working Knowledge of
Information Systems and
Technology
General
Business
Knowledge
Problem- Solving
Skills
Interpersonal
Communications
Skills
Flexibiliy
and
Adaptabil
ity
Interpersonal
Relations Skills
Character
and Ethics
System Owner
Owner interested
in the things that
data describes.
The things are
business
resources, such as;
Tangible things
(such as materials,
supplies,
machines) Roles
(such as
costumers,supplies
,empoyees) Events
(Such as
Order,requisitions,
contract)Places
(Such as
sales&offices)
DATA
System User
Entities are
forms, files,
records.
Knowledgeable
about data
attributes.
Knowledgeable
about the rules
(relationship)that
govern data and
entities.
System
Designer
Translate data
requirements into
computer files &
databases. View
of data consists of
record layouts,
data
structures,databa
se schemas,file
organizations,
fields,indexes,
and other
technical items.
15
System Builder
Write data program
to implement the
computer files and
database.
ACTIVITIES
System Owner
System owner are
usually interested
in the big picture
groups of activities
called functions
that consist of
Business, system
functions(eg.
Sales,service,man
ufacturing) and
information system
function(eg. Data
processing,officea
utomation,etc).
System User
System Designer
Users see
activities in terms
of distinct
business process,
Business process
are distinct
activities that have
inputs and
outputs(process
models, for short),
Specify methods
and step-by-step
procedurs often
underlie these
process.
16
System designers
view activities are
constrained by the
limitations of
specific
technology. In
other word, the
designers view of
activities is more
technical
System
Builder
System builder
represent
activities using
precise
computer
programming
language that
describe inputs,
outputs, and
logic. These
languages are
used to write
applications
programs.
NETWORK
System Owner
System User
System owner
view networks
geographical.The
geography of a
system is those
geographic
locations in which
the business
choose or needs to
operate.
Systems designers
view network in
term of computer
network. Computer
network is
technical
arrangement that
interconnects
computers and
peripherals such
that they can
change data &
share technical
resources. It is
sometimes called a
distributed system
architecture.
Technologies
Data
Processing Communications Technical
Technology Technology Technology
Specialist.
Includes all
hardware and
software
required to
capture,store
and manage
the data
resources.
Includes all
hardware and
software
required to
support
business and
information
system
activiies. It
also inlude
applications
programs.
Also called
networking or
telecommunications
technology includes
hardware &
software used to
interconnect data
and process
technology at
different locations.
18
Technical
specialist sell,
configure,repa
ir,and
maintain
information
technology for
systems
owners and
users.
Keuntungan
S DL C
RA D
Merupakan
metoda yang paling
awal
Kelemahan
End-User tidak terlibat terlalu aktif
dalam penyusunan system.
Pada saat implementasi sistim
kemungkinan akan banyak modifikasi
sistem.
Prototy
ping
K ekuatan
K elemahan
End-User become
more active
participants in
systems
development.
They tend to be
more excited by
working protypes
than paper design
specification.
Requirements
definition is
simplified through
realization that
many end-user
will not
understand or be
able to state their
detailed
requirements until
they see a
prototypes.
Kekuatan
J AD
23
RAD
Keuntungan
Kelemahan
26
Roles
Techniques
Input
Output
Top
Management
There are no
special techniques
or skilled required
to complete this
activity
Role
definition
assignment
Fact finding
Based on
Organization
JAD
interviews
charts.
Context or Scope
and facilitated
Context
modelimg
group
models
discussion
(scopewithin the
oriented
planning
pictures)
team, the
Scope
scope of the
description.
project
27
defined
Roles
Technique
Input
Output
Identify Busimess Performance Measures
Planning
Team
Executive
Manager
Fact finding
JAD
The scope
as defined
in the
previous
activity
Business
performance
measures
Planning
Team
Project
Management
The scope
as defined in
the previous
activity
Project plan
Budget
manager
Feasibility
Appropriate
Planning
Assesment
documentation
Project charter
Report
writing
Verbal
Presentation28
Roles
Techniques
Input
Output
Planning
team with
help from
appropriate
executive
managers
Fact finding
Joint
application
development
Data
modeling
Process
modeling
Network
modeling
Scope (from
Enterprise
models.
Planning
team &
appropriate
executive
managers
Interviewing
Performance
Sampling
measures
Studying
The enterprise
Joint
models
application
Design
29
Roles
Technique
Input
Output
Interviewing
Sampling
Studying
Joint
application
design
Business
performance
measures
and
Technology
application assesments in
various formats such as
questionnaire
response
summaries,
association
matrixces, and narrative
analyses.
Affinity
analysis
Clustering
Enterprise
Proposed business area
models
(specifically,da
ta
subjects,
business
process
&
organization
units)
Business
performance
measures
Association
matrices
30
Roles
Technique
Input
Output
Planning
There are
Proposed
Proposed
team
and
no
special
business
information
optionally
techniques or
area
and
architecture
unbiased
skilled require
enterprise
experts
or
to complete
models
consultants
this activity
Technology
and
information
service
assessments
Technology
trends
and
insights
Planning
Team
Project
Business
Planning
area Models
Schedulling
Proposed
Information
31
architecture
Projects
Plans
Rol es
Techniques
Input
Output
Feasibility
Appropria Approved
assesment
te
information
Report writing
documentati architecture
Walkthroughs
ons
and plan
Verbal
presentations
32
Roles
Techniques
Input
Establish the Analysis Team
Business
area details
Output
Roles
Overall
Business
business
area
performance
performance
measures
measures
Roles
Techniques
Input
Output
Fact finding
JAD
Data modeling
Process
Modeling
Network
Modeling
Analysis
team with
help from
business
managers
and
appropriate
business
experts
Interviewing
Observations
Sampling
Studying
Joint
Application
Design
Business
area subset
of business
models
Expanded and
refined
business area
models
34
Business
area models
Business
performance
measures
Association
matrices and
interpretations
Roles
Techniques
Input
Output
Analysis
team
There are no
special
techniques
Business
area models
Association
matrices
interpretations
Proposed
development
projects and
technology
architecture
Proposed
development
projects
Analysis
Team
Project
planning
Schedulling
35
Planned
development
projects
Roles
Techniques
Input
Output
Planning Team
Feasibility
Appropriate
Planned
assesment
documentation
application
Report writing
development
Walkthroughs
projects
Verbal
Planned
presentations
database and/or
network
development
project(s),
Business area
plan
36
Roles
Technique
Input
Output
Identify Requirements
System
Users
System
owner(s) with
direction by
systems
analyst
System
analyst
System
user
System
Owner(s)
Data
analyst
Network
analyst
Interviewing
New
Group Meetings
System
Discussions
objectives
Surveys
(and
Research
constraints)
Brainwriting
Brainstorming
Business and
user requirements
Data
modeling
Process
Modeling
Network
modeling
Business &
user
requirements
Current
system details
(and possibly
programs)
Models from
strategic
planning
37
Proposed
systems models
Roles
Techniques
Input
Output
System
Analyst
System
Owners
Systems
users
Business &
Prototypes
User
& Refined
requirements
requirements
System
Owner
System
Users
There are
no tangible
skills required
except for
experience
38
Proposed
systems
requirements
Models and
prototypes
Priorities
Roles
System
Analyst
System
owners
Techniques
Input
Output
Modify Project Scope and Plan
Function point
analysis
Project
management
Proposed
system
requirements
Prioritize
system
models
Projects
Modified
project plan
and size
estimates
System
Analyst
Feasibility
assessment
Report writing
Walkthroughs
Verbal
presentations
39
Appropriate
Business
supporting
requirements
documentation
statements
System Design
System Design is the
evaluation of alternative
solutions and the specification
of a detailed computer-based
solution. It is also called
physical design.
40
Roles
Techniques
Input
Specify Alternative Solutions
-
Analyst
Business
Requirements
Approved
technology
architecture
Ideas
Output
Candidate
solutions
Analyst,
owners
and users
Feasibility Candidate
assessment
solutions
Technical
opinions
Attitude
opinions
Cost and
42 benefits
Feasibility
analysis
Roles
Techniques
Input
Output
43
Roles
Techniques
Input
Output
43
Roles
Techniques
Input
Output
Research Technical Criteria and Options
_
Analyst
Hardware
Potential
and Software
vendors
requirements Options
Product and Technical
vendor facts
criteria
Analyst
45
RFP or
RFQ and
selection
criteria
Roles
Techniques
Input
Output
Analyst
Demonstration
Validation
Criteria
Test
Results
Findings
Proposal
and
quotation
Validated
proposal
Analyst
Feasibility
assessment
Evaluation Hardware
criteria
and
Software
Validated
Proposals
recommen
dation
46
Roles
Techniques Input
Output
Analyst
Hardware and
software
recommendation
Not validated
proposals
Hardware and
software
approval
Hardware and
software aspecs
Debrief of
proposal
Contract and
order
Hardware and
software
recommendation
Analyst
Hardware
and Software
spec
47
Integration
requirement
Techniques
Input
Output
Analyze and Distributed Data
Analyst
with users
Data analysis
Normalization
Event
analysis
Normalized
distributed
data models
and revised
process
models
Analysts,
designers
and users
Data
model
diagram
Target
solution
48
Distributed
process
models