Software Project Management Brochure Template Page 23
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29Software Project Management
23
best practice" [43]. Such standards include universally recognized control
frameworks for software process control and improvement. Some examples
include ISO 9000, ISO 12207, TickIt, and CMM. They provide a basis for
defining systematic activities, roles, and tasks that can be carried out in software
development, independent of individual projects, companies, or designers.
Furthermore, they make possible to understand and manage all of the diverse
forms of software activity from the standpoint of a single framework. Software
project managers should understand and apply these standards and frameworks
as points of reference in software development, in order to ensure that quality is
being designed and built into the products.
The ISO 9000 series of standards provide a generic model for the Quality
Management System (QMS) of a supplier organization that is involved in design
and development activities. It specifies the requirements against which the
organization’s QMS can be formally assessed. ISO 9000’s issue of particular
interest for software industry is ISO 9000-3 Guideline for the Application of ISO
9001 to the Development, Supply and Maintenance of Software.
The ISO 12207 standard covers the entire lifecycle of software, from
inception through extinction. It details processes for acquiring and supplying
software products and services.
TickIt is the standard related to ISO 9000-3. Its purpose is to fill in the gaps
and clarify the relationship between ISO 9000-3 and ordinary software
development operations. It does this by adding additional documentation and
audit requirements to the ISO 9000-3 Guidelines, and by providing direction
needed to implement ISO 9000-3 compliant quality system.
Software Engineering Institute’s Capability Maturity Model (CMM),
described in the Organizational aspects section does not have a formal status;
hence it is called a model, or a framework, rather than a standard. It is used as a
reference to establish the maturity level of an organization's software processes.
The other aspect of the term ``standards" in software development is that of
deploying organizational standards across the life of a project [38]. In large
organizations, having many software development teams, some standardization
of methods across teams is important. For example, an organization may
prescribe standard (consistent) processes, roles, schedules, and reusability
policies across teams and projects. It can lead to many benefits, including better
planning, more predictable outcomes, increased staffing flexibility (decreased
sensitivity to employee turnover), and reuse of experience.
In that sense, the most important standards are those used for the roles and
processes in a development team. There are many such informal standards.
Some of them are developed internally by a company for its sole use; other
standards are developed and marketed by for-profit companies as products. A
good example is the Microsoft Solutions Framework (MSF), which is used in a
number of software development organizations. It revolves around a team with a
process. The roles it prescribes are product management (focusing on customer
satisfaction), program management (on-time delivery), development, testing,
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business