0. Identifying software project stages, tasks and deliverables
José Onofre Montesa Andrés
Universidad Politécnica de Valencia
Escuela Superior de Informática Aplicada

1. GpiI-2C Identifying software project stages, tasks and deliverables
Aim
Breakdown the estimated effort into tasks.
To do that, we shall identify:
project deliverables,
project stages and
project tasks.
GpiI-2C Identifying software project stages, tasks and deliverables

2. GpiI-2C Identifying software project stages, tasks and deliverables
Breakdown Methods:
By Processes
Different conceptual stages
What?, How?, Development, Test ...
by Products
We identify different products that will make up the required system.
Example: Sales, Stock Control, ...
GpiI-2C Identifying software project stages, tasks and deliverables

3. It will be focused to an only product.
Reasons:
Project Size - failure risk.
Coordination costs.
Incremental development.
It is logic that the “strategic direction” is the one in charge to identify the needed products for the enterprise.
GpiI-2C Identifying software project stages, tasks and deliverables

4. Work Breakdown Structure (WBS)
method of representing, in hierarchical manner the components of a process or product.
GpiI-2C Identifying software project stages, tasks and deliverables

5. Graphic representation of WBS.
GpiI-2C Identifying software project stages, tasks and deliverables

6. List representation of WBS.
0. Accounting project.
1. Specify needs
1.1. Study present system.
1.2. Add New characteristics.
2. Analyze Accounting.
2.1. Study Processes.
2.2. Study Data
3. System Design.
3.1. Data Base Design.
3.2. Programs Design.
4. Coding
4.1. Scheme development.
4.2. Programs code.
5. Test.
5.1. Unit test.
5.2. System test.
GpiI-2C Identifying software project stages, tasks and deliverables

7. GpiI-2C Identifying software project stages, tasks and deliverables
WBS
Numbers help to locate tasks in the WBS.
Nodes are read as:
“is contained in”
Developing a WBS.
Identify the top of the WBS.
Partition each component into 72
The lowest level are the task in a project
GpiI-2C Identifying software project stages, tasks and deliverables

8. GpiI-2C Identifying software project stages, tasks and deliverables
TASK CARD
Task specification
Number: 3.1.
Name: Data Base Design.
Description: Designing the data base as proposed in the analysis by entity-relation model, and with the aim to get a system functioning with DB2 .
Estimated Effort : 2 weeks/person
Deliverables: D.B. implementation structure
…: …
GpiI-2C Identifying software project stages, tasks and deliverables

9. Software project Deliverables.
Concept:
"Products interchanged among clients and developers during the software project development".
Relatives:
To the object.
To the project management.
GpiI-2C Identifying software project stages, tasks and deliverables

10. It has to be defined a minimum set of deliverables.
They provide:
the component set that will make the product once the development ended.
The means to measure the progress and quality of the product development.
The needed materials for the following stage.
Usually the enterprises have their own deliverables check list.
GpiI-2C Identifying software project stages, tasks and deliverables

11. Breakdown in stages of a system development.
Since time ago, many enterprises classify the kind of tasks achieved in a project and analyze the effort dedicated to each of them.
We will see same examples provided by Martyn A. Ould, and one an other from HP.
GpiI-2C Identifying software project stages, tasks and deliverables

12. Effort distribution about middle of the ´70
GpiI-2C Identifying software project stages, tasks and deliverables

13. Effort distribution at beginning of the ´80
GpiI-2C Identifying software project stages, tasks and deliverables

14. Effort distribution at the end of the ´80
GpiI-2C Identifying software project stages, tasks and deliverables

15. Effort distribution in HP (´96)
GpiI-2C Identifying software project stages, tasks and deliverables

16. Activity-Based software costing Caper Jones, Computer May 96
GpiI-2C Identifying software project stages, tasks and deliverables

17. Activity-Based software costing Caper Jones, Computer May 96
GpiI-2C Identifying software project stages, tasks and deliverables

18. Activity-Based software costing Caper Jones, Computer May 96
GpiI-2C Identifying software project stages, tasks and deliverables

19. Breakdown the software project into tasks.
By deliverables (More than a week?)
Two horizon levels.
Immediately
Half term
GpiI-2C Identifying software project stages, tasks and deliverables

20. Equipment focusing to identify tasks by activities.
Implying to developers.
Use their knowledge and experience.
The worker perception.
Submission to the goals
Responsibility
GpiI-2C Identifying software project stages, tasks and deliverables

21. Usual ways to identify tasks to a deliverable.
To document, to find out or research,
To Organize, to write documents,
To check, to verify, to review
To Revise, to update documents,
To deliver, to finalize
Other ways:
Breakdown provided by employed technician
GpiI-2C Identifying software project stages, tasks and deliverables

22. Usual tasks in a software project.
Same enterprises have their own check list with a tasks list, were you can find the more important tasks to be considered.
GpiI-2C Identifying software project stages, tasks and deliverables

23. Some ideas on the software project breakdown.
Make the tasks in order to be done by one or two persons in one or to weeks.
Try to have independent tasks, don´t cut natural process.
Worry about people communications.
Reuse code, but it cost time to.
GpiI-2C Identifying software project stages, tasks and deliverables