Handbook for the CPRE Foundation Level according to the IREB Standard

by Martin Glinz, Hans van Loenhoud, Stefan Staal

In practice, requirements engineering tasks become more and more complex. In order to ensure a high level of knowledge and training, the International Requirements Engineering Board (IREB) worked out the training concept “Certified Professional for Requirements Engineering”, which defines a requirements engineer’s practical skills on different training levels. This handbook provides education and training for “Certified Professional for Requirements Engineering” (CPRE) defined by the International Requirements Engineering Board (IREB). It supports its readers in preparing for the test to achieve the “Foundation Level” of the CPRE based on the syllabus version 3.0

Genres: Computer Science, Science, Nonfiction, Textbooks, Technology, Design

139 pages, ebook

First published January 1, 2009

Reviews

[Slávek Rydval · Rating 1 out of 5]

Another group that thinks a new certification and a book must be produced (well, it makes money). Translation from German ain't good, many things in the book don't reflect the reality. From my perspective, this book is time-waster.

[Petra]

Read it quickly because of the exam, bud I like it. Useful for anyone dointg a BA job.

[Klara Näslund · Rating 3 out of 5]

Utdaterad..

[Martyft · Rating 2 out of 5]

Sjeldent kjedelig bok. Håper det hjelper mtp. å stå på eksamen. Utdatert informasjon.

[Kristofer Carlson · Rating 5 out of 5]

This book is a study guide for the Certified Professional for Requirements Engineering Exam. Requirements Engineering is a European term, and is roughly equivalent to what we in the U.S. call Business Systems Analysis. In my opinion, this book is superior to the Business Analysis Book of Knowledge (BABOK). For one thing, it provides a level of precision and detail lacking in the BABOK. For another, it's shorter.

[Fredrik Folkeryd · Rating 1 out of 5]

The introductory chapter is ok. The rest is pretty much an expanded table of contents, with very few exceptions only stating the obvious in a bloated way. For example, there is a tip to create a checklist of all stakeholders early on by asking around, to avoid missing important input.

Or, as expressed in the book:
"Stakeholder lists provide overview. An auxiliary technicque for stakeholder identification is maintaining checklists. This allows for systematic and targeted elicitation of relevant stakeholders. If the stakeholder list is updated too late or incompletely, the result may be that important aspects of the system remain undetected, that the project goal is missed or that significant additional costs arise from fixing issues. The starting point for stakeholder elicitation is often suggestions of relevant stakeholders that are made by management or by domain experts, for example. On the basis of these suggestions, relevant stakeholders can be identified."

Further, the text is riddled with references to academic works from 1955 (!) to 2014, but there is very little tangible advice on how to actually do the work.

Save your money and time.

[Dmytro Tymoshchenko · Rating 4 out of 5]

I think it`s good reading for newcomers or not very experienced BAs or as it titled in IREB Requirements engineers. Of course, there more techniques, methods, and tools for every part of requirements management, but for the start and for only to get a concept of the activity with a little drill down into details this book is definitely a good one. It good structured there aren`t a lot of useless content and it is quite laconic as for me.
I added the book in my recommendation list and without a doubt will utilize it in teaching BA beginners))

[Jose Sanz · Rating 3 out of 5]

Good read. Basic, I think. It is not part of my job the crafting and managing of requirements, but I doubt that in most companies more than this is actually needed. Only for very big companies , like I don't know, banks for example, there is the need for such rigorous process, only for requirements.

[Carlos Silva · Rating 4 out of 5]

Great book about RE and SE.
A good start for the topic for any engineer.

[Johanna · Rating 4 out of 5]

A well written introduction and self-study material. The outset is written from a mainly SW Dev perspective..but is definitely applicable to other industries and sectors.

[Sindy · Rating 5 out of 5]

I have read the German version 1.1.2 and I can really recommend it to everyone who is writing the IREB exam.

[Lijadora del Prado · Rating 1 out of 5]

This guide is must have if you need an IREB certificate. I hope you never do - or if you seem to need it (typically a job requirement for contractors) that you can talk yourself out of it. Otherwise you have my deep sympathy.

Granted, there is some usefull knowledge in there. Most of the stuff was very up to date, in the eighties of the last century.

It seems to be targeted towards beginners in the analysis craft. There's probably not a book on the market these days that is a worse introduction. The writing is dry as paper. We abandoned the way of working advocated in this book because it is guaranteed to give large overhead and projects that are late with a bad match to actual customer needs.

[Fabio L. S. · Rating 5 out of 5]

(Revisão do livro em Português)
Apresenta os principais tópicos de Engenharia de Requisitos de forma direta e objetiva. Parece ser uma versão compacta do livro do Klaus Pohl (Requirements Engineering de 2011), com um capítulo adicional sobre ferramentas.

Como o livro é a base para uma certificação, percebe-se o esforço de apresentar o consenso da área de Engenharia de Requisitos de uma forma isenta. O que torna o livro interessante é que isso é feito de uma forma adequada e objetiva. Ainda assim existem algumas questões discutíveis. Talvez a principal seja a definição dos tipos de modelos de requisitos, divididos em metas, casos de uso e requisitos de sistema (inadequadamente chamado de "tipos de requisitos" na página 87). Outro ponto discutível é definir meta apenas como parte do modelo de meta – o mais adequado seria apresentar esse conceito junto com a definição de requisitos (concordo que ainda há discussões sobre a relação entre requisitos e metas).

De qualquer forma, é um bom livro introdutório de Engenharia de Requisitos. Existem outros livros recentes que tratam o tema com maior profundidade, como o próprio livro do Pohl, o livro do van Lamsweerde, o livro da Robertson e do Robertson e o livro do Wiegers (a 3a edição com a Betty). E um último comentário: a diagramação, a formatação e as figuras da versão em português não são boas – não sei se isso é só da minha versão, que foi entregue no RE 2013.

[Andrey · Rating 3 out of 5]

Bevor ich das Buch gelesen habe, hatte ich nur ganz wenig Erfahrung mit Requirements Engineering gehabt. Von daher fand ich "Basiswissen Requirements Engineering" eine gute Einführung ins Thema, wobei ich nicht wirklich gut abschätzen kann, inwiefern die im Buch dargestellten Informationen praxistauglich sind.

[Matthias Lampe · Rating 4 out of 5]

very good compendium if you want to study for the IREB CPRE FL exam or as an entry book to requirements engineering. gives a good overview if the relevant topics. To really use the techniques and methods more detailed books are needed.

[RAFAEL VENTURA · Rating 4 out of 5]

It's a book that includes several knowledge areas I've been interesting in during the last years (Communication, Analysis, Process Modelling, Decision Making, Governance,...). I recommend reading this book for those to whom business analysis is a career choice.

[Yuri]

Its a good book

[ابراهيم الصالحي · Rating 5 out of 5]

Very powerful book. I recommend this book to anyone who wants to learn about Requirements Engineering.