Management Information Systems Blog 6

There are seven phases in the systems development life cycle:

1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Implementation
7. Maintenance

 The phase that I feel is the hardest would be the planning stage. They have to come up with what is needed to be developed, how it will be developed, what their project scope is going to be, and what the project's plan and resources are going to be. Sometimes its the initial step that is the hardest.

The phase that I feel is the easiest would be the analysis stage. In this stage you must analysis your business's requirements for the system that will be built.

 The phase that I feel is most important is the testing phase. Because you have to make sure that the system is working properly and is maintaining the same expected outcome that the are wanting performed. If there are any faults or unexpected outcomes, the system then must go backwards into the design phase and must be fixed to yet again be tested to make sure it is performing efficiently and accurately.

The phase that I find least important through the system development life cycle would have to be none. I find that they are all  important and critical in the development of systems for businesses, and that none should be skipped. Without having the planning stage, you do not have a set idea of what the system should be and what tasks and resources the plan will have. If it does not have the analysis stage, then there is no vital information about what the system must have in order of requirement for the business, which therefore will be useless to have a system that does not target your needs and requirements. If you do not have the design stage, you do not achieve the models for the system or the required design to produce the needed architecture in the development stage, that is needed to support your new system. If you do not have the development stage, your system does not get the database it needs to store vital information nor the programs it needs to operate smoothly. If there was no testing stage, then who knows if your system is going to work properly  when needed? Or if there will be unexpected outcomes and issues that must be fixed.  If there was no implementation stage, there would not be individuals who know how to use the system since there is no training provided to its users. And lastly, if there was no maintenance, there would not be any changes to the system nor  support to help the system's users incase it is needed. Everything is constantly changing, so are businesses and their requirements to run efficiently, and with that their systems need to change along with it.