Module-V

• Managing Contracts and People

By. Dr.Madhulika 3
By. Dr.Madhulika 5
By. Dr.Madhulika 6
By. Dr.Madhulika 7
By. Dr.Madhulika 8
By. Dr.Madhulika 9
Lets try!

By. Dr.Madhulika 10
By. Dr.Madhulika 11
By. Dr.Madhulika 12
By. Dr.Madhulika 13
By. Dr.Madhulika 14
By. Dr.Madhulika 15
By. Dr.Madhulika 16
By. Dr.Madhulika 17
By. Dr.Madhulika 18
Stages in Tendering

By. Dr.Madhulika 19
By. Dr.Madhulika 20
Terms-Contract Management

By. Dr.Madhulika 21
By. Dr.Madhulika 22
By. Dr.Madhulika 23
Managing people-M5-PART2

By. Dr.Madhulika 24
By. Dr.Madhulika 25
By. Dr.Madhulika 26
By. Dr.Madhulika 27
By. Dr.Madhulika 28
By. Dr.Madhulika 29
By. Dr.Madhulika 30
By. Dr.Madhulika 31
By. Dr.Madhulika 32
By. Dr.Madhulika 33
By. Dr.Madhulika 34
By. Dr.Madhulika 35
By. Dr.Madhulika 36
By. Dr.Madhulika 37
By. Dr.Madhulika 38
By. Dr.Madhulika 39
By. Dr.Madhulika 40
By. Dr.Madhulika 41
By. Dr.Madhulika 42
By. Dr.Madhulika 43
Extreme programming

By. Dr.Madhulika 44
 Module -5-Contd..
• Software Quality

45
 The importance of software
quality
• Increasing criticality of software
• The intangibility of software
• Project control concerns:
– errors accumulate with each stage
– errors become more expensive to remove the later
they are found
– it is difficult to control the error removal process
(e.g. testing)

46
Dr.Madhulika Bhatia
ISO standards: development life
cycles
A development life cycle (like ISO 12207) indicates
the sequence of processes that will produce the
software deliverable and the intermediate products
that will pass between the processes.
deliverable
intermediate
elicit require-
requirements products tested code
ments

processes design s/w code/test

software architecture

48
 ISO standards
ISO 9126 Software product quality
Attributes of software product quality
– External qualities i.e apparent to the user of the
deliverable
– Internal qualities i.e. apparent to the developers
of the deliverables and the intermediate products

ISO 14598 Procedures to carry out the

assessment of the product qualities defined
in ISO 9126

49
 ISO standards
ISO 15504
Assessment of the quality of the processes in the
defined life cycle that produce intermediate
and deliverable software products.

50
ISO 9126 software product quality
Software products Effect of software
Process
product

influences influences influences

internal external quality
process quality quality in use
quality attributes attributes attributes
depends on
depends on

Process measures Internal External Quality in use

Context
(ISO 15504) measures measures measures
of use

51
 Quality in use
• Effectiveness – ability to achieve user goals with
accuracy and completeness
• Productivity – avoids excessive use of resources in
achieving user goals
• Safety – within reasonable levels of risk of harm
to people, business, software, property,
environment etc,
• Satisfaction – happy users!

‘users’ include those maintain software as well as

those who operate it.

52
ISO 9126 software qualities
functionality does it satisfy user needs?

reliability can the software maintain its level

of performance?
usability how easy is it to use?

efficiency relates to the physical resources

used during execution

maintainability relates to the effort needed to

make changes to the software

portability how easy can it be moved to a

new environment?
53
 Sub-characteristics of Functionality
• Suitability
• Accuracy
• Interoperability
– ability of software to interact with other
software components
• Functionality compliance
– degree to which software adheres to
application-related standards or legal
requirements e.g audit
• Security
– control of access to the system 54
 Sub-characteristics of Reliability
• Maturity
– frequency of failure due to faults - the more
the software has been used, the more faults
will have been removed
• Fault-tolerance
• Recoverability
– note that this is distinguished from ‘security’ -
see above
• Reliability compliance
– complies with standards relating to reliability

