<p>Thirty years ago, I first entered the dark realm of software engineering, through a prior interest in documentation. In those days, documentation pretty much meant functional specifications. The idea that stakeholders in a system (its implementers, its end-users, its maintainers, and so forth) mi
Rationale Management in Software Engineering
β Scribed by Allen H. Dutoit, Raymond McCall, Ivan Mistrik, Barbara Paech
- Year
- 2006
- Tongue
- English
- Leaves
- 449
- Edition
- 1
- Category
- Library
No coin nor oath required. For personal study only.
π SIMILAR VOLUMES
<P>The emphasis on new and changing technologies and process models in todayβs software development obscures the fact that software engineering is still primarily a human-based activity and that the success of a software project largely depends on the decisions made by humans during engineering. Rat
<p><P>Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choice
<P>Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices m
Software engineering products are becoming ever more complex, because software is being used in the solution of more technically difficult problems and because the size of software projects continues to grow. A key question for software engineers is how to cope with this complexity. There is no sing