SDLC (System Development Life Cycle)
The software development lifestyles cycle is the method used within the software industry to design and develop a new software program.
SDLC defines the various steps in planning and executing any software improvement venture.
The SD project typically involves many activities and goes through different development of stages.
These stages in the development process are also referred to as software development life cycle phases.
7 phases of SDLC
- Software planning
2. System analysis
3. System development
4. Implementation
5. Testing and Integration
6. Maintenance
- Software planning
Before we even start the planning phase, the best tip we can give you is to take the time to properly understand the app development lifecycle.
The planning phase (also called the feasibility phase) is exactly what it sounds like: a phase in which the developers will plan the upcoming project.
It helps define the problem and scope of any existing systems as well as determine the goals for their new systems.
By creating an effective outline for the upcoming development cycle, theoretically catches problems before they affect development.
And help secure the funding and resources they need to realize their plan.
Perhaps most importantly, the planning phase establishes the project schedule, which can be of key importance when it comes to the development of a commercial product that must be shipped to market by a certain time.
2. Define the requirements
Defining requirements is considered part of planning to determine what the application is supposed to do and what its requirements are. For example, a social media application would require the ability to connect with a friend. The inventory program may require a search function.
3. System Analysis
The analysis phase involves gathering all the specific details required for the new system as well as determining the first ideas for prototypes.
Developers can:
Define any requirements for the prototype system,
Evaluate alternatives to existing prototypes
Conduct research and analysis to determine end-user needs
In addition, developers often create a software requirements specification or SRS document.
This includes all the specifications for the software, hardware, and network requirements for the system they plan to build. This will prevent them from draining funds or resources when working in the same location as other development teams.
4. System development
The development phase is the part where developers actually write the code and build the application according to earlier design documents and outlined specifications.
This is where static application security testing or SAST comes into play.
Product program code is created according to design document specifications. In theory, all the prior planning and outlining should make the actual development phase relatively straightforward.
Developers will follow all coding guidelines as defined by the organization and will use a variety of tools such as compilers, debuggers, and interpreters.
Programming languages can include basic tools like C++, PHP, and more. Developers select the correct programming code to use based on project specifications and requirements.
5. Implementation
After testing, the overall design of the software comes together. Various modules or designs will be integrated into the primary source code through developer efforts, typically using training environments to detect additional bugs or defects.
The information system will be integrated into its environment and possibly installed. After passing this phase, the software is theoretically ready for market launch and can be provided to all end users.
6. Testing and Integration
Creating software is not the end.
It must now be tested to ensure that there are no bugs and that the end-user experience is not negatively affected at any point.
During the testing phase, developers go through their software with a fine-tooth comb and note any bugs or defects that need to be tracked, fixed, and retested later.
It is important that the software generally meets the quality standards previously defined in the SRS document.
Depending on the skills of the developers, the complexity of the software, and the requirements of the end user, testing can be either an extremely short phase or can take a very long time.
7. Maintenance
The SDLC does not end when the software reaches the market. Developers now need to move into maintenance mode and start practicing all the activities needed to resolve issues reported by end users.
In addition, developers are responsible for implementing any changes that the software may need after deployment.
This may include addressing residual bugs that could not be fixed prior to launch or addressing new issues that arise due to user reports. Larger systems may require longer maintenance phases compared to smaller systems.
If you need more information to follow these links as well.
https://www.w3schools.in/sdlc/software-development-life-cycle-sdlc
