The System Life Cycle Evaluation Essay

System Development Life Cycle (SDLC) is a series of six main phases to create a hardware system only, a software system only or a combination of both to meet or exceed customer’s expectations.

System is a broad and a general term, and as per to Wikipedia; “A system is a set of interacting or interdependent components forming an integrated whole” it’s a term that can be used in different industries, therefore Software Development Life Cycle is a limited term that explains the phases of creating a software component that integrates with other software components to create the whole system.

Some more specific takes on SDLC include:

Below we’ll take a general look on System Development Life Cycle phases, bearing in mind that each system is different from the other in terms of complexity, required components and expected solutions and functionalities:

System Development Life Cycle Phases:


1- System Planning 

The Planning phase is the most crucial step in creating a successful system, during this phase you decide exactly what you want to do and the problems you’re trying to solve, by:

  • Defining the problems, the objectives and the resources such as personnel and costs.
  • Studying the ability of proposing alternative solutions after meeting with clients, suppliers, consultants and employees.
  • Studying how to make your product better than your competitors’.

After analyzing this data you will have three choices: develop a new system, improve the current system or leave the system as it is.

2- System Analysis

The end-user’s requirements should be determined and documented, what their expectations are for the system, and how it will perform. A feasibility study will be made for the project as well, involving determining whether it’s organizationally, economically, socially, technologically feasible. it’s very important to maintain strong communication level with the clients to make sure you have a clear vision of the finished product and its function.

3- System Design

The design phase comes after a good understanding of customer’s requirements, this phase defines the elements of a system, the components, the security level, modules, architecture and the different interfaces and type of data that goes through the system.

A general system design can be done with a pen and a piece of paper to determine how the system will look like and how it will function, and then a detailed and expanded system design is produced, and it will meet all functional and technical requirements, logically and physically.

4- Implementation and Deployment

This phase comes after a complete understanding of system requirements and specifications, it’s the actual construction process after having a complete and illustrated design for the requested system.

In the Software Development Life Cycle, the actual code is written here, and if the system contains hardware, then the implementation phase will contain configuration and fine-tuning for the hardware to meet certain requirements and functions.

In this phase, the system is ready to be deployed and installed in customer’s premises, ready to become running, live and productive, training may be required for end users to make sure they know how to use the system and to get familiar with it, the implementation phase may take a long time and that depends on the complexity of the system and the solution it presents.

5- System Testing and Integration

Bringing different components and subsystems together to create the whole integrated system, and then Introducing the system to different inputs to obtain and analyze its outputs and behavior and the way it functions. Testing is becoming more and more important to ensure customer’s satisfaction, and it requires no knowledge in coding, hardware configuration or design.

Testing can be performed by real users, or by a team of specialized personnel, it can also be systematic and automated to ensure that the actual outcomes are compared and equal to the predicted and desired outcomes.

6-  System Maintenance

In this phase, periodic maintenance for the system will be carried out to make sure that the system won’t become obsolete, this will include replacing the old hardware and continuously evaluating system’s performance, it also includes providing latest updates for certain components to make sure it meets the right standards and the latest technologies to face current security threats.

These are the main six phases of the System Development Life Cycle, and it’s an iterative process for each project. It’s important to mention that excellent communication level should be maintained with the customer, and Prototypes are very important and helpful when it comes to meeting the requirements. By building the system in short iterations; we can guarantee meeting the customer’s requirements before we build the whole system.

Many models of system development life cycle came up from the idea of saving effort, money and time, in addition to minimizing the risk of not meeting the customer’s requirement at the end of project, some of theses models are SDLC Iterative Model, and SDLC Agile Model.

The best of the bug capturing tools

Continues improvement and fixing of the system is essential, Airbrake provides robust bug capturing in your application. In doing so, it notifies you with bugs instantly, allows you to easily review them, tie the bug to an individual piece of code, and trace the cause back to recent changes.

Airbrake enables for to categorize, search, and prioritize errors so that when bugs occur, your team can quickly determine the root cause. The time and effort you save by capturing your errors with Airbrake is invaluable!


 Capture and Track Your Application’s Exceptions in 3 Minutes





The program evaluation process goes through four phases — planning, implementation, completion, and dissemination and reporting — that complement the phases of program development and implementation. Each phase has unique issues, methods, and procedures. In this section, each of the four phases is discussed.


The relevant questions during evaluation planning and implementation involve determining the feasibility of the evaluation, identifying stakeholders, and specifying short- and long-term goals. For example, does the program have the clarity of objectives or transparency in its methods required for evaluation? What criteria were used to determine the need for the program? Questions asked during evaluation planning also should consider the program’s conceptual framework or underpinnings. For example, does a proposed community-engaged research program draw on “best practices” of other programs, including the characteristics of successful researcher-community partnerships? Is the program gathering information to ensure that it works in the current community context?

