Please enable JavaScript.

Coggle requires JavaScript to display documents.

3.3 (BUSINESS APPLICATION DEVELOPMENT (Initiated in following situations…

- - - - Objective
        
        collect, collate, store, archive and share information with business users
        
        various applicable support functions on a need-to-know basis.
      - use the SDLC or other, more detailed software engineering approaches for development. #
    - - Objective
        
        to provide different views of data for their performance optimization.
      - includes decision support systems (DSSs) and geographic
        information systems (GISs).
  - - - which allows objective evidence to be collected in order to measure the business value of an application and to prioritize requirements.
- - - - approach is based on a systematic, sequential approach to system and/or software development
    - - widely commonly used for developing
        business applications
      - when a project’s requirements are likely to be STABLE AND WELL DEFINED
      - useful in web applications in which prototypes of screens are necessary to aid in the completion of requirements and design.
    - - facilitates theDETERMINATION OF SYSTEM ARCHITECTURE RELATIVELY EARLY in the development effort.
      - primary advantage of the traditional approach is that it provides a template into which methods for the requirements
        
        (i.e., definition, design, programming, etc.) can be placed
    - - • Unanticipated events that result in iterations, implementations hazards
      - • difficulty of obtaining an explicit set of requirements from the customer/user
      - • Managing requirements and convincing the user about the undue or unwarranted (completely not justifiable ) requirements in the system functionality,
      - • The necessity of customer/user patience,
        
        under this approach a working version of the system’s programs will not be available until late in the project’s life cycle
      - • A changing business environment that alters or changes the customer/user requirements before they are delivered
  - - - testing occurs to validate the detailed design.
      - RELATES TO ARCHITECTURAL SPECIFICATION OF THE SYSTEM while final UAT references the requirements
    - - • An IS auditor’s influence is significantly increased when there are formal procedures and guidelines
        
        identifying each phase in the business application life cycle and the extent of IS auditor involvement.
      - • An IS auditor can review all relevant areas and phases of the systems development project and
        
        report independently to management on the adherence to planned objectives and organizational procedures.
      - • An IS auditor can identify selected parts of the system and
        
        become involved in the technical aspects on the basis of his/her skills and abilities.
      - • An IS auditor can provide an evaluation of the METHODS AND TECHNIQUES applied through the development phases of the business application lifecycle.
  - - - During each iteration, the development process goes through each phase, from requirements through testing, and each subsequent cycle incrementally improves the process.