% correct and verified
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
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 functionality 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 operating 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 and
responsiveness
Software Security Architect
ensures that the stakeholder security requirements necessary to protect the
organization's mission and business processes are adequately addressed
Software Security Champion
an expert on promoting security awareness, best practices, and simplifying
software security
Software Security Evangelist
an expert to promote awareness of products to the wider software community
Functional Requirements
describe what the system will do and its core purpose