INFO3333 Lecture Notes - Lecture 3: Software Requirements Specification, Scope Creep, Project Management Body Of Knowledge
22 Jun 2020
School
Department
Course
Professor
Document Summary
The scope sets out what the funder of the project gets for their money (contractual) Poor scope decisions can lead to wasted work and scope creep. It projects are very different/varied to other projects. Customers not as clear on what they want. Shared understanding between customers and designers is harder to reach. Features of the project interact a lot small changes can have big effects so the product must be described in high detail. Processes include: plan scope management, collect requirements, define scope, create wbs: documents include: scope management plan, requirements management plan, requirements document (especially srs for software dev. Software requirements are separated into functional (something the system can do) and non- functional (a characteristic of how the system does things) Software requirements specification (srs): a format of requirements document for a software dev. project with international content standards includes a list of requirements separated into functional and non-function (each with an id).
