SDLC

Metode Pengembangan Sistem Informasi:
Information Systems
Development Life Cycle
Dr. R. Teduh Dirgahayu

teduh.dirgahayu@uii.ac.id
teduh.dirgahayu@gmail.com
Metode Pengembangan Sistem Informasi
Agenda
Methodology
SDLC
Requirement engineering (RE)
Elicitation
Prioritization
Negotiation
2
26 September 2015
Methodology
The use of methodology improves the practice of IS
development. A methodology includes
Philosophy: set of principles
Phases: series of activities and deliverables
Techniques
Tools
Training
3
26 September 2015
SDLC
Although there are many variants, SDLC has the following
basic structure:
Feasibility study
Requirement analysis
System design
Implementation
Review and maintenance
4
26 September 2015
Feasibility study
Legal
Organizational
Social
Technical
Economical
5
26 September 2015
Requirement analysis
Functional requirements
Non-functional requirements: quality and constraints
Exception conditions
6
26 September 2015
System design
System behavior: processes, inputs, outputs
System structures
Aspects (non-functional requirements): security,
Testing and implementation plans
7
26 September 2015
Implementation
Quality control
Education and training
Documentation
Migration
8
26 September 2015
Migration
Big bang
Parallel
Phased: functionality or organizational unit
I II III IV
I II III IV
9
26 September 2015
Review and maintenance
Change management
Organizational learning
10
26 September 2015
Requirement engineering (RE)
A requirement (IEEE 610.12-1990)
1. A condition or capability needed by a user to solve
a problem or achieve an objective;
2. A condition or capability that must be met or
possessed by a system or system component to
satisfy a contract, standard, specification, or other
formally imposed documents;
A documented representation of a condition or
capability as in (1) or (2).
11
26 September 2015
Ideally, requirements are independent of design, showing
what the system should do, rather than how it should
be done.
In practice, the meanings of what and how differ from
person to person
Requirements Design
12
26 September 2015
Classification
Functional vs. non-functional requirements
Product vs. process requirements
Business vs. technical requirements
Levels: goal, domain, product, design
Source: primary, derived
Role: customer, user, manager
13
26 September 2015
RE process
Elicitation Specification Prioritization Negotiation Validation
14
26 September 2015
Requirement elicitation
Requirements elicitation is the process of seeking,
uncovering, acquiring, and elaborating requirements for
computer based systems.
Stakeholders
Requirements
15
26 September 2015
Elicitation process
Selecting Eliciting
Understanding Identifying
Analyzing the techniques, requirements
application the sources of
stakeholders approaches from
domain requirements
and tools stakeholders
16
26 September 2015
Techniques and approaches
Interview
Questionnaires
Domain analysis
Task analysis
Protocol analysis
Introspection
Prototyping
Scenario
17
26 September 2015
Groupwork
Brainstorming
Requirement workshop
Joint application development
Ethnography
Observation
Apprenticing
Goal-based approach
Viewpoints
18
26 September 2015
Requirement prioritization
Difficulties in decision making
Many alternatives
Trade-offs between aspects to consider
Time and cost constraints
Prioritization helps to identify the most valuable

requirements from this set by distinguishing the critical
few from the trivial many.
19
26 September 2015
Aspects of prioritization
Importance
Cost (in terms of man-hour)
Time
Risks
Penalty
Volatility, uncertainty
20
26 September 2015
Techniques
Categories: quantitative, negotiation
Scale: ordinal, ratio
AHP (analytical hierarchy process)

Cumulative voting, the 100-dollar test
Numerical assignment (grouping)
Ranking
Top-ten requirements
21
26 September 2015
Aspects to consider
Requirements are not mixed between abstraction
levels
Reprioritization when requirements change
Functional and non-functional requirements are
separated
Evaluation of prioritization
22
26 September 2015
Requirement negotiation
The primary purpose of requirements negotiation is to
identify and resolve conflicts among stakeholders. It
contributes to the goal of defining feasible and mutually
satisfactory requirements that accommodate all
stakeholder goals and expectations.
23
26 September 2015
Negotiation process
Pre- Post-
Negotiation
negotiation negotiation
24
26 September 2015
Pre-negotiation:
Problem definition
Stakeholder identification
Goal elicitation
Goal analysis (identify conflicts)
25
26 September 2015
Negotiation:
Structuring issues
Developing alternatives
Defining decision rules
Decision making (resolving conflicts)
26
26 September 2015
Post-negotiation:
analyze and evaluate the negotiation outcomes
suggest re-negotiation if necessary
27
26 September 2015
Conflict resolution strategy
Competing : forcing, win-lose
Accommodating : smoothing, self-sacrificing
Collaborating : problem-solving, win-win
Avoiding : withdrawing form, denial
Compromising : sharing
28
26 September 2015
Summary
SDLC
RE
Elicitation
Prioritization
Negotiation
29
26 September 2015

SDLC

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SDLC

Загружено:

Авторское право:

Доступные форматы

Metode Pengembangan Sistem Informasi:

Dr. R. Teduh Dirgahayu

Phased: functionality or organizational unit

Elicitation Specification Prioritization Negotiation Validation

Prioritization helps to identify the most valuable

AHP (analytical hierarchy process)

Вам также может понравиться