Every system analyst knows what requirements are, where they come from, what kinds of requirements exist, how to collect and analyse them. Unfortunately, requirements management is often confined to these aspects only. In fact, requirements management is needed until the customer accepts the product.
I’ll present you a set of practices, which we use in requirements management. I’ll tell you how to record requirements collected, their estimation and distribution of resources, how to create patterns on the basis of common requirements, how to track changes to requirements and what should be done to prevent losing requirements in the process of engineering.
Then I’ll show you the examples of how to apply these “analytics lifehacks” in Enterprise Architect. This tool allows establishing the connection between the documented need of the customer and the function that implements this need, via connection with the formalised requirement. I’ll outline the advantages of EA.