Problem

You would like to define a concise and complete requirements document using UML formalisms to state the functional requirements and the definition of the application domain.

Process

• Audit the needs of the end-users
• Training of those involved in Use Case formalisms and UML activity diagrams
• Implementing a tool for capturing requirements, e.g. Objecteering/UML Requirements, and a process of traceability process for the requirements
• Writing the requirements document together
• Transfer of know-how to your teams

Benefits

• The development teams acquire know-how on requirements capture, and then become the means of diffusing object technology within the company itself
• Your requirements document is precise and complete, and both parties (project owners, project implementors) can commit themselves to the project on a solid contractual basis