- Paperback: 288 pages
- Publisher: Wiley; 5 edition (February 28, 2012)
- Language: English
- ISBN-10: 1118084144
- ISBN-13: 978-1118084144
- Product Dimensions: 8.3 x 0.8 x 8.3 inches
- Shipping Weight: 12 ounces (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
- Amazon Best Sellers Rank: #51,570 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Problem Seeking: An Architectural Programming Primer 5th Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
About the Author
William M. Peña, FAIA, a retired partner of Caudill Rowlett Scott, is often referred to as the "father" of architectural programming, having spent more than fifty years developing, refining, and explaining the programming process.
Steven A. Parshall, FAIA, is a Senior Vice President of HOK, Inc. and Director of Programing.He has been lead programmer on more than 250 major international building projects
Browse award-winning titles. See more
Top customer reviews
One section I always refer software architects to is the "cost estimation" section. If you are creating a building, you have to come in very close to your estimated cost if you want to stay in business. Compare this to the estimation of how much a software project will cost because we do not have a good estimation process. I always liked the estimate that you can park 125 cars per acre when you are trying to estimate how big a parking garage should be. We need to develop similar guidelines/estimates for software projects.
We were fortunate enough to have spent time with William Pena because he was very interested in how we had applied the techniques in his book to the development of software architectures.