B2T Training

Introduction

• Define students learning objectives.
• What are solution requirements? What are transition requirements?
• Review requirements categories and classifications.
• What are the differences between business and functional requirements?
• Discuss requirements implications based on the type of solution being developed (COTS, in house development, maintenance, BI)
• Learn about the software development approaches used by the team (change driven vs. plan driven) as it relates to solution requirements.

1 hour

Determine the Solution Scope

• Define the solution scope model. Use approved business requirements to define a solution and allocate the solution components to each requirement (traceability).
• Learn a six-step approach to bringing the business domain stakeholders and implementation stakeholders to consensus about the definition of the solution scope:
  • Determine the functionality desired.
  • Elicit the business priority of each function.
  • Assess technical priority and estimated cost of the desired functionality.
  • Break project into phases or iterations.
  • Create a scope model using a use case diagram:
    • Define actors involved with the application.
    • Identify actor interactions.
    • Determine use cases within each phase or iteration.
  • Obtain approval.
• Review the backlog and learn the change driven approach to iteration planning.
• Allocate the requirements to the solution components.

4 hours

Defining Functional Requirements

• Learn to elicit user stories and scenarios.
• Learn to identify use cases.
• Outline each use case for a high-level understanding of broad behavior.
• Identify primary path, alternate path, and exception paths.
• Decompose large use cases into smaller sub-sets, identifying reusable use cases where possible.
• Learn how and where to document system user messages.
• Learn to create detailed use case descriptions.

4 hours

Designing User Interfaces

• Learn to identify where prototypes are necessary.
• Create and document prototypes.
• Learn to document report requirements, including ad-hoc and predefined. Learn the definition of business intelligence.
• Learn to document field edits and screen functionality.
• Incorporate usability principals into user interfaces.

2 hours

Analyze Interface Requirements

• Identify required interfaces based on the phase/iteration plan.
• Determine how each interface is affected by the solution design.
• Write interface requirements for each interface.

3 hours

Identify Non-Functional Requirements

• Identify requirements not previously addressed by business, functional, or technical requirement categories:
  • Performance requirements
  • Security requirements
  • Quality requirements
  • Scalability
• Consider which non-functional requirement types are important for your project.
• Discuss the business analyst role in the development of these requirements.

2 hours

Develop Transition Requirements

• Identify requirements for a smooth rollout of the solution to the business
  • Consider scheduling and timing issues
  • Determine the timing of interface transition and data conversion
  • Consider parallel operations vs. cutover
  • Develop an implementation plan

3 hours

Develop Action Plan/Course Summary Workshop

• Review Business Analysis tasks and skills learned.
• Workshop: What would you do? Determine analysis approach based on case study.
• Develop an Action Plan with next steps on the student's current project.

2 hours