1. Requirements Planning Phase
   
   

   Goal: map broad capabilities of system from the business perspective
   · Outcomes:
   · System's goals
   · Preliminary effort and schedule estimates
   · Decision whether to continue
   
   

2. Design Phase
   · Goal: to create user-level design of the software
   · Detailed user-interface design
   · A database schema (if appropriate)
   · Refined budget and schedule estimates
   · Uses prototyping extensively
   · Does NOT focus on the functional design of the system

   1. Customization
      - Tailor method to project, 1 - 10 days
      - Session: All parties meet, lasts from 1 - 10 days
      - Wrap-up: Notes and visual aids converted into formal documents. Takes 3 - 5 days.
      - Planning
      Customization Session Wrap-up
      Review materials
      
      

3. JAD Analysis Session:
   · orientation
   · define high-level requirements
   · map out system, identify business needs system will address, system objectives,
   anticipated benefits, list of possible system functions, rough prioritization of system
   functions, and strategic and future considerations
   · limiting the system scope
   · decisions on what NOT to include is as important as what the system will include
   · identify and estimate JAD design phase(s)
   · identify the JAD design participants
   · agree on schedule of the JAD design phases
   · document the issues and considerations -- options and reasons
   Joint Application Development (JAD)

4. JAD Analysis Wrap-up Session Document
   · List of system objectives,
   · including strategic and future considerations
   · Details of
   · possible system functions,
   · business needs that each function addresses,
   · benefits of each function,
   · estimate of the return on investment of each function,
   · a rough prioritization of each function
   · Limitation on the system's scope,
   · including a list of functions that the system will NOT include
   · List of interfaces to other systems
   · List of unresolved issues during JAD session,
   · including name of the issue, the person responsible, and the promised resolution date
   · Plan for what happens next,
   · including identification of follow-on JAD design phases, JAD design participants, JAD
   design schedules and rough target dates for implementation.
   
   

JAD Design Session

• orientation

• review JAD planning requirements and scope

• develop workflow diagrams:

  • process charts (BPMN 2.0) linked to

  • textual guides and term glossary

  • design the screen layouts and report formats

• interactive prototypes created by developers and end-users

• specify processing requirements

• specify data volumes, rates, audit requirements, security requirements, …
  · define interface requirements
  · specify systems that the new system must interface to
  · identify system data groups and functions
  · map out major data structures and relationships. If system is database-oriented create a
  normalized database schema
  · document the issues and consideration
  · Record the options considered and reasons issues were resolved how they were
  Joint Application Development (JAD)
  
  

Design Wrap-up Session Document

• Complete documents and solution demo

• Present result to the executive sponsor, including

  • a summary of the design session

  • the JAD design

  • preliminary target implementation dates

  • the project current status and resources