Course Duration: 2 Days

Course Category: Business Analysis & Requirements Engineering


14 Contact Hours

Mind Mapping Requirements

About the Course


Mind maps are diagrams that are used to capture, visualise and organise ideas. They are an invaluable tool for brainstorming, problem solving and decision making. This two-day course shows how to apply mind mapping techniques to requirements analysis.
The requirements specification is often the weakest link in many software and engineering projects.
Common problems include:
  • lack of stakeholder participation
  • poor communication between stakeholders and requirements analysts
  • over reliance on complicated diagramming notations that stakeholders do not understand
  • the inherent ambiguity of natural language
This course shows how mind maps can be used as a workshop technique to help overcome these problems while at the same time stimulating individual and group creativity.
The course is a hands on course based on a learning by doing philosophy. During the course participants are given ample opportunity to construct a variety of mind maps based on a set of proven requirements analysis templates.
The course also includes an overview of popular open source and freeware software tools that can be used to construct, organise and present mind maps.




Course Features


  • Introduces a simple set of requirements analysis templates and shows how they are
    used to guide the creation of mind maps.
  • Demonstrates how software tools can encourage the on. going restructuring,
    refinement and improvement of mind maps and the requirements they describe.
  • Illustrates how mind maps can serve as the starting point for more formal documents
    and models.
  • Compatible with both large and small teams and formal or agile software development life cycles.




Participant Benefits


  • Toolbox of mind mapping templates and techniques that can be tailored and adapted to new situations.
  • Understanding of how mind mapping can be used to identify, analyse and document requirements.
  • Awareness of mind mapping software tools and how they are best used.




Who Should Attend


  • Process Engineers, Software Engineering Process Group (SEPG) Staff,
    Methodologists, Process Improvement Staff
  • Business Analysts, Business Systems Analysts, Systems Analysts, Functional Analysts
  • Software Development Managers, Software Engineers, Developers, Requirements Engineers, Requirements Analysts
  • Engineering Managers, Systems Engineers, Electrical Engineers, Control Engineers, Mechanical Engineers, Human Factors Specialists
  • Users, User Representatives, Stakeholders, Project Sponsors, Project managers, Program Managers
  • Consultants, educators and trainers




Course Agenda


Introduction to Mind Mapping

  • Underlying theory of mind maps
  • The classic approach to mind mapping
  • Others mind mapping approaches
    • Triangular mind maps

    • Circular mind maps

    • Trees and networks

    • Classifying ideas with mind maps

  • Comparison of mind maps and formal diagrams

Mind Mapping Tools

  • Open source and freeware tools
    • Freemind

    • XMind

    • Cmap Tools

  • Other freeware and proprietary tools

Requirements Analysis Steps

  • Understand system context
  • Identify and analyse stakeholders
  • Identify and decompose system goals
  • Define system concepts
  • Identify and allocate requirements
  • Elaborate requirements

Understanding the System Context

  • "Rich pictures"
  • Mind maps
  • Activity template
    • Stakeholders

    • Actors

    • Objects

    • Tools

    • Rules

    • Responsibilities

Identifying and Analysing Stakeholders

  • Identifying and classifying stakeholders
  • The stakeholder template

    • Customers

    • Actors

    • Viewpoint

    • Goals

    • Owners

    • Environment

  • The environment template

    • Political

    • Economic

    • Social

    • Technological

    • Legal

    • Ecological

Identifying and Decomposing System Goals

  • Types of system goal
    • Maintenance goals

    • Achievement goals

  • System goals and activities

  • Activity breakdowns

  • The activity breakdown template

    • Plan

    • Organise

    • Execute

    • Monitor

    • Control

  • Functions vs. "atomic" activities

  • Drawing and managing activity breakdowns using software tools

Defining System Concepts

  • Concept maps
  • The concept mapping template
    • Events and periods

    • People, places, things

    • Roles

    • Types

  • Drawing and managing concept maps using software tools

Allocating Requirements

  • Requirements template
    • Inform

    • Control

    • Enforce

    • Store

  • Using mind mapping software tools to manage requirements

    • Prioritising and filtering requirements

    • Highlighting dependent and conflicting requirements

  • Identifying systems and sub-systems

  • Defining interfaces

  • Allocating requirements to systems and sub-systems

Elaborating Requirements

  • Text editing features of mind mapping software tools
  • Mind mapping use cases and user stories
  • Scenario template

Using mind maps as the starting point for formal documents and models

  • Exporting mind maps as text from software tools
  • Converting mind maps to UML diagrams

Review and Conclusion



Leave a Reply

Your email address will not be published. Required fields are marked *

PMI, PMP, PMBOK, CAPM, PMI-ACP and the Registered Education Provider logo are registered marks of the Project Management Institute, Inc.
CMMI®, Capability Maturity Model®, Capability Maturity Modeling®, CMM®, PCMM® and Carnegie Mellon® are registered in the US Patent and Trademark Office by Carnegie Mellon University.
ISTQB® is a Registered Trade Mark of the International Software Testing Qualifications Board.
IIBA®, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
The APMG-International Agile Project Management, AgilePM and Swirl Device logos are trademarks of The APM Group Limited.
PRINCE2®, ITIL®, IT Infrastructure Library®, and MSP® are registered trademarks of AXELOS Limited. The Swirl logo™ is a trade mark of AXELOS Limited.
The ITIL Licensed Affiliate logo is a trademark of AXELOS Limited.
SCRUM Alliance REP SM is a service mark of Scrum Alliance, Inc.