Defining and identifying stakeholders is a significant component of the planning stage. Stakeholders are people or organizations that have an interest in or could be affected by the program evaluation. They can be people who are involved in program operations, people who are served or affected by the program, or the primary users of the evaluation. The inclusion of stakeholders in an evaluation not only helps build support for the evaluation but also increases its credibility, provides a participatory approach, and supplies the multiple perspectives of participants and partners (Rossi et al., 2004).

Stakeholders might include community residents, businesses, community-based organizations, schools, policy makers, legislators, politicians, educators, researchers, media, and the public. For example, in the evaluation of a program to increase access to healthy food choices in and near schools, stakeholders could include store merchants, school boards, zoning commissions, parents, and students. Stakeholders constitute an important resource for identifying the questions a program evaluation should consider, selecting the methodology to be used, identifying data sources, interpreting findings, and implementing recommendations (CDC, 1999).

Once stakeholders are identified, a strategy must be created to engage them in all stages of the evaluation. Ideally, this engagement takes place from the beginning of the project or program or, at least, the beginning of the evaluation. The stakeholders should know that they are an important part of the evaluation and will be consulted on an ongoing basis throughout its development and implementation. The relationship between the stakeholders and the evaluators should involve two-way communication, and stakeholders should be comfortable initiating ideas and suggestions. One strategy to engage stakeholders in community programs and evaluations is to establish a community advisory board to oversee programs and evaluation activities in the community. This structure can be established as a resource to draw upon for multiple projects and activities that involve community engagement.

An important consideration when engaging stakeholders in an evaluation, beginning with its planning, is the need to understand and embrace cultural diversity. Recognizing diversity can improve the evaluation and ensure that important constructs and concepts are measured.

 Top of Page

Implementation — Formative and Process Evaluation

Evaluation during a program’s implementation may examine whether the program is successfully recruiting and retaining its intended participants, using training materials that meet standards for accuracy and clarity, maintaining its projected timelines, coordinating efficiently with other ongoing programs and activities, and meeting applicable legal standards. Evaluation during program implementation could be used to inform mid-course corrections to program implementation (formative evaluation) or to shed light on implementation processes (process evaluation).

For community-engaged initiatives, formative and process evaluation can include evaluation of the process by which partnerships are created and maintained and ultimately succeed in functioning.

 Top of Page

Completion — Summative, Outcome, and Impact Evaluation

Following completion of the program, evaluation may examine its immediate outcomes or long-term impact or summarize its overall performance, including, for example, its efficiency and sustainability. A program’s outcome can be defined as “the state of the target population or the social conditions that a program is expected to have changed,” (Rossi et al., 2004, p. 204). For example, control of blood glucose was an appropriate program outcome when the efficacy of empowerment-based education of diabetes patients was evaluated (Anderson et al., 2009). In contrast, the number of people who received the empowerment education or any program service would not be considered a program outcome unless participation in and of itself represented a change in behavior or attitude (e.g., participating in a program to treat substance abuse). Similarly, the number of elderly housebound people receiving meals would not be considered a program outcome, but the nutritional benefits of the meals actually consumed for the health of the elderly, as well as improvements in their perceived quality of life, would be appropriate program outcomes (Rossi et al., 2004). Program evaluation also can determine the extent to which a change in an outcome can be attributed to the program. If a partnership is being evaluated, the contributions of that partnership to program outcomes may also be part of the evaluation. The CBPR model presented in Chapter 1 is an example of a model that could be used in evaluating both the process and outcomes of partnership.

Once the positive outcome of a program is confirmed, subsequent program evaluation may examine the long-term impact the program hopes to have. For example, the outcome of a program designed to increase the skills and retention of health care workers in a medically underserved area would not be represented by the number of providers who participated in the training program, but it could be represented by the proportion of health care workers who stay for one year. Reduction in maternal mortality might constitute the long-term impact that such a program would hope to effect (Mullan, 2009).

 Top of Page

Dissemination and Reporting

To ensure that the dissemination and reporting of results to all appropriate audiences is accomplished in a comprehensive and systematic manner, one needs to develop a dissemination plan during the planning stage of the evaluation. This plan should include guidelines on who will present results, which audiences will receive the results, and who will be included as a coauthor on manuscripts and presentations.

Dissemination of the results of the evaluation requires adequate resources, such as people, time, and money. Finding time to write papers and make presentations may be difficult for community members who have other commitments (Parker et al., 2005). In addition, academics may not be rewarded for nonscientific presentations and may thus be hesitant to spend time on such activities. Additional resources may be needed for the translation of materials to ensure that they are culturally appropriate.

Although the content and format of reporting may vary depending on the audience, the emphasis should be on full disclosure and a balanced assessment so that results can be used to strengthen the program. Dissemination of results may also be used for building capacity among stakeholders.

 Top of Page

0 thoughts on “The System Life Cycle Evaluation Essay

Leave a Reply

Your email address will not be published. Required fields are marked *