Software Process and Requirement Analysis

Software Process and Requirement Analysis

1• It is mentioned that "Clients often lack appreciation for the complexities inherent in software engineering, particularly regarding the impact of changing requirements." Imagine you are in this situation, what would you do to handle this situation, using knowledge you have learned in software process?

2 Explain why it is important to document quality procedures at the beginning of a project rather than later on. In addition, think about 2 advantages and 2 disadvantages of using standards for documentation in each of the software phases.

3 Give an example of a software application in which the customer is the same as the end user. Give an example in which they are different. In each case, identify the customer and end user.

4 What are three major advantages and disadvantages of describing detailed requirements with unit tests?

5 Explain why a defective requirement could be 100 times more expensive to fix after software is deployed versus being fixed during requirements analysis.

6 Give two advantages and two disadvantages to using standards for documentation of the `various software phases.

7List four of what you consider to be the most important high-level requirements for an application that tracks bar-coded invoices within a company.

8 Describe in your own words the difference between customer wants and customer needs. Provide an example that illustrates the difference