CSC b1.2 s2

• SDLC or the Software Development Life Cycle is a process that produces software with the highest quality and lowest cost in the shortest time possible.
• SDLC provides a well-structured flow of phases that help an organization to quickly produce high-quality software which is well-tested and ready for production use.
• SDLC Involves six phases as explained in the introduction. Popular SDLC models include the Waterfall model, iterative model, and Agile model.
• How SDLC work

  1. SDLC works by lowering the cost of software development while simultaneously improving quality and shortening production time. SDLC achieves these apparently divergent goals by following a plan that removes the typical pitfalls of software development projects. That plan starts by evaluating existing systems for deficiencies.
• How SDLC works

  2. Next, it defines the requirements of the new system. It then creates the software through the stages of analysis, planning, design, development, testing, and deployment. By anticipating costly mistakes like failing to ask the end-user or client for feedback, SLDC can eliminate redundant rework and after-the-fact fixes.
• 6 phase SDLC

  1. Requirements analysis
  2. Planning
  3. Architectural design
  4. Software development
  5. Testing
  6. Deployment
• STEP 1 SDLC: REQUIREMENT ANALYSIS

  "What are the current problems?"
• STEP 1 SDLC: REQUIREMENT ANALYSIS

  What are the current problems?" This stage of the SDLC means getting input from all stakeholders, including customers, salespeople, industry experts, and programmers. Learn the strengths and weaknesses of the current system with improvement as the goal.
• STEP 2 SDLC: PLANNING "What do we want?"
• STEP 2 SDLC: PLANNING • In this stage of the SDLC, the team determines the cost and resources required for implementing the analyzed requirements. In other words, the team should determine the feasibility of the project and how they can Implement the project successfully with the lowest risk in mind.
• STEP 3 SDCL : ARCHITECTURAL DESIGN "How will we get what we want?"
• STEP 3 SDCL : ARCHITECTURAL DESIGN

  • This phase of the SDLC starts by turning the software specifications into a design plan called the Design Specification. All stakeholders then review this plan and offer feedback and suggestions. Failure at this stage will almost certainly result in cost overruns at best and the total collapse of the project at worst.
• STEP 4 SDLC: SOFTWARE DEVELOPMENT "Let's create what we want."
• STEP 4 SDLC: SOFTWARE DEVELOPMENT At this stage, the actual development starts. It's Important that every developer sticks to the agreed blueprint. Also, make sure you have proper guidelines in place about the code style and practices.
• STEP 4 SDLC: SOFTWARE DEVELOPMENT

  For example, define a nomenclature for files or define a variable naming style such as Student Name. This will help your team to produce organized and consistent code that is easier to understand but also to test during the next phase.
• STEP 5 SDLC: TESTING "Did we get what we want?"
• STEP 5 SDLC: TESTING in this stage, we test for defects and deficiencies. We fix those issues until the product meets the original specifications. In short, we want to verify if the code meets the defined requirements.
• STEP 6 SDLC: DEPLOYMENT "Let's start using what we got."
• STEP 6 SDLC: DEPLOYMENT At this stage, the goal is to deploy the software to the production environment so users can start using the product. However, many organizations choose to move the product through different deployment environments such as a testing or staging environment.

  • This allows any stakeholders to safely play with the product before releasing it to the market. Besides, this allows any final mistakes to be caught before releasing the product.
• STEP 7 SDLC (Extra): MAINTENANCE✩ "Let's get this closer to what we want."
• STEP 7 SDLC (Extra): MAINTENANCE The plan almost never turns out perfect when it meets reality. Further, as conditions in the real world change, we need to update and advance the software to match.
• SDLC model

  1. Waterfall model
  2. Agile model
  3. Iterative model
• Waterfall model is the oldest and most straightforward. With this methodology, we finish one phase and then start the next. Each phase has its own mini-plan and each phase "waterfalls" into the next. The biggest drawback of this model is that small details left Incomplete can hold up the entire process.
• Agile SDLC model separates the product into cycles and delivers a working product very quickly. This methodology produces a succession of releases. Testing of each release feeds back info that's Incorporated into the next version. According to Robert Half, the drawback of this model is that the heavy emphasis on customer interaction can lead the project in the wrong direction in some cases.
• Iterative Model This SDLC model emphasizes repetition. Developers create a version very quickly and for relatively little cost, then test and improve it through rapid and successive versions. Orie big disadvantage here is that it can eat up resources fast if left unchecked.
• Benefits of the SDLC 1. Developers understand what they should build and why. 2. Everyone understands the costs and resources required. 3. The benefits of SDLC only exist if the plan is followed faithfully.