Is there a way to learn about the SDLC in practice while self teaching? /u/XLLani CSCQ protests reddit

I have a diagram of a full SDLC but it’s pretty high level. Is there a way to learn what it’s like in practice or is that something you learn on the job? I’m looking at the diagram and writing the code is such a small fraction of the work it seems.

  1. Gathering requirements

  2. Develop changes

  3. Submit pull request

  4. Automated build

  5. Code quality analysis

  6. Automated unit test execution

  7. Fail – back to Dev / Pass – peer code review

  8. Dev deployment

  9. Vulnerability scan

  10. Dev automated test execution

  11. Manual unit test

  12. Test deployment

  13. Test automated test execution

  14. Manual functional test

  15. QA approval

  16. QA deployment

  17. Vulnerability scan

  18. Performance test

  19. QA automated test execution

  20. Fail – defect management back to Dev / Pass – prod approval

  21. Prod deployment

  22. Smoke test

  23. Health monitoring

submitted by /u/XLLani
[link] [comments]

​r/cscareerquestions I have a diagram of a full SDLC but it’s pretty high level. Is there a way to learn what it’s like in practice or is that something you learn on the job? I’m looking at the diagram and writing the code is such a small fraction of the work it seems. Gathering requirements Develop changes Submit pull request Automated build Code quality analysis Automated unit test execution Fail – back to Dev / Pass – peer code review Dev deployment Vulnerability scan Dev automated test execution Manual unit test Test deployment Test automated test execution Manual functional test QA approval QA deployment Vulnerability scan Performance test QA automated test execution Fail – defect management back to Dev / Pass – prod approval Prod deployment Smoke test Health monitoring submitted by /u/XLLani [link] [comments] 

I have a diagram of a full SDLC but it’s pretty high level. Is there a way to learn what it’s like in practice or is that something you learn on the job? I’m looking at the diagram and writing the code is such a small fraction of the work it seems.

  1. Gathering requirements

  2. Develop changes

  3. Submit pull request

  4. Automated build

  5. Code quality analysis

  6. Automated unit test execution

  7. Fail – back to Dev / Pass – peer code review

  8. Dev deployment

  9. Vulnerability scan

  10. Dev automated test execution

  11. Manual unit test

  12. Test deployment

  13. Test automated test execution

  14. Manual functional test

  15. QA approval

  16. QA deployment

  17. Vulnerability scan

  18. Performance test

  19. QA automated test execution

  20. Fail – defect management back to Dev / Pass – prod approval

  21. Prod deployment

  22. Smoke test

  23. Health monitoring

submitted by /u/XLLani
[link] [comments] 

Leave a Reply

Your email address will not be published. Required fields are marked *