what are the 8 stages of system development life cycle (SDLC)? Define each stages please.?

Answer 1

I had this from my CIS course:

System Analysis and Design:
Is the process of examining a business situation with the intent of improving it by better methods and procedures.
System Analysis:
Is the process of fact finding and determining how to make improvements. The system analyst, with user approval, specifies "what" the system should do.
System Design:
Is the process of determining the methods for making improvements.
The system designer specifies "how" to do the "what".
System development life cycle (SDLC):
The sequence of tasks required to conceive, to develop and to implement a new system or modify an existing system.
The Six Steps of SDLC:
•Preliminary Investigation
•System Study
•System Design
•Software Development
•System Implementation
•Post Implementation & Evaluation
1.Preliminary Investigation:
•Define the system's scope.
Sets the boundaries, that is, what the system will and will not do.
•Estimate the time to implement the system.
Important tasks in systems that take over a year to implement usually fail.
Systems requiring more than a year to implement should be done in phases.
•Estimate the cost to implement.
Usually actual cost of system implementation is 10 to 100 times greater than the estimated cost.
•Describe the benefits.
In some cases, the intangible benefits out-weigh the tangible ones.
2.System Study:
•Determine how the current system works by:
Interview
Observations
Survey
Documentation
•Determine solution to improve the new or existing system.
This is called the "What" phase, what is needed to make improvements.
•Look for alternative solutions.
The first solution may not be the best.
3.System Design:
•Known as the "How" phase, the system design determines how to implement the system study solutions. This involves:

Output requirements:
Determine the output media, such as, hard or soft output.
Input requirements:
The output is determined first since it dictates the input requirements.
Determine the input source, such as, databases, data entry by keyboard, mouse or screens (monitors), data screening, voice, data communications, etc.
Storage requirements:
Define the databases.
Records and Fields
System controls and backup:
Determine "The what can go wrong scenarios".
Unauthorized access, determine security measures for software & hardware.
Lost or corrupted databases (bank vaults of information), determine on-site backup.
Disasters, determine off-site database storage, computer processing and communication network back-ups (AT&T, MCI & Sprint).
•Develop system specifications for the programmers.
4.Software Development:
•Build software programs according to design sepcifications.
Make or by decision.
Write the programs in-house or purchase software packages.
Purchase Considerations:
Customization: Programs you write will meet or exceed design specifications. Software packages on-the-other-hand must be customized to meet your specifications.
Extensive customization should be avoided for two reasons.
First, it is costly and time consuming.
Second, implementing software package revisions, requires that customization changes be reapplied which in some cases does not retrofit easily.
Re-Engineering: An alternative to customization in that the company changes it's procedures to comply with the software package specifications.
Note: The SDLC must be completed regardless of the write or buy decision.
5.System Implementation:
•Test the system.
Alpha testing until the system stabilizes.
Beta testing by the system users.
"What if" testing by the system analyst.
•Populate the databases.
•Develop user procedures.
•Train the users.
•Some approaches for turning-on the system:
Direct: Turn-off the old system and start-up the new system.
Parallel: Run the old & new system side by side until the new system has proven to be reliable. Should be avoided when there is not enough users to keep both systems running.
Phased: Parts of the new system are phased in separately.
Pilot: The system is used by a limited number of users like a department, or a district, or a region, etc.
6.Post Implementation & Evaluation:
•Does the system meet user expectations?
•Maintain the system.
Fix bugs.
Keep the system current.
Make improvements.
•Some of the post implementation problems:
Insufficient support during the initial turn-on phase.
Insufficient support for maintaining the system.
Prototype Systems:
•Prototype systems are developed when the system requirements are not firm, that is, when there are more questions than answers. This usually involves systems that have never been tried before or those involving leading edge technology.
•Prototype systems involve an iteration process, that is, they are reworked again and again until the system meets user expectations. Sometimes, they are discarded, regardless of the outcome valuable insights & knowledge are gained.
7. The Perfect System:
The best systems are the replacement systems. We learn by doing; knowledge gained from the previous system is used to develop the next system, & so on. If you wait to develop the perfect system, you will develop nothing.
Considerations:
•Be aware of future needs.
•Try to find alternative solutions for improving the system.
•Secure user & management support before starting the project.
•Turning on a system before it is properly tested is an invitation to disaster.
Turn on the system when ready not when promised.
•Allow extra time for new technology.
•When purchasing software, push for zero customization.
•Don't allow the bounders to be expanded as you run the risk of an extended implementation.
•Try to use the pilot or phased approach when turning on a system.
•Don’t take short cuts and don’t assume anything.
•Don’t hide the facts, if the system is in trouble, report it immediately. Trust between users, management and the development team is essential for a successful implementation.

That's about a close as I can get.

Answer 2

There are 7 stages in the UK version:

1. Terms Of Reference — the management will decide what capabilities and objectives they wish the new system to incorporate;
2. Feasability Study — asks whether the managements' concept of their desired new system is actually an achievable, realistic goal, in-terms of money, time and end result difference to the original system. Often, it may be decided to simply update an existing system, rather than to completely replace one;
3. Fact Finding and Recording — how is the current system used? Often questionnaires are used here, but also just monitoring (watching) the staff to see how they work is better, as people will often be reluctant to be entirely honest through embarrasment about the parts of the existing system they have trouble with and find difficult if merely asked;
4. Analysis — free from any cost or realisticality constraints, this stage lets minds run wild as 'wonder systems' can be thought-up, though all must incorporate everything asked for by the management in the Terms Of Reference section;
5. Design — designers will produce one or more 'models' of what they see a system eventually looking like, with ideas from the analysis section either used to discarded. A document will be produced with a description of the system, but nothing is specific — they might say 'touchscreen' or 'GUI operating system', but not mention any specific brands;
6. System Specification — having generically decided on which software packages to use and hardware to incorporate, you now have to be very specific, choosing exact models, brands and suppliers for each software application and hardware device;
7. Implementation and Review — set-up and install the new system (including writing any custom (bespoke) code required), train staff to use it and then monitor how it operates for initial problems, and then regularly maintain thereafter. During this stage, any old system that was in-use will usually be discarded once the new one has proved it is reliable and as usable.

And only six in the official version:
1. Preliminary Investigation
2. Systems Analysis
3. Systems Design
4. Systems Development
5. Systems Implementation
6. Systems Maintenance

Sorry couldn't be of more use

Answer 3

System Life Cycle Stages

Answer 4

1) Initial study
2) System Analysis and Design
3) Program Design
4) Program development
5) Forget
6)Testing
7)Implementation
8) Maintance

Answer 5

This Site Might Help You.

RE:
what are the 8 stages of system development life cycle (SDLC)? Define each stages please.?

Answer 6

uhmm they might vary depending on the process you are using (watterfall, RAD, Spiral, Agile...etc) but basically they are just five Communication (getting the software concept) Scheduling, Analysis (getting the Requirements 'right') Design (architectural design ) Implementation and debugging ( CODING) deployment, release... as i say they vary and it depends on the software process you are using, but in a general way, thats it.

Answer 7

so amazed that I found this topic already answered! it's like you've read my thoughts!