Systems Development Process

Overview of systems operations and maintenance as part of the systems development process.

Operations and Maintenance

Post-Implementation Review: Essential for evaluating the effectiveness of a system post-launch. Questions to consider include:
- Does the system meet the organization’s goals?
- Importance of alignment with the strategic objectives of the organization.
- Are users satisfied?
- Assessment of user experience and acceptance of the system.
- Were expected benefits achieved?
- Comparison of anticipated vs. actual benefits derived from the system.
- Were actual costs in line with expected costs?
- Financial scrutiny regarding the budget and expenditures relative to forecasts.
- Is the system reliable?
- Evaluation of the system's uptime and performance consistency.
- Does the system produce accurate and complete data and in a timely basis?
- Reliability of data output as a factor of operational effectiveness.
- Is the system compatible with existing systems?
- Assessing integration and interoperability with legacy systems.
- Is the system safeguarded from errors, fraud, and intrusion?
- Review of security measures and risk management strategies.
- Are there adequate error-handling procedures in place?
- Procedures for addressing operational discrepancies or failures.
- Is everyone trained to use the new system?
- Importance of user readiness and training initiatives.
- Is systems documentation complete and accurate?
- Evaluation of support documentation for users and administrators.

Process of Installing Hardware and Software: Critical steps involved in establishing an Accounting Information System (AIS):
- Planning: Development of a comprehensive strategy for implementation.
- Prepare Site: Setting up physical locations for hardware and software.
- Test Hardware: Ensuring all physical components function correctly.
- Train Personnel: Educating users on the new system.
- Complete Documentation: Finalizing all supporting documents.
- Test System: Systematic testing to confirm operability.
- Conversion: Transitioning from the old system to the new one.

Different types of documentation play vital roles in system deployment:
- Development Documentation: Includes a system description, copies of outputs, inputs, layouts, flowcharts, test results, and user acceptance forms.
- Operations Documentation: Comprises operating schedules, accessed files/databases, equipment security, and file-retention mandates.
- User Documentation: Provides guidance for users on operating the AIS, encompassing a procedures manual and training materials.

Walk-through: Step-by-step procedural reviews to identify incorrect logic, errors, or omissions.
Processing Test Data: Utilizing both valid transactions and various error conditions in testing.
Acceptance Tests: Employing real transactions and user input to ascertain system viability and final acceptance.

Different methods of transitioning from old systems to new ones include:
- Direct Conversion: Phasing out the old AIS immediately upon implementation of the new system.
- Parallel Conversion: Running both old and new systems concurrently for a designated period to mitigate risk.
- Phase-In Conversion: Incrementally replacing components of the old AIS with the new one.
- Pilot Conversion: Testing the new system in a localized environment (e.g., a single branch) before full-scale rollout.

Developers create a framework to implement user requirements and address problems from the analysis phase:
- Evaluate Design Alternatives: Assess various design options for effectiveness.
- Prepare Design Specifications: Document detailed design specifications including output requirements and data storage solutions.
- Prepare Conceptual Systems Design Report: Compilation of frameworks and evaluations into a formal report.

Translation of conceptual designs into detailed specifications for coding and testing computer programs:
- Output: Determining the nature, format, content, and timing of various reports and displays.
Design Considerations:
- File and Database Design: Determining storage mediums, processing modes, maintenance needs, and growth estimates.
- Input Design: Evaluating data entry methods, formats, sources, volumes, and error handling procedures.
- Program Design: Steps include assessing user needs, documenting development plans, writing and testing program instructions, and training users.

Development of procedures regarding:
- Input preparation.
- Transaction processing and error handling.
- Controls and reconciliation of balances.
- Database access and output preparation.