Business users often describe requirements from their perspective and from what they want. System architects turn these desires into technical requirements. Within this process, there are many places for ambiguity to take hold. Complete the following:
· Research and find a recent software/programming example where the final application did not meet the end user's needs.
· Describe if the requirements were written in quantitative or qualitative measurable terms.
· Discuss what could have been done to help mitigate ambiguity and improve the requirement capture and implementation processes.
Full Answer Section
To help mitigate ambiguity and improve the requirement capture and implementation processes, the following could have been done:
- The requirements for the MCAS system should have been written in quantitative terms. This would have made it clear to pilots how the system should work.
- The requirements should have been communicated to pilots in a clear and concise way. Pilots should have been trained on how to use the system and how to disable it if necessary.
- The software should have been tested thoroughly before it was put into production. This would have helped to identify and fix any potential problems with the system.
By following these steps, the Boeing 737 MAX software crisis could have been avoided.
Here are some other examples of software applications that did not meet the end user's needs due to ambiguity in the requirements:
- The Theranos blood testing machine: The Theranos blood testing machine was supposed to be able to run hundreds of tests from a single drop of blood. However, the machine was not accurate and it did not meet the needs of doctors and patients.
- The Healthcare.gov website: The Healthcare.gov website was supposed to make it easier for people to sign up for health insurance under the Affordable Care Act. However, the website was plagued by technical problems and it did not meet the needs of users.
- The Millennium Falcon ride at Disneyland: The Millennium Falcon ride at Disneyland was supposed to be an immersive experience that would allow guests to feel like they were flying the Millennium Falcon. However, the ride was not as immersive as expected and it did not meet the expectations of guests.
In all of these cases, the ambiguity in the requirements led to problems with the final product. By taking steps to mitigate ambiguity, organizations can improve the chances of their software applications meeting the end user's needs.
Sample Answer
here is a recent software/programming example where the final application did not meet the end user's needs:
The Boeing 737 MAX software crisis: In 2018, two Boeing 737 MAX airplanes crashed, killing 346 people. The crashes were caused by a software problem that was not properly communicated to pilots.
The software problem was related to the MCAS system, which is designed to prevent the plane from stalling. The MCAS system would automatically point the nose of the plane down if it detected that the plane was in danger of stalling. However, the MCAS system was not properly explained to pilots, and they did not know how to disable it.
The requirements for the MCAS system were written in qualitative terms. The requirements said that the system should "prevent the plane from stalling," but they did not specify how the system should do this. This ambiguity led to the software problem that caused the crashes.