During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes “the cost of errors in requirements that weren’t discovered until later” may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided?

Need a paper written? Our academic experts can create an original essay on any subject for ~~$13.00~~ $11/page Learn More

System development aims to create software capable of meeting users’ needs within a specific time frame and budget. This process goes through several stages, and the most important of them is the first – the phase of requirements development. Its clarity and organization determine the project’s success, the development process, and the quality result. This stage’s importance is also confirmed by the fact that the mistakes made here bring the highest financial losses. There are a few ways that can reduce the probability of error and improve the quality of work.

Clients of system developers can be different people and companies, but they are united by one goal – the creation of high-quality software. The most severe problems in the process of development arise from such factors as inaccurate requirements and specifications, insufficient information from the client, or changes in demands in the work process. These reasons are related to the first phase of the requirements analysis. If the errors of requirements could be quickly and economically fixed, the problem would not be so serious. However, they are often detected after a long period and can be masked as design errors.

Using some techniques will help prevent errors that happen due to requirements. For example, Bilal et al. insist on different methods of requirements validation as an effective method of avoiding a problem. Among the four ways they tested, the most effective were requirements prototyping and viewpoint-oriented requirements validation. They involve close cooperation with customers, are suitable for large and small companies, and are less costly than requirements inspection and requirements testing. Prototypes provide customers with an idea of what the end result will be and helps to adjust requirements early in development. Discussion of stakeholder viewpoints helps to identify contradictions and gives impetus to more specific and productive dialogue. The number of error avoidance methods in the analysis of requirements is not limited to these techniques, but they are quite sufficient for the process.

Rate the answer:

Further research on topic

Answer by Academic.tip's expert

An answer to this question is provided by one of our experts who specializes in technology & it. Let us know how much you liked it and give it a rating.

Cite this page

Select a citation style:

References

Academic.Tips. (2022) 'During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes "the cost of errors in requirements that weren’t discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided'. 23 September.

Reference

Academic.Tips. (2022, September 23). During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes "the cost of errors in requirements that weren’t discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided? https://academic.tips/question/during-the-systems-development-life-cycle-sdlc-certain-key-problems-discovered-in-the-later-stages-could-be-directly-traced-back-to-inadequate-and-poor-efforts-in-the-requirements-phase-and-industr/

References

Academic.Tips. 2022. "During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes "the cost of errors in requirements that weren’t discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided?" September 23, 2022. https://academic.tips/question/during-the-systems-development-life-cycle-sdlc-certain-key-problems-discovered-in-the-later-stages-could-be-directly-traced-back-to-inadequate-and-poor-efforts-in-the-requirements-phase-and-industr/.

1. Academic.Tips. "During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes "the cost of errors in requirements that weren’t discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided?" September 23, 2022. https://academic.tips/question/during-the-systems-development-life-cycle-sdlc-certain-key-problems-discovered-in-the-later-stages-could-be-directly-traced-back-to-inadequate-and-poor-efforts-in-the-requirements-phase-and-industr/.

Bibliography

Academic.Tips. "During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes "the cost of errors in requirements that weren’t discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided?" September 23, 2022. https://academic.tips/question/during-the-systems-development-life-cycle-sdlc-certain-key-problems-discovered-in-the-later-stages-could-be-directly-traced-back-to-inadequate-and-poor-efforts-in-the-requirements-phase-and-industr/.

Work Cited

"During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in this week lecture notes "the cost of errors in requirements that weren’t discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided?" Academic.Tips, 23 Sept. 2022, academic.tips/question/during-the-systems-development-life-cycle-sdlc-certain-key-problems-discovered-in-the-later-stages-could-be-directly-traced-back-to-inadequate-and-poor-efforts-in-the-requirements-phase-and-industr/.

Copy