Checkpoint 8.2.2.
Put the Software Development Cycle steps into the correct order.
Section 8.2 Developing Large Projects
When you are developing a large project, there are more steps in the SDLC.
- Requirements Analysis
- Users and designers work together on this step to spell out in detail what the software should do.
- Design
- Developers determine what functions, variables, and modules the project needs, and how they are all connected.
- Development
- Programmers write the program according to the design specifications.
- Testing
- This step usually happens concurrently with development. Large companies often have Quality Assurance (QA) teams that are independent of the developers to do the testing. They will also have people who fit the profile of the product’s customers test the product for usability and accessibility. This does not have to be an expensive process; this interesting article 1 makes a case for needing only five people to do usability testing—if you test often as you develop the product.
- Deployment
- Once you are satisfied that testing has shown your project is solid, it’s time to put the project out into the world. Given user experience, you may have to return to the development/testing subcycle, or even farther back to the design stage to handle users’ needs as the product gets more and more customers. You might even have to go back to the first step if people tell you that they need things you had not anticipated when you started the project.
- Maintenance
- Bugs will inevitably occur in all software. Fixing them is important to keep customers happy. Also, changes to the underlying operating system may require you to change your code and re-test and re-deploy.
Note 8.2.3.
If you look up the Software Development Life Cycle on the web, you will find that there are many different versions. The one we have presented here has six stages; others have as many as ten. All of them, however, have similar steps.
www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/
