Â
There's a process to everything.
From the very first set of classes where Dr. Mohan said that "IT cannot exist by itself...", it shows us that in building software (since we are doing IT) cannot merely proceed without any sort of consultation with those in authority. The decision makers, etc.
The SDLC-System (or Software) Development Life Cycle has 4 stages. It is not only used in IT (as I once thought), but also in any sort of project management activity. There is a mnemonic for the stages of the SDLC called
FADPIM. This stands for
Feasibility Study,
Analysis,
Design,
Programming and Testing,
Implentation and
Maintainance. If these steps are followed, ur almost sure to come out of all of your projects happy. So, let's break down the phases.
Feasibility Study:- This is the process where the 'sponsor' of the project usually says that there's a problem that needs to be addressed. As a consultant,you go in and you see if the problem can be solved in the way that the 'sponsor' may be suggesting. During this phase, cost of replacement/upgrade should be taken into account to give the best advice possible to come to a solution. Keep in mind however, at this stage certain documents should be at hand. eg. contracts.
Analysis:- Since IT can't exist by itself, an analysis of the organization should be done to see exactly where an HOW to use the IT Infrastructure. The current business procedure should be looked at in order to see where there may be inefficiencies in the system. The customer's needs and solutions should be documented and signed to at the end of this stage. The purpose is two-fold. 1. to ensure that you have your guidelines as to what you should do, 2. so that you would know scope of work and you do not go outside of your scope of work unless agreed upon.
Design:- after all the documents have been drawn up and you begin ur design,it is then that you make preparations to treat with the problem at hand. Design can be done in different phases, hardware,software and the planning for training to use new system.
Programming and
Testing:- Now that you're designs are all drawn up and you've gotten the appoval to start the actual code of the program and the testing in the environment.Testing really cannot truly be done during the implementation stage. It is better done in the Programming stage.
Implementation:- this stage is where the new solution is carried out.There are different types of implementation: Direct, Simultaneous and Phase implementation. Direct implementation is where the OLD system is scrapped (please understand the word "system" doesn't strictly mean computers) and the NEW one is used immmediately. Simultaneous implementation is where the old and new systems are used at the same time.The purpose of this is so that the new system can be taken through the business process and data is slowly but surely transferred to the system. This method can also be used to knock out the kinks in the system and to make further customizations for the organization. The phase implementation is were the new system is broken up and is implemented in different stages so that it can minimize the stress on the organization and make the implementation smoother.
and finally....
Maintainance:- prob the best part cuz u get paid each time..lol. BUT other than that, it is the part of the cycle where you go back into the organization and upkeep their systems with any relevant updates and procedures as well as make any additional changes to the system that need to be done!
From experience, this has been my basic understanding of the system. Hope it's clear!
insert a brief autobiography here
i like blah blah blah
i hate blah blah blah
i want blah blah blah