Object Oriented Software Engineering View all facts Glossary Help| Object Oriented Software Engineering View all facts Glossary Help |
| subject > software project |
  | ||||||||||||||
| software project comparison table | ||||||||||||||
| Subject | divide into | be | exceed | is a subtopic of | enjoy by | handle carefully | cancel before | require | become | give | start with | constrain by | has definition | allow |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| average software project | at risk from models that are incomplete, incorrect or not flexible enough | its budget by 90% and its schedule by 120% according to the Standish Group | 11.3 - Cost Estimation | completion 30% of the time according to the Standish Group | ||||||||||
| evolutionary project | more common than green field project | 1.6 - Software Engineering Projects | A software project to modify an existing system | |||||||||||
| green field project | less common than evolutionary project | 1.6 - Software Engineering Projects | software developers because they have a wider freedom to be creative about the design | the design decisions and errors made by predecessors | A software project to develop an entirely new software system from scratch | |||||||||
| large software project | many smaller software projects | at risk from models that are incomplete, incorrect or not flexible enough | 1.6 - Software Engineering Projects | |||||||||||
| project that builds on framework or components | at risk from models that are incomplete, incorrect or not flexible enough | 1.6 - Software Engineering Projects | increasingly common | the developer much of the freedom to innovate that he or she would have if performing green field development | a framework, or involves plugging together several components that are already developed and provide significant functionality | the developer to benefit from reusing software that has been shown to be reliable | ||||||||
| project where requirements have already been determined | at risk from models that are incomplete, incorrect or not flexible enough | 4.2 - The Starting Point for Software Projects | because if the customer has not done a good job of analysis and specification, the requirements are likely to be poor | |||||||||||
| project where requirements must be determined | at risk from models that are incomplete, incorrect or not flexible enough | 4.2 - The Starting Point for Software Projects | ||||||||||||
| small software project | at risk from models that are incomplete, incorrect or not flexible enough | 1.6 - Software Engineering Projects | a single team of three or four developers |
Next subject: state Up: subject Previous subject: software library