31269 Lecture Notes - Lecture 6: Scrum (Software Development), Software Requirements Specification, User Story
Lecture 6 – Software Requirements Specification and Documentation
SRS
• A software Requirements Specification is a document that provides the
detailed description of what the system should do. It is sometimes known as
a functional specification and serves as a contract between the client and the
vendor.
• Its purpose is to analyse the elicited requirements and define what designers
and developers have to build. It is also a verification against the delivered
system and serves to validate that the system is indeed what the stakeholder
wants.
• The SRS is used to support the testing of the software, and is a baseline for
evaluating the software.
Requirements Specification
• There are two approaches, being the traditional or agile approach.
• The traditional approach:
o Has an upfront and detailed requirements specification with simple
plain language statements and structured use cases.
• The Agile Approach
o Is iterative and makes use of user stories
▪ Card, conversation, confirmation
▪ User story map
▪ Estimation and prioritisation
▪ Agile Card Wall
o The basic idea behind an iterative and incremental development
process is to develop a system through repeated cycles in smaller
portions at a time. This allows developers to take advantage of what
was learning during previous development cycles/versions of the
system
find more resources at oneclass.com
find more resources at oneclass.com
