Please enable JavaScript.

Coggle requires JavaScript to display documents.

SOFTWARE PROCESSES (PROCESS WITH ACTIVITIES (Software Design &…

- - - - :question: Design a software structure that realizes the specification.
      - Design activities
        
        Component design
        
        Database design
        
        Architectural design :
        
        Interface design
    - - :question: Translate this structure into an executable program.
  - - - System testing
      - Acceptance testing
      - Component testing
  - - - Feasibility study
      - Requirements elicitation and analysis
      - Requirements specification
      - Requirements validation
- - - - Software prototyping
        
        A prototype is an initial version of a system used to demonstrate concepts and try out design options
        
        Benefits
        
        Improved system usability
        
        • Improved design quality
        
        • Improved maintainability
        
        • Reduced development effort
        
        Process
        
        1.Establish prototype objectives
        
        Define prototype funtionality
        
        3.Develop prototype
        
        4.Evaluate prototype
        
        Throw-Away Prototype
        
        may be impossible to tune the system to meet
        non-functional requirements
        
        Prototypes are normally undocumented
        
        The prototype structure is usually degraded
        through rapid change
        
        The prototype probably will not meet normal
        organizational quality standards
      - Incremental delivery
        
        definition
        
        the development and delivery is broken down into increments with each increment delivering part of the required functionality
        
        the development of an increment is
        started, the requirements are frozen though requirements for later increments can continue to envolve
        
        Incremental development
        
        Develope system and evaluate each increment
        
        agile method
        
        evaluation done by user or customer proxy
        
        incemental delivery
        
        Deploy an increment for use by end-users
        
        realistic evaluation about practical use of software
        
        Difficult to implement for replacement system
        
        Benefit
        
        Customer value can be delivered with each increment so system functionality is available earlier
        
        Lower risk of overall project failure
        
        Early increments act as a prototype to help
        elicit requirements for later increments
        
        highest priority system services tend to
        receive the most testing.
      - Boehm's spiral model
        
        Spiral model sector
        
        objective setting
        
        risk assessment and reduction
        
        development and validation
        
        planning
        
        Usage
        
        helping people think about iteration in software processes and introducing the riskdriven approach to development
        
        represent spiral than sequence of activities backtracking
- - - - In-phase which each of phase is iterative with results developed incrementally.
      - Cross-phase make the whole set of phase may be enacted incrementally.