Phased Process Tutorial

Phase 1

  • Requirements Analysis
    • Define project goals/scope
    • Define key users/system
    • Define users/system needs - understanding
    • Gather user/stakeholder input
      • User/stakeholder interviews/Questions
    • Define constraints of the system.
      • What the system cannot do.
      • What the system must adhere to.
    • Define requirements
      • Critical
      • Non-critical
      • System
      • Features
      • Nice to haves
      • Create use cases

Phase 2

  • Design and Specification
    • Architecture
      • High level architecture
    • Specification
      • Define operating environment specifications
      • Define hardware specifications
      • Define software specifications, technologies used, etc
    • Design
      • System and subsystems
      • UML
        • Class diagrams
        • Sequence diagrams
        • Database/ER diagrams
        • Data flows

Phase 3

  • Implementation
    • Development team education
      • System Design
      • Subsystem design
      • J2EE programming
      • J2EE standards and practice
        • Buddy Programming
        • Pair programming junior/senior developers
        • Peer code reviews?

Phase 4

  • Testing
    • Create test cases
    • Create unit tests

Methodology

  • Rational Unified Process (RUP) vs. eXtreme Programming (XP)
    • RUP
      • Formal iterative phases
      • Requirements Analysis
      • Design
      • Implementation
      • Testing
    • XP
      • Informal iterative phases
      • No design, creation of user stories
      • Buddy programming, refractoring
      • Standup meetings

Possible Artifact Creation

  1. Process document
  2. Requirements document
  3. Architecture document
  4. Design document
  5. Creation of J2EE learning materials
  6. Test document

Possible Process

1. Elicit/Document requirements

  • Requirements document
    2. Create Use cases
  • Use case document
    3. Create Specification
  • Specification document
    4. Design system architecture
  • Architecture document
    5. Design subsystems
  • Design Document
    • Class diagrams
    • Sequence diagrams
      6. Iteration creation
  • Decide on use case subset
  • Implement use case subset
    7. Test
    8. Create new iteration

Procedures

  1. Initial Formal process
  2. Code Reviews
  3. Coding standards
  4. Buddy Programming
  5. Stand up meetings
  6. Requirements Management system
  7. Design Management system
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.