View Module

An error occurred while attempting to get the requested module. Cannot open database "AspNetForums" requested by the login. The login failed. Login failed for user 'swenet'. at AspNetForums.Data.SqlDataProvider.GetRatingForUser(String username, Int32 parentID) at AspNetForums.Ratings.GetRatingForUser(String username, Int32 parentID) at SwenetDev.ModuleRatingsControl.getRatingForUser(String username, ModuleRatingInfo ratingInfo) at SwenetDev.viewModule.Page_Load(Object sender, EventArgs e)

General Information

Title Problem Statement Creation and Use
Version Info Version 1 , submitted by chenoweth on 7/7/2005 at 10:46 PM
View Revision History
Module Identifier chenoweth.2005.1
Abstract Students learn to create a general vehicle, the problem statement, which communicates the needs to all stakeholders, and is used to guide their expectations and their project work.
Size Lecture: 25 min
Lab: 25 min
Homework: 2 hours
Comments This module follows common industry practice for large projects and for new work, both of which are difficult to control and tend to drift away from critical targets.

SEEK Categories

  1. Architectural design (DES.ar)
  2. Requirements specification & documentation (MAA.rsd)
  3. Project control (MGT.ctl)


  1. Steve Chenoweth


  1. 1. Prior experience with real software projects (and so understanding how often stakeholder expectations are misaligned).
  2. 2. Basic grasp of process improvement and software menagement tools and appreciation of their value.

Learning Objectives

  1. Evaluation - 1. Assess the ability of a software project and its design to deliver value to its external stakeholders.
  2. Synthesis - 2. Use very general, non-technical goals as a starting point in creating an architecture.
  3. Analysis - 3. Coordinate high-level needs statements with very detailed versions of software requirements.


  1. 1. Build problem statements interactively with project stakeholders.
  2. 2. Compare problem statements to other project artifacts, histories and outcomes.
  3. Make architectural decisions based on high-level priorities expressed in a problem statement.


  1. Problem statement introduction with example (Word) 0.00/5 [Rate Material]


See Also...

No alternate modules.

Other Resources

  1. Problem Seeking: An Architectural Programming Primer, Third Edition by William Pena. AIA Press, 1987, ISBN 0-913962-87-2.


Number of Ratings:   0

Log in to rate this module.


Discuss this module in the forums.

Related Modules