COMP682
Comp 682 Final Exam Questions and Answers 2026
1
Factors that influence the organization of requirements
-nature and scope of the system under development;
-Techniques and strategies used to elicit and capture reqts;
-Tools and environments employed
2
Organizing by Subsystem
Complex systems can only be visualized and built as systems of subsystems;
1st build system-level reqts wo/ref to subsystems;
Refine into subsystems/define interfaces;
Hierarchy of requirements
3
Organizing by Product Families
Common functionality across family of products;
Product-family Vision doc = ways products work together;
Use cases show how apps work together;
Common SW reqts doc for shared func (menus, GUI, protocols etc.);
Each product has its own Vision/UC/SS
4
COMP682
,COMP682
Documenting Future Requirements
During elicitation find some reqts for later;
Including them might cause confusion but not including them we might forget
about them;
Designers need to be aware of them;
Include but show not for current.
5
Vision Document Purpose
The purpose of the vision document is to collect, analyze and define high-level
user needs and features of the product. The Vision document describes the
application in general terms to assure that all stakeholders are working
toward a single objective.
6
Vision Document Main Contents
The vision document captures the needs of the user, the features of the system,
and other common requirements for the project;
It contains at a high-level of abstraction the definition of both the problem
and the solution
7
Vision Document Sections"
User Description;
Product Overview;
Feature Attributes;
COMP682
, COMP682
Product Features;
Use Cases;
Other Product Reqts;
Documentation Reqts.
8
Vision Document User Description
It describes the perspective of the users of the system including the
demographics, the user environment, key needs alternatives and competition.
9
Vision Document Product Overview
It contains a product overview including the product position statement, a
summary of capabilities, assumptions, dependencies, cost, and pricing.
10
Vision Document Other Product Requirements
It identifies the non-functional requirements for the system including:
applicable standards; system requirements; licensing, security, installation,
performance.
11
Vision Document: How used/by whom
The vision document is used as a basis for discussion and agreement by the
three primary internal stakeholder communities of the project: the marketing
team, the development team and the management team.
COMP682
Comp 682 Final Exam Questions and Answers 2026
1
Factors that influence the organization of requirements
-nature and scope of the system under development;
-Techniques and strategies used to elicit and capture reqts;
-Tools and environments employed
2
Organizing by Subsystem
Complex systems can only be visualized and built as systems of subsystems;
1st build system-level reqts wo/ref to subsystems;
Refine into subsystems/define interfaces;
Hierarchy of requirements
3
Organizing by Product Families
Common functionality across family of products;
Product-family Vision doc = ways products work together;
Use cases show how apps work together;
Common SW reqts doc for shared func (menus, GUI, protocols etc.);
Each product has its own Vision/UC/SS
4
COMP682
,COMP682
Documenting Future Requirements
During elicitation find some reqts for later;
Including them might cause confusion but not including them we might forget
about them;
Designers need to be aware of them;
Include but show not for current.
5
Vision Document Purpose
The purpose of the vision document is to collect, analyze and define high-level
user needs and features of the product. The Vision document describes the
application in general terms to assure that all stakeholders are working
toward a single objective.
6
Vision Document Main Contents
The vision document captures the needs of the user, the features of the system,
and other common requirements for the project;
It contains at a high-level of abstraction the definition of both the problem
and the solution
7
Vision Document Sections"
User Description;
Product Overview;
Feature Attributes;
COMP682
, COMP682
Product Features;
Use Cases;
Other Product Reqts;
Documentation Reqts.
8
Vision Document User Description
It describes the perspective of the users of the system including the
demographics, the user environment, key needs alternatives and competition.
9
Vision Document Product Overview
It contains a product overview including the product position statement, a
summary of capabilities, assumptions, dependencies, cost, and pricing.
10
Vision Document Other Product Requirements
It identifies the non-functional requirements for the system including:
applicable standards; system requirements; licensing, security, installation,
performance.
11
Vision Document: How used/by whom
The vision document is used as a basis for discussion and agreement by the
three primary internal stakeholder communities of the project: the marketing
team, the development team and the management team.
COMP682
