PRINCIPLES OF SOFTWARE ENGINEERING
Glass' law: Requirement deficiencies are the prime source of project failures. This law is backed up by case study evidence from large software development projects. Glass found that in the failed cases, there were far too many requirements, they were unstable due to late changes, and they were ambiguous and incomplete. This project is supported by evidence from the case studies of large software development projects. Glass found in unsuccessful cases, there were too many requirements were unstable due to changes in an advanced stage, and were ambiguous and incomplete. This suggests that there is a relation between the quality of requirements and the project outcome. This suggests that there is a relationship between quality and performance requirements of the project. Boehm's first law: Errors are most frequent during the requirements and design activities and are the more expensive the later they are removed. This is also backed up by case study evidence and contributes to answering the question in the following way: doing the requirements properly will reduce the number of errors in the system, and correcting the errors before starting implementation is going to be less expensive than hunting them down when implementation has already started (or worse, when the system has already shipped). This is also supported by evidence from the case studies and helps to answer the question as follows: the requirements correctly reduces the number of system errors and correct errors before starting your application will be less expensive to take them to the low when...
Please join StudyMode to read the full document