Software Requirements For Software Engineering

3078 Words Oct 11th, 2014 13 Pages
John W. Brackett states that “The subject of software requirements is often given far less attention in software engineering education Because of the dependence of this module on than software design, even though its importance is Software Specification: The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, including all the inter-faces to people, to machines and to other software systems. No part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later” (Brackett, 1996). This paper will give the definition of software requirements; how they are determined, specified, documented, and who is included in the process of requirements; and the roles these individuals play in processing requirements. The end of this paper will bring all of these concepts together to help explain why these processes are extremely important. Bracket provides a definition of software requirements that is specifically defined by the Institute of Electrical and Electronics Engineer’s software engineering glossary as “a condition or capability needed by a user to solve a problem or achieve an objective” (IEEE, 1983). IEEE also defines requirements as “condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally…
Open Document