what is SDLC? what are the different stages in SDLC?
Answer Posted / mohd. alquama anjum
SDLC Model Basic Stages
SDLC or the Software Development Life Cycle refers to the steps involved in creating a software from scratch. During earlier days, software used to be scarce and its creation was comparatively easier. Developers could create any programs they want and experience no competition. In present time, every software released to the public can easily be compared to another software. Few software can even be considered as a version of another program without any credit.
That’s why careful planning has to be made before a single code is written. Analysis has to be done before anything else is made. SDLC is known as the traditional way of executing and implementing a program. The following are the basic stages of SDLC:
1. Market Research
Before anything is implemented or written, SDLC should always understand their customers in the first place. It’s just basic business to consider what is required and what’s in demand in today's market. An abstract program could be created from this stage. Since researchers are technically not the developers, all they could do is create a list of what could be used by the public. This will basically be the mission of the software – to meet and exceed the needs that are laid out by the market research team.
2. Hardware Preparation
Once the need has been set, it is time to determine the required hardware to create the specific software. Hardware usually comes after research since the company does not know the actual requirement. They still need a plan before hardware could be purchased or upgraded.
3. Software Analysis
Once the hardware is in place, it is time to go to the specifics of the software. Developers will have to work closely with the research team and present a specific solution for their needs. In this stage of software development, the framework of the software is created. The software gains some foundation as the developers will know what to work on.
4. Software Design
The specifics of the software are elaborated in this stage of web development. Developers will now create a layout of how the software should perform. The workflow is eventually established and the front-end of the software is laid out. The rough design of the software is also presented. Analysis is constantly made on the look of the layout since it will be the first thing that customers will see. This stage is very crucial since the foundation is elaborated and things are extended for the first time. The end result and structure will be based on the initial design. The workflow is laid out and it will be the backbone of the coding structure. Developers have to ensure that each step has been explained carefully if not other developers will find it difficult to understand the software.
5. Coding
If you compare it to a business model, coding is the “operations” of the software development plan. Everything is realized during this stage. The colors and the functions are gradually developed at this point. Developers will make use of different kinds of coding techniques in their preferred platforms. They may create different platforms or create a mash-up of different platforms to different programs. Whatever their coding technique is, they will be adhering to the plans set out by the workflow. Once the program is finished, a prototype is set out for the next stage of the process.
6. Testing
Of course the program, on its first run will not perfect or wouldn’t exactly work as planned. It has to go through rigorous testing. In this stage, bugs are found and some irregularities in the software are somehow fixed. If something goes wrong with the program, it could be fixed with a simple change in codes but if the program is not working as planned, it will be returned to the developers for another round of coding. Testing will make sure the customer gets what they want all the time. Nothing is compromised during this stage. Depending on the program’s coding efficiency, testing could last for a very long time.
7. Implementation
Once the testing of program has been completed the software is ready for implementation. For various developers, implementation could mean releasing the software for public beta-testing. That means everyone can use this program but the service is not yet complete. This implementation is used to give them a glimpse of something better. The beta release is also used to test the program if it can withstand thousands of users at the same time. Of course, in theory it has to work but there is software that, for some reason crashes when it reaches a certain number of users at the same time. These are usually done for gaming programs. MMORPG games are the perfect example of implementing the program in beta version. Once the program has been under beta version for some time without any glitch, the final version is released to the public.
8. Closing
This is not very popular with the US developers, but in the UK, closing refers to the final version of the software. Everything is already in place once closing has been posted – the documentation, source codes and business plans were also implemented at the same time.
9. Maintenance
Once the program has been released, it will not be left out alone. Developers will still work on the software full time as they will monitor its popularity and performance. No one knows if something will happen to a program. This could be the easiest part of the software development stage or the most difficult – depending on the programs efficiency. That is why even at an early stage, coding and design has to be tight and precise.
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
How do you ensure that your project plan is available for others to see? Where will you find the plans of other projects executed (in the past or currently) in the center?
How do you rate yourself in c#,vb.net,Asp.net,oracle,sql server ?
I want question and paper based MS Projects. Also is there any exam which microsoft conduct for Ms Project professional to issue certification?
What is the role of CLR in ASP.NET?
When you come in to the office, how do you know what you have to do during the day?
Can any one please give me an effective format for designing a functional specification and technical specification sheet for a software developemnt related company asap...it would be highly useful for my final year project.
Write a function that inserts an integer into a linked list in ascending order. Write the test cases for this function.
How would you deal with a bug that no one wants to fix? Both the SDE and his lead have said they won?t fix it?
How did you choose the appropriate lifecycle for your project?
Please, i am a final year student in nigeria and i have a project on pension fund administration and i need help in starting.
Assignment A software house got a project to automate sales/purchase department of a furniture store. The store management is clearly transferred their requirements to the software house management. There is no chance of changing the requirements afterwards. Software house management use waterfall process model to make the project. Given is the progress flow of water-fall process model In waterfall process model, the deliverable (document) produced in one phase serves as an input to the next phase. Suppose you are a project manager who is leading this project. It is decided to work and complete the project using waterfall process model approach. You are required to develop a plan in which the key task is to decide the deliverable that should be built during and after completion of each phase. Also give a description or required contents that must be included in those deliverables. You are not supposed to make the complete project. All you are required to do is to make a Project plan. In that, you need to give a set of deliverables (documents) which according to you, should be developed in each of the phase (Requirements, Designing, implementation, Testing, Maintenance). Also provide contents which should be there in each deliverable. The contents should be clear and have brief explanation. Note:: There are one folder and one file in the attached folder. The file is named as Assignment 4 write-up which is your assignment write-up. The other folder named Project deliverables is the folder in which you are required to organize and place your deliverables. Name of the document/deliverable saved in each folder should be mentioned in the file named checklist (This file is placed in the “Project deliverables” folder) For Example If you produce a deliverable named Requirement Specification (RS) in the “Requirements” phase. You need to do following tasks 1) Finalize the RS contents 2) Save the file in sub-folder named Requirements 3) Write the name of this document in the checklist file under the heading Requirements. Similarly, you need to make and save deliverables of each phase. Not all phases contain one deliverable. There must be some phases having more than one deliverables. PLEASE SIR PRIVIDE ME THE CHECK LIST FOR GIVE SENERION ? CHECKLIST ARE: 1-Requirements 2- Designing 3- Implementation 4- Testing 5- Maintenance
Given a MAKEFILE (yeah a makefile), design the data structure that a parser would create and then write code that iterates over that data structure executing commands if needed.
How do you create the Software Project Management Plan (SPMP)?
Explain dll hell?
Explain the various activities you do (as a PL) when the project is started up.