Please enable JavaScript.

Coggle requires JavaScript to display documents.

General Computer Controls; Recommendations, Recommendations - Coggle…

- - - - Automatic system request
      - Re-use of password prohibited
    - - Limit access to part of system
      - Limit access to part of system
      - Limit access to part of system
    - - Alpha /numerical
      - Alpha /numerical
      - And other - ! @ # *
      - Minimum 6 characters (Minimum length)
  - - - Located in visible area
      - Located in visible area
      - Physically locked
- - - - 4 Involvement from different departments is essential:
        
        2.) Data processing department:
        
        Compatibility with other systems should be considered.
        
        Operational aspects need to be addressed.
        
        Technical soundness should be ensured.
        
        3.) Quality control department:
        
        Standard of design should be maintained.
        
        Testing should be conducted.
        
        Documentation should be prepared.
        
        1.) User department:
        
        Departmental requirements should be considered.
        
        Internal and external auditors should be involved.
      - 5 Perform a feasibility study, which includes:
        
        Deciding between buying or self-developing the project.
        
        Conducting a cost/benefit analysis.
      - 3 The steering committee has the responsibility to ensure:
        
        2.) Adherence to timetables.
        
        3.) Achievement of budgets.
        
        1.) Project authorization.
        
        4.) Meeting quality requirements.
      - 6 Create a project team responsible for:
        
        Developing the project in stages.
        
        Preparing timetables for each stage.
        
        Day-to-day management of the project.
      - 2 A steering committee should be formed, consisting of senior management from both user and computer departments.
      - 7 Project authorization should occur after the feasibility study/analysis is completed and before commencing the project.
      - 1 Development plan needs to be authorized before starting a project.
    - - 2.) System Testing
        
        Ensure that individual programs work together as a cohesive system.
      - 3.) Live Testing (Deployment)
        
        Types:
        
        Parallel Running:
        
        Challenges
        
        Cost of double processing and difficulty in comparison due to additional information.
        
        Implement the new system alongside the old system.
        
        Pilot Running:
        
        Definition
        
        Introduce the system in small portions or specific group.
        
        Test the system under operational conditions.
      - 1.) Program Testing
        
        Check if the program's logic is correct and if it meets the required specifications.
    - - Two methods of specifying systems
        
        2.) Prototype systems
        
        User department try out
        
        Refine the design through a series of prototypes
        
        Design prototype
        
        1.) Traditional method
        
        Written systems specification by means of discussions between the data processing department and users
    - - System design and programming standards needed to
        
        Ensure there is supervision over system design
        
        Comply with predetermined standards
        
        Ensure that appropriate control-related programmed procedures are built in
        
        Done on program library not live data
        
        Ensure system interacts properly with existing systems and system software
  - - - Keep in mind
        
        :star:Minimum changes should be made to package
        
        If modifications is necessary, use normal rules i.r.o system development
        
        Possibility of future amendments (e.g. tax updates)
        
        :star:Quality of maintenance service from supplier
      - Package must meet user requirements
        
        Prepare statement of requirements
        
        Measure available packages against requirements
    - - 1.) Specification and selection of package
        
        :star:When selecting a Program; Have discussions with other users
        
        Observing operation of package
        
        :star:Questioning other users of package re:
        
        :star:Facilities offered by program
        
        :star:Freedom from program errors
        
        :star:Speed & efficiency
        
        :star:Ease of use
        
        :star:Quality of support
      - 2.) Implementation and testing of package
        
        Implementation
        
        Involvement of:
        
        Data processing
        
        Management
        
        User departments
        
        Quality assurance
        
        Testing
        
        Independent testing
        
        Review of experiences of other users
  - - - System Description
      - Operating Manuals
      - System flowcharts
    - - Supervision by seniour management
      - Auditor Involvement
    - - Define methods used (e.g. parallel/pilot)
      - Training of Stuff
      - Prepare timetables for conversion:
      - Prepare premises (constant power/ air-con)
    - - Approval by users
      - Follow up of exception reports
      - Manuel comparison of data
- - - - extinguishers should be in a working condition and available for use
      - The extinguisher should be tested to ensure it is operating effectively
    - - away from water pipes, and any water used