Systems Development Lifecycle

• What are the six parts of the Systems Development Life Cycle?

  System Investigation, Analysis, Design, Implementation, Maintenance, Evaluation
• What is the purpose of a Data Flow Diagram in systems development?

  • Visualizes processes in the system
  • Shows how data moves through the system
  • Helps in analyzing existing or proposed processes
• What are the methods used in System Investigation for fact-finding?

  Interviews, questionnaires, observation, document sampling
• What does a feasibility report consider in System Investigation?

  Scope, hardware/software, problems, user requirements, costs/benefits
• What are the technical requirements for the implementation of a new system?

  • Hardware: CPU, storage, peripherals
  • Software: System and application software
  • Network: Server specifications, network speed
  • Staff issues: Skills assessment, training, hiring
  • Security: Identify weaknesses, establish procedures, install software
• What are the three phases of System Implementation?

  Installing hardware/software, staff training, conversion methods
• What tools does a systems analyst use in System Analysis?

  Data Flow Diagrams, decision tables, data dictionaries
• What are the elements of Data Flow Diagrams?

  • Start/Stop Procedure
  • Decision box
  • Input/Output
  • Operation
  • Connector
  • Store/subroutine demand
  • Control flow
• What information do users need after training in System Maintenance?

  User guides, technical manuals, error-checking instructions
• What types of changes can be made during Technical Maintenance?

  • Corrective: Fix serious errors
  • Adaptive: Respond to changes (e.g. new formats)
  • Perfective: Improve system performance
• What is the purpose of System Investigation at the end of the cycle?

  To determine if the new system meets requirements
• How does the Systems Development Life Cycle ensure a systematic approach to system development?

  By breaking down the process into defined phases
• If a company needs to improve its system performance, which type of change should it implement?

  Perfective change
• System investigation

  The system analyst will conduct a thorough investigation of the current system, using methods such as interviews, questionnaires, direct observation, and document sampling. They will identify issues and requirements, as well as any constraints on the new system, such as timetable, cost, hardware, software, and staff capability. The report will also include a list of problems with the existing system, user requirements for the new system, and the cost and benefits of introducing the new system, including available features, required hardware or software, and likely costs.
• System analysis

  System analysis involves using tools like data flow diagrams, decision tables, and data dictionaries to analyze existing systems and implement new ones. Data flow diagrams represent processes, including start/stop procedures, decision boxes, input/output, operation, connectors, store/subroutine demand, and control flow. Decision tables simplify decision rules in a user-friendly format. Data dictionaries describe data in databases, saving users from understanding complex databases or examining each area in detail.
• System design

  The new system's technical requirements include CPU requirements, primary/secondary storage, and peripherals. Software includes system and application software. Networking includes server, CPU, speed, and related storage. Staff issues include identifying technical skills, offering training, and recruiting new staff. Security issues involve identifying and implementing security procedures, such as backups and recovery processes, and installing security software.
• System implemation

  The system must be implemented, which involves three steps: installing hardware and software, training staff, and using different transition methods such as parallel, direct, pilot, or phased.
• Systems maintenence

  To ensure users can use the new system after training, they need user manuals and technical manuals. User manuals provide step-by-step instructions for general users, while technical manuals assist technical users with the system's backend. Error checking is also necessary, with software developers making modifications beyond technical staff's capacity. These changes can be rectifying, adaptive, or perfecting to improve system performance.
• Systems evaluation


  The new system evaluation assesses if it meets the company's initial requirements and needs, and considers how the software can evolve for further improvement.
• What is essential for users to operate a new system after training?

  Information that can be modified periodically
• What do user manuals provide for general users?

  Step-by-step instructions
• What do technical manuals provide for technical users?

  Technical documentation
• Why is error checking essential in a system?

  To ensure the system operates correctly
• What types of changes can be made to the system?

  Rectified, adaptive, or perfecting changes
• What might be a limitation of the technical staff regarding system modifications?

  The system may need modifications beyond their capacity
• Why is it important for users to have necessary information about the system?

  To operate the system effectively