Price: $2,999.00
Length: 3 Days
Print Friendly, PDF & Email

Requirements Engineering Workshop with Use Cases, – Model-Based Requirements Engineering with Use Case

Requirements Engineering Workshop with Use Cases, Use Cases describe possible interactions involving a system and its environment. Use Cases are considered as great tools and effective means for operational and functional requirements elicitation and analysis.

Requirements Engineering Workshop with Use Cases informal definitions of use cases in the analysis process. We present an approach supported by any tool for use cases based requirements engineering and management.

Requirements engineering process based on use cases  provide promising solutions concerning the early high-level requirements gathering problem dealing with system operation and ConOps:

  • One of the primary challenges in a system design process is the ability to elicit the correct and necessary system requirements from the stakeholders and specify them in a manner understandable to them so those requirements can be verified and validated.
  • Data and process models, prototypes, requirement specifications.
  • Understood by designers but not by users.
  • Leads to scope creep, schedule creep, cost overruns.

Requirements Engineering Workshop with Use Cases drives the development of a system by understanding how the system will be used and then helping systems engineers and project managers  for an appropriate system to support the users.

Learn how to drive agile projects using use cases in Requirements Engineering Workshop with Use Cases training course.  All the delegates will model use cases and system validation cases in the beginning of the workshop.

A use case is a description of normal and abnormal conditions and step-by-step,  interactions between a system and actors in its environment.

A use case model includes:

  • Use case description
  • Actors
  • Relationships
  • A relationship between an actor and a use case captures the fact that the actor participates in the use case.
  •  A use case diagram shows use case names, pre and post conditions, actors, relationships between actors and use cases, and relationships between use cases.
  • Include and extend relationship

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. The role of use case modeling in requirements engineering and its relation to system verification and validation, plays a big role in 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.

Learn the benefits of Requirements Engineering and Use-Case Modeling at the Workshop

  • 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.

Requirements Engineering Workshop with Use Case – COURSE AGENDA

Requirements Engineering by Use Case Analysis

  • UML based modeling and analysis
  • Requirements engineering process
  • Identifying, organizing, documenting and modeling changing requirements
  • Requirement and System Conformance
  • Consistent, complete and unambiguous set of requirements
  • Gathering of requirements as a very complex engineering task
  • Iterative refinement process with regular control
  • Problems of Requirements Analysis
  • Failure of projects
  • Projects never completed
  • Completed projects with only partial success
  • Causes of failure
  • Problems with requirements specification
  • Lack of interaction with users
  • Incomplete requirements
  • Changing requirements
  • Use cases and the conceptual model
  • Business modeling based on UML activity diagrams
  • Use cases are elicited and structured starting from the activities of each process
  • Concepts of the conceptual model are obtained from the data that flow between activities

Definition of Requirements Analysis

  • Goals and the objectives of the system
  • Services
  • Functionality needed to design
  • Restrictions of the design process
  • Responsibilities to each requirement
  • Categorization of Requirements
  • High-level (System-level) requirements
  • Stakeholder needs
  • Agreement between the customer and the system analyst
  • Operational requirements
  • Use Cases and Actors
  • Use cases and functional requirements
  • Supplementary requirements
  • Non-functional requirements
  • Software and hardware requirements
  • Low-level (Software-level) requirements

Requirements Engineering with Use Case modeling

  • Actors, Use Cases, Subsystems
  • Scenarios as workflow
  • Architectural description
  • Detailed textual description of Use cases and Scenarios
  • Communication with end users
  • Use Cases and System Validation
  • Use Cases and Requirements Missing Requirements

User-Centered Development and Use-Case Modeling

  • User-centered development
  • Process of systems development based on understanding the needs of the stakeholders
  • Use-case modeling
  • Process of modeling a system’s functions in terms of business events, who initiated the events, and how the system responds to those events
  • Use-case modeling in development environments
  • Compliments traditional modeling tools

Use Case Driven Analysis and Requirements Engineering   

  • Elicit and analyze enough requirements information
  • Use-case diagram
  • Use-case narrative
  • Primary actors
  • External actors
  • Use Case Association Relationship
  • Use Case Extends Relationship
  • Free of specific details about how the system will be built or implemented
  • System implementation assumptions
  • Construct use-case model diagram
  • Documents business requirements use-case narratives

Use Case Driven Approach to Requirements Engineering Process

  • Usage-Oriented Requirements Engineering
  • Hierarchical Use Cases Model with
  • Graphical Representation
  • Ontological and Methodological Issues
  • Integration of Use Case Modeling and Usage-Based Testing
  • An Integrated View on Usage Modeling
  • Functional Requirements Specification with Use Cases
  • Reliability Requirements Specification
  • Use Case Based Requirements
  • Operational Profiles
  • Experiment Planning
  • Experiment Operation
  • Data Analysis
  • Interpretations of Results
  • From Requirements to Design, Testing and V&V with Use Cases

 

 

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.