SDLC-Software Deveolpment Life Cycle

Conclusion

Works Cited

• T. (n.d.). SDLC - Overview. Retrieved October 18, 2016, from https://www.tutorialspoint.com/sdlc/sdlc_overview.htm
• @. (n.d.). What is the Software Development Life Cycle (SDLC)? - Definition from Techopedia. Retrieved October 18, 2016, from https://www.techopedia.com/definition/22193/software-development-life-cycle-sdlc
• By breaking the product into cycles, the Agile model quickly delivers a working product and is considered a very realistic development approach. The model produces ongoing releases, each with small, incremental changes from the previous release. At each iteration, the product is tested. (2016). 6 Basic SDLC Methodologies: Which One is Best? Retrieved October 18, 2016, from https://www.roberthalf.com/technology/blog/6-basic-sdlc-methodologies-the-pros-and-cons
• T. (n.d.). SDLC - Quick Guide. Retrieved October 18, 2016, from https://www.tutorialspoint.com/sdlc/sdlc_quick_guide.htm
• @. (n.d.). What is a Patch? - Definition from Techopedia. Retrieved October 18, 2016, from https://www.techopedia.com/definition/24537/patch
• @. (2007). Understanding the pros and cons of the Waterfall Model of software development - TechRepublic. Retrieved October 18, 2016, from http://www.techrepublic.com/article/understanding-the-pros-and-cons-of-the-waterfall-model-of-software-development/

Step 6: Maintenance

After having looked at all the research, I personally believe that the Waterfall Model is the better method. For a person such as myself that does not like something to be particularly complicated, the Spiral Model’s process is just too complex. Having to start at the baseline spiral over and over again is a huge drawback. I am preferable to structure, and would not like not knowing when the software would be completed. Though no actual software is made until the later phases, it is very useful to have all your information organized and ready to go. The Waterfall method makes it simple to arrange tasks in an orderly manner.

Problems often occur in the customer environment. In fixing these problems, patches (software updates that fix bugs) are released. The product will be constantly updated to a newer version to keep up with the customer environment. Maintenance is done to deliver these advancements.

Though both methods are a good, solid way to plan your work, in my opinion, the Waterfall Model is the better way to go.

Waterfall Model

Spiral Model

Pros

Cons

Pros

Cons

• Easy to go back to fix requirements
• Users can see the system early on
• Requirements are more accurate
• Development can be organized in smaller parts

• Process is complex
• Expensive for small projects
• Spiral could go on indefinitely
• Many things to record
• Unable to identify when project may end

• Risky and uncertain
• No actual software made until later stages
• Not suitable for longer projects
• Cannot go back and change previous things that happened in the earlier phases
• Software cannot be particularly complex

• Easy to understand
• Straightforward, every stage has a defining beginning and end part
• Progress easily seen
• Emphasis on requirements and design ensures that no time is wasted
• Phases done one at a time
• Easy to organize tasks

Step 4: Integration and Testing

Step 5: Deployment of System

When the functional and nonfunctional testing is finished, the product is sent in the customer environment, or discharged into the market.

The units formerly mentioned in Step 3: Implementation, join into a system after each unit is tested. Before actually integrating, the entire system must be evaluated, to see if there are any errors or defects.

Step 4: Evaluation and Risk Analysis

Risk analysis is classifying, estimating, and overseeing how easily the software runs, as well as management risks. After the build testing is done, the client analyzes the software and gives feedback.

Step 3: Construct or Build

This step includes the actual making of the product at each spiral. The commencement of the spiral is when the product is thought of and the design is being processed. The Proof of Concept (POC-a realization of a certain method to demonstrate its feasibility, whose purpose is to verify that some concept has the potential of being used) is made to receive customer criticism. More detailed requirements are put in the ensuing spirals, along with design details. A working model of the software called build is created with a version number. The builds are then sent to customer feedback.

Step 3: Implementation

With information from the previous step, the system begins to develop. It starts out in small programs called units (used in the next phase). Each unit is eventually tested and advanced for its functionality (which is referred to as Unit Testing).

Step 2: System Design

The requirements documented in the first phase are reflected upon, and the system design is arranged. The System Design specifies hardware and system requirements.It also defines the general architecture system.

Step 2: Design

The baseline spiral in step 2 starts off with the concept design. In the following spirals, it further progresses into architectural design, logical design of modules, physical product design and final design.

Step 1: Requirement Gathering and Analysis

Every requirement and necessity for the system to be developed are put in this first step. It is then recorded and put in a requirement specification doc.

Waterfall Model:

Step 1: Identification

The first step starts in the baseline spiral, where the business requirements go.The identification of system requirements, subsystem requirements and unit requirements all go in the ensuing spirals where the product develops. This phase also involves comprehending the system requirements, by having ongoing communication between the client, and the system analyst. The product is then sent in the identified market as the last part of the spiral.

Software Development Life Cycle

“If you fail to plan, you are planning to fail.”

-Benjamin Franklin

Introduction to SDLC

Spiral Model:

Software Development Life Cycle, more commonly referred to as SDLC, is defined as “a framework defining tasks performed at each step in the software development process. SDLC is a structure followed by a development team within the software organization. It consists of a detailed plan describing how to develop, maintain and replace specific software”. Though there are many different types of models, the focus today is on the Waterfall Model, and the Spiral Model. The average model consists of six steps:

Stage 1: Planning and Requirement Analysis

Stage 2: Defining Requirements

Stage 3: Designing the product architecture

Stage 4: Building or Developing the Product

Stage 5: Testing the Product

Stage 6: Deployment in the Market and Maintenance

The steps for both models will be gone through, as well as discussing the pros and cons of each.

By: Laura Hawkins