Академический Документы
Профессиональный Документы
Культура Документы
GOOD COOKING TAKES TIME. IF YOU ARE MADE TO WAIT, IT IS TO SERVE YOU BETTER, AND TO PLEASE YOU.
MENU OF RESTAURANT ANTOINE. NEW ORLEANS
Overview
Context Software project problems Mythical man-month Possible solutions Lessons learned
Context Software improving the quality life of people. Software production is a very complex and expensive task. The global software market exceeds 541 billion dollars. Software costs are composed for:
Direct cost related with its production; Indirect cost as training, installation and maintenance; Hidden costs such as those caused by faults.
Problem
Technology evolution
Problem (2)
between software engineering and software management Product oriented No documentation No project measurement
Progress tracking
"Question: How does a large software project get to be one year late? Answer: One day at a time!"
Conceptual integrity
To make a user-friendly system, the system must have conceptual integrity, which can only be achieved by separating architecture from implementation
Solutions
Lack communication
The software architecture is the tool to communicate decisions that impact on the project and it is the site to achieve the agreement of stakeholders and project participants.
Solutions (2)
Poor quality
Documentation of project activities Identification and definition of process Monitoring activities Definition of metrics Measuring process Postmortem task to end each cycle of development
lessons learned
The process of software development is complex. Some proposed solutions can not be quantified and they are developed by people. Devote more effort in planning offers more chance of success in the project. Future projects need to learn from past mistakes.
Questions
g.pedraza56@uniandes.edu.co