Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHƯƠNG 2: DEFINE AND DOCUMENT SOFTWARE PROCESS (2/PROCESS COMPONENTS…
CHƯƠNG 2: DEFINE AND DOCUMENT SOFTWARE PROCESS
1/
WHY DEFINE PROCESSES?
nếu mà có thể trả lời "CÓ" một trong 3 câu hỏi, thì CẦN DEFINE PROCESSES
Is there only one person who knows how to do
the task?
Do many people perform the task, but one way
is preferred?
Is the process important for the business goals?
2/
PROCESS COMPONENTS
Input & Output
Items needed to perform the process (input)
Items that are created (artifacts) as part of the
process (output)
Roles & Activities (steps)
Activities define what steps are being performed
Roles define who is performing the step
Process activities are defined at a high-level and
decomposed into
ower levels (e.g. each step may be a subprocess)
Entry & Exit Conditions/Criterias
Conditions/Criterias that must be met before
starting or exiting
Tools
Lists what tools is used in the process
Purpose
Describes what is accomplished & when it is to
be accomplished
Measurement(s)/Metrics
What measurement(s) are performed as part of
the process (e.g. number of defects found, review
time, etc.)
Process Name
Training & References
What training is needed in order to perform the
process
Identifier
Unique identifier; shows where the process fits
within a hierarchy of processes
Templates
Lists reference material necessary
3/
PROCESS DOCUMENTATION METHODS
Graphical
Integrated Definition for Functional
Modeling (IDEF) diagrams
International standard
Standard symbols used
Shows:
Input (material, requirements, equipment, etc.)
Control (data that restricts or provides direction for
an activity)
Mechanisms (humans, machines, & software)
Output (products, services, etc.)
:check: IMPORTANT
Decomposed into lowerlevel activities
Cross-functional diagrams
Shows roles and functions performed
Uses standard symbols
“swim lane”
diagram
Flowcharts
Flowcharts
show activities,
decisions, etc
Standard
symbols used
Narrative description
Entry-Task-Verification/Validation-eXit
(ETVX)*
The model is based on four steps or activities to successfully complete a process, these are represented by the abbreviations ETVX : :check: IMPORTANT
"T" TASKING
"V" VALIDATION
"E" ENTRY CRITERIA (Before starting)
"X" EXIT CRITERIA (After done)
Tasks can be further sub-divided to more detailed
descriptions.
ETVX was developed in the 1980s by IBM to
document their processes.
4/
PROCESS CHARACTERISTIC
8 NHÂN TỐ
VISIBILITY
SUPPORTABILITY
UNDERSTANDABILITY
ACCEPTABILITY
RELIABILITY
ROBUSTNESS
MAINTAINABILITY
RAPIDITY
BENEFIT DEFINE PROCESS
Provides visibility into areas of quality, productivity,
cost and schedule
Improves communication and understanding
Aids in the planning & execution of plans
Provides the ability to capture Lessons Learned
Helps facilitate the analysis/execution of
organization-wide processes
Provides basis for training & skills assessment
