Consider your school, how do you know that the life cycle was developed specifically for the university. How do we know that it meets our needs?
I am currently studying at the University of Southeastern Philippines. I would have to admit that I had a hard time figuring out what are the stages or life cycle that our university underwent or developed. However, I have read their Strategic Plan which had quite a contribution for me to have an overview on our University's life cycle. But before I lay down my understanding on the University's developed life cycle I will first define what a life cycle is.
Initial Idea
All projects must start with an initial idea. Usually this consists of a brief definition on what is the project all about, what is its purpose and what the project aims to accomplish. How will the success of the project be measured?
Feasibility Study
Expanding on the Initial Idea, the Feasibility Study involves drawing up the terms of reference, which state the objectives and scope of the project, how long it should take and how the results should be presented. The terms of reference are usually drawn up by senior management. The feasibility study must determine if development of the project is justified in terms of economic and organisational terms. The main role of the analyst in the feasibility study is to analyse the current system at a high level. Data Flow Diagrams (DFD) are used to describe how the current system performs and to illustrate known problems. Feasibility studies are not carried out for all projects, and smaller projects omit this stage.
Requirements Analysis
The Requirements Analysis stage defines a series of possible solutions to the problem and presents them to management in terms of business options. These options may be supported by technical documents such as high-level DFD’s, Logical Data Models (LDM) and Work Practise Models. The requirements analysis report must also contain financial and risk assessments to be presented and supported by outline implementation descriptions. The steps involved within the requirements analysis will define the flow of data in the system, deriving system functions and to develop user role specifications, prototypes and process specifications.
Systems Analysis and Specification
The Systems Analysis stage is an extension to the feasibility study. If the project has a feasibility study then the bulk of the work has already been done. A terms of reference will also be required if one does not exist. The output from this stage is the System Specification which gives precise details of what the new system is required to do, but does not go into how it does it. It provides a logical model of the new system. Once agreed, the specification is the basis for the work done by the system designers.
Systems Design
This stage deals with how the requirements of the new system are carried out (how the logical model is implemented as a physical system). The system designer will develop a number of design options and test them against the requirements specification and design criteria. The one that comes closest to the design brief with the most cost effective use of equipment and personnel is selected and broken down into more detailed specs. Because of this the design stage has two phases: produce outline designs based on requirements specification with input from users and the detailed designs produced from the selected design.
Development
This is the only stage in the development where program code is written. The designs and specifications provide enough detail for the programmer to code and test individual modules. Each unit is tested to ensure that it meets the requirements of the specification.
Testing
Within the life cycle there are various levels of testing as well as the unit testing performed in the development stage.
Link testing ensures that programs work together, e.g. the data passed from one program to another has the correct format.
System testing ensures that the system as a whole performs according to the design specification. Recovery procedures must be tested as well as normal operation procedures.
Finally user acceptance testing is carried out by the users in stages to ensure that the system is usable.
Any modifications are passed back to the design stage where changes are made as necessary and passed to the development team.
Implementation
When the testing has been carried out to the users satisfaction the system, or parts of it, are put live. The “put live” phase can also be known as implementation, cutover or production. This is when the users start using the system to carry out their business activities.
There are two main approaches to implementation a project:
Phased: Stand-alone subsets of the system are implemented over a period of time.
Big Bang: The whole system is put live in one go.
Some systems will require special programs or tasks to convert existing data to a format usable by the new system. The process of changing data from the old system to the new is called conversion.
Maintenance and Review
Once the system is put into place, maintenance is required to ensure satisfactory operation. Maintenance should include regular reviews and evaluations to ensure that it is achieving its objectives, identify any aspects that can be improved or any operational problems. Maintenance falls into two categories, implementation of new features or elimination of errors.
Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.
Various SDLC methodologies have been developed to guide the processes involved, including the waterfall model (which was the original SDLC method); rapid application development (RAD); joint application development (JAD); the fountain model; the spiral model; build and fix; and synchronize-and-stabilize. Frequently, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely the particular plan was followed.
To sum it up, an SDLC methodology follows the following steps:
1. The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel.
2. The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement.
3. The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues.
4. The new system is developed. The new components and programs must be obtained and installed. Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage.
5. The system is put into use. This can be done in various ways. The new system can phased in, according to application or location, and the old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once.
6. Once the new system is up and running for a while, it should be exhaustively evaluated. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures.
The University
As I have observed while reading the Strategic Plan of our university, I could conclude that they are using the Traditional Systems Life Cycle. Indicated on the Strategic Plan Action is conducting different studies on different factors that comprises the University. Analysis was also included in the Strategic Plan. They have involved a so-called Key Performance Indicators on the different concerned factors. Under that Key Performance Indicators are the possible response of the concerned group of people.
The life cycle developed by our university will most probably meet our needs (if only it will be strongly implemented) , for the fact that they had made a deep study and a thorough analysis. If you are wondering why I'm using the term "will" it is because I have noticed on the Strategic Plan that some of the projects are YET to be implemented.
I am currently studying at the University of Southeastern Philippines. I would have to admit that I had a hard time figuring out what are the stages or life cycle that our university underwent or developed. However, I have read their Strategic Plan which had quite a contribution for me to have an overview on our University's life cycle. But before I lay down my understanding on the University's developed life cycle I will first define what a life cycle is.
Initial Idea
All projects must start with an initial idea. Usually this consists of a brief definition on what is the project all about, what is its purpose and what the project aims to accomplish. How will the success of the project be measured?
Feasibility Study
Expanding on the Initial Idea, the Feasibility Study involves drawing up the terms of reference, which state the objectives and scope of the project, how long it should take and how the results should be presented. The terms of reference are usually drawn up by senior management. The feasibility study must determine if development of the project is justified in terms of economic and organisational terms. The main role of the analyst in the feasibility study is to analyse the current system at a high level. Data Flow Diagrams (DFD) are used to describe how the current system performs and to illustrate known problems. Feasibility studies are not carried out for all projects, and smaller projects omit this stage.
Requirements Analysis
The Requirements Analysis stage defines a series of possible solutions to the problem and presents them to management in terms of business options. These options may be supported by technical documents such as high-level DFD’s, Logical Data Models (LDM) and Work Practise Models. The requirements analysis report must also contain financial and risk assessments to be presented and supported by outline implementation descriptions. The steps involved within the requirements analysis will define the flow of data in the system, deriving system functions and to develop user role specifications, prototypes and process specifications.
Systems Analysis and Specification
The Systems Analysis stage is an extension to the feasibility study. If the project has a feasibility study then the bulk of the work has already been done. A terms of reference will also be required if one does not exist. The output from this stage is the System Specification which gives precise details of what the new system is required to do, but does not go into how it does it. It provides a logical model of the new system. Once agreed, the specification is the basis for the work done by the system designers.
Systems Design
This stage deals with how the requirements of the new system are carried out (how the logical model is implemented as a physical system). The system designer will develop a number of design options and test them against the requirements specification and design criteria. The one that comes closest to the design brief with the most cost effective use of equipment and personnel is selected and broken down into more detailed specs. Because of this the design stage has two phases: produce outline designs based on requirements specification with input from users and the detailed designs produced from the selected design.
Development
This is the only stage in the development where program code is written. The designs and specifications provide enough detail for the programmer to code and test individual modules. Each unit is tested to ensure that it meets the requirements of the specification.
Testing
Within the life cycle there are various levels of testing as well as the unit testing performed in the development stage.
Link testing ensures that programs work together, e.g. the data passed from one program to another has the correct format.
System testing ensures that the system as a whole performs according to the design specification. Recovery procedures must be tested as well as normal operation procedures.
Finally user acceptance testing is carried out by the users in stages to ensure that the system is usable.
Any modifications are passed back to the design stage where changes are made as necessary and passed to the development team.
Implementation
When the testing has been carried out to the users satisfaction the system, or parts of it, are put live. The “put live” phase can also be known as implementation, cutover or production. This is when the users start using the system to carry out their business activities.
There are two main approaches to implementation a project:
Phased: Stand-alone subsets of the system are implemented over a period of time.
Big Bang: The whole system is put live in one go.
Some systems will require special programs or tasks to convert existing data to a format usable by the new system. The process of changing data from the old system to the new is called conversion.
Maintenance and Review
Once the system is put into place, maintenance is required to ensure satisfactory operation. Maintenance should include regular reviews and evaluations to ensure that it is achieving its objectives, identify any aspects that can be improved or any operational problems. Maintenance falls into two categories, implementation of new features or elimination of errors.
Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.
Various SDLC methodologies have been developed to guide the processes involved, including the waterfall model (which was the original SDLC method); rapid application development (RAD); joint application development (JAD); the fountain model; the spiral model; build and fix; and synchronize-and-stabilize. Frequently, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely the particular plan was followed.
To sum it up, an SDLC methodology follows the following steps:
1. The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel.
2. The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement.
3. The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues.
4. The new system is developed. The new components and programs must be obtained and installed. Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage.
5. The system is put into use. This can be done in various ways. The new system can phased in, according to application or location, and the old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once.
6. Once the new system is up and running for a while, it should be exhaustively evaluated. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures.
The University
As I have observed while reading the Strategic Plan of our university, I could conclude that they are using the Traditional Systems Life Cycle. Indicated on the Strategic Plan Action is conducting different studies on different factors that comprises the University. Analysis was also included in the Strategic Plan. They have involved a so-called Key Performance Indicators on the different concerned factors. Under that Key Performance Indicators are the possible response of the concerned group of people.
The life cycle developed by our university will most probably meet our needs (if only it will be strongly implemented) , for the fact that they had made a deep study and a thorough analysis. If you are wondering why I'm using the term "will" it is because I have noticed on the Strategic Plan that some of the projects are YET to be implemented.
