Collaborative Requirements Gathering Sessions for Agile Projects

The definition of an application’s business requirements is an iterative process.  The main purpose of the JAD sessions is to capture consensus based business requirements and provide the developers with a good understanding of what the business wants the system to do.  JAD sessions should create documents describing the business activities and system interfaces by utilizing use cases and business models.

JAD Requirements Analysis Session-Activity Steps:

1.   Build the High Level Activity Diagram

2.   Develop the Use Case requirements by identifying the following:

·         Further document the software requirements by identifying the main flows, alternate flows, exception flows, business rules, and design constraints.

·         Prioritize the use cases and requirements lists.  These are later used for the iterative release strategy.

3.   Create the State Diagrams for GUI design and/or a Requirements Storyboard

4.   Site Maps (Storyboards) and screen inventories can also be developed

5.   Identify the business objects and their relationships for each use case. The steps for building the Domain Object Model are as follows:

·         Identify the “real world” objects

·         Identify the associations to the other objects

·         Identify the multiplicity

·         List the attributes and operations associated with each object

6.   Build a glossary of definitions – actors, use cases and business objects

JAD Focus Groups

Iterative development requires that further analysis be done on user requirements to support each incremental release.  This requirement is addressed by having JAD-like sessions (focus groups) that build on the results of the requirements sessions.  The purpose of these focus groups is to drill down the requirements into a high-level design solution.  These focus groups are made up of the technical project team and business subject matter experts. 

JAD Focus Group Analysis (High Level Design) Session- Activity Steps:

1.  Provide a detailed definition of the use cases created in the requirements analysis phase.  The use case should describe the details of the user interaction with the system and have the associated screen shots or paper prototypes.

2.   Build use case views for each use case to show how the objects are used in the use case.

3.   Build the sequence diagram for use cases with more complicated workflows and refine the domain object models.

Pierson Requirements Group, Inc. provides the project teams with Agile Modeling Techniques for Collaborative Solutions — check out the class agenda

This is a good article to review on this subject.  http://www.startupcto.com/processes/business-vs-technical-requirements

Joy E. Matthews is the cofounder and Vice President of Training and Consulting Services for Pierson Requirements Group, Inc., (www.piersonrequirementsgroup.com), founded in 1990. She is an Information Systems Specialist with expertise in implementing Iterative Development and Joint Application Development using many development tools.  She is accomplished in business modeling and facilitation techniques.  She has participated in all phases of Information Engineering systems development and Total Quality Management projects.  She has successfully completed Business Process Re-engineering, Information Strategy Planning, Business Area Analysis, Functional Area Analysis and Business System Design projects for a number of organizations and is a certified facilitator.

Joy trains the latest in UML and the use case methodology using JAD.  She is an expert in JAD and UML best practices and industry standards.  She is the co-author of Pierson’s repeatable development Methodology for Multi-Tier Architecture projects using Object-Oriented methods and JAD.  Joy is the author of the JAD Facilitation and Requirements Gathering Seminar:  A Process for Implementing Object-Oriented Projects. She is accomplished in Object-Oriented Requirements Analysis, Analysis and Detailed Design.  She has facilitated and managed projects for all phases of the system development life cycle. 

Joy is the author of the following seminars:  Requirements Gathering & Writing Seminar using Data Techniques, JAD, UML and Use Cases, Business Analysis Seminar, Requirements Gathering & Writing Seminar using JAD, Use Cases and UML, User Acceptance Testing Seminar, Requirements & Specifications Seminar, Facilitated Session Leader Seminar, Learning Use Cases and UML Seminar and Writing Requirements That Work Seminar. Joy can be reached at jmatthews@piersonrequirementsgroup.com