دانلود کتاب راهنمای نیازمندی ها و تحلیل کسب و کار

If a system is a solution, requirements state the problem. Since a solution to the wrong problem is useless, stating the problem is as important as building the solution. Hence the centrality of requirements engineering — also known as business analysis — in information technology. Good requirements are among the most treasurable assets of a project. Bad requirements hamper it at best and doom it at worst. In software development as practiced today, requirements are more often bad than good. What passes for requirements in too many projects is a loose collection of “use cases” or “user stories”, revealing the kind of amateurish process that used to plague other tasks of software engineering such as design, programming and testing. While these solution-side tasks have benefited from enormous progress in the last decades, on the problem side requirements remain the sick part of software engineering. The goal of this book is to redress the balance so that the requirements you produce will support rather than hinder your projects. It is not a theoretical treatise but a Handbook, devised to provide you with concrete and immediately applicable guidance.