Business Analysis Methodology

Methodology can be purchased as is or customized to your needs.

Business Requirements Methodology Methodology can be purchased as is or customized to your needs.

Business Analysis Methodology Services we offer

  • The format is easy to use and is concise. For each workstep the following is given: Description, Input, Output, Tips & Techniques, Agendas, Roles and Responsibilities, Templates.
  • The methodology is a detailed guide telling you exactly ‘how to’ successfully conduct your projects.
  • Our training is patterned after the methodology and assists you in successfully implementing it. The author of the methodology also wrote the related training seminars.
  • The methodology is relevant and current. It incorporates the Unified Process and uses the notation of the Unified Modeling Language.
  • A number of leading Web Development and E-Commerce consulting companies as well as companies writing intranet and mainframe applications are using our services for development methodology and to train their project teams.
  • Pierson mentors and trains companies to assist them in implementing the methodology.
  • Object-Oriented Methodology

    Pierson’s development methodology can be purchased to provide your organization with:

    • work steps
    • inputs and outputs
    • templates
    • JAD agendas, tips & techniques
    • roles and responsibilities
  • Data, UML & JAD Techniques

    lifecycle_thumbPierson also offers JAD and Business Analysis training which focuses on a data approach using such techniques as data modeling and dataflow diagramming combined with UML, use cases and JAD techniques for the project initiation, requirements gathering and analysis/design phases of software development projects. Pierson’s Requirements Gathering and Writing Training Seminar Using Data Techniques is an intensive class for learning how to develop effective business requirements for Data Driven and Data Warehouse Projects.

  • Methodology

    Pierson’s business analysis training provides a framework for project teams that promotes development iterations throughout the life cycle of a project using an Agile software development approach. Agile requirements gathering and design techniques, agendas and scripts to provide project teams with easy implementation are included in Pierson’s Agile Training.

Customized Development Methodology

Pierson can provide you with a customized methodology for Object-Oriented development projects using the notation of the Unified Modeling Language (UML) and the Unified Process. This customized methodology can be placed on your intranet to serve as a handbook or guide for the software system development teams. This document defines the steps and phases that should be followed, technical modeling options, and refers to quality procedures which should be employed. In this methodology Pierson will provide your company with a repeatable process for:

  • Using the notation of UML Modeling and Unified Process
  • System Development Life Cycle deliverables
  • Joint Application Development (JAD) activities and JAD Session agendas
  • Rapid Application Development (RAD)
  • Documentation templates
  • Best practices to be utilized throughout the Problem Statement, Requirements, Analysis, Design, Construction, Business User Final Acceptance and Transition phases of the system development life cycle.


Pierson can also provide your company with a methodology to evaluate and select a vendor for outsourcing and for evaluation and selection of software packages.

JAD/RAD Process

  • Discovery

    Problem Statement

    JAD Project Scope Definition

    • Use Case Diagram/Mgt. Perspective
    • Project Definition Document

    Requirements Analysis

    JAD Requirements Definition

    • Process Flows, Use Cases, & Glossary
    • CRCs Role Playing or
    • Object Model & Interaction Diagram
    • Prototypes & Functional Specification Draft


    JAD Reviews/Focus Groups – Prototypes

    • Detailed Use Cases & Interaction
    • Static Object Model
    • Functional Specification
  • Design

    Release Plan

    •          JAD – Final Prototype Review & Release
    •         Project Plan


    Design the system and database

    •     Server Object Model, Sequence Diagram
    •     Design Document

  • Why use JAD?

    Why use JAD?

    JAD is a proven method that offers time and cost savings:

    •     25% – 50% of time saved for requirements gathering
    •     25% – 33% time saved over the entire project or 3-4 months out of a year long project

    Not just time and cost savings using JAD:

    •      JAD and prototyping used together give 95% of the user-required functionality
    •     Getting it right the first time
    •     No redesign
    •     Consensus based requirements
    •     Key measure is customer satisfaction
    •     Provides a tool for communication between developer and customer

    Industry studies have shown that 56% of the problems with software are due to poor requirements gathering while only 7% are due to poor coding. 82% of a company’s maintenance effort is due to poor requirements definition while only 1% of its maintenance effort is for fixing code problems

    +find out more

  • Why do facilitated session work?

    Why do facilitated sessions work?

    They create a forum for conflict resolution, creative solutions, consensus and commitment. JAD provides a tool for clear communication and requirements definition. Documentors are available in the workshop to capture the group’s information creating a requirements document that can be distributed. Prototypes are reviewed and discussed.

    +find out more

  • What is RAD?

    What is RAD?

    Rapid Application Development (RAD) is a process that speeds the delivery of functionality to end-users by segmenting software into pieces for delivery rather than delivering all of the software functionality in one large implementation. It is an iterative process utilizing a spiral methodology and is also customer driven following an evolutionary process using continuous application engineering in a time-boxed fashion with a dedicated professional team. The goal of the iterative approach is to reduce the time between requests and delivery of Business Application Software. Some of the primary characteristics of RAD projects are:

    •     There is a strict deadline for basic functionality
    •     Projects can be released in increments
    •     Techniques such as time-boxing, dedicated teams and focus sessions are used
    •     Business users are involved throughout the project and JAD is used
    •     Total project time is usually 3 – 6 months

    +find out more

  • What is UML?

    What is UML?

    An object-oriented graphical modeling language for specifying and communicating the structure and dynamics of software systems. Pierson uses the Unified Modeling Language (UML) and the Unified Process standards. It is used to create business models for requirements analysis, analysis models and design models.

    +find out more