No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
The requirements engineering body of knowledge (REBoK)
Abstract
A body of knowledge is a term used to represent the complete set of concepts, terms and activities that make up a professional domain. It encompasses the core teachings, skills and research in a field or industry. So far, the discipline of RE is lacking an official Requirements Engineering Body of Knowledge (REBoK). This working session brings together researchers and practitioners to elaborate the goals, requirements and constraints for a REBoK that shall serve as commonly agreed basis for developing a draft over the following months.
... BOK must be embodying the consensus reached by the community; for this reason BOK will be of applicate. This consensus is a prerequisite for the adoption of the BOK by the community [9]. BOK may include technical terms and theoretical concepts as well as recommended practices [14]. ...
... Many people, groups, companies, and other organizational or governmental entities have a stake in educational programs [9]. i. ...
... BOK must embody the consensus reached by the community for which this BOK will be of application. This consensus is a prerequisite for the adoption of the BOK by the community[9].Knowledge Area Structure of a body of knowledge whichdefine what a professional needs to understand and the tasks a practitioner must be able to perform.[2].ProfilesA set of characteristics that identify or are thought to identify a particular type of knowledge.[2]. ...
Bodies of Knowledge (BOK), contain the relevant
knowledge for a discipline, and it is necessary for the development of
the science, and application in the professional, and occupational
profiles, and the possible incidence in the industry of Ecuador. In this
paper, it is shown an evaluation of professional and occupational
profiles based on standard Software
Engineering Body of Knowledge
SWEBOK 2004 (Spanish Version), and the development of
ontological model, in order to obt
ain the necessary information to
establish the relationship, and the criteria to evaluate the profiles
based on the guide of knowledge
... BOK must be embodying the consensus reached by the community; for this reason BOK will be of applicate. This consensus is a prerequisite for the adoption of the BOK by the community [1]. A BOK may include technical terms and theoretical concepts as well as recommended practices [2]. ...
... BOK must embody the consensus reached by the community for which this BOK will be of application. This consensus is a prerequisite for the adoption of the BOK by the community [1]. id code levels Of Abstraction context structure by Knowledge Area Structure of a BOK, which define what a professional needs to understand and the tasks that a practitioner must be able to perform [3]. ...
Bodies of Knowledge (BOK), contain the relevant information for an area of knowledge, and it is necessary for the development of the science and application in the professional and occupational profiles and the possible incidence in the industry. This paper showed an evaluation of professional and occupational profiles based on standard Software Engineering Body of Knowledge (SWEBOK) and ontological model in order to obtain the necessary information to establish the relationship in these contexts.
... Calazans et. al. (2017) apresentam uma comparação entre a academia e o mercado de trabalho brasileiro, competências que o engenheiro de requisito deve ter segundo o REBoK (PENZENSTADLER et al., 2013), como sendo: entendimento, análise e mapeamento de processos de negócio; gerenciamento de projetos; técnicas de elicitação, análise, especificação, documentação e validação das necessidades dos stakeholders de um projeto; entre outras. Nota-se nesse documento a descrição de algumas soft skills e, principalmente, hard skills. ...
p>As soft skills ou habilidades interpessoais são uma gama de traços de personalidade, comunicação, linguagem, hábitos pessoais que caracterizam nossos relacionamentos com outras pessoas. Essas habilidades são imprescindíveis na vida dos profissionais das diversas áreas, sendo estes conceitos difundidos e procurados cada dia mais pelo mercado de trabalho. No contexto dos profissionais da área de informática existe uma demanda prioritária para o desenvolvimento de diversas competências técnicas (e.g., linguagens de programação, bancos de dados entre outras tecnologias). Contudo, existe também uma necessidade crescente de desenvolvimento de competências não-técnicas por parte desse tipo de profissional. Assim, compreender quais soft skills são mais relevantes no contexto destes profissionais é de suma importância para o desenvolvimento de suas atividades. Esta pesquisa tem por objetivo analisar como profissionais de informática enxergam a importância do desenvolvimento das soft skills em suas carreiras e quais destas têm maior impacto em suas atividades. Através de dados coletados por meio de um questionário eletrônico efetuado com profissionais da área de informática foram obtidos dados quantitativos e qualitativos para suportar as diversas questões de pesquisa do presente estudo. Dados obtidos a partir de 62 respostas válidas demonstram que os profissionais de informática entendem que as soft skills têm um impacto em suas atividades diárias bem como no desenvolvimento de suas carreiras. Contudo, identificamos ainda que não existe grande preocupação com o desenvolvimento destas habilidades, sendo necessária sua melhor difusão entre os profissionais da área de informática. </p
... Competence-oriented didactics (COD) [12,13] that were used by two studies, others are only used once by different articles. Role playing 2 [6,7] Motivational modeling 2 [8,9] Requirement modeling tool 2 [10,11] Competence-oriented didactics (COD) 2 [12,13] Rebok 2 [14,15] Scoring rubrics 1 [16] Workshop videos 1 [17] Agile 1 [18] IOT aware model 1 [19] Direction framework 1 [20] KOAS model 1 [6] Soft system methodology SSM ...
Requirements engineering is an essential activity of software development lifecycle (SDLC) and its importance has enormously grown in recent years due to exponential growth of software industry. In this context, requirements engineering education has become largely indispensable for computing graduates and trainees in software industry. Several studies have explored different dimensions of requirements engineering education and relevant pedagogical techniques over the past few years. This systematic review aims at identifying and highlighting the extant research on REE that is available and to select useful approaches that can help in expediting the growth in this field. The systematic literature review is performed to classify existing literature related to REE into four categories: method/techniques, tools, comparison studies, and frameworks used in REE. After a rigorous evaluation process, 32 primary studies were selected and classified according to these categories. Results of this SLR indicate a significant shift toward this dimension. We have highlighted several research trends and gaps that need to be addressed by the RE community.
... BoKs exist for many professions but are normally only discussed or critiqued when a nascent profession feels it needs one, e.g. recent work on requirements engineering (Penzenstadler et al., 2013), or when a major update is required, e.g. project management (Morris, 2001). ...
As our dependency on ever-more complex, opaque, and ubiquitous information and communication technologies (ICTs) increases, ethical concerns about the development of those technologies are also rising. One approach to mitigate these concerns is to improve the maturity of the ICT profession through codification of its knowledge base and professional ethics. In this paper, some key theoretical approaches to ethics with a long-established tradition within Philosophy are explored and how these approaches may manifest in the codification of knowledge within ICT Bodies of Knowledge (BoKs) is discussed. BoKs provide a common vocabulary and knowledge inventory to aid communication and encourage shared values and practices, particularly in emerging professional areas such as the ICT profession. Thus, identifying and understanding how ethics are codified in ICT BoKs is important for maturing ICT professional practice in general, and more specifically, for the resolution of ethical concerns. This paper 1) explores considerations and approaches to how ethics are incorporated within ICT BoKs, and 2) conducts content analysis on how ethics are codified within the content structure of ICT Boks. It is found that theoretical ethical approaches are rarely explicated cited in BoKS though, in the more mature BoKs, the discussion of ethics does include consideration of most of the major philosophical approaches. The implications of how knowledge about ethics is described and integrated into the wider knowledge infrastructure of the ICT profession including curriculum guidelines and accreditation processes is discussed. In a wider contribution to the Knowledge Management discipline, potential lessons to increase maturity for other emerging professions through the development of BoKs are also outlined.
... BoKs exist for many professions but are normally only discussed or critiqued when a nascent profession feels it needs one, e.g. recent work on requirements engineering (Penzenstadler et al., 2013), or when a major update is required, e.g. project management (Morris, 2001). ...
As our dependency on ever-more complex, opaque, and ubiquitous information and communication technologies (ICTs) increases, ethical concerns about the development of those technologies are also rising. One approach to mitigate these concerns is to improve the maturity of the ICT profession through codification of its knowledge base and professional ethics. In this paper, some key theoretical approaches to ethics with a long-established tradition within Philosophy are explored and how these approaches may manifest in the codification of knowledge within ICT Bodies of Knowledge (BoKs) is discussed. BoKs provide a common vocabulary and knowledge inventory to aid communication and encourage shared values and practices, particularly in emerging professional areas such as the ICT profession. Thus, identifying and understanding how ethics are codified in ICT BoKs is important for maturing ICT professional practice in general, and more specifically, for the resolution of ethical concerns. This paper 1) explores considerations and approaches to how ethics are incorporated within ICT BoKs, and 2) conducts content analysis on how ethics are codified within the content structure of ICT Boks. It is found that theoretical ethical approaches are rarely explicitly cited in BoKS though, in the more mature BoKs, the discussion of ethics does include consideration of most of the major philosophical approaches. The implications of how knowledge about ethics is described and integrated into the wider knowledge infrastructure of the ICT profession including curriculum guidelines and accreditation processes is discussed. In a wider contribution to the Knowledge Management discipline, potential lessons to increase maturity for other emerging professions through the development of BoKs are also outlined.
(
... According to [1], a Body of Knowledge (BOK) is a concept used to represent concepts, terms, and activities that make up a professional domain. In addition, an Open BOK is necessary because it allows us to develop the abilities and talents of professionals in different Knowledge Areas (KAs) [2]. ...
In this review, a Systematic Literature Review (SLR) on Open Body of Knowledge (BOK) is presented. Moreover, the theoretical base to build a model for knowledge description was created, and it was found that there is a lack of guidelines to describe knowledge description because of the dramatically increasing number of requirements to produce an Open BOK, the difficulty of comparing related BOK contents, and the fact that reusing knowledge description is a very laborious task. In this sense, this review can be considered as a first step in building a model that can be used for describing knowledge description in Open BOK. Finally, in order to improve the educational context, a comparison among BOK, structure, and evolution is conducted.
... • AT1.2 -BPMN4EIS: application of business process modelling to support requirements engineering and information systems modelling, as described in BABOK [II15], SWEBOK (guide to the Software Engineering Body Of Knowledge) [BF14] or REBoK (Requirements Engineering Body of Knowledge ) [Pe13] guides. Papers using this approach also cover ontologies for business process application to requirements engineering, notably the development of methodologies, languages and heuristics to derive software requirements from business process models (such as UML artefacts from BPMN models, for example). ...
The advent of Business Process Management offered a new approach to improve business and IT strategic alignment in organizations throughout development of process-aware Enterprise Information Systems. For that matter, extracting software requirements from business process models leverages engineering of adaptive information systems, which are able to adjust to changes in operation as of process redesign. This study describes a systematic literature review in Requirements Engineering approaches to derive Enterprise Information Systems from Business Process Management, aiming to provide the state-of-the-art academic overview on this research topic. Results reveal six different approach types, with variations on software development degree of automation, suggesting diverse strategies for process-oriented information systems adoption.
... They exist for many professions but are normally only discussed or critiqued when a nascent profession feels it needs one, e.g. recent work on requirements engineering (Penzenstadler et al., 2013), or when a major update is required, e.g. project management (Morris, 2001). ...
Ethical concerns about the development and ubiquity of ICT (Information and communications technology) are becoming heightened as awareness of our increased dependency, though corresponding lack of understanding and transparency of new technologies such as IoT and AI unfold. One way of tackling this is to increase professionalism within ICT, and Bodies of Knowledge (BoKs) are an important part of this. BoKs represent the knowledge needed to function as a profession, and are becoming increasingly essential to aid communication and encourage shared and agreed upon values and practices, such as in emerging areas. They are valuable and influential in developing the scope and maturity of the ICT profession and in-turn ICT development in society. Thus, identifying and understanding the codification of ethics in BoKs is important to maturing ICT professional practice in resolving ethical concerns. This paper 1) explores considerations and approaches to the incorporation of ethics within BoKs, and 2) carries out content analysis on how ethics is codified within the content structure of ICT BoK. Findings reveal a range of different approaches which suggests the value of categorising these approaches and developing guidance on a more consistent approach. We conclude by recommending future research for revealing and tackling both overt and implicit aspects to ethics within BoKs.
... Firstly, the general structure of the BOK is described, in order to establish the core (skills, knowledge, and experience to be taught in the curriculum to achieve the expected student outcomes). In the same way, the BOK established Knowledge Areas (KAs) Each KA descriptions should use the following structure: Acronyms, Introduction, Breakdown of Topics of the KA, Matrix of Topics vs. Reference Material, List of Further Readings, and References (Penzenstadler et al., 2013) and (Fairley et al., 2014); each area is broken down into smaller divisions called units, which represent individual thematic modules within an area. Unit is further subdivided into a set of topics, which are the lowest level of the hierarchy. ...
The Internet of Things (IoT) has taken an important boom in different areas of knowledge, especially in education. The inclusion of new technologies has impacted the education sector and changed the ways of teaching. Thus, the curricula that are taught in the context of engineering and knowledge areas should be aligned to such change. In this paper, an information mapping was carried out as a scientific methodology to establish the base elements to create a book of knowledge (BOK). This information mapping is aligned with IoT for a standardized education.
... In [28] [29], knowledge areas are focused on innovation and its incidence in industry in the context of software engineering. ...
Bodies of Knowledge (BOK) contain the most relevant knowledge for a discipline. BOK must embody the consensus reached by the community for which a specific BOK will be applied. This consensus is a prerequisite for the adoption of the BOK by the community. In this context, at the level of higher education, especially in the field of software engineering, the academic world shows a significant enthusiasm for the development of various competencies related to entrepreneurship and innovation, focusing on both the promotion of opportunities and the strengthening of existing connections between university and software industry. The reality is that one of the main challenges in software engineering is to find the correct entrepreneurship competencies that should be promoted when training professionals, once the latter have finished their studies and started working in either the national or international software industry. In this sense, this paper is aimed at generating innovation and entrepreneurship skills in professionals in software engineering training. These competences are based on BOK principles.
... A BOK is a term used to represent the complete set of concepts, terms, and activities that make up a professional Domain. It encompasses the core teachings, skills, and research in a field or industry [38]. One of the main concerns of the software industry is to develop the talent of its human resources, since the quality, and innovation of its products and services depend to a great extent on the knowledge, the ability and the talent of software engineers [1]. ...
Bodies of Knowledge (BOK), contain the relevant knowledge for a disciplines as example Software Engineering (SE), System Information (SI), Information Technology (IT), Computer Science (CS), Medicine, Economics, and others areas of knowledge. BOK describes relevant knowledge for a discipline, and will need show the consensus in the Knowledge Areas (KA), and related disciplines. The development of this consensus is a prerequisite to the adoption of coherent skills development in the education context, and continuing professional programs both in public and private organizations. In this context a systematic mapping study (SMS), it was performed to evaluate quantity and types of primary studies in an area of interest. SMS will be used as the research method within this research. The research method proposed will allow to sort and classify the information referent to the topics of this research. This paper is an attempt to analyze existing proposals on BOK contents, structure, and make a proposal what the kind of contents it should have, and how it should be structured so that this consensus among all parties can be described and best achieved. In the same way the relevance, and useful of the BOK in the curricular design for the innovation, and the industry context is present.
... BOK must be embodying the consensus reached by the community; for this reason BOK will be of applicate. This consensus is a prerequisite for the adoption of the BOK by the community Penzenstadler et al. (2013). A BOK may include technical terms, and theoretical concepts as well as recommended practices Taguchi et al. (2013). ...
Knowledge representation is a multidisciplinary subject that needs to apply theories, and techniques from logic, ontology, and computation, for this reason the Bodies of Knowledge (BOK), contain the relevant information for an area of knowledge, and it is necessary for the development of the science, and application in the professional, occupational profiles, and the possible incidence in the industry.
This paper showed an evaluation of professional, and occupational profiles based on standard Software Engineering Body of Knowledge (SWEBOK), and ontological model as tool in order to obtain the necessary information to establish the relationship in these contexts.
... III. BACKGROUND A BOK is a collection of substantial concepts; it includes theory models [13], [3] and skills that represent knowledge of a certain area in engineering or scientific discipline, and ensures its common understanding. A BOK may include technical terms and theoretical concepts as well as recommended practices [18]. ...
A Body of Knowledge (BOK) is a term used to represent the complete set of concepts, terms, and activities
that make up a professional domain. It encompasses the core teaching skills and research in a field or industry [13]. One of the main concerns of the software industry is to develop the talent of its human resources since the quality and innovation of its products and services depend of a great extent on the Knowledge, the ability, and the talent of technical engineers.
In the educational area the used of BOK and Cloud Computing Tools are becoming the best way to provide solutions that meet the current need for greater collaboration between business,industry, education, and society; for this reason, the development of software products based in innovation is important for the professional life of a software engineering, since it leads to transform routine tasks into automated tasks;
in the same way, it allows to manage processes focused on aligning services of Information Technology (IT) to the needs of companies with an emphasis on the benefits that the final customer added may perceive to the factor of I+D+I in order to create an innovative product. The current study focuses on the use of computer tools in the cloud in its phases: definition, planning, and control of software project based on the innovation
as a tool for development and knowledge generation based in BOK.
The tools of Computing in the Cloud analyzed were: Alfresco, Redbooth, DotProject, Dealines, and Redmine. The use of these tools permitted to obtain information to formulate a BOK in the context of projects.
The Bodies Knowledge (BOK) shows information relevant to the different areas of science, the knowledge representation for BOK is essential to understand the real context and the possible application of these BOKs in science especially in the educational context. This article shows the combination of EITBOK, ITBOK - BIZBOK and Enterprise Architecture (EA) as a framework for educational process improvement.KeywordsBusiness architectureBody of knowledgeEITBOKITBOKBIZBOKEducationEnterprise Architecture (EA)
Disponível em: http://repositorio.utfpr.edu.br/jspui/handle/1/4281
Esta dissertação propõe um método e uma linguagem de modelagem gráfica de requisitos de software e sistemas sob o nome de RIMON (Requirements and Interdependencies MOdeling Notation). Esta linguagem permite representar requisitos e suas interdependências de forma sistemática, precisa e expressiva, visando contribuir para a melhoria da qualidade da especificação de requisitos de softwares e sistemas. Originada a partir de conceitos da abordagem RON (Requisitos Orientados a Notificações), a RIMON foi criada para ser visualmente atrativa em possíveis usos comerciais. Essa atratividade decorre de um desenvolvimento fundamentado na teoria de física das notações (Physics of Notations – PoN), que fornece princípios destinados a produzir notações visuais eficientes em termos de comunicação. Adicionalmente, a linguagem é definida por meio de uma sintaxe abstrata (metamodelo) e de uma sintaxe concreta (sintaxe visual) complementada por um mapeamento semântico preciso. Em relação ao método proposto, este consiste em um ciclo iterativo de atividades para identificação e análise dos dados de entrada e modelagem gráfica dos requisitos e suas interdependências. A RIMON oferece características tais como suporte a modelagem de requisitos funcionais e não-funcionais, entidades, atributos, pré-condições, pós-condições e identificação de conflitos. Como diferencial, a modelagem de pré-condições possibilita representar restrições relativas a requisitos não-funcionais por meio de atributos contendo condições lógico-matemáticas. Por fim, este trabalho apresenta três experimentos de modelagem usando RIMON, tanto de requisitos de sistemas (extraídos da literatura) quanto de requisitos de software (projeto real), destinados a demonstrar e verificar as capacidades da linguagem.
Available in: http://repositorio.utfpr.edu.br/jspui/handle/1/4281
This dissertation proposes a method and a language for graphic modeling of software and systems requirements, under the name of RIMON (Requirements and Interdependencies MOdeling Notation). This language allows to represent requirements and their interdependencies in a systematic, precise and expressive way, aiming to contribute to the quality improvement of software and systems requirements specifications. Sourced in concepts of RON (Requirements Oriented to Notifications) approach, RIMON was designed to be visually attractive in its possible commercial usage. This attractiveness results from a development grounded in the Physics of Notations (PoN), which provides principles for creating efficient visual notations in terms of communication. In addition, the language is defined by an abstract syntax (metamodel) and a concrete syntax (visual syntax), complemented by a precise semantic mapping. Regarding the proposed method, it includes a set of steps for identification and analysis of input data, graphical requirements and interdependencies modeling. RIMON offers features such as support for modeling functional and nonfunctional requirements, entities, attributes, preconditions, postconditions and conflict identification. As a notable characteristic, the modeling of preconditions allows the representation of constraints related to non-functional requirements by means of attributes containing logical-mathematical conditions. At last, this work presents three modeling experiments using RIMON, including system requirements (extracted from the literature) and software requirements (real project) environments, designed to demonstrate and verify the capabilities of the language.
The information systems (IS) discipline is in an ongoing crisis because of several reasons. Learning institutions do not have a well-defined curriculum on what should be taught in the IS discipline. Recently, there are many organizations and researchers who have come up with different BoKs in the IS discipline as discussed in this article. Additionally, IS discipline does not have a universal body of knowledge like in other fields such as electrical engineering which makes it even more challenging to align the existing industry knowledge and academic curriculum. Therefore, there is a need to develop a unified knowledge framework in the IS discipline which offers a single source of reference in both professional sector and development of academic curriculum. The major challenge in the developing of a unified knowledge framework in the IS discipline is that it is changing and evolving rapidly.
The cyber world is an ever-changing world, cyber security is most importance and touches the lives of everyone on the cyber world including: researchers, students, businesses, academia, and novice user. The paper suggests a body of knowledge that incorporates the view of academia as well as practitioners. This research attempts to put basic step and a framework for cyber security body of knowledge and to allow practitioners and academicians to face the problem of lack of standardization. Furthermore, the paper attempts to bridge the gap between the different audiences. The gap is so broad that the term of cyber security is not agreed upon even in spelling. The suggested body of knowledge may not be perfect yet it is a step forward.
Bodies of Knowledge (BOK) contains the relevant knowledge for a discipline. BOK must embody the consensus reached by the community for which this BOK will be of application. This consensus is a prerequisite for the adoption of the BOK by the community. In this paper, we utilize a combinations of Software Engineering Body of Knowledge (SWEBOK), models representation, and design science methodology in order to describe the software engineering knowledge context (SEC). SWEBOK serves as backbone taxonomy, while models representation provides a context of representation. In the process of develop of this paper science design methodology was used to provide fundamental knowledge in software engineering (SE).
Several similar but different disciplines have evolved in the arena of requirements engineering and business analysis, including business analysis, BPM (Business Process Management), and business architecture. Yet, they are forming bodies of knowledges in each discipline. Each discipline has its raison d’etre. However, such diversity of the bodies of knowledge causes a confusion. This article is intended to review the bodies of knowledge, and proposes a unified knowledge framework of the bodies of knowledge across the disciplines.
The conference is part of The Fourth World Congress on Computing, Engineering and Technology (WCET) held at Asia Pacific University of Technology and Innovation (APU), Kuala Lumpur, Malaysia during the period of September 8-10, 2015
We introduce a whole view of current status of requirements engineering based on REBOK (Requirements Engineering Body Of Knowledge) and its practical use with case studies.
We introduce a whole view of current status of requirements engineering based on REBOK (Requirements Engineering Body Of Knowledge) and its practical use with case studies.
We introduce a whole view of current status of requirements engineering based on REBOK (Requirements Engineering Body Of Knowledge) and its practical use with case studies.
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 learn and apply requirements engineering. As a guideline for practitioners to learn and apply requirements engineering, we developed REBOK (Requirements Engineering Body Of Knowledge). In the development, we found there is no common model of BOKs in software engineering. This article proposes the model and architecture of the body of knowledge of REBOK and its proof of the concept.
We initiate the discussions on the REBOK (Requirements Engineering Body of Knowledge) in requirements engineering community.
Requirements bibliography
- Al Davis
Al Davis. Requirements bibliography, 1996-2010. accessible online at
http://www.reqbib.com/.
REedu: science-based education, relevant for practice
- Birgit Penzenstadler
- Daniel Mendez
- Gerd Beneken
- Ulrike Hammerschall
Birgit Penzenstadler, Daniel Mendez, Gerd Beneken, and Ulrike Hammerschall. REedu: science-based education, relevant for practice, 2013.
http://www.requirementsengineering.org/.
Syllabus: IREB Certified Professional for Requirements Engineering (CPRE)-Foundation Level
International Requirements Engineering Board (IREB). Syllabus: IREB
Certified Professional for Requirements Engineering (CPRE)-Foundation Level. IREB e.V., 2009.
Software Engineering Body of Knowledge (SWEBOK)
IEEE Computer Society. Software Engineering Body of Knowledge
(SWEBOK). Angela Burgess, EUA, 2004.