Product Design

Part 2: Product Design FB 5

Software design

Process of specifying the nature and composition of a software system that satisfies client needs and desires, subject to constraints

Software product design

Process of specifying software product features, capabilities, and interfaces to satisfy client needs and desires

Analysis

Understanding the problem; result in needs; A statement of the “problem”; “The user needs to”

Resolution

Solving the problem; results in requirements; A statement of the “solution”; “The product must”

Heavyweight/Non-Incremental

Software process that has product design (mostly) completed “up front”; result is (mostly) “set in stone”/”non-negotiable”; Analysis is (mostly) completed before resolution begins

Agile/Incremental

Software process that has product design done “just in time”; Product is modified continuously based on conversations and negotiations with stakeholders

Consumer product

Product for a large number of customers

Niche product

Product for more than one customer but not “mass market”

Custom product

Product for one customer

New

Adjective that describes a product thats different from anything else

Derivative

adjective that describes a product similar to one or more existing products

Maintenance/Update

adjective that describes a product that is a new version of an existing product

Visionary

adjective to describe a product that requires new technology to be developed

Leading edge

Adjective that describes a product involving proven technology that isn’t in widespread use

Established

Adjective that describes a product that is widely used in other products

Problem Domain Glossary

The terms (and their definitions) that are specific to the problem/product of interest

Organization Chart

A hierarchical display of the positions and reporting relationships in an organization

Stakeholder Goals List

A catalog of important stakeholder categories and their goals

Needs List

A collection of need statements, each of which documents a single product feature, function, or property desired by a stakeholder

Functional Requirement

How a product must map inputs to outputs (i.e., behavioral requirements)

Nonfunctional Requirement

A statement that a product must have certain properties (e.g., quality, performance, and security requirements)

Data Requirement

A statement that certain data must be input to, output from, or stored by a product

User-Level Requirement

A statement about how a product must support stakeholders in achieving their goals

Operation-Level Requirement

A statement about individual operations, inputs, outputs, etc… that a product must have/provide

Physical-Level Requirement

A statement about the physical form of a product, its physical interface to its environment, or its data formats