Escolar Documentos
Profissional Documentos
Cultura Documentos
- People
- The Players
- Team Leaders
- The Software Team
- Coordination and Communication Issues
- The Problem
- Software Scope
- Problem Decomposition
- The Process
- Melding the Problem and the Process
- Process Decomposition
- People:
- Three P’s:
Effective software project management focuses on the three P’s:
(1) people, (2) problem, and (3) process
- Process:
- End users, who interact with the software once it is released for use.
People - Team Leaders
- Project management is a people-intensive activity.
DD: group
communication
group
group
People - The Software Team
Functional tasks
FT1 FTm
P1 X X
X X
X
Pn X
Project manager + n engineers + m tasks
team
engineer
FT1 FTm T1 Tm
P1 X P1 X
X X
Pn X X Pn X X
Team Type DD CD CC
- A closed paradigm:
a team with a traditional hierarchy of authority (like CC)
- The random paradigm:
a team loosely and depends on individual initiative of the team members
- The open paradigm:
heavy communication + control structure like CC
- The synchronous paradigm:
relies on the nature compartmentalization of a problem + little active
communications
- Software scope:
(a) Context:
- How does the software to be built fit into a large system, product, or business?
- What constraints are imposed as a result of the context?
- Functional decomposition:
- Identify and define the functional scope of the system
in terms of functional features and/or sub-functional systems.
- Apply decomposition method on each feature.
Each function to be engineered by the software team must pass through the set
of framework activities:
- customer communication
- tasks to establish effective communications with customers.
- planning - tasks to define resources, timelines, an so on.
- risk analysis - tasks to assess both technical and management risks.
- engineering - tasks to build the application system
- construction and release - installation, release control, and customer support.
- customer evaluation - task to obtain customer feedback and evaluation result.
Process decomposition:
- Select a software process model for the project.
- Define a preliminary project plan based on the set of common
process framework activities.
- Partition the software process based on the tasks and activities
Each function to be engineered by the software team must pass through the set
of framework activities:
- customer communication
- tasks to establish effective communications with customers.
- planning - tasks to define resources, timelines, an so on.
- risk analysis - tasks to assess both technical and management risks.
- engineering - tasks to build the application system
- construction and release - installation, release control, and customer support.
- customer evaluation - task to obtain customer feedback and evaluation result.
Process decomposition:
- Select a software process model for the project.
- Define a preliminary project plan based on the set of common
process framework activities.
- Partition the software process based on the tasks and activities