Life Cycle can be defined in many ways and forms, and as for this topic, we would only tackle the three views life cycle.
Systems Development Life Cycle
The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in systems engineering and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. The concept generally refers to computer or information systems.
In software engineering the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information system: the software development process.
A Systems Development Life Cycle (SDLC) is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.
Computer systems have become more complex and often (especially with the advent of Service-Oriented Architecture) link multiple traditional systems potentially supplied by different software vendors. To manage this level of complexity, a number of systems development life cycle (SDLC) models have been created: "waterfall"; "fountain"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and "synchronize and stabilize".[citation needed]
SDLC models can be described along a spectrum of agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on light-weight processes which allow for rapid changes along the development cycle. Iterative methodologies, such as Rational Unified Process and Dynamic Systems Development Method, focus on limited project scopes and expanding or improving products by multiple iterations. Sequential or big-design-upfront (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks to successful and predictable results.[citation needed]
Some agile and iterative proponents confuse the term SDLC with sequential or "more traditional" processes; however, SDLC is an umbrella term for all methodologies for the design, implementation, and release of software.
In project management a project can be defined both with a project life cycle (PLC) and an SDLC, during which slightly different activities occur. According to Taylor (2004) "the project life cycle encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements".
Systems development phases
Systems Development Life Cycle (SDLC) adheres to important phases that are essential for developers, such as planning, analysis, design, and implementation, and are explained in the section below. There are several Systems Development Life Cycle Models in existence. The oldest model, that was originally regarded as "the Systems Development Life Cycle" is the waterfall model: a sequence of stages in which the output of each stage becomes the input for the next. These stages generally follow the same basic steps but many different waterfall methodologies give the steps different names and the number of steps seem to vary between 4 and 7. There is no definitively correct Systems Development Life Cycle model, but the steps can be characterized and divided in several steps.
Initiation/planning
To generate a high-level view of the intended project and determine the goals of the project. The feasibility study is sometimes used to present the project to upper management in an attempt to gain funding. Projects are typically evaluated in three areas of feasibility: economical, operational or organizational, and technical. Furthermore, it is also used as a reference to keep the project on track and to evaluate the progress of the MIS team.[8] The MIS is also a complement of those phases. This phase is also called the analysis phase.
[edit] Requirements gathering and analysis
The goal of systems analysis is to determine where the problem is in an attempt to fix the system. This step involves breaking down the system in different pieces and drawing diagrams to analyze the situation, analyzing project goals, breaking need to be created and attempting to engage users so that definite requirements can be defined. Requirement Gathering sometimes require individual/team from client as well as service provider side to get a detailed and accurate requirements.
(http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle)
Enterprise life cycle
Enterprise Life Cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance and disposition of existing elements of the enterprise.
The enterprise life cycle is a concept in Enterprise Architecture (EA). The Enterprise Architecture process is closely related to other processes, such enterprise engineering and program management cycle, more commonly known as the Systems Development Life Cycle. This concept aids in the implementation of an Enterprise Architecture, and the Capital Planning and Investment Control (CPIC) process that selects, controls, and evaluates investments. Overlying these processes are human capital management and information security management. When these processes work together effectively, the enterprise can effectively manage information technology as a strategic resource and business process enabler. When these processes are properly synchronized, systems migrate efficiently from legacy technology environments through evolutionary and incremental developments, and the Agency is able to demonstrate its return on investment. The figure on top illustrates the interaction of the dynamic and interactive cycles as they would occur over time.
Enterprise Architecture Process
As a prerequisite to the development of every enterprise architecture, each Agency should establish the need to develop an EA and formulate a strategy that includes the definition of a vision, objectives, and principles. Executive buy-in and support should be established and an architectural team created within the organization. The team defines an approach and process tailored to Agency needs. The architecture team implements the process to build both the baseline and target EAs. The architecture team also generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis. The architecture is employed in the CPIC and the enterprise engineering and program management processes via prioritized, incremental projects and the insertion of emerging new technologies. Lastly, the architectures are maintained through a continuous modification to reflect the Agency's current baseline and target business practices, organizational goals, visions, technology, and infrastructure.
Architecture Life Cycle
The architecture is re-analyzed, and the process continues until the operational deficiencies are minimized. The final sets of viable candidates are assessed for operational viability. Based on the results of the assessments, design changes are made and submitted for inclusion into the budgeting process. This process of developing, analyzing, and modifying continues throughout the architecture’s life cycle.
Enterprise Life Cycle activities
An Enterprise Life Cycle integrates the management, business, and engineering life cycle processes that span the enterprise to align its business and IT activities. Enterprise Life Cycle refers generally to an organization’s approach for managing activities and making decisions during ongoing refreshment of business and technical practices to support its enterprise mission. These activities include investment management, project definition, configuration management, accountability, and guidance for systems development according to a System Development Life Cycle (SDLC). The Enterprise Life Cycle applies to enterprise-wide planning activities and decision making. By contrast, a System Development Life Cycle generally refers to practices for building individual systems. Determining what systems to build is an enterprise-level decision.
The figure on the right depicts notional activities of an Enterprise Life Cycle methodology. Within the context of this document, Enterprise Life Cycle does not refer to a specific methodology or a specific bureau’s approach. Each organization needs to follow a documented Enterprise Life Cycle methodology appropriate to its size, the complexity of its enterprise, and the scope of its needs.
(http://en.wikipedia.org/wiki/Enterprise_Life_Cycle)
Here is an example of school life cycle:
Future School: Product life cycle
The Future School product life cycle guidelines provide advance notification in relation to individual product licenses and their life cycles. These guidelines apply to all Future School products, and provide information about the period of time licenses are available for purchase (mainstream phase) and the associated support Future School distributors provide during the entire life cycle of Future School products. These guidelines are intended to assist customers with their product planning and future information technology decisions.
Future School's policy is that its product licenses can only be purchased for a maximum of three (3) years from the date each product license is first released for sale, and that varying levels of support for a product will only be available for a period of five (5) years from the date that product licence is first released for sale. The different phases of a product are illustrated in the life cycle graph shown above, and are explained below.
Product life cycle phases products and services
Mainstream phase: 3 years
1. Each Future School product license is available for purchase through all standard product distribution channels;
2. Distributor assisted support is available from the distributor from whom the product license is purchased;
3. Website support is available from national distributors, and registered license users are also able to upgrade their version of a product to include any modifications to the version during this phase.
Extended phase: 1 year (4th year after release for sale)
1. Future School product licenses are not available for purchase;
2. Distributor assisted support is available from the distributor from whom the product license is purchased;
3. Website support is available from national distributors and all registered license users, except educational volume licensing agreement customers, are able to upgrade their version of a product to include any modifications to the version during this phase.
Final life cycle phase: 1 year (5th year after release for sale)
1. Future School product licenses are not available for purchase;
2. Distributor assisted support is no longer available, unless specifically agreed to in writing by the distributor from whom the product licence is purchased;
3. Website support is available from national distributors, and provides for registered licence users to request limited electronic assistance. Upgrades or modifications to a version are not available during or after this phase.
(http://www.futureschool.com/prodlifecycle.html)
Systems Development Life Cycle
The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in systems engineering and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. The concept generally refers to computer or information systems.
In software engineering the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information system: the software development process.
A Systems Development Life Cycle (SDLC) is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.
Computer systems have become more complex and often (especially with the advent of Service-Oriented Architecture) link multiple traditional systems potentially supplied by different software vendors. To manage this level of complexity, a number of systems development life cycle (SDLC) models have been created: "waterfall"; "fountain"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and "synchronize and stabilize".[citation needed]
SDLC models can be described along a spectrum of agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on light-weight processes which allow for rapid changes along the development cycle. Iterative methodologies, such as Rational Unified Process and Dynamic Systems Development Method, focus on limited project scopes and expanding or improving products by multiple iterations. Sequential or big-design-upfront (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks to successful and predictable results.[citation needed]
Some agile and iterative proponents confuse the term SDLC with sequential or "more traditional" processes; however, SDLC is an umbrella term for all methodologies for the design, implementation, and release of software.
In project management a project can be defined both with a project life cycle (PLC) and an SDLC, during which slightly different activities occur. According to Taylor (2004) "the project life cycle encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements".
Systems development phases
Systems Development Life Cycle (SDLC) adheres to important phases that are essential for developers, such as planning, analysis, design, and implementation, and are explained in the section below. There are several Systems Development Life Cycle Models in existence. The oldest model, that was originally regarded as "the Systems Development Life Cycle" is the waterfall model: a sequence of stages in which the output of each stage becomes the input for the next. These stages generally follow the same basic steps but many different waterfall methodologies give the steps different names and the number of steps seem to vary between 4 and 7. There is no definitively correct Systems Development Life Cycle model, but the steps can be characterized and divided in several steps.
Initiation/planning
To generate a high-level view of the intended project and determine the goals of the project. The feasibility study is sometimes used to present the project to upper management in an attempt to gain funding. Projects are typically evaluated in three areas of feasibility: economical, operational or organizational, and technical. Furthermore, it is also used as a reference to keep the project on track and to evaluate the progress of the MIS team.[8] The MIS is also a complement of those phases. This phase is also called the analysis phase.
[edit] Requirements gathering and analysis
The goal of systems analysis is to determine where the problem is in an attempt to fix the system. This step involves breaking down the system in different pieces and drawing diagrams to analyze the situation, analyzing project goals, breaking need to be created and attempting to engage users so that definite requirements can be defined. Requirement Gathering sometimes require individual/team from client as well as service provider side to get a detailed and accurate requirements.
(http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle)
Enterprise life cycle
Enterprise Life Cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance and disposition of existing elements of the enterprise.
The enterprise life cycle is a concept in Enterprise Architecture (EA). The Enterprise Architecture process is closely related to other processes, such enterprise engineering and program management cycle, more commonly known as the Systems Development Life Cycle. This concept aids in the implementation of an Enterprise Architecture, and the Capital Planning and Investment Control (CPIC) process that selects, controls, and evaluates investments. Overlying these processes are human capital management and information security management. When these processes work together effectively, the enterprise can effectively manage information technology as a strategic resource and business process enabler. When these processes are properly synchronized, systems migrate efficiently from legacy technology environments through evolutionary and incremental developments, and the Agency is able to demonstrate its return on investment. The figure on top illustrates the interaction of the dynamic and interactive cycles as they would occur over time.
Enterprise Architecture Process
As a prerequisite to the development of every enterprise architecture, each Agency should establish the need to develop an EA and formulate a strategy that includes the definition of a vision, objectives, and principles. Executive buy-in and support should be established and an architectural team created within the organization. The team defines an approach and process tailored to Agency needs. The architecture team implements the process to build both the baseline and target EAs. The architecture team also generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis. The architecture is employed in the CPIC and the enterprise engineering and program management processes via prioritized, incremental projects and the insertion of emerging new technologies. Lastly, the architectures are maintained through a continuous modification to reflect the Agency's current baseline and target business practices, organizational goals, visions, technology, and infrastructure.
Architecture Life Cycle
The architecture is re-analyzed, and the process continues until the operational deficiencies are minimized. The final sets of viable candidates are assessed for operational viability. Based on the results of the assessments, design changes are made and submitted for inclusion into the budgeting process. This process of developing, analyzing, and modifying continues throughout the architecture’s life cycle.
Enterprise Life Cycle activities
An Enterprise Life Cycle integrates the management, business, and engineering life cycle processes that span the enterprise to align its business and IT activities. Enterprise Life Cycle refers generally to an organization’s approach for managing activities and making decisions during ongoing refreshment of business and technical practices to support its enterprise mission. These activities include investment management, project definition, configuration management, accountability, and guidance for systems development according to a System Development Life Cycle (SDLC). The Enterprise Life Cycle applies to enterprise-wide planning activities and decision making. By contrast, a System Development Life Cycle generally refers to practices for building individual systems. Determining what systems to build is an enterprise-level decision.
The figure on the right depicts notional activities of an Enterprise Life Cycle methodology. Within the context of this document, Enterprise Life Cycle does not refer to a specific methodology or a specific bureau’s approach. Each organization needs to follow a documented Enterprise Life Cycle methodology appropriate to its size, the complexity of its enterprise, and the scope of its needs.
(http://en.wikipedia.org/wiki/Enterprise_Life_Cycle)
Here is an example of school life cycle:
Future School: Product life cycle
The Future School product life cycle guidelines provide advance notification in relation to individual product licenses and their life cycles. These guidelines apply to all Future School products, and provide information about the period of time licenses are available for purchase (mainstream phase) and the associated support Future School distributors provide during the entire life cycle of Future School products. These guidelines are intended to assist customers with their product planning and future information technology decisions.
Future School's policy is that its product licenses can only be purchased for a maximum of three (3) years from the date each product license is first released for sale, and that varying levels of support for a product will only be available for a period of five (5) years from the date that product licence is first released for sale. The different phases of a product are illustrated in the life cycle graph shown above, and are explained below.
Product life cycle phases products and services
Mainstream phase: 3 years
1. Each Future School product license is available for purchase through all standard product distribution channels;
2. Distributor assisted support is available from the distributor from whom the product license is purchased;
3. Website support is available from national distributors, and registered license users are also able to upgrade their version of a product to include any modifications to the version during this phase.
Extended phase: 1 year (4th year after release for sale)
1. Future School product licenses are not available for purchase;
2. Distributor assisted support is available from the distributor from whom the product license is purchased;
3. Website support is available from national distributors and all registered license users, except educational volume licensing agreement customers, are able to upgrade their version of a product to include any modifications to the version during this phase.
Final life cycle phase: 1 year (5th year after release for sale)
1. Future School product licenses are not available for purchase;
2. Distributor assisted support is no longer available, unless specifically agreed to in writing by the distributor from whom the product licence is purchased;
3. Website support is available from national distributors, and provides for registered licence users to request limited electronic assistance. Upgrades or modifications to a version are not available during or after this phase.
(http://www.futureschool.com/prodlifecycle.html)
