Requirements modeling within Requirements Management
Telelogic DOORS®/Analyst™ provides an easy-to-learn, UML-based requirements modeling capability for drawing models, pictures, and diagrams inside DOORS, the industry's leading requirements management tool. This powerful modeling facility enables requirements analysts to supplement textual requirements with models of the requirements, and maintain complete traceability of the models as well as the requirements. Requirements modeling enhances communication, collaboration, and verification, improving quality by increasing the chance that the requirement will be understood. With DOORS/Analyst, textual requirements and models are automatically kept in-sync; models are 'baselined' and stored with their requirements, ensuring complete consistency and traceability of requirements. |
Analyst Reviews
Butler Group - Telelogic Lifecycle Solutions Technology Audit
Telelogic Lifecycle Solutions is a new grouping of the company’s existing portfolio into a suite that embraces most of the application development lifecycle. This lifecycle is an increasingly collaborative function, and the standalone tools of the past need to be better integrated to streamline the application development process, in order to support the rapid and accurate development of applications that genuinely support the organizations they are deployed in. Read the full Butler Group Technology Audit and find out why they name Telelogic as a leader in advancing ALM tools.
Resources
White Paper: The Systems Engineering Sandwich: Combining Requirements, Models, and Design
In the Systems Engineering "sandwich," requirements management is the "bread and butter" of the development cycle and system modeling provides the "filling." Requirements alone are a little dry; the filling holds the bread together and makes the whole more interesting. It is both the bread and the filling that make the sandwich.
To The Point Guide: Can Pictures Paint a Thousand Requirements?
Have you ever used pictures or diagrams to explain a set of requirements? Have you ever sketched on a whiteboard or a flipchart to ensure that a colleague, user, or customer really understood what was meant by a particular requirement? Chances are that you have. Requirements analysts often find supplementing textual requirements with graphic representations helpful, and many already use drawing tools to make their requirements more effective. But what if the requirements change? How do you make sure that it be useful if you could link to, trace, and 'baseline' the pictures?
