43 Change Control Board(CCB)
CCB reviews the changes made to the work
product certifies certain aspects about the change such as
🞑 Change is well motivated
🞑 Developer has considered and documented the
effects of the change
🞑 Changes interact well with the by other
changes made developers
🞑 Appropriate people (CCB) have validated the
change
Incompletely modified or improperly modified
work products cannot be updated in the
configuration
44 Open source configuration tools
SCCS (Source Code Control System) and RCS
(Revision Control System)
are two popular configuration management tools available
on most UNIX systems
They are used for controlling and managing different versions
of text files
They do not handle binary files
They provide an efficient way of storing versions
that minimize the amount of occupied disk space.
The change control facilities provides by these tools are
🞑 The ability to incorporate restrictions on set of individuals who can
create new versions and facilities for checking components in and
out
45 Contract Management
Definition: Contract management or contract administration is
the management of contracts made with customers, vendors,
partners, or employees.
Types of contract
Acquiring software from external supplier could be done via:
(one way of classification)
a bespoke system - created specially for the customer
off-the-shelf - bought ‘as it is’
customized off-the-shelf (COTS) - a core system
is customized to meet needs of a particular customer
46 Types of contract ( based on paymen
Fixed price contracts
Time and materials contracts
Fixed price per delivered unit
47 Fixed price contracts
Advantages to customer:
known expenditure
supplier motivated to be cost-effective
Disadvantages:
supplier will increase price to meet contingencies
difficult to modify requirements
upward pressure on the cost of changes
threat to system quality
48 Time and materials
Advantages to customer:
easy to change requirements
lack of price pressure can assist product quality
Disadvantages:
Customer liability - the customer absorbs all the
risk associated with poorly defined or changing
requirements
Lack of incentive for supplier to be cost-effective
49 Fixed price per unit delivered
FP count Design implement- total cost/FP
cost/FP ation cost/FP
U p to 2,000 $242 $725 $967
2,001- $255 $764 $1,019
2,500
2,501- $265 $793 $1,058
3,000
3,001- $274 $820 $1,094
3,500
3,501- $284 $850 $1,134
4,000
50 Fixed price/unit example
Estimated system size 2,600 FPs
Price
🞑 2000 FPs x $967 plus
🞑 500 FPs x $1,019 plus
🞑 100 FPs x $1,058
🞑 i.e. $2,549,300
What would be charge for 3,200 FPs?
51 Fixed price/unit
Advantages for customer
customer understanding of how price is calculated
comparability between different pricing schedules
emerging functionality can be accounted for
supplier incentive to be cost-effective
Disadvantages
difficulties with software size measurement - may need
independent FP counter
changing (as opposed to new) requirements: how do you charge?
52 The tendering process
Open tendering
🞑 any supplier can bid in response to the invitation to tender
🞑 all tenders must be evaluated in the same way
🞑 government bodies may have to do this
by local/international law
Restricted tendering process
🞑 bids only from those specifically invited
🞑 can reduce suppliers being considered at any stage
Negotiated procedure
🞑 negotiate with one supplier e.g. for extensions to software already
supplied
53 Stages in contract placement
requirements
analysis
evaluation
plan
invitation to
tender
evaluation of
proposals
54 Requirements document
Introduction
Description of existing system and current environment
Future strategy or plans
System requirements - mandatory/desirable features
Deadlines
🞑 Functions in software, with necessary inputs and outputs
🞑 Standards to be adhered to
🞑 Other applications with which software is to be
compatible
🞑 Quality requirements e.G. Response times
Additional information required from bidders
55 Evaluation plan
How are proposals to be evaluated?
Methods could include:
• 🞑reading proposals
• 🞑interviews
• 🞑demonstrations
• 🞑site visits
• 🞑practical tests
56 Evaluation plan - contd.
Need to assess value for money for each
desirable feature
Example:
🞑 feeder file saves data input
🞑 4 hours a month saved
🞑 cost of data entry at RM20 an hour
🞑 system to be used for 4 years
🞑 if cost of feature RM1000, would it be worth it?
57 Invitation to tender (ITT)
Note that bidder is making an offer in response
to ITT
acceptance of offer creates a contract
Customer may need further information
Problem of different technical solutions to the
same problem
58 Memoranda of agreement (MoA)
Customer asks for technical proposals
Technical proposals are examined and discussed
Agreed technical solution in MoA
Tenders are then requested from suppliers based
in MoA
Tenders judged on price
Fee could be paid for technical proposals
by customer
59 Evaluation of proposals
Check the that it contains all
document
requirements
Interviewing suppliers
Demonstrations
Site visits
Practical tests
60 Typical terms of a contract
Definition-Form of agreement-lease, license, Sale
Goods and services to be supplied
Ownership of software
Environment
Acceptance Standards
Time table
Price and payment method
Legal requirements
61 Acceptance
When work is completed, customer needs
to carry out acceptance testing.
Contract may put a time limit to
acceptance testing – customer must perform
testing bf time expired.
Part or all payment to the supplier
should depend on acceptance testing
62 Contract Management-STEPS
There must be communication between supplier and customer
while the contracted work is carried out.
This interaction leads to changes which vary the terms
of contract.
When the contract is negotiated, certain points in project may
be identified where customer approval is needed.
Example :a project to develop the large system could be
divided into increments ,for each increment there is interface
design phase, customer has to approve the interface first
For each decision point, the deliverable to be presented by
suppliers.
Most changes to requirement may emerge .This vary the
contract terms.
63 Acceptance
When the work is completed, customer
needs to tack action to carry out
acceptance testing.
The contract may put a time limit on how
long acceptance testing can take.
