Requirements Engineering Workshop with Use Cases Informal Definitions of Use Cases in The Analysis Process

Requirements Engineering Workshop with Use Cases Informal Definitions of Use Cases in The Analysis Process

Requirements engineering is the process of stimulating the needs and desires of stakeholders and developing them into an agreed set of detailed requirements, which can be used as the basis for all subsequent development activities.

The purpose of requirements engineering methodology is to make the stated problem more clear and complete, and to ensure that the solution is correct, reasonable and effective.

Use cases are methods used in system analysis to identify, clarify, and organize system requirements.

A use case consists of a set of possible interaction sequences between a system and a user related to a specific goal in a specific environment. This method creates a document that describes all the steps the user takes to complete the activity.

The use-case-based requirements engineering process provides promising solutions for the collection of early high-level requirements, which collect issues related to system operation and concept of operations:

• Derive correct and necessary system requirements from stakeholders and specify them in a way that they can understand so that those requirements can be verified and confirmed.
• Data and process models, prototypes, requirement specifications.
• Understood by designers but not by users.
• Leads to scope creep, schedule creep, cost overruns.

The Use Case Model describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between a user (human or machine) and the system. A Use Case is a single unit of meaningful work; for example login to system, register with system and create order are all Use Cases. Each Use Case has a description which describes the functionality that will be built in the proposed system. A Use Case may 'include' another Use Case's functionality or 'extend' another Use Case with its own behavior.

A Use Case description will generally include:

• General comments and notes describing the use case
• Requirements – Things that the use case must allow the user to do
• Constraints – Rules about what can and can’t be done
• Scenarios – Sequential descriptions of the steps taken to carry out the use case.
• Scenario diagrams – Sequence diagrams to depict the workflow.
• Additional attributes such as implementation phase, version number, complexity rating, stereotype and status.

Successful development of systems and software systems depends on the quality of the requirements and requirements engineering process. Use cases and operational scenarios are promising tools for identifying, eliciting, analyzing, specifying and validating requirements.

Tonex provided Requirements Engineering Workshop with Use Cases. The workshop covers the concepts and representations in use case modeling. Semantic issues are described and illustrated and notations based on natural and graphical languages are provided.

Course Objectives:

• Provides a tool for capturing functional requirements.
• Assists in decomposing system scope into more manageable pieces.
• Provides a means of communicating with users and other stakeholders concerning
• system functionality in a language that is easily understood.
• Provides a means of identifying, assigning, tracking, controlling, and management system development activities, especially incremental and iterative development.
• Provides an aid in estimating project scope, effort, and schedule.
• Provides a baseline for testing in terms of defining test plans and test cases.
• Provides a baseline for user help systems and manuals as well as system development documentation.
• Provides a tool for requirements traceability.
• Provides a starting point for the identification of data objects or entities.
• Provides functional specifications for designing user and system interfaces.
• Provides a means of defining database access requirements.
• Provides a framework for driving the system development project.

Course Outline:

• Requirements Engineering by Use Case Analysis
• Definition of Requirements Analysis
• Requirements Engineering with Use Case modeling
• User-Centered Development and Use-Case Modeling
• Use Case Driven Analysis and Requirements Engineering
• Use Case Driven Approach to Requirements Engineering Process

For More Information:

Requirements Engineering Workshop with Use Cases