Please enable JavaScript.

Coggle requires JavaScript to display documents.

3.3 (6) (IS AUDITOR’S ROLE IN SDLC PROJECT MANAGEMENT (Adequacy of…

- - - - (at a minimum, signed approvals from systems development and user management responsible for the cost of the project and/or use of the system)
  - - - • Objectives defining what is to be accomplished during that phase
      - • Key deliverables by phases with project personnel assigned direct responsibilities for these deliverables
      - • A project schedule with highlighted dates for the completion of key deliverables
      - • An economic forecast for that phase, defining resources and the cost of the resources required to complete the phase
- - - - process of creating a system through controlled trial-and-error procedures to reduce the level of risk in developing the system.
        
        traditional SDLC approach in system but stepwise + interative model
        
        EMPHASIS during the development of the prototype is usually placed on the REPORTS AND SCREENS
      - two basic methods or
        approaches to prototyping:
        
        build model that create design >> based on that model develop system design with all the performance, quality and maintenance features needed
        
        considerable pressure
        to implement an early prototype.
        
        prototype needs to be expanded to , these is often not understood
        
        handle transaction volumes,
        
        clientserver network connectivity
        
        backup and recovery procedures,
        
        provide for security,
        
        auditability and control
        
        Gradually build the actual system that will operate in production using a 4GL that has been determined to be appropriate for the system being built.
        
        works with small applications
        
        for larger efforts ,necessary to develop a design strategy
        for the system even if a 4GL is used
        
        4GL techniques alone will
        cause the same difficulties
        
        low user acceptance
        
        poor maintainability
        
        poor quality
      - Disadvantages
        
        often leads to functions or extras being added to the system that are not included in the initial requirements document.
        
        other factors such as additional req. meet strategic objectives and cost effectiveness is an repetitive excecise
        
        potential risk with prototyped systems is that the finished system will have poor controls. by giving prime focus on user needs
        
        such as backup recovery, security and audit trails, # #
        
        Change control often becomes much more complicated with prototyped systems
        
        CHANGES IN DESIGN AND REQUIREMENTS HAPPEN SO QUICKLY !!!! that they are seldom documented or approved
    - - methodology that enables an organization to develop strategically important systems quickly while reducing development costs and maintaining quality.
        
        achieved by using a series of proven application development techniques within a well-defined methodology.
      - techniques include the use of:
        
        • Small, well-trained development teams :male-technologist: :female-technologist::skin-tone-2:
        
        • Evolutionary prototypes :fish_cake:
        
        • Integrated power tools that support modeling, prototyping and component reusability :hocho: :knife_fork_plate: :fork_and_knife:
        
        • A central repository :tent: #
        
        • Interactive requirements and design workshops :arrows_counterclockwise: :silhouettes: #
        
        • Rigid limits on development time frames :clock1:
      - four major stages:
        
        The concept definition
        
        stageDEFINES THE BUSINESS FUNCTIONS AND DATA SUBJECT AREAS that the system will support and determines the system scope.
        
        The functional design stage
        
        uses workshops to model the system’s data and processes and build a working prototype of critical system components.
        
        The development stage
        
        completes the construction of the physical database and application system, builds the conversion system, and develops user aids and deployment work plans.
        
        The deployment stage
        
        includes final-user testing and training, data conversion and the implementation of the application system.
      - Supports only individual application systems and do not support information needs etc for enterprise as a whole or of a major business area of the enterprise.
        
        provides a means for developing systems faster while reducing cost and increasing quality.
        
        By imposing rigid limits on development time frames and reusing existing components. #