UNIT – V
Project Organizations and Responsibilities:
Organizations engaged in software Line-of-Business need to support projects with the infrastructure
necessary to use a common process.
Project organizations need to allocate artifacts & responsibilities across project team to ensure a balance
of global (architecture) & local (component) concerns.
The organization must evolve with the WBS & Life cycle concerns.
Software lines of business & product teams have different motivation.
Software lines of business are motivated by return of investment (ROI), new business discriminators,
market diversification&profitability.
Project teams are motivated by the cost, Schedule&quality of specific deliverables
1) Line-Of-Business Organizations:
The main features of default organization are as follows:
• Responsibility for process definition & maintenance is specific to a cohesive line of business.
• Responsibility for process automation is an organizational role & isequal in importance to the
process definition role.
• Organizational role may be fulfilled by a single individual or several different teams.
Fig: Default roles in a software Line-of-Business Organization.
Software Engineering Process Authority (SEPA)
The SEPA facilities the exchange of information & process guidance both to & from project
1
practitioners
This role is accountable to General Manager for maintaining a current assessment of the
organization’s process maturity & its plan for future improvement
Project Review Authority (PRA)
The PRA is the single individual responsible for ensuring that a software project complies with all
organizational & business unit software policies, practices & standards
A software Project Manager is responsible for meeting the requirements of a contract or some other
project compliance standard
Software Engineering Environment Authority( SEEA )
The SEEA is responsible for automating the organization’s process, maintainingthe organization’s
standard environment, Training projects touse the environment&maintaining organization-wide
reusable assets
The SEEA role is necessary to achieve a significant ROI for common process.
Infrastructure
An organization’s infrastructure provides human resources support, project-independent research &
development, &other capital software engineering assets.
2) Project organizations:
Software Management
Artifacts Activities
Business case Customer interface, PRA interface
Software development plan Planning, monitoring
Status assessments Risk management
Software process definition
Process improvement
System engineering Administration
Software Architecture Software Development Software Assessment
Figure 11-2. Default project organization and responsibilities
• The above figure shows a default project organization and maps project-level roles and
responsibilities.
• The main features of the default organization are as follows:
• The project management team is an active participant, responsible for producing as well as
managing.
• The architecture team is responsible for real artifacts and for the integration of components,
2
not just for staff functions.
• The development team owns the component construction and maintenance activities.
• The assessment team is separate from development.
• Quality is everyone’s into all activities and checkpoints.
• Each team takes responsibility for a different quality perspective.
3) EVOLUTION OF ORGANIZATIONS:
Software Software
Management Management
50% 10%
Software Software Software Software Software Software
Architecture Development Assessment Architecture Development Assessment
20% 20% 10% 50% 20% 20%
Inception Elaboration
Software Software
Management Management
10% 10%
Software Software Software Software Software Software
Architecture Development Assessment Architecture Development Assessment
5% 35% 50% 10% 50% 30%
Transition Construction
Inception: Elaboration:
Software management: 50% Software management: 10%
Software Architecture: 20% Software Architecture: 50%
Software development: 20% Software development: 20%
Software Assessment Software Assessment
(measurement/evaluation):10% (measurement/evaluation):20%
Construction: Transition:
Software management: 10% Software management: 10%
Software Architecture: 10% Software Architecture: 5%
Software development: 50% Software development: 35%
Software Assessment Software Assessment
(measurement/evaluation):30% (measurement/evaluation):50%
