The discipline of requirements and requirements as a discipline

Before getting into the requirements themselves, let's briefly talk about the need to have a strong tool and approach to manage these requirements, and create a traceability matrix and automated reporting for all functional and nonfunctional business and IT requirements. This would allow an easy flow of communication between business owners, business analysts, project managers, architects, specialists, and stakeholders involved in the development lifecycle. The system and customer requirements should be mapped to owners of those requirements and subsequently to the test cases, tests scripts, and any other artifacts, work item, or activity related to that requirement. Based on the best practices in requirements engineering and management for any development methodology, A2Z Bullion Bank decided to adopt the Collaborative Application Lifecycle Management (CALM) approach. It provides automation, traceability, and reporting needed...