|
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
Problem Statement Creation and Use |
Version
1
, submitted by
chenoweth
on
7/7/2005
at
10:46 PM
View Revision History |
chenoweth.2005.1 |
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. |
Lecture: 25 min
Lab: 25 min
Homework: 2 hours
|
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
-
Architectural design
(DES.ar)
-
Requirements specification & documentation
(MAA.rsd)
-
Project control (MGT.ctl)
Authors
-
Steve Chenoweth
Prerequisites
-
1. Prior experience with real software projects (and so understanding how often stakeholder expectations are misaligned).
-
2. Basic grasp of process improvement and software menagement tools and appreciation of their value.
Learning Objectives
-
Evaluation
-
1. Assess the ability of a software project and its design to deliver value to its external stakeholders.
-
Synthesis
-
2. Use very general, non-technical goals as a starting point in creating an architecture.
-
Analysis
-
3. Coordinate high-level needs statements with very detailed versions of software requirements.
Topics
-
1. Build problem statements interactively with project stakeholders.
-
2. Compare problem statements to other project artifacts, histories and outcomes.
-
Make architectural decisions based on high-level priorities expressed in a problem statement.
Materials
-
Problem statement introduction with example
(Word)
0.00/5
[Rate Material]
See Also...
No alternate modules.
Other Resources
-
Problem Seeking: An Architectural Programming Primer, Third Edition by William Pena. AIA Press, 1987, ISBN 0-913962-87-2.
Ratings
Log in to
rate this module.
Discussions
Discuss this module in the forums.
Related Modules
|