LIFE CYCLE OF AN INFORMATION SYSTEM: 6 PHASES - TECHNOLOGY - 2024

The life cycle of an information system comprises all the processes that occur from the time the need for a system arises until another emerges to replace it.

According to the ISO-12207 standard, it is the reference framework that contains all the implications of the development, operation and maintenance of a software product.

An information system includes all the people, machines and / or methods that are involved in the collection, processing and transmission of information.

Typically, the roles that are identified in the implementation of an information system are the project manager, the technicians of the technological area, the analysts and the users.

Objectives of an information system

An information system meets three fundamental objectives:

- Define the tasks that must be performed and the order in which they must be done.

- Ensure consistency with the rest of the organization's information systems.

- Provide control points for project management

There are several models of information systems, among which the following stand out:

• Cascade model.
• Prototype-based models.
• Prototype building model.
• Incremental development model.
• Evolutionary prototyping model.
• Alternative models.
• Spiral pattern.
• Models based on transformations.
• Rational Unified Software Development Process (RUP).
• Component Based Software Development (DSBC or CBSB).
• Extreme Programming Model (eXtreme Programming).

Of this list of models, the cascade is the most used because it requires verifying and validating each stage before moving on to the next.

The 6 phases of the life cycle of an information system

Although computer information systems are a type of information system, the stages of their life cycle are relevant to any innovation in information management.

1- Preliminary investigation

It is the first step in the process because it implies knowing the activity of the organization in question.

It is at this time when the needs and problems related to information management are identified.

The reason for the need for the system is discovered, and how it is expected to satisfy that need within the entity. That is, expectations are also valued.

In this phase the review of institutional bibliography and conducting interviews are the typical ways of finding useful information for the work to be done.

Likewise, a review of the existing information systems should be made to detect usage habits, more frequent difficulties and positive experiences with other systems.

2- Information analysis

Once all the information is gathered, it is time to organize it in a way that is useful for the next phase: the design.

Charts, mind maps and flow charts can be the ways to condense the collected data, and make it understandable and useful for the team.

3- Design of the new system

Based on the information that was organized in the previous phase, the new system is designed.

The level of complexity of the new system must progressively increase so that the user has the opportunity to become familiar with the new procedures and / or devices.

Here is the language in which the software code will be written, or how the system that will be purchased on the market will be adapted. At this point the appearance of the system is also defined.

The objective of this design must be clearly and directly related to the solution of the identified needs.

4- Development and documentation of the new system

It is the development phase itself. The programming of the new software starts here.

If you are purchasing a ready-made program, the phase concentrates more on its documentation.

The idea is that the entire system is supported by the relevant documentation so that the necessary modifications can be made if they are required. The user manual should come up at this point.

5- Implementation of the information system

It is the practical phase of the system. Here it is put to the test, and used with a critical eye to be able to detect the main advantages and possible flaws it may have.

The fundamental objective of this phase is to detect errors so that they can be corrected before the system is implemented to the rest of the organization.

The introduction of the new system can be done in several ways:

In parallel

The new system is inserted without eliminating the previous one, at least for a certain time, so that users can progressively adapt.

With a pilot plan

When implemented in a defined space for a defined time.

With instant replacement

When the deficiency of the previous one makes the change urgent.

With a trial period

It's about experiencing how efficient the new system is over a given period of time.

Part by part

When the new system is very large and involves many changes.

6- System maintenance

This is a continuous phase that consists of ensuring the perfect functioning of the system.

This is the support phase in which a technical staff is available to help others in the adoption and operation of the new system.

It is also here when errors that occur with operability and new user demands are solved.

This phase usually takes 40 to 80% of the resources allocated to the development of the system, and lasts until it becomes obsolete. It is also the phase in which updates are made or functionalities are added.

References

1. Blanco, Lázaro (2008). Information system for the economist and accountant. Recovered from: eae-publishing.com
2. Fernández, Francisco and others (s / f). Life cycle of a computer system. Recovered from: ecured.cu
3. Gestiopolis (s / f). Life cycle of an information system. Recovered from: gestiopolis.com
4. Mcconnell, Steve (1997). Development and management of computer projects. Translation by Isabelm del Aguila. Mcgraw-Hill.
5. IT and Telecommunications examinations to be an ICT official (2011). The life cycle of systems. Recovered from: oppositionestic.blogspot.com
6. Wikipedia (s / f). Information system. Recovered from: es.wikipedia.org