Neneng, M.Kom.

LEARNING OBJECTIVE

• Having ability to describe systems development

projects fail
• Having ability to define the unique role of systems
analysts in the development of information systems
• Having ability to describe systems development life
cycle
• Having ability to describe systems development
methodology
Textbook
1 45% mengalami
over budget
2 7% mengalami
over time

3 56% proyek
memberikan dari
manfaat yang dijanjikan

(Bloch dkk., 2012)

 1 2
Dalam satu tahun,
hanya 2% dari seluruh
49% responden
organisasi yang selalu
mengalami
berhasil mencapai
setidaknya satu kali
manfaat yang
kegagalan proyek 3 ditargetkan,

86% dari seluruh

organisasi yang
disurvei kehilangan
sampai 25% dari
target keuntungan

(Zarrella dkk., 2005)

CONTOH KEGAGALAN PROYEK TI

(Keil dkk., 2014)

CONTOH KEGAGALAN PROYEK TI (lanjutan)

(Kanaracus, 2012)
10
11
 Analyst Related Role
1 Business analyst

2 System analyst

3 Infrastructure analyst

4 Change management analyst

5 Project manager
Project Manager
 Focuses on business issues surrounding the
system
• The business value of the system
• Improvements in business processes
• New business processes needed with new
system

 Requires business skills and professional

training
 The systems analyst is a key person analyzing
the business, identifying opportunities for
improvement, and designing information
systems to implement these ideas
 Focuses on Information System (IS) Issues
◦ How IS can improve business processes
◦ Designs new information system
◦ Ensures IS quality standards are maintained

 Requires training & experience in design

analysis, programming, business (to lesser
degree)
1 Working
Working knowledge of information technology

Computer programming experience

experience and
2 expertise

General business knowledge

3
4 General problem-solving skills

5 Good interpersonal communication skills

6 Good
Good interpersonal relations skills

Flexibility and adaptability

7
8 Character and ethics
 Focuses on interfaces between new system
& existing infrastructure
◦ Makes sure new system follows organizational
standards
◦ Identifies required infrastructure changes

 Requires experience in network & database

administration
 Requires knowledge of hardware systems
 Focuses on system installation
• Documentation & support for users
• Coordinate training of users
• Strategies to overcome resistance
 Requires experience in organizational
behavior
 Requires experience in change management
 Responsible for schedule and budget
 Ensures promised benefits are delivered
 Manages team members
 Responsible for project plan and reporting
progress
 Requires project management experience
1. Planning: Why build the system?
• System request, feasibility analysis, project
size estimation
2. Analysis: Who, what, when, where will the system be?
1. Requirement gathering, business process
modeling
3. Design: How will the system work?
• Program design, user interface design, data
design
 Implementation: System construction and delivery
• System construction, testing, documentation
and installation
1. Identifying business value (System
Request)
• Lower costs
• Increase profits

2. Analyze feasibility
• Technical Feasibility
• Economic Feasibility
• Organizational Feasibility

(System Proposal)
1. Requirement gathering by answering the
questions:
• Who will use the system?
• What will the system do?
• When will it be used?
2. Investigate the current system
3. Identify possible improvements
4. Develop a concept for new system

(System Specification)
1. Program Design (UML Diagrams)
• What programs need to be written
• Exactly what each program will do
2. User Interface Design
• How users interact with system
• Forms / reports used by the system
3. Data Design (ER Diagrams)
• What data is to be stored
• What format the data will be in
• Where the data will be stored

(System Specification)
1. Construction
• New system is built and tested
• Often testing is the longest part
2. Testing
• Unit Testing
• Integration Testing
• System Testing
• User Acceptance Test
3. Installation
• Old system is turned off
• New system is turned on
 A formalized approach to implementing
the Software Development Life Cycle
(SDLC) (Dennis, 2012)
 A simplified representation of a software
process (Sommerville, 2015)
 A distinct set of activities, actions, tasks,
milestones, and work products required to
engineer high quality software (Pressman, 2015)
1. Structured Design
• Waterfall method
• Parallel development
2. Rapid Application Development
• Phased Development
• Prototyping
• Throw-away Prototyping
3. Agile Development
• Extreme Programming (XP)
• Scrum
• Lean Development
(Dennis, 2012)
 The systems analyst is a key person
analyzing the business, identifying
opportunities for improvement, and
designing information systems to
implement these ideas
 There are five major team roles:

1. Business analyst
2. Systems analyst
3. Infrastructure analyst
4. Change management analyst
5. Project manager
 The Systems Development Lifecycle
consists of four stages: Planning, Analysis,
Design, and Implementation
 The major development methodologies:
1. Structured design
 Waterfall method
 Parallel development
2. RAD development
 Phased Development
 Prototyping
 Throw-away Prototyping
3. Agile development
 Extreme Programming
 Scrum
1. Alan Dennis et al, Systems Analysis and Design with
UML 4th Edition, John Wiley and Sons, 2013
2. Kenneth E. Kendall and Julie E Kendall, Systems
Analysis and Design 8th Edition, Prentice Hall, 2010
3. Hassan Gomaa, Software Modeling and Design: UML,
Use Cases, Patterns, and Software
Architectures, Cambridge University Press, 2011
4. Gary B. Shelly and Harry J. Rosenblatt, Systems
Analysis and Design 9th Edition, Course
Technology, 2011
5. Howard Podeswa, UML for the IT Business Analyst
2nd Edition, Course Technology, 2009
6. Jeffrey A. Hoffer et al, Modern Systems Analysis and
Design 6th Edition, Prentice Hall, 2010

41