Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 2 (Prototyping (Benefits (Improved system usability, Close match…

- - - - focus on areas of product that are not well understood
      - focus on fuctional rather than nonfuctional requirements
      - error checking and recovery may not be included in prototype
  - - - May be impossible to tune the system to meet nonfunctional requirements
      - undocumented
      - structure is degraded through rapid change
      - will not meet organisational quality standards
- - - - System testing
        
        testing system as a whole
      - Acceptance testing
        
        testing with customer data (to check it meets the customer's need)
      - Component testing
        
        individual components are tested independently
  - - - technically and financially feasible to build system
    - - what do clients require/expect from the system
    - - define requirements in detail
    - - check the validity
- - - - System and Software Design
      - Implementation and Unit Testing
      - Requirements Definition
      - Integration and System Testing
      - Operation and Maintenance
  - - - Requirements Specification
      - Requirements Modification
      - Component Analysis
      - System Design with Reuse
      - Development and Intergration
      - System Validation
- - - - Risk Assessment & Reduction
        
        Risk are assessed and activities put
        in place to reduce the key risks
      - Development & Validation
        
        A development model for the system
        is chosen which can be any generic models
      - Objective Setting
        
        Specific objectives for the phase identified
      - Planning
        
        The project is reviewed and the next phase of spiral is planned
- - - - In-phase
        
        Each phase iterative with results developed incrementally
      - Cross-phase
        
        All iteration can be done incrementally
    - - Manage requirements
      - Use component-based architectures
      - Develop software iteratively
      - Visually model software
      - Verify software quality
    - - Elaboration
        
        Develop understanding of problem domain and system architecture
      - Construction
        
        Systen design, programming and testing
      - Inception
        
        Establish business case for system
      - Transition
        
        Deploy the system in its operating environment