System Development

This is about chapter 1 and it concerns the system development life cycle. I have studied this before but it seems that I need to go through it again. But this time it is a bit different. The phases of the system development life cycle are:

• Business need - how the system can help the business
• Concept study - see how the system can be built and check for similar existing systems
• Feasibility analysis - of the system to be built. whether it is worth building.
• Requirements analysis - what the system will need to have/do
• Specification - what features/functions/properties the system will have, and how useful/powerful it will be
• Overall system design
• Detailed design
• Coding of individual “modules”
• Testing of individual “modules”
• Integration - actually use it in the business
• System level testing - checking for errors and stuff
• Verification - see if everything runs as intended
• System “implementation” - making the system live and usable for the customers
• Operational Use - the stage where the system is in use
• Maintenance - fixing bugs that are found during operational use
• Retirement - the system is discontinued when it gets too old, out-of-date, useless or outperformed by newer and better systems

A lot of stuff for me to remember, eh? This is basically the waterfall model of system development. Very old, tedious, long and time-consuming. I personally don''t like it much. Nowadays, other models are being used. But that would be a story saved for another time to tell.
Share this with your friends:

System Development Comments

From the Josh Tam Universe