55
 Sub-characteristics of Usability

• Understandability
– easy to understand?
• Learnability
– easy to learn?
• Operability
– easy to use?
• Attractiveness – this is a recent addition
• Usability compliance
– compliance with relevant standards
56
Sub-characteristics of Efficiency

• Time behaviour
– e.g. response time
• Resource utilization
– e.g. memory usage
• Efficiency compliance
– compliance with relevant standards

57
 Sub-characteristics of Maintainability
• Analysability
– ease with which the cause of a failure can be
found
• Changeability
– how easy is software to change?
• Stability
– low risk of modification having unexpected
effects
• Testability
• Maintainability conformance
58
 Sub-characteristics of portability
• Adaptability
• installability
• Co-existence
– Capability of co-existing with other independent
software products
• Replaceability
– factors giving ‘upwards’ compatibility - ‘downwards’
compatibility is excluded
• Portability conformance
– Adherence to standards that support portability

59
 Using ISO 9126 quality standards

• Judge the importance of each quality for

the application
– for example, safety critical systems - reliability
very important
– real-time systems - efficiency important
• Identify relevant external measurement
within ISO 9126 framework for these
qualities, for example
– mean-time between failures for reliability
– response-time for efficiency

60
 Using ISO 9126 quality standards
response rating
(secs)
• map measurement <2 Exceeds
onto ratings scale requirement
2-5 Target range
to show degree of
user satisfaction – 6-10 Minimally
acceptable
for example >10 Unacceptable
response time

61
 Using ISO 9126 quality standards

• Identify the relevant internal

measurements and the intermediate
products in which they would appear
e.g. at software design stage the estimated
execution time for a transaction could be
calculated

62
Specifying software evaluation
• may apply to:
– final products
– intermediate products (predictive metrics)
• may be:
– relative or binary (does it/ does it not exist?) –
latter may need expert judgment or use of
checklists
– direct or indirect

63
How do we achieve product quality?
• the problem: quality attributes tend to
retrospectively measurable
• need to be able to examine processes by
which product is created beforehand
• the production process is a network of sub-
processes
• output from one process forms the input to
the next
• errors can enter the process at any stage
64
 Correction of errors
• Errors are more expensive to correct at
later stages
– need to rework more stages
– later stages are more detailed and less able to
absorb change
• Barry Boehm
– Error typically 10 times more expensive to
correct at coding stage than at requirements
stage
– 100 times more expensive at maintenance
stage
65
 For each activity, define:

• Entry requirements
– these have to be in place before an activity can
be started
– example: ‘a comprehensive set of test data and
expected results be prepared and
independently reviewed against the system
requirement before program testing can
commence’

66
 For each activity, define

• Implementation requirements
– these define how the process is to be
conducted
– example ‘whenever an error is found and
corrected, all test runs must be completed,
including those previously successfully passed’

67
 For each activity, define

• Exit requirements
– an activity will not be completed until these
requirements have been met
– example: ‘the testing phase is finished only
when all tests have been run in succession with
no outstanding errors’

68
 Inspections - general principles

• when a piece of work is completed, copies

are distributed to co-workers
• time is spent individually going through the
work noting defects
• a meeting is held where the work is then
discussed
• a list of defects requiring re-work is
produced

69
Inspections - advantages of approach

• an effective way of removing superficial

errors from a piece of software
• motivates the software developer to
produce better structured and self-
descriptive code
• spreads good programming practice
• enhances team-spirit
• the main problem maintaining the
commitment of participants
70
Dr.Madhulika Bhatia
SO 9001
ISO 9001 was first published in 1987 by the International Organization for
Standardization (ISO), an international agency composed of the national standards
bodies of more than 160 countries. The current version of ISO 9001 was released in
September 2015.

Dr.Madhulika Bhatia
 SEE YOU IN NEXT SEMESTER

BEST OF LUCK

NICE TEACHING YOU

Dr.Madhulika Bhatia