| project that builds on framework or components | allows the developer to benefit from reusing software that has been shown to be reliable |  |
| gives the developer much of the freedom to innovate that he or she would have if performing green field development | |
| is a subtopic of 1.6 - Software Engineering Projects | |
| is becoming increasingly common | |
| is a kind of software project | |
| starts with a framework, or involves plugging together several components that are already developed and provide significant functionality | |
| software project | does not have economy of scale as it gets larger due to the increasingly large amount of co-ordination involved | |
| is often completed behind schedule and over budget, or are not completed at all | |
| may be at risk from models that are incomplete, incorrect or not flexible enough | |
| often has problem failure to stick to cost and time because of the inherent complexity of software, the relative immaturity of software engineering and its technologies, lack of knowledge and experience on the part of software engineers, the inherent human tendency towards over-confidence, , and pressure to offer excessively low prices and short development times in order to obtain contracts or make sales | |
| should not be undertaken without a sound domain analysis | |
| usually involves modifying an existing system | |
Object Oriented Software Engineering View all facts Glossary Help
