Home > Articles > Information Technology

📄 Contents

  1. Define the Real Customer Needs
  2. Pitfalls
  3. Summary
  4. Key References and Suggested Readings
  • Print
  • + Share This

Key References and Suggested Readings

Barry Boehm. WinWin Spiral Model & Groupware Support System. 1998 Available at http://sunset.usc.edu/research/WINWIN/index.html. Dr. Boehm is Director of the University of Southern California Center for Software Engineering. The Center is under contract to the Defense Advanced Research Projects Agency via the Air Force Research Laboratory (formerly known as Rome Laboratories). It plans to develop (in collaboration with The Aerospace Corporation) a robust version of the WinWin System and to apply it to the domain of satellite ground stations.

Barry Boehm, Alexander Egyed, Julie Kwan, Dan Port, Archita Shah, and Ray Madachy. "Using the WinWin Spiral Model: A Case Study." IEEE Computer 1998:31 33–44. This University of Southern California Center for Software Engineering research project has three primary elements: (1) Theory W, a management theory and approach that says making winners of the system's key stakeholders is a necessary and sufficient condition for project success; (2) the WinWin Spiral Model, which extends the spiral software development model by adding Theory W activities to the front of each cycle; and (3) WinWin, a groupware tool that makes it easier for distributed stakeholders to negotiate mutually satisfactory system specifications. The authors found in this work that the most important outcome of product definition is not a rigorous specification but a team of stakeholders with enough trust and shared vision to adapt effectively to unexpected changes. The researchers believe that the approach will transition well to industry use.

Daniel P. Freedman and Gerald M. Weinberg. Handbook of Walkthroughs, Inspections, and Technical Reviews. 3rd ed. Chicago: Scott, Foresman and Co., 1990. This book provides a variety of examples of peer reviews and is a good source for organizations that want to consider alternative approaches.

Donald C. Gause and Gerald M. Weinberg. Are Your Lights On? How to Know What the Problem REALLY Is. 2nd ed. New York: Dorset House Publishing, 1989. As the title suggests, this book is interesting and light reading but offers valuable insights concerning real needs. The authors' perspective is that customers need assistance in defining their real requirements. A good requirements process will (1) identify the real problem, (2) determine the problem's "owner," (3) identify its root cause, and (4) determine whether to solve it. This is recommended reading for requirements engineers and their customers.

Tom Gilb and Dorothy Graham. Software Inspection. Reading, MA: Addison-Wesley, 1993. This book is about inspections of any work product, not just software. The authors' approach is very rigorous and therefore requires more training and is more expensive than normal peer reviews. However, it results in more defects being removed earlier, thus saving costs later in the development cycle. This book is invaluable for an organization that is committed to using inspections of work products—a proven method with good payback. Note that Rob Sabourin offers an economical inspections training and implementation approach. Contact him at rsabourin@amibug.com.

Rita Hadden. "How Scalable Are CMM Key Practices?" CROSSTALK 1998: vol. 11(4) 18–23. Hadden provides process improvement consulting services for organizations of all sizes. She notes that many practitioners are convinced that models such as the SW-CMM are not practical for small organizations because the cost of applying the recommended practices outweighs benefits. Her experience with more than 50 small projects does not support this view. The article describes using a disciplined, repeatable approach for projects of short duration. She concludes that CMM key practices are scalable.

Ivy Hooks. Guide for Managing and Writing Requirements. 1994. Available at ivyh@complianceautomation.com. This is a concise, well-written guidebook based on extensive experience by a practicing requirements engineer and consultant. It addresses scoping a project, managing requirements, how systems are organized, and levels of requirements, writing good requirements, requirements attributes, and specifications.

Ivy Hooks. Managing Requirements. 1994. This white paper is available at the Compliance Automation Web site http://www.complianceautomation.com/. It provides a good analysis of how failure to invest in the requirements process affects projects, and it describes major problems based on Hooks's experience. Also, it describes some of the characteristics of good requirements.

