Errata

Errata for Visual Models for Software Requirements

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version	Location	Description	Submitted By	Date submitted	Date corrected
PDF	Page 270 1st paragraph	"BDDs are conceptual data models that show business data objects from a business stake- holder?s perspective, whereas ERDs show the actual implementation of objects in a database schema" The entity relationship diagrams (ERDs) do not in general "show the actual implementation of objects in a database schema", they are used at various levels of abstraction, from physical to conceptual Note from the Author or Editor: Change the sentence she mentions to add "more commonly" in it so it's less extreme! BDDs are conceptual data models that show business data objects from a business stakeholder?s perspective, whereas ERDs more commonly show the actual implementation of objects in a database schema.	Anonymous	Aug 09, 2013
Printed, PDF, ePub, Mobi, , Other Digital Version	Page 338 4th Reference	In the references listed on pg 338. Karl Wiegers' book More About Software Requirements, "Redmond" is mentioned twice: Wiegers, Karl E. 2006. More About Software Requirements: Thorny Issues and Practical Advice. Redmond, WA: Microsoft Press, Redmond. The second "Redmond" after "Microsoft Press" should be omitted.	Joy Beatty	Jun 25, 2013
Printed	Page 181 First paragraph under Example	"You can also infer that any order fulfillment, order entry, or fraud services information in the Data Warehouse is probably provided via the Order Routing and Tracking System. Finally, you can see that there are no other systems in the ecosystem relevant to the project.." There should be only one period after project. It should read: "You can also infer that any order fulfillment, order entry, or fraud services information in the Data Warehouse is probably provided via the Order Routing and Tracking System. Finally, you can see that there are no other systems in the ecosystem relevant to the project."	Joy Beatty	Jan 28, 2013
Printed	Page 53 First paragraph, last sentence	"In this example, there are two objective factors that should be written, as shown in Figure 4-9." Since Figure 4-9 shows four objective factors, it should say four. Replace original sentence with: "In this example, there are four objective factors that should be written, as shown in Figure 4-9."	Joy Beatty	Jan 28, 2013
Printed	Page 95 Figure 7-12	The REQIDs are not properly numbered. Should start at REQ001 and add 1 to that last digit for each row. You might need me to recapture this image though for you? REQ001 REQ002 REQ003 REQ004 REQ005 REQ006	Joy Beatty	Jan 25, 2013
Printed	Page 90 Figure 7-3	"Figure 7-3 An example L3 Process Flow" This is a L1 process flow, therefore it should read: "Figure 7-3 An example L1 Process Flow"	Joy Beatty	Jan 25, 2013
Printed	Page 66 3rd sentence in the 3rd pararaph	"The overall net effect might be zero, or even positive" Should change positive to negative, therefore the sentence should read "The overall net effect might be zero, or even negative".	Joy Beatty	Jan 25, 2013
Printed	Page 41 Scenario paragraph	"You have approximately 10,000 customers, and your annual revenue is $10 million." It should be 100,000 customers as in: "You have approximately 100,000 customers, and your annual revenue is $10 million."	Joy Beatty	Jan 25, 2013
Printed	Page Index Index and Glossary	Numerous requirements terms, that have been defined in the glossary section are not marked correctly in the Index. For example: Page 433, under "Ecosystem Maps, defined" says to go to p. 430, but it should be p. 424. Page 432, under "design, defined" and "diagrams, defined" also say p. 430, but it should be p. 424. Page 430, under "business problems, defined" says to go to p. 429, but it should be p. 423. Page 433, under "features, defined" says to go to p. 430, but it should be p. 424. I believe these are being fixed by doing a re-indexing	Joy Beatty	Jan 25, 2013	Jan 24, 2014
Printed	Page 168 4th paragraph	Four sentences were duplicated. Remove ONE of the instances of this block of text so it only appears once in that paragraph: "For example, it might support an overarching requirement that states that "Users can only perform actions granted by their role". The matrix defines the business rules to support those requirements, but does not help identify those overarching requirements. However, you can discover requirements when you are reviewing a Role and Permissions Matrix with the business stakeholders. The permissions or operations might trigger them to remember additional needed functionality." Worried this might change paging btw.	Joy Beatty	Jan 25, 2013
Printed	Page 115 3rd Sentence of New Section near top of page	The third sentence of the new section on page 115 should be removed. The sentence reads: "That user is represented in an Org Chart." Note from the Author or Editor: This sentence should be deleted "That user is represented in an Org Chart."	Tony Higgins	Aug 07, 2012