The systems life cycle (1)

Evaluation of the new system.

List of minimum hardware and software, installation instructions, usage features, screenshots, example inputs and outputs, error message explanations, and a troubleshooting guide.

Type of data to be captured, required tables, relationships, fields, and data types.

Details of hardware and software, data structures, expected inputs, validation checks, data processing, diagrams, and flowcharts.

To ensure all components of the system are working correctly before implementation.

In modular form, where each part of the system is developed separately.

Identifying data that is inputted, processed, and outputted into the system.

Interact with the system and input data.

If the new system does not meet the requirements, the old system is still available.

Clear heading and instructions, text boxes for information, tick boxes for choices, and clear fonts and text styles.

Modifications will be made to the system.

The existing and new system work together for a period of time until the new system fully takes over.

Text, Integer, Double, Boolean, OLE Object.

User Documentation and Technical Documentation.

Developing and testing the new system.

An easy to read font, appropriate font size, and sensible font colour/background colour.

Live data (actual data) will be entered into the system and results will be compared to those produced from the current system.

To find out a range of opinions about the current system.

The old system is phased out over a period of time as the new system is introduced.

To ensure the correct data is entered into the fields.

Each module is tested separately before combining them into a full program.

Appropriate spacing for each field.

Input areas for each field.

To check if an item of text is too short or too long (e.g., if a full number has been entered).

The new system is gradually introduced, with parts implemented only if the current phase is working correctly.

It requires the same data to be entered twice (e.g., typing a new password twice).

If the new system fails, only one department is affected.

To store specific data.

Analysis, which involves collecting information about the present system and identifying problems.

Designing a new system to correct the problems identified in the analysis.

The Requirements Specification.

Necessary adjustments could be made to improve overall efficiency and usability of the new system.

Data outside the range limits, such as less than 0% or more than 100%.

Go forward or backwards, add, save, and delete records.

The database.

Data/file structures, validation rules, input methods, and output formats.

The solution with the original task requirements.

Any limitations and necessary improvements to the system.

What is being tested, the test data that will be used, and the expected outcome of the test.

To make choices easier, such as selecting gender.

Data on the boundaries of the range or at the limits of acceptability, such as 0%-5% or 95%-100%.

The limitations of the current system.

Following the steps of analysis, design, development & testing, implementation, and documentation.

It is a method of double-checking the data to see if it is correct.

Interact via a data capture form for easier and quicker data input.

Tasks will be duplicated as data is inputted into both systems, requiring more employees and increasing costs.

Technical and user documentation for the new system.

Drop down lists, tick boxes, and navigation aids.

It involves checking the entered data to see if it is correct (e.g., checking if a name is spelled correctly).

If the system fails in one department, modifications and further training may cause delays.

Creating and verifying the system.

To help the users of the system.

If the new system fails, the old system is not available to fall back to.

The system analyst will refer back to the design stage of the systems life cycle.

The analyst can obtain reliable information about the current system.

To gauge feedback from people who use the system.

The new system is trialed in one department before being implemented across all departments.

It can be a time-consuming and costly process.

The existing system is stopped and replaced by the new system immediately.

The whole system would have been fully tested before implementation, reducing the chance of errors.

Maintainers, usually technical people.

Data may be paper-based.

Each step is checked for errors.

Users' responses to the results of testing the system.

To ensure only correct values can be entered into relevant fields.

Different tables that may be required.

Designing a new system.

Can ask open-ended questions to gather more feedback.

To identify what data is inputted and outputted in the current system.

To determine if the new system has resolved previous issues and met the requirements specified in the design.

To resolve the issues identified in the current system.

Problems with the current system and potential improvements.

To resolve the problems identified by the users and the systems analyst.

It checks whether the data entered fulfills specific criteria to ensure it is valid.

Extreme data, Normal data, and Abnormal data.

To replace the old system with the new system.

It checks if the data entered is in the correct range (e.g., Year 7-12).

Some employees may feel uncomfortable being observed.

It is time-consuming as each implemented part needs to be evaluated satisfactorily.

They may not be completed accurately or returned.

They should be user-friendly and functional (e.g., navigation buttons).

Too much white space and overlapping of items.

The required improvements and expectations for the new system.

Data within a given range, such as 10%-90%.

It checks if the type of data entered is correct (e.g., no letters in a numeric field).

If a part of the new system does not meet requirements, you can revert to the last working point.

They can reach a larger audience quickly and cheaply.

Training sessions are required for employees as each step of the new system is introduced.

To deploy the system for use.

Employees can be trained gradually on how to use the new system.

It checks if the data has been entered (is it present).

To find out how the current system works by observing its use.

Systems Analysts.

It checks if the data has been entered in the correct format (e.g., Date – DD/MM/YYYY).

It can be a time-consuming process.

Analysis.

Analysts can see how the current paper system operates.

To determine whether the new system meets the design requirements.

Design.

Evaluation.

It provides necessary information for users and developers.