It all starts with requirements. Not only do they define the problem you are trying to solve, but also its value. If used correctly, requirements enable you to make decisions about priority, business value, and even architectural risk. But for many organizations requirements live on an island – an island that sends out communications, but increasingly becomes less and less relevant as the project progresses. How many of your requirement documents are still up to date at the end of the project? When there is a problem, where do you look first – the code, the architecture, the tests, the deployment or the requirements documents? Agile solves this problem by empowering individuals, ‘product owners’, to keep the essence of the requirements in their head to make decisions and drive progress. But for many organizations, the requirements for a system or product are too big to hold in any single person’s head, and maybe your product or system has to be compliant, requiring a documented and traced understanding of the requirements.
Requirements need to be connected to the rest of the lifecycle. They must flow from inception to implementation, and be up to date. To do this requires not just good, modern requirements practices, but also automation. Automation that, in near real-time, synchronizes and links requirements to the other disciplines and integrates requirements into the lifecycle.
Tom Capelle, President, Sodius and Dave West, Chief Product Officer, Tasktop describe how Tasktop Sync can connect IBM Rational DOORS and DOORS Next Generation (DOORS NG) to the lifecycle of development and beyond. They will define the challenge to modern requirements practice and how automation, combined with modern requirements practices, can build bridges from the island that is requirements to the rest of the lifecycle.