D487 SECURE SOFTWARE DESIGN 2024 VERIFIED QUESTIONS AND ANSWERS 100% CORRECT

D487 SECURE SOFTWARE DESIGN 2024 VERIFIED QUESTIONS AND ANSWERS 100% CORRECT SDLC Phase 1: planning - a vision and next steps are created SDLC Phase 2: requirements - necessary software requirements are determined SDLC Phase 3: design - requirements are prepared for the technical design SDLC Phase 4: implementation - the resources involved in the application from a known resource are determined SDLC Phase 5: testing - software is tested to verify its functions through a known environment SDLC Phase 6: deployment - security is pushed out SDLC Phase 7: maintenance - ongoing security monitoring is implemented SDLC Phase 8: end of life - the proper steps for removing software completely are considered BSIMM: a study of real-world software security that allows you to develop your software security over time OWASP SAMM: flexible framework for building security into a software develop - ment organization Static Analysis: the analysis of computer software that is performed without executing programs Dynamic Analysis: the analysis of computer software that is performed when executing programs on a real or virtual processor in real time Fuzz Testing: automated or semi -automated testing that provides invalid, unex - pected, or random data to the computer software program Waterfall Development: software development methodology that breaks down development activities into linear sequential phases; each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks D487 SECURE SOFTWARE DESIGN 2024 VERIFIED QUESTIONS AND ANSWERS 100% CORRECT Waterfall Phases (typical): plan -> build -> test -> review -> deploy Iterative Waterfall Development: each phase of a project is broken down into its own waterfall phases Agile Development: software development methodology that delivers function - ality in rapid iterations called timeboxes, requiring limited planning but frequent communication Scrum: framework for Agile that prescribes for teams to break work into goals to be completed within sprints Scrum Master (Scrum Role): responsible for ensuring a Scrum team is oper - ating as effectively as possible by keeping the team on track, planning and leading meetings, and working out any obstacles the team might face Product Owner (Scrum Role): ensures the Scrum team aligns with overall product goals by managing the product backlog by ordering work by priority, setting the product vision for the team, and communicating with external stakeholders to translate their needs to the team Development Team (Scrum Role): professionals who do the hands -on work of completing the tasks in a Scrum sprint by lending their expertise to program, design, or improve products Lean Development: software development methodology that focuses on further isolating risk to the level of an individual feature V-Model: a variation of the waterfall model, where the stage is turned back upwards after the coding phase Extreme Programming (XP): an Agile methodology that is intended to improve software quality