| project where requirements have already been determined | is a subtopic of 4.2 - The Starting Point for Software Projects |  |
| is a kind of software project | |
| must be handled carefully because if the customer has not done a good job of analysis and specification, the requirements are likely to be poor | |
| 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
