Scribd
Upload
72 views

Software Requirements Engineering

This document discusses Team Skill 3 which focuses on defining the system through use cases, organizing requirements, creating a vision document, and understanding product management. It explains that a vision document describes the target market, users, and high-level features of a software project. The document also provides a template for a vision document and discusses how a delta vision document focuses only on changes from previous releases to keep the document concise.

Uploaded by

Talha Khalid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
72 views

Software Requirements Engineering

This document discusses Team Skill 3 which focuses on defining the system through use cases, organizing requirements, creating a vision document, and understanding product management. It explains that a vision document describes the target market, users, and high-level features of a software project. The document also provides a template for a vision document and discusses how a delta vision document focuses only on changes from previous releases to keep the document concise.

Uploaded by

Talha Khalid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 14

Software Requirements

Engineering

Lecture: 08
Overview of Lecture 7
Content of Lecture
• Defining the System: Skill 3
• Ch14 - Use Cases
• Ch15 - Organizing Requirements
• Ch16 - Vision Document
• Ch17 - Product Management
Sequence [Todays Agenda]
Content of Lecture
• Defining the System: Skill 3
• Ch14 - Use Cases
• Ch15 - Organizing Requirements
• Ch16 - Vision Document
• Ch17 - Product Management
Team Skill 3 -
Defining the System
(Chapters 16-17 of the requirements text)

4
Recap
 In Team Skill 1, we
developed the skills that
focus the team on analyzing
the problem.
 In Team Skill 2, we
described a set of techniques
the team can use to
understand user needs and
features proposed for the
system.
 In Team Skill 3, we'll
continue to focus on the 5

features we identified earlier.


The Vision Document

6
Key Points
 Every software project will benefit from having a Vision
document.
 The Vision document describes the application in general
terms, including descriptions of the target market, the system
users, and the application features.
 The Vision document defines, at a high level of abstraction,
both the problem and the solution.
 The Delta Vision document focuses on what has changed

7
Scope of Vision Document
 The Vision document captures the needs
of the user, the features of the system,
and other common requirements for the
project.
 As such, the scope of the Vision
document extends over the top two
levels of the requirements pyramid,
thereby defining at a high level of
abstraction both the problem and the
solution

8
Vision document serves whom?
 The marketing and product management team
 which serves as the proxy for the customer and
the user and held accountable for the success of
the product after release
 The project team developing the application
 The management team, which will be held
responsible for the business outcome of the
endeavour
9
Importance of Vision Document
 It captures the essence of the product from all
significant perspectives in a short, abstract, readable,
and manageable form
 The Vision document primarily focuses on the early
phases of the project.
 It leads to handsome returns in later phases of the project

10
Vision Document Template
1. Introduction
2. User Description
3. Product Overview
4. Feature Attributes
5. Product Features
6. Exemplary Use Cases
7. Other Product Requirements
8. Documentation Requirements
9. Glossary 11

See the Detailed version of Vision Document from the Text. (Appendix B)
The Delta Vision Document
 Keeping the Vision document understandable and
manageable is an important team skill.

 To assist in this process, it is helpful to keep the Vision


document as short, concise, and "to the point" as possible

 However, in future releases, you may discover that it is


counterproductive to repeat features that have been
incorporated in prior releases

 Delta Vision document, addresses these issues 12


The Delta Vision Document

13
Assignment 3 (CLO 3)
• Define Vision Document for the Project
according to the Template provided in the
Text

• Divide different Sections among teams


members equally and mention those
names at the start of the Document

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy