This tool mentor provides information on how to use IBM Rational® Requirements Composer® to gain control of evolving
business objectives and drive clarity, context and consensus across the software delivery lifecycle
This collaborative toolset provides the ability to visually capture requirements information as process sketches,
storyboards, user-interface sketches, and rich text to better articulate and communicate the context of your
requirements. Requirements context is further enhanced through shared glossaries, comment threads, and rich-text
editors that facilitate collaboration and communication so teams anywhere in the world can provide inputs, get clarity,
and achieve consensus quickly around developing business-driven architectures, code, test plans, and ultimately
solutions.
-
Reduces risks across the IT lifecycle by eliciting and interconnecting ideas to clarify actual business issues and
enable more effective solutions supported by better architecture, quality, and release management processes.
-
Drive faster project delivery by providing the history and context that team members need to reduce rework, reduces
meetings focused on understanding requirements, and allowing teams to reuse requirements artifacts for future
projects.
-
Iterate quickly with stakeholders using simplified palettes to create business process sketches, UI sketches and
storyboards, use cases, and dynamic glossaries that help remove confusion and build consensus around requirements.
-
Integrates with Rational RequisitePro 7.1 to enhance requirements management capabilities for greater traceability
and alignment to business objectives across the lifecycle. (Also available as Open Beta through the link below).
Tool How-to
The IBM Rational® Requirements Composer® Help provides the most comprehensive instruction on how to actually use
the tool.
Tool Practice mapping
Business Analysis Skill
|
IIBA knowledge area
|
Our Practices
|
Our Tools supporting the practice
|
Organize, Analyze, elaborate on requirements and
document
|
Requirements Analysis and documentation
|
Business Process Sketching
Use-Case Driven Development
|
Information captured in Rich text documents or
using storyboarding, ui sketching, fisrt cut use cases will be categorized into structured set of
requirements (NFR, FR , BR). UC wil be further elaborated, structured and and detailed
|
Verify Requirements
|
Requirements Analysis and documentation
|
Business Process Sketching
Use-Case Driven Development : Determine that the requirements are correctly and completely
defined.
|
Verify specified requirements with Linkability, navigability features
|
Validate Requirements
|
Requirements Analysis and documentation
|
Business process Sketching
Use-Case Driven Developement
Validate that a requirement will satisfy a business need
|
Traceability, Linkability
Commenting on any requirement/artifact
Collaborative environment
|
Data Object
Decision
End Event
Exclusive_Choice
Fork
Intermediate Event
Join
Lane
Message
Pool
Process
Result
Start Event
Sub-Process
Task
|