ề
ấ
Các v n đ khác trong SE
BM CNPM – Khoa CNTT –
HVKTQS
10/2012
Outline
ự
ầ
ề :
Qu n lý d án ph n m m
ả
ể
ả
ể
ề
ầ
ầ
ề (SE Cost
Ki u thành viên
Qu n lý nhóm phát tri n ph n m m
Ướ ượ
ng chi phí ph n m m
c l
Estimation)
ả ế
ề
ể
ầ
C i ti n qui trình phát tri n ph n m m
(Software Process Improvement)
Software project management
ạ ộ
ế
ả
Liên quan đ n các ho t đ ng đ m b o:
ượ
ầ
ờ
ả
c giao đúng th i gian và
ầ
ủ
ổ
ứ
Phù h p v i các yêu c u c a các t
ch c phát
ể
ế
t vì
ả
ệ
ế
ị ạ
Vi c phát tri n ph n m m luôn b h n ch
ở
ế ậ
t l p b i
c thi
ượ
ề
ứ
ầ
ầ
ề
Ph n m m c n đ
ộ
ế
đúng ti n đ ;
ớ
ợ
tri n và khách hàng.
ầ
ự
Qu n lý d án là c n thi
ề
ầ
ể
ngân sách và l ch trình đ
ổ
t
ị
ể
ch c phát tri n ph n m m.
Software management – nét riêng
ả
ầ
ẩ
ạ
ẩ
S n ph m vô hình.
ạ ả
ề
Ph n m m là lo i s n ph m linh ho t
duy nh t.ấ
ề
ầ
đ
ể
Quy trình phát tri n ph n m m không
ẩ
ượ
c chu n hóa.
ầ
ề
ỉ ượ
ề
Nhi u d án ph n m m ch đ
ự
c th c
ự
ộ ầ
ệ
hi n m t l n.
Management activities
ế ề
ấ
t đ xu t).
ế
ậ
ạ
Proposal writing (vi
Project planning and scheduling (L p k ho ch và
ự
ậ ị
l p l ch d án).
ự
ậ
Project costing (L p chi phí d án).
Project monitoring and reviews (Giám sát và ra soát
ự
d án).
ự
ọ
Personnel selection and evaluation (L a ch n nhân
ự
s và đánh giá).
Report writing and presentations (Ghi chép và báo
ố
cáo th ng kê).
Project staffing – Nhân sự
ườ
ưở
ữ
Th
ng không có nh ng con ng
ng trong
i lý t
ườ
các d ánự
Ngân sách d án không cho phép s d ng các nhân viên
ử ụ
ượ ả ươ ự
ng cao; đ
ữ ệ ợ
Có th không có nh ng nhân viên có kinh nghi m thích h p;
ự
ỹ
T ch c mu n phát tri n k năng nhân viên thông qua d
ể ố c tr l
ể
ứ
ữ
ả
ả
ớ
ự
ệ
ế
ộ
ệ
Các nhà qu n lý ph i làm vi c v i nh ng khó khăn
ụ ủ
t khi có s thi u h t c a đ i ngũ nhân viên
ạ
ặ
đ c bi
ượ
đ
c đào t o.
ổ
án.
ả
ấ
ầ
Chú ý: Nhóm s n xu t ph n
m mề
ầ
ầ
ứ
ệ ố
ữ
:
Yêu c u v i nh ng thành ph n này
ứ
ậ
ậ
ứ
ầ
ệ
ữ ậ
ể
ộ ố
ỏ ề
ả
ề
ế
ữ
ệ
ế ề
t v công ngh ph n m m
ế
t m t s ngôn ng l p trình
ị
ả
ườ
ự
ả
i ph i gi
ụ
i v lĩnh v c mình ph
ế ủ
Ch nhi m
Cán b phân tích thi t
Cán b ph trách
ứ
ườ
ả
ệ
ạ
ả
ầ
ầ
Cán b ph trách
ề
ế ế ệ ố
ườ
i phân tích thi
i
ớ
ầ
Tri th c ph n c ng
ế
Kh năng ti p c n h th ng
ơ ả
Ki n th c c b n v toán và thu t toán
ề
Nh ng hi u bi
Bi
ế
Kh năng ti p th
ỗ
Ngoài ra, m i ng
ụ ể
trách. C th :
ả
ề
ệ
ủ
+ Ch nhi m đ tài ph i là ng
i có kh năng
ế
ứ
ấ ề ặ ổ
nh t v m t t
ch c, quán xuy n các công vi c
ố ộ ố
ả
chung, có kh năng đ i n i đ i ngo i và kh năng
tâm lí h c.ọ
ườ
+ Ng
ấ ề
ệ ố
ứ
ể
ộ
ế ệ ố
k h th ng
ụ
ộ
ph n c ng
ụ
ộ
ph n m m
ậ
ườ
Các l p trình viên
ụ
ữ
Nh ng ng
i ph
ườ
ầ
i ph trách ph n m m, có
ề
ấ
ả
ươ
ầ
ớ
ụ
ả
ề
ặ
ự
ỏ
i gi
t k h th ng là ng
ụ
ầ
ậ
nh t v chuyên môn, ph trách thu nh n yêu c u
ủ
ế ế
ủ
t k 1 h th ng đáp ng c a
c a khách hàng đ thi
khách hàng.
ế
ế
ụ
+ Ti p đ n là ng
ụ ợ
ệ
nhi m v tr giúp cho c nhóm, cung c p cho nhóm
ợ
ấ ả
t c các ch
t
ng trình tr giúp liên quan, các ph n
ề
m m liên quan, các công c . Đi u đó giúp gi m b t
ứ
ờ
th i gian, công s c và s trùng l p.
trách marketing
People in the process
People are an organisation’s most
important assets.
The tasks of a manager are essentially
peopleoriented. Unless there is some
understanding of people, management
will be unsuccessful.
Poor people management is an
important contributor to project failure.
People management factors
ủ ả ấ ộ
ấ
Consistency (Tính nh t quán): t
ố ử ộ ượ ằ ầ t c các thành viên c a đ i
c đ i x m t cách công b ng, không phân
ể
phát tri n c n đ
ệ ố ử
t đ i x
bi
Respect (Tôn tr ng): các thành viên trong nhóm có các k năng
ỹ
ệ ầ ọ t đó c n đ c tôn tr ng
Inclusion (Hòa đ ng): Có s tham gia c a t
khác nhau và nh ng khác bi
ự ọ
ữ
ồ
ượ
ủ ấ ả
ắ ằ ủ ể ắ
ườ ề t c các thành viên
trong nhóm vào m i công vi c, ch c ch n r ng quan đi m c a
ọ
m i ng i đ u đ
ọ
ệ
ượ
c xem xét.
ạ
ự
ứ ế ể ả ố ự
ề
ả
Honesty (Trung th c): B n ph i luôn luôn báo cáo trung th c v
ẹ
t đ p và
ữ
ự ứ
ứ ữ
ữ ễ
nh ng th đang di n ra: c nh ng th ti n tri n t
ề
ấ
nh ng th đang có v n đ trong d án.
Project planning
ủ
ệ
ế
ầ
ả
ờ
Chi m h u h t th i gian c a công vi c qu n lý
ự
ế
d án.
ữ
ưở
Là ho t đ ng liên t c t
ng
ạ ộ
ầ
ẩ
ế
khi có nh ng ý t
ả
ượ
ườ
ử
ng xuyên đ
ổ
c s a đ i khi có
ạ
Các lo i k ho ch d án khác có th đ
c
ụ ừ
ế
ban đ u cho đ n khi bàn giao s n ph m.
ả
ạ
K ho ch ph i th
thông tin m i.ớ
ạ ế
ể
ể ượ
ầ
ự
ề
ạ
ự
ể ỗ ợ ế
ớ ị
ợ
phát tri n đ h tr k ho ch d án ph n m m
chính phù h p v i l ch trình và ngân sách.
Types of project plan
Plan
Description
Quality plan
Describes the quality procedures and standards that will be
used in a project. See Chapter 27.
Validation plan
Describes the approach, resources and schedule used for
system validation. See Chapter 22.
Configuration
management plan
Describes the configuration management procedures and
structures to be used. See Chapter 29.
Maintenance plan
Predicts the maintenance requirements of the system,
maintenance costs and effort required. See Chapter 21.
development
Staff
plan.
Describes how the skills and experience of the project team
members will be developed. See Chapter 25.
Project planning process
Establish the project constraints
Make initial assessments of the project parameters
Define project milestones and deliverables
while project has not been completed or cancelled loop
Draw up project schedule
Initiate activities according to schedule
Wait ( for a while )
Review project progress
Revise estimates of project parameters
Update the project schedule
Re-negotiate project constraints and deliverables
if ( problems arise ) then
Initiate technical review and possible revision
end if
end loop
The project plan
The resources available to the
project;
The work breakdown;
A schedule for the work.
Project plan structure
Introduction.
Project organisation.
Risk analysis.
Hardware and software resource
requirements.
Work breakdown.
Project schedule.
Monitoring and reporting mechanisms.
Project scheduling
ự
ờ
ụ
ự
Chia d án thành các nhi m v và d toán th i
ỗ
ầ
ệ
ế ể
t đ hoàn thành m i
ệ
ồ ự
gian, ngu n l c c n thi
ụ
nhi m v .
ệ
ứ
ờ ể
T ch c th c hi n các nhi m v đ ng th i đ
ổ
ử ụ
ả
ự
ụ ể
Gi m thi u s ph thu c gi a nhi m v đ
ụ
ự
ệ
ố ư ự ượ
i u l c l
s d ng t
ụ
ể
ễ
ậ
ộ
ế
ụ ồ
ộ
ng lao đ ng.
ệ
ữ
ộ
ệ
ở
tránh s ch m tr gây ra b i m t nhi m v nào
ộ
đó đ d án hoàn thành đúng ti n đ .
ệ
ự
ả
Ph thu c vào tr c giác và kinh nghi m qu n
ự
ể ự
ụ
ộ
ự
lý d án.
The project scheduling process
Identify
activities
Identify activity
dependencies
Estimate resources
for activities
Allocate people
to activities
Create project
charts
Software
requirements
Activity charts
and bar char ts
Scheduling problems
ủ
ứ
ề
ấ
ộ
ể
Đánh giá m c đ khó khăn c a v n đ và
ộ
ả
i pháp là m t bài toán
chi phí phát tri n gi
khó.
Năng su t lao đ ng không t
ườ
ệ
ệ
ộ
ớ
ậ
ỷ ệ
thu n v i
l
ộ
i làm vi c trên m t nhi m
ấ
ng ng
ố ượ
s l
v .ụ
ườ
ự
Thêm ng
ị
ề
ự
ậ
i vào d án ch m làm cho d
án b kéo dài do phát sinh các chi phí
truy n thông.
Bar charts and activity
networks
Graphical notations used to illustrate the
project schedule.
Show project breakdown into tasks. Tasks
should not be too small. They should take
about a week or two.
Activity charts show task dependencies
and the critical path.
Bar charts show schedule against
calendar time.
Task durations and
dependencies
Dependencies
Activity
T1
Duration (days)
8
T2
15
T3
15
T1 (M1)
T4
10
T5
10
T2, T4 (M2)
T6
5
T1, T2 (M3)
T7
20
T1 (M1)
T8
25
T4 (M5)
T9
15
T3, T6 (M4)
T10
15
T5, T7 (M7)
T11
7
T9 (M6)
T12
10
T11 (M8)
Activity network
15 da ys
14/7 /03
15 da ys
M1
T3
8 days
T9
4/8/03
25/8/03
T1
5 days
25/7 /03
M4
M6
T6
4/7 /03
M3
7 days
start
20 days
15 days
T7
T11
T2
5/9/03
25/7 /03
11/8/03
10 days
10 da ys
M8
M2
M7
T5
15 da ys
T4
10 days
T10
18/7 /03
T12
M5
25 days
Finish
T8
19/9/03
Activity timeline
4/7
11/7
18/7
25/7
1/8
8/8
15/8
22/8
29/8
5/9
12/9
19/9
Start
T4
T1
T2
M1
T7
T3
M5
T8
M3
M2
T6
T5
M4
T9
M7
T10
M6
T11
M8
T12
Finish
Staff allocation
4/7
11/7 18/7 25/7
1/8
8/8
15/8 22/8 29/8
5/9
12/9 19/9
Fred
T4
T11
T8
T12
Jane
T1
T3
T9
Anne
T2
T6
T10
Jim
T7
Mary
T5
Risk management
Risk management is concerned with
identifying risks and drawing up plans to
minimise their effect on a project.
A risk is a probability that some adverse
circumstance will occur
Project risks affect schedule or resources;
Product risks affect the quality or performance
of the software being developed;
Business risks affect the organisation
developing or procuring the software.
Software risks
Risk
Affects
Description
Staff turnover
Project
Experienced staff will leave the project before it is finished.
Management change
Project
There will be a change of organisational management with
different priorities.
Hardware unavailability
Project
Hardware that is essential for the project will not be
delivered on schedule.
Requirements change
Project and
product
There will be a larger number of changes to the
requirements than anticipated.
Specification delays
Project and
product
Specifications of essential interfaces are not available on
schedule
Size underestimate
The size of the system has been underestimated.
Project and
product
Product
CASE tool under
performance
CASE tools which support the project do not perform as
anticipated
Technology change
Business
The underlying technology on which the system is built is
superseded by new technology.
Product competition
Business
A competitive product is marketed before the system is
completed.
The risk management process
Risk identification
Identify project, product and business risks;
Risk analysis
Assess the likelihood and consequences of
these risks;
Risk planning
Draw up plans to avoid or minimise the effects
of the risk;
Risk monitoring
Monitor the risks throughout the project;
The risk management process
Risk analysis
Risk planning
Risk
identification
Risk
monitoring
List of potential
risks
Prioritised risk
list
Risk
assessment
Risk avoidance
and contingency
plans
Working environments
The physical workplace provision has an important
effect on individual productivity and satisfaction
Comfort;
Privacy;
Facilities.
Health and safety considerations must be taken
into account
Lighting;
Heating;
Furniture.
The People Capability Maturity Model
Intended as a framework for managing
the development of people involved in
software development.
PCMM Objectives
To improve organisational capability by
improving workforce capability.
To ensure that software development
capability is not reliant on a small
number of individuals.
To align the motivation of individuals
with that of the organisation.
To help retain people with critical
knowledge and skills.
PCMM levels
Five stage model
Initial. Adhoc people management
Repeatable. Policies developed for capability improvement
Defined. Standardised people management across the
Managed. Quantitative goals for people management in
organisation
Optimizing. Continuous focus on improving individual
place
competence and workforce motivation
Software cost estimation
Fundamental estimation questions
How much effort is required to complete an
activity?
How much calendar time is needed to
complete an activity?
What is the total cost of an activity?
Project estimation and scheduling are
interleaved management activities.
Software cost components
Hardware and software costs.
Travel and training costs.
Effort costs (the dominant factor in most
projects)
The salaries of engineers involved in the project;
Social and insurance costs.
Effort costs must take overheads into account
Costs of building, heating, lighting.
Costs of networking and communications.
Costs of shared facilities (e.g library, staff restaurant, etc.).
Costing and pricing
Estimates are made to discover the
cost, to the developer, of producing a
software system.
There is not a simple relationship
between the development cost and the
price charged to the customer.
Broader organisational, economic,
political and business considerations
influence the price charged.
Productivity measures
Size related measures based on some
output from the software process. This
may be lines of delivered source code,
object code instructions, etc.
Functionrelated measures based on an
estimate of the functionality of the
delivered software. Functionpoints are
the best known of this type of measure.
Lines of code
What's a line of code?
The measure was first proposed when programs were typed
How does this correspond to statements as in Java which
can span several lines or where there can be several
statements on one line.
What programs should be counted as part of the
system?
This model assumes that there is a linear relationship
between system size and volume of documentation.
on cards with one line per card;
Function points
Based on a combination of program characteristics
external inputs and outputs;
user interactions;
external interfaces;
files used by the system.
A weight is associated with each of these and the
function point count is computed by multiplying each
raw count by the weight and summing all values.
UFC = (cid:0)
(number of elements of given type) *(weight)
Function points
The function point count is modified by complexity of
the project
FPs can be used to estimate LOC depending on the
average number of LOC per FP for a given language
LOC = AVC * number of function points;
AVC is a languagedependent factor varying from 200300
FPs are very subjective. They depend on the
estimator
Automatic functionpoint counting is impossible.
for assemble language to 240 for a 4GL;
Object points
Object points (alternatively named application points)
are an alternative functionrelated measure to
function points when 4Gls or similar languages are
used for development.
Object points are NOT the same as object classes.
The number of object points in a program is a
weighted estimate of
The number of separate screens that are displayed;
The number of reports that are produced by the system;
The number of program modules that must be developed to
supplement the database code;
Object point estimation
Object points are easier to estimate from a
specification than function points as they
are simply concerned with screens,
reports and programming language
modules.
They can therefore be estimated at a fairly
early point in the development process.
At this stage, it is very difficult to estimate
the number of lines of code in a system.
Productivity estimates
Realtime embedded systems, 40160
LOC/Pmonth.
Systems programs , 150400 LOC/P
month.
Commercial applications, 200900
LOC/Pmonth.
In object points, productivity has been
measured between 4 and 50 object
points/month depending on tool support
and developer capability.
Quality and productivity
All metrics based on volume/unit time are
flawed because they do not take quality into
account.
Productivity may generally be increased at the
cost of quality.
It is not clear how productivity/quality metrics
are related.
If requirements are constantly changing then an
approach based on counting lines of code is not
meaningful as the program itself is not static;
Estimation techniques
There is no simple way to make an accurate estimate
of the effort required to develop a software system
Initial estimates are based on inadequate information in a
The software may run on unfamiliar computers or use new
user requirements definition;
The people in the project may be unknown.
Project cost estimates may be selffulfilling
The estimate defines the budget and the product is adjusted
technology;
to meet the budget.
The COCOMO model
An empirical model based on project experience.
Welldocumented, ‘independent’ model which is not
tied to a specific software vendor.
Long history from initial version published in 1981
(COCOMO81) through various instantiations to
COCOMO 2.
COCOMO 2 takes into account different approaches
to software development, reuse, etc.
COCOMO 81
Process Improvement
Process improvement
ế ề
ể
Hi u bi
ệ
ệ
ệ
ớ
i thi u
t v các quy trình hi n có và gi
ả
ấ ượ
ng s n
ả
ế
ế
ẩ
ả ế
ả
ế
ế
ậ
ẩ
ầ
ế
ề
ả
ủ
ệ
ấ
ố
ớ
ổ ể ả
quá trình thay đ i đ c i thi n ch t l
ộ
ặ
ph m, gi m chi phí ho c đ y nhanh ti n đ .
ệ
H u h t các công vi c c i ti n quy trình cho
ệ
đ n nay t p trung vào vi c gi m khi m khuy t.
ự
Đi u này ph n ánh s quan tâm ngày càng
tăng c a ngành công nghi p đ i v i ch t
ượ
l
ng.
ộ
Tuy nhiên, các thu c tính khác c a quá trình
ể
ấ
ả
ầ
ượ
s n xu t phát tri n cũng c n đ
ủ
ả ế
c c i ti n.
Process attributes
The process improvement cycle
Measure
Change
Analyse
Process improvement stages
Process measurement
Attributes of the current process are
measured. These are a baseline for
assessing improvements.
Process analysis
The current process is assessed and
bottlenecks and weaknesses are identified.
Process change
Changes to the process that have been
identified during the analysis are introduced.
Process and product quality
Process quality and product quality are closely
related and process improvement benefits arise
because the quality of the product depends on its
development process.
A good process is usually required to produce a
good product.
For manufactured goods, process is the
principal quality determinant.
For designbased activity, other factors are also
involved especially the capabilities of the designers.
Principal product quality factors
Development
technolo gy
Process
quality
Product
quality
People
quality
Cost, time and
schedule
Quality factors
For large projects with ‘average’
capabilities, the development process
determines product quality.
For small projects, the capabilities of the
developers is the main determinant.
The development technology is
particularly significant for small projects.
In all cases, if an unrealistic schedule is
imposed then product quality will suffer.
Process measurement
Wherever possible, quantitative process data
should be collected
However, where organisations do not have clearly defined
process standards this is very difficult as you don’t know
what to measure. A process may have to be defined before
any measurement is possible.
Process measurements should be used to
assess process improvements
But this does not mean that measurements should drive the
improvements. The improvement driver should be the
organizational objectives.
Classes of process
measurement
Time taken for process activities to be
completed
E.g. Calendar time or effort to complete an
activity or process.
Resources required for processes or
activities
E.g. Total effort in persondays.
Number of occurrences of a particular
event
E.g. Number of defects discovered.
GoalQuestionMetric Paradigm
Goals
What is the organisation trying to achieve?
The objective of process improvement is to
satisfy these goals.
Questions
Questions about areas of uncertainty
related to the goals. You need process
knowledge to derive these.
Metrics
Measurements to be collected to answer
the questions.
Process analysis and
modelling
Process analysis
The study of existing processes to understand
the relationships between parts of the process
and to compare them with other processes.
Process modelling
The documentation of a process which
records the tasks, the roles and the entities
used;
Process models may be presented from
different perspectives.
Process analysis and
modelling
Study an existing process to understand
its
activities.
Produce an abstract model of the process.
You should normally represent this
graphically. Several different views (e.g.
activities, deliverables, etc.) may be required.
Analyse the model to discover process
problems.
This involves discussing process activities with
stakeholders and discovering problems and
possible process changes.
The CMMI framework
The CMMI framework is the current stage of work on
process assessment and improvement that started at
the Software Engineering Institute in the 1980s.
The SEI’s mission is to promote software technology
transfer particularly to US defence contractors.
It has had a profound influence on process
improvement
Capability Maturity Model introduced in the early 1990s.
Revised maturity framework (CMMI) introduced in 2001.
Process capability
assessment
Intended as a means to assess the
extent to which an organisation’s
processes follow best practice.
There have been various process
assessment and improvement models
but the SEI work has been most
influential.
The SEI capability maturity
model
Initial
Essentially uncontrolled
Repeatable
Product management procedures defined and used
Defined
Process management procedures and strategies defined
Managed
Quality management strategies defined and used
Optimising
Process improvement strategies defined and used
and used
Problems with the CMM
Practices associated with model levels
Companies could be using practices from different levels at
the same time but if all practices from a lower level were not
used, it was not possible to move beyond that level
Discrete rather than continuous
Did not recognise distinctions between the top and the
Concerned with how things were done (the practices) rather
bottom of levels
Practiceoriented
than the goals to be achieved.
The CMMI model
An integrated capability model that
includes software and systems
engineering capability assessment.
The model has two instantiations
Staged where the model is expressed in
terms of capability levels;
Continuous where a capability rating is
computed.
CMMI model components
Process areas
24 process areas that are relevant to process capability and
Goals
Goals are descriptions of desirable organisational states.
improvement are identified. These are organised into 4
groups.
Practices
Practices are ways of achieving a goal however, they are
advisory and other approaches to achieve the goal may be
used.
Each process area has associated goals.
CMMI process areas 1
CMMI process areas 2
CMMI goals
CMMI practices
Practice
Associated goal
Analyse derived requirements to ensure that they are
necessary and sufficient
The requirements are analysed and
validated and a definition of the
required functionality is developed.
Validate requirements to ensure that the resulting
product will perform as intended in the userÕs
environment using multiple techniques as
appropriate.
Select the defects and other problems for analysis.
Root causes of defects and other
problems are systematically determined.
Perform causal analysis of selected defects and other
problems and propose actions to address them.
The process is institutionalised as a
defined process.
Establish and maintain an organisational policy for
planning and performing the requirements
development process.
Assign responsibility and authority for performing
the process, developing the work products and
providing the services of the requirements
development process.
CMMI assessment
Examines the processes used in an organisation and
assesses their maturity in each process area.
Based on a 6point scale:
Not performed;
Performed;
Managed;
Defined;
Quantitatively managed;
Optimizing.
The staged CMMI model
Comparable with the software CMM.
Each maturity level has process areas and
goals. For example, the process area
associated with the managed level
include:
Requirements management;
Project planning;
Project monitoring and control;
Supplier agreement management;
Measurement and analysis;
Process and product quality assurance.
The staged CMMI model
Level 5
Optimizing
Level 4
Quantitatively
managed
Level 3
Defined
Level 2
Managed
Level 1
Initial
Institutional practices
Institutions operating at the managed level
should have institutionalised practices that
are geared to standardisation.
Establish and maintain policy for performing
the project management process;
Provide adequate resources for performing the
project management process;
Monitor and control the project planning
process;
Review the activities, status and results of the
project planning process.
The continuous CMMI model
This is a finergrain model that considers individual or
groups of practices and assesses their use.
The maturity assessment is not a single value but is a
set of values showing the organisations maturity in
each area.
The CMMI rates each process area from levels 1 to
5.
The advantage of a continuous approach is that
organisations can pick and choose process areas to
improve according to their local needs.
A process capability profile
Project monitoring
and control
Supplier ag reement
management
Risk
management
Configuration
management
Requirements
management
Verification
Validation
1
2
3
4
5
ệ
ả
Tài li u tham kh o
ụ ề ậ ầ
R. Pressman, K ngh ph n m m. T p 1, 2, 3. NXB Giáo d c,
i d ch: Ngô Trung Vi
R. Pressman, Software Engineering: A Practioner’s Approach.
ệ
ườ ị ệ ộ ỹ
Hà N i, 1997 (Ng t).
I. Sommerville, Software Engineering. 5th Ed., AddisonWesley,
5th Ed., McGrawHill, 2001. Chapters 3, 4, 5, 6, 7.
1995. Chapters 22, 23, 25.