ICT Chapter 7

Systems life cycle

The series of stages that a system goes through from creation to maturity and potential replacement.

Analysis

The stage where the current system is examined in detail to identify problems and requirements for a new system.

User documentation

Documentation aimed at the end user providing guidance on how to use the system.

Technical documentation

Documentation intended for developers, detailing system design and specifications.

Implementation methods

Strategies to transition from an old system to a new system, including Direct changeover, Parallel running, Pilot running, and Phased implementation.

Validation checks

Checks performed during data entry to ensure that the entered data is sensible and reasonable.

Direct changeover

A quick implementation method where the old system is completely replaced with a new system at once.

Parallel running

An implementation method where both the old and new systems operate simultaneously for a period of time.

Pilot running

An implementation method where the new system is introduced in a limited area before full-scale deployment.

Phased implementation

An incremental implementation method where the new system is introduced in stages or modules.

Evaluation

The process of reviewing the performance and effectiveness of a system after implementation.

Data entry checks

Assure that the data submitted fits the prescribed format and type for input fields.

Length checks

Validation technique that checks if the data entered meets the required length specifications.

Presence checks

Validation approach that ensures required fields are not left empty.

Consistency checks

Validation step ensuring related data fields are logically aligned.

Range checks

Validation checks that verify if numerical data falls within a specified range.

Format checks

Validation to confirm data adheres to a specific format or pattern.

Check digits

Digits added to data (like bank account numbers) used to verify correctness.

Questionnaires

Data collection method involving structured questions to gather user information.

Interviews

Qualitative method of collecting data via direct dialog to gather in-depth insights.

Observation

A data collection technique where an analyst watches users interact with current systems.

Existing documentation examination

Reviewing current system documents to understand data flows and structures.

Requirements gathering

The process of identifying and documenting the needs of the users for the new system.

Hardware requirements

Specifications of physical machines needed for the new system to function.

Software requirements

Specifications detailing the software applications needed for the new system's operation.

What is the primary purpose of user documentation?

To provide guidance to end users on how to effectively use a system.

What does technical documentation typically include?

Details about system design, architecture, and specifications for developers.

What is the significance of validation checks?

They ensure that the data entered into the system is sensible and reasonable.

How does parallel running differ from direct changeover?

Parallel running involves operating both old and new systems simultaneously, while direct changeover replaces the old system with the new one at once.

What is the role of requirements gathering in system development?

To identify and document the specific needs of users for the new system.

Why is evaluation important after system implementation?

It assesses the performance and effectiveness of the new system to ensure it meets user needs.

What are presence checks designed to ensure in data entry?

That required fields are not left empty.

What does phased implementation entail?

Introducing a new system in stages or modules rather than all at once.

What is the purpose of a questionnaire in data collection?

To gather information from users through structured questions.

What are hardware requirements?

Specifications of the physical machines needed for a new system to operate.