The phrase “requirements management” is used so often that already seems to have lost its original meaning. It is often assumed In the process of development that to manage the requirements is to create them or shifting from state to state. Also assumed that to improve the manageability of the project is enough to describe the system implementation in the form of requirements or to making all the information available about the project in control system development. The report shows why the approach is not working. And that you’ll make work more predictable, if you’ll form the same understanding of the information structure оf project for all project team. First of all it concerns: business requirements, domain description, architecture, system requirements, prototype of GUI, system description.
Anna Abramova
system and business analyst, trainer, SPb СoA
Higher education, Saint Petersburg State University, faculty of applied mathematics and control processes, specialist
6 years as lecturer/trainer in SPbSU, ITMO University, self employed
7 years as system and business-analyst
Experience in problem domains: payment systems, telecommunications, medicine
Development experience with distributed systems and algorithms for processing large amounts of data
Co-founder of Saint-Petersburg Community of Analysts
Speaker and a regular participant of conferences, Analyst Days, Summer Analyst Festival (ЛАФ)
Comment