Ivy Hooks. Writing Good Requirements: A One-Day Tutorial. McLean, VA, 1997 Compliance Automation, Inc. Sponsored by the Washington metropolitan area chapter of the International Council on Systems Engineering, June 1997. This is an example of the types of briefings and courses that can be provided to facilitate a project or an organization in dealing with the requirements process. The pearl here is to ensure that you have a requirements process and that you take advantage of industry best practices in executing it. Don't find your own way and learn the errors of your ways at considerable financial, personal, project, and organizational costs.

Pradip Kar and Michelle Bailey. Characteristics of Good Requirements. 1996. Available at http://www.complianceautomation.com/. This document provides a valuable, readily available discussion of the characteristics of individual and aggregate requirements (note that characteristics of individual requirements are applicable to aggregates too). Kar and Bailey emphasize that writing good requirements is difficult, requires careful thinking and analysis, but is not magical. Time spent up front, carefully defining and articulating the requirements, is essential to ensuring a high-quality product. This is recommended reading for requirements engineers.

Joachim Karlsson and Kevin Ryan. "A Cost-Value Approach for Prioritizing Requirements." IEEE Software 14(5) 1997: 67–74. This is an excellent article that explains a method for prioritizing requirements (see the summary of their method provided in this chapter). Karlsson and Ryan provide a process for using the cost-value approach, utilizing the Analytic Hierarchy Process (AHP), which is also explained in their article.

Geri Schneider and Jason P. Winters. Applying Use Cases: A Practical Guide. Reading, MA: Addison-Wesley, 1998. This is a practical guide to developing and using use cases. Schneider and Winters provide examples from their experience and provide a case study that offers insight into common errors. An illustration of the UML notation for diagramming use cases is provided. Of particular use to requirements engineers is a "how-to" discussion on applying use cases to identify requirements.

I. Sommerville, P. Sawyer, and S. Viller. "Viewpoints for Requirements Elicitation: A Practical Approach." In: Proceedings of the 1998 International Conference on Requirements Engineering (ICRE'98), April 6–10, 1998, Colorado Springs, CO. New York: IEEE Computer Society, 1998: 74–81. Sommerville and colleagues introduce an approach called PREview to organize requirements derived from radically different sources. They show how concerns that are key business drivers of the requirements elicitation process may be used to elicit and validate system requirements. They note that PREview has been designed to allow incremental requirements elicitation (see Figure 4-12 for a high-level view of the PREview process).

Gerald M. Weinberg. The Secrets of Consulting. New York: Dorset House Publishing, 1986. Weinberg defines consulting as the art of influencing people at their request. As noted by Virginia Satir in the foreword, this book actually advises people on how they can take charge of their own growth. The author provides a light-hearted view of the role of a consultant, sharing valuable insights about people. A fundamental tenet is that we all need to follow a personal learning program. Several sources for readings and other experiences are provided.

Karl Wiegers. "First Things First: Prioritizing Requirements." Software Development Magazine 1999: 7(10):24–30. This is a good explanation of why requirements need to be prioritized and a helpful description of how to do it. Wiegers provides a Microsoft Excel requirements prioritization spreadsheet and other requirements tools that can be downloaded from his Web site, http://www.processimpact.com.

Karl Wiegers. "Habits of Effective Analysts." Software Development Magazine 2000: 8(10):62–65. See also http://www.sdmagazine.com. Wiegers provides thoughtful and provocative insights concerning the role of the requirements engineer (also called the requirements analyst, business analyst, systems analyst, or requirements manager), patterned after Steven Covey's acclaimed book The Seven Habits of Highly Effective People (Fireside, 1989). He emphasizes that requirements engineering has its own skill set and body of knowledge, which is given scant attention in most computer science educational curricula and even by most systems and software engineering organizations. Many organizations expect developers or project managers to handle this vital function on their own. A competent requirements engineer must combine communication, facilitation, and interpersonal skills with technical and business domain knowledge. Even a dynamite developer or a systems-savvy user needs suitable preparation before acting in this role. Wiegers recommends that every organization should develop an experienced cadre of requirements analysts, even though requirements engineering may not be a full-time function on every project. This article is recommended reading for all PMs and task leaders.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020