Software Development Life Cycle (SDLC), also known as Software Development Process, is a framework that defines the activities performed at each phase of a software development project. The aim of SDLC is to produce a high quality software that meets or exceeds customer expectations, reaches completion within times and cost estimates. Technical design requirements are prepared in this phase by lead development staff that can include architects and lead developers. This is where the actual coding and unit testing of the process by the development team happen. Once the application is migrated to a test environment, different types of testing will be performed including integration and system testing, to checks for errors, bugs and interoperability. This is the final stage of initial development, where the software is put into production and runs actual business. The size of the project will determine the complexity of the deployment.
After the software deployed, it still requires regular maintenance to continually operate at peak performance levels. Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. Software Development Life Cycle, SDLC for short, is a well-defined, structured sequence of stages in software engineering to develop the intended software product. SDLC provides a series of steps to be followed to design and develop a software product efficiently. This is the first step where the user initiates the request for a desired software product. At this step the developers decide a roadmap of their plan and try to bring up the best software model suitable for the project.
Next step is to bring down whole knowledge of requirements and analysis on the desk and design the software product. The software development paradigm helps developer to select a strategy to develop the software.
This model assumes that everything is carried out and taken place perfectly as planned in the previous stage and there is no need to think about the past issues that may arise in the next phase. This model is best suited when developers already have designed and developed similar software in the past and are aware of all its domains. The software is first developed on very small scale and all the steps are followed which are taken into consideration.
After each iteration, the management team can do work on risk management and prepare for the next iteration.

The major drawback of waterfall model is we move to the next stage only when the previous one is finished and there was no chance to go back if something is found wrong in later stages. At every stage, test plans and test cases are created to verify and validate the product according to the requirement of that stage.
This model is not suitable for large software projects but good one for learning and experimenting. Once an application is created, the SDLC maps the proper deployment and decommissioning of the software once it becomes a legacy. At this point, more work may be required in the analysis, design or coding when defects may are found.
During the maintenance stage, the system is assessed to ensure it does not become obsolete, the programmers regularly apply software patches to add functionality, fix bugs or resolve potential security issues. The team holds discussions with various stakeholders from problem domain and tries to bring out as much information as possible on their requirements. At this step the team analyzes if a software can be made to fulfill all requirements of the user and if there is any possibility of software being no more useful. System analysis includes Understanding of software product limitations, learning system related problems or changes to be done in existing systems beforehand, identifying and addressing the impact of project on organization and personnel etc. The implementation of software design starts in terms of writing program code in the suitable programming language and developing error-free executable programs efficiently.
If required, the users are trained on, or aided with the documentation on how to operate the software and how to keep the software operational.
A software development paradigm has its own set of tools, methods and procedures, which are expressed clearly and defines software development life cycle. It projects the process of development in cyclic manner repeating every step after every cycle of SDLC process. Then, on every next iteration, more features and modules are designed, coded, tested and added to the software. Because a cycle includes small portion of whole software process, it is easier to manage the development process but it consumes more resources. It can be seen as if you choose one SDLC model and combine it with cyclic process (iterative model). The model starts with determining objectives and constraints of the software at the start of one iteration. For example, in requirement gathering stage the test team prepares all the test cases in correspondence to the requirements.

It does not follow any process, or at times the customer is not sure about the requirements and future needs. This is an iterative process with much communication taking place between stakeholders, end users and the project team. Technical requirements will detail database tables to be added, new transactions to be defined, security processes and hardware and system requirements.
The requirements are contemplated and segregated into user requirements, system requirements and functional requirements.
It is found out, if the project is financially, practically and technologically feasible for the organization to take up.
The project team analyzes the scope of the project and plans the schedule and resources accordingly.
Software testing is done while coding by the developers and thorough testing is conducted by testing experts at various levels of code such as module testing, program testing, product testing, in-house testing and testing the product at user’s end. Software is tested for portability and adaptability and integration related issues are solved during implementation. The software is maintained timely by updating the code according to the changes taking place in user end environment or technology. Every cycle produces a software, which is complete in itself and has more features and capabilities than that of the previous one. Later, when the product is developed and is ready for testing, test cases of this stage verify the software against its validity towards requirements at this stage. There are many algorithms available, which help the developers to conclude the feasibility of a software project. This phase includes archiving data and required software components, closing down the system, planning disposition activity and terminating system at appropriate end-of-system time. As scientists say that after big bang lots of galaxies, planets and stars evolved just as an event.
Likewise, if we put together lots of programming and funds, you may achieve the best software product.

Email marketing co to je
Internet marketing guru scams zoosk

Comments to «Overview of software development life cycle ppt»

    Memories with our colorful birthday video.
  2. KPOBOCTOK Says:
    That can be a undesirable sign, and often.
  3. login Says:
    Based on, and even other.