Trillium Model

CS587 Group Presentation
 Improve
product development
 Support Process capability against the
best industry standards
 Help identify possible improvements
within the development organization
 Assist in selecting a supplier
need for lower development and
maintenance costs
 A need for shorter development cycles
 A need to meet schedule requirements
 A need for an improved development
 The
Trillium Model, created by Bell
Canada, combines requirements from the
ISO 9000 series, the CMM for Software,
and the Malcolm Baldrige criteria, with
software quality standards from the IEEE.
 The
effort was initiated in 1994 and it’s
main focus is to consistently deliver a
product or an enhancement to an existing
 that meets customer expectations,
 with minimal defects
 for the lowest life-cycle cost, and
 in the shortest time.
 Northern
 Bell-Northern Research
 Bell Canada
 Mostly Telecommunication companies
voiced the uses of Trillium Model.
Unstructured: The development process is adhoc. Projects frequently
cannot meet quality or schedule targets. Success, while possible, is based
on individuals rather than on organizational infrastructure. (Risk - High)
Repeatable and Project Oriented: Individual project success is
achieved through strong project management planning and control, with
emphasis on requirements management, estimation techniques, and
configuration management. (Risk - Medium)
Defined and Process Oriented: Processes are defined and utilized at the
organizational level, although project customization is still permitted.
Processes are controlled and improved. ISO 9001 requirements such
as training and internal process auditing are incorporated. (Risk - Low)
Managed and Integrated: Process instrumentation and analysis is used
as a key mechanism for process improvement. Process change
management and defect prevention programs are integrated into
processes. CASE tools are integrated into processes. (Risk - Lower)
Fully Integrated: Formal methodologies are extensively used.
Organizational repositories for development history and process are
utilized and effective. (Risk - Lowest)
The Trillium Model covers all aspects of the software development
life-cycle, most system and product development and support
activities, and a significant number of related marketing activities.
Although Trillium has been designed to be applied to embedded
software systems such as telecommunications systems, much of
the model can be applied to other segments of the software
industry such as Management Information Systems (MIS). The
various differences between the Trillium Model and the CMM as
given as follow:
Trillium model architecture is based on roadmaps, rather than key
process areas (KPAs) present in CMM
Trillium Model has a wider product perspective rather than only
based on software process improvement
Trillium claims a wider coverage of capability impacting issues.
Trillium Model has orientation towards customer focus,
technological maturity and telecommunication industry.
We believe that trillium is a pretty good model
compared to other initiatives. It is much more
effective in improving the quality of software.
Because Trillium combines many different
features from many other quality models, as a
result, it is much more flexible and at the same
time it keeps all of the qualities from other
initiatives. For example Trillium model is used for
marketing and hardware development. Since it's
so easy to be used, business can save by using
this model (time, people, learning and etc. )

similar documents