Fix bibliography and reference to banfield

isaqb-org · Sep 5, 2024 · bdde5c8 · bdde5c8
1 parent af6b564
commit bdde5c8
Show file tree

Hide file tree

Showing 3 changed files with 28 additions and 37 deletions.
diff --git a/docs/03-Functional-Requirements/02-learning-goals.adoc b/docs/03-Functional-Requirements/02-learning-goals.adoc
@@ -37,7 +37,7 @@ Understand that many different criteria can be applied to decompose a system int
 ==== LG 3-4:Decomposing or grouping requirements into value-adding processes
 
 * Know that a process-oriented decomposition (business processes, use cases, stories, event process chains, ...) are a proven approach to allow for early implementation of some of them and postpone others), thus creating early business value.
-* Understand the first part of "INVEST" <<Wake2003>>: functional requirements should be "independent", "negotiable" and "valuable".
+* Understand the first part of "INVEST" <<wake2003>>: functional requirements should be "independent", "negotiable" and "valuable".
 
 [[LG-3-5]]
 ==== LG 3-5: Documenting value-adding processes
@@ -50,7 +50,7 @@ Understand that many different criteria can be applied to decompose a system int
 [[LG-3-6]]
 ==== LG 3-6: Refining functional requirements
 
-* Know criteria for decomposing coarse level functional requirements <<Lawrence>>, <<jacobson>>, <<hruschka19>>
+* Know criteria for decomposing coarse level functional requirements <<lawrence>>, <<jacobson>>, <<hruschka19>>
 * Know that in agile requirements engineering that decomposed parts of a larger requirement still should offer business value.
 
 [[LG-3-7]]
@@ -63,7 +63,7 @@ Understand that many different criteria can be applied to decompose a system int
 ==== LG 3-8: Knowing when to stop refining functional requirements
 
 * Understand that functional requirements are precise enough as soon as the development team has no more questions about their meaning
-* Understand the second part of "INVEST" <<Wake2003>>: "Estimable", "Small enough", "Testable"
+* Understand the second part of "INVEST" <<wake2003>>: "Estimable", "Small enough", "Testable"
 * Know the "Definition of Ready" (DoR) and why it is important for the cooperation between stakeholders
 
 [[LG-3-9]]

diff --git a/docs/07-REQ-ARCH-development-process/02-learning-goals.adoc b/docs/07-REQ-ARCH-development-process/02-learning-goals.adoc
@@ -16,7 +16,7 @@
 [[LG-7-2]]
 ==== LG 7-2: Know cooperative approaches to product development
 
-* Know the basic ideas of cooperative approaches like _Discover to Deliver_ <<Gottesdiener-12>>, Design Thinking <<gerstbach>>, Lean Startup <<ries>>, Design Sprints <<Banfield>>
+* Know the basic ideas of cooperative approaches like _Discover to Deliver_ <<gottesdiener-12>>, Design Thinking <<gerstbach>>, Lean Startup <<ries>>, Design Sprints <<banfield>>
 * Understand how such iterative approaches can be scaled to larger systems, that involve more than one development team, potentially geographically distributed.
 
 

diff --git a/docs/99-references/00-references.adoc b/docs/99-references/00-references.adoc
@@ -2,100 +2,91 @@
 // (c) iSAQB e.V. (https://isaqb.org)
 // ===============================================
 
-
-
-
-
+[bibliography]
+== {references}
 
 // tag::DE[]
+Dieser Abschnitt enthält Quellenangaben, die ganz oder teilweise im Curriculum referenziert werden.
 // end::DE[]
 
 // tag::EN[]
+This section contains references that are cited in the curriculum.
+// end::EN[]
+
 [bibliography]
 == Bibliography
 This section contains references relevant for the curriculum and/or requirements engineering in general.
 
-A +
+**A**
 
 - [[[adzic-11,Adzic-2011]]] Adzic, Goyko: Specification by Example. Manning, 2011. More info: https://gojko.net/books/specification-by-example/
 - [[[adzic-14,Adzic-2014]]] Adzic, Goyko: 50 Quick Ideas to Improve Your User Stories.
 - [[[ATAM]]] Kazman, Rick: ATAM Method for Architecture Evaluation, (_Architecture Tradeoff Analysis Method_), SEI Technical Report, https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5177
 
-B +
+**B**
 
 - [[[banfield,Banfield-16]]] Banfield, Richard: Design sprint: a practical guidebook for building great digital products, O'Reilly, 2016
 
-C +
+**C**
 
 - [[[clegg,Clegg-94]]] Dai Clegg and Richard Barker (1994). Case Method Fast-Track: A RAD Approach. Addison-Wesley.
 
