Please enable JavaScript.

Coggle requires JavaScript to display documents.

Requirements Analysis (Ensure that requirements gathered so far are (Clear…

- - - - Constraints - Budget, timescale, resources etc.
      - Policies - Standards, business rules
      - Legal - Legislative and regulatory constraints
      - Branding - Image, style guide
      - Cultural - Vision, approach, management style
      - Language - if operating across international boundaries
      - Continuity - coping with disaster
    - - Hardware - IT and other hardware
      - Software - Operating Systems, package applications, networking, communications, etc.
      - interoperability - standards for communication between systems and devices
      - Internet - policies on Internet use and web services
  - - - What the product must do
      - What actions it must take, in order to satisfy the product's goals, as defined by the stakeholders
      - They relate to some form of data/information manipulation
      - Must be be implementable and testable
        
        Examples
        
        The System will hold details of all customers including name, address, credit list, date of first order
        
        The system will allow changes to be made to customer details
        
        Report on all orders placed in the last week
        
        Data Entry - Gathering and recording data
        
        Data Maintenance - changes to data including data deletion
        
        Procedural - implementation of business rules
        
        Retrieval requirements - reporting and responding to enquiries
    - - Specify how the product must be
      - What characteristics it must have
      - Specify the way the functionality is to be delivered (the form)
      - Constrains the way the functionality operates
      - Must be implementable and testable
        
        Examples
        
        The systems must be able to respond to 10k queries per day
        
        Reprint the report on demand
        
        Respond to an enquiry on available customer credit within 5 seconds.
        
        Performance -speed of processing transactions
        
        Security - security levels for protection of data
        
        Access - who has access to which functionality and how?
        
        Backup and recovery - Protection against data loss
        
        Archiving and retention -duration, methods, eventual deletion
        
        Robustness -reliability, data integrity, user error
        
        Availability - timeframe for availability of functionality
        
        Usability - ease of learning, ease of use
        
        Capacity - data volumes, transaction volumes, user volumes
      - Major factors in the cost of the product
      - Criteria
        
        Bounded
        
        Independant
        
        Issue on BCM chipsets
        
        Negotiable
        
        may need to be negotiated to align
        cost and benefit
        
        Testable
    - - Functional Requirements (FR) may have non-functional requirements.
      - Non-functional requirements, could lead to the need for functionality
        
        I.e. Access Control leads to functionality for:
        
        Identification of User
        
        Authentication of User