Development of REBOK (Requirements Engineering Body Of Knowledge)

Requirements engineering has been extensively developed as a discipline. Many statistics on the software development indicate requirements process is the most influential to both success and failure of software development. However, practitioners are still difficult to understand and apply requirements engineering. We have been working together to promote requirements engineering for last four years. As the result, we developed REBOK (Requirements Engineering Body Of Knowledge) as a guideline for practitioners to learn and apply requirements engineering. This article explains the approach, knowledge model, knowledge architecture and a proof of concept of REBOK. 1. はじめに

[1]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[2]  Barbara Paech What Is a Requirements Engineer? , 2008, IEEE Software.

[3]  Jason Rubens Business analysis and requirements engineering: the same, only different? , 2007, Requirements Engineering.

[4]  Alain Abran,et al.  The Guide to the Software Engineering Body of Knowledge , 1999, IEEE Softw..

[5]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[6]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[7]  Mark T True,et al.  Software Requirements , 2005 .

[8]  P. Cochat,et al.  Et al , 2008, Archives de pediatrie : organe officiel de la Societe francaise de pediatrie.

[9]  Simon Wiedemann,et al.  Requirements Management , 2008 .

[10]  Alain Abran,et al.  Bloom's taxonomy levels for three software engineer profiles , 2003, Eleventh Annual International Workshop on Software Technology and Engineering Practice.

[11]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[12]  Benjamin S. Bloom,et al.  A Taxonomy for Learning, Teaching, and Assessing: A Revision of Bloom's Taxonomy of Educational Objectives , 2000 .

[13]  VERSION , 1922 .

[14]  Keri Schreiner The Bridge and Beyond: Business Analysis Extends Its Role and Reach , 2007, IT Professional.

[15]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[16]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[17]  Takako Nakatani,et al.  Instructional Design of a Requirements Engineering Education Course for Professional Engineers , 2010 .