-G +
+**G**
 
 - [[[gerstbach,Gerstbach-16]]] Gerstbach, Ingrid: Design Thinking im Unternehmen: Ein Workbook für die Einführung von Design Thinking, GABAL Verlag, 2016 (in German)
-- [[[Gottesdiener-12]]] Gottesdiener, Ellen: Discover to Deliver: Agile Product Planning and Analysis, EGB Consulting, 2012
+- [[[gottesdiener-12]]] Gottesdiener, Ellen: Discover to Deliver: Agile Product Planning and Analysis, EGB Consulting, 2012
 
-H +
+**H**
 
 - [[[hathaway,Hathaway-19]]] Hathaway, Angela + Tom: Getting and Writing IT-Requirements in a Lean and Agile World. Self-published, https://leanpub.com/lean-requirements-user-stories-agile
-
 - [[[hruschka19,Hruschka-19]]] Hruschka, Peter: Business Analysis und Requirements Engineering,
 Hanser Verlag, 2nd Edition 2019 (in German)
 
-I +
+**I**
 
 - [[[ireb-agile,IREB]]] IREB: Handbook Advanced Module “RE@Agile”, online: https://www.ireb.org/de/downloads/tag:advanced-level-re-agile
-
 - [[[isaqb-foundation,iSAQB-Foundation]]] iSAQB Foundation Level Curriculum: https://isaqb-org.github.io/curriculum-foundation/
-
 - [[[iso25010,ISO-25010]]] ISO-25010: Standard for Systems and software Quality Requirements and Evaluation (SQuaRE), defining a generic model for software quality. https://www.iso.org/standard/35733.html
 
-J +
+**J**
 
 - [[[jacobson,Jacobson+2011]]] Dr. Ivar JacobsonIan SpenceKurt Bittner: Use-Case 2.0: The Guide to Succeeding with Use-Cases. Online: https://www.ivarjacobson.com/publications/white-papers/use-case-ebook
 
-L +
+**L**
 
-- [[[Lawrence]]] Lawrence, Richard: How to split a story, https://agileforall.com/resources/how-to-split-a-story
+- [[[lawrence]]] Lawrence, Richard: How to split a story, https://agileforall.com/resources/how-to-split-a-story
 
-M +
+**M**
 
 - [[[mcgreal,McGreal]]] McGreal, D.: The Professional Product Owner: Leveraging Scrum as a Competitive Advantage
 
-N +
+**N**
 
 - [[[north,North]]] North, Dan: Introducing Behavior Driven Development, https://dannorth.net/introducting.bdd
 
-P +
+**P**
 
 - [[[pichler, Pichler-10]]] Pichler, R.: Agile Product Management with Scrum: Creating Products that Customers Love. Addison-Wesley, 2010
 
-R +
+**R**
 
 - [[[ries,Ries-11]]] Ries, Eric: The Lean Startup, Crown Business, 2011
 - [[[robertson-12,Robertson-12]]] Robertson,J./Robertson,S.: Mastering the Requirements Process: Getting Requirements Right. Addison Wesley; 3rd edition 2012. https://www.volere.org/mastering-the-requirements-process-getting-requirements-right/
 - [[[robertson-19,Robertson-19]]] Robertson, J. /Robertson, S.: Business Analysis Agility. Addison Wesley, 2019
 
-S +
+**S**
 
 - [[[smart-bdd,Smart-2014]]] Smart, J.F.: BDD in Action, Behavior-Driven Development for the whole software lifecycle. Manning 2014. See https://www.manning.com/books/bdd-in-action
 - [[[smart-amigo,Smart-Amigo]]] Smart, J.F.: The Anatomy of a Three Amigo requirements discovery Session. https://johnfergusonsmart.com/three-amigos-requirements-discovery/
-
 - [[[starke-hruschka-arc42,Starke-Hruschka]]] Starke,G + Hruschka, P: Communicating Software Architectures: lean, effective and painless documentation. Leanpub https://leanpub.com/arc42inpractice
 
-T +
+**T**
 
 - [[[toth,Toth-19]]] Toth, Stefan: Vorgehensmuster in der Softwarearchitektur.
 Carl Hanser Verlag, 3rd edition 2019  (in German) - especially for "_Architecturally significant requirements_"
 
-W +
+**W**
 
-- [[[Wake2003]]]: Wake, Bill: INVEST in good stories and SMART Tasks,
+- [[[wake2003,Wake-2003]]]: Wake, Bill: INVEST in good stories and SMART Tasks,
 xp123.com/Articles/invest-in-good-stories-and-smart-tasks, 2003
-
 - [[[wynn,Wynn]]] Wynn, Matt: Introducing Example Mapping: https://cucumber.io/blog/example-mapping-introduction/
-
-// end::EN[]
-
-
-
-