Knowledge description model for bodies of knowledge in software engineering context

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)

Estrategias didácticas y plan de actividades para el diseño curricular del curso básico de la enseñanza de la "ingeniería del software" a partir del proyecto Swebok

Las instituciones de educación superior han tenido que evolucionar sus metodologías de enseñanza de la Ingeniería del Software, para gestar profesionales eficientes en el desarrollo de aplicativos informáticos. Este artículo pretende presentar una nueva didáctica y un diseño curricular de un curso de "Ingeniería del Software Básico", basado en el modelo SWEBOK de la IEEE (Guide to the software engineering body of knowledge. Swebok) y adaptado al modelo por competencias presentes en el Modelo Pedagógico del INSTITUTO TECNOLÓGICO METROPOLITANO, como resultado del proyecto de investigación HICAP-IOI del ITM. Higher education institutions have taken up new software engineering teaching methodologies in order to prepare professionals who are efficient in the development of informatics applications. This article aims at showing a new didactic, and a syllabus design for a course of "Basic Software Engineering", based on the SWEBOK model of IEEE (GUIDE TO THE SOFTWARE ENGINEERING BODY OF KNOWLEDGE SWEBOK), whic his adapted to the model by competences which is applied in the ITM's Pedagogical Model as a result of the HICAP-IOI research project at ITM.

Estrategias didácticas y plan de actividades para el diseño curricular del curso básico de la enseñanza de la "ingeniería del software" a partir del proyecto Swebok

Higher education institutions have taken up new software engineering teaching methodologies in order to prepare professionals who are efficient in the development of informatics applications. This article aims at showing a new didactic, and a syllabus design for a course of "Basic Software Engineering", based on the SWEBOK model of IEEE (GUIDE TO THE SOFTWARE ENGINEERING BODY OF KNOWLEDGE SWEBOK), whic his adapted to the model by competences which is applied in the ITM's Pedagogical Model as a result of the HICAP-IOI research project at ITM. Las instituciones de educación superior han tenido que evolucionar sus metodologías de enseñanza de la Ingeniería del Software, para gestar profesionales eficientes en el desarrollo de aplicativos informáticos. Este artículo pretende presentar una nueva didáctica y un diseño curricular de un curso de "Ingeniería del Software Básico", basado en el modelo SWEBOK de la IEEE (Guide to the software engineering body of knowledge. Swebok) y adaptado al modelo por competencias presentes en el Modelo Pedagógico del INSTITUTO TECNOLÓGICO METROPOLITANO, como resultado del proyecto de investigación HICAP-IOI del ITM.

Measuring the SWEBOK Coverage: An Approach and a Tool

The definition of a software engineering body of knowledge (SWEBOK) is an important milestone in the history of the software engineering discipline. One of the main questions that might be asked in front of such knowledge definition is: to which extent does my knowledge cover this body of knowledge ? In a more general perspective we can be interested in measuring the coverage of any entity w.r.t. the SWEBOK. It could be a book, a paper, a course, . . . . In this paper, we present the method we defined to answer such question, the tool we developed and the experiments we did with the lessons learned

Analysis of software engineering principles from an engineering perspective

Software engineering has recently emerged as a new engineering field in a continuing evolution. Software engineering is a discipline whose aim is the production of high quality software, but lacks maturity compared to other traditional engineering fields. Traditional engineering fields have their own principles originating from physics, chemistry and mathematics. However, since the software engineering discipline is not based on natural laws, establishing a set of principles is more challenging. This research on the set of candidate fundamental principles will contribute to a better understanding and possibly, to the teaching of the principles of software engineering and it will help improve the content of the software engineering body of knowledge (SWEBOK) Guide from an engineering perspective. This research work investigated the issue of software engineering as an engineering discipline using Vincenti categories of engineering knowledge; identified engineering fundamental principles from a set of candidates; and finally investigated the lack of explicit and systematic descriptions of these principles and their application, as in the SWEBOK Guide. The two main research objectives are the identification of the fundamental principles of software engineering from the 34 candidates principles; and the description of operational guidelines for these principles, based on the content of the SWEBOK Guide. To achieve these objectives, the following research methodology was used. The main phases of this research methodology are: the analysis, from an engineering perspective, of software engineering and the set of 34 ftandamental principles candidates; the identification of the software engineering principles in the content of the SWEBOK Guide - ISO TR 19759; the description of the operational guidelines on the basis of the content of the SWEBOK Guide and aligned with the IEEE standard 1362-1998 Concept of Operations (ConOps) Document. The main outcome of this research study is the identification of a set of nine software engineering fundamental principles and the description of operational guidelines

Guide to the software engineering body of knowledge

0 7 4 0 -7 4 5 9 / 9 9 / $ 1 0 . 0 0 © 1 9 9 9 I E E E N o v e m b e r / D e c e m b e r 1 9 9 9 I E E E S o f t w a r e 3 5 he IEEE Computer Society and the Association for Computing Machinery are working on a joint project to develop a guide to the Software Engineering Body of Knowledge (SWEBOK). Articulating a body of knowledge is an essential step toward developing a profession because it represents a broad consensus regarding the contents of the discipline. Without such a consensus, there is no way to validate a licensing examination, set a curriculum to prepare individuals for the examination, or formulate criteria for accrediting the curriculum. The SWEBOK project (http://www.swebok.org) is now nearing the end of the second of its three phases. Here we summarize the results to date and provide an overview of the project and its status. The Guide to the Software Engineering Body of Knowledge Repor ting on the SWEBOK project, the authors-who represent the project's editorial team-discuss the three-phase plan to characterize a body of knowledge, a vital step toward developing soft ware engineering as a profession.

Evaluation of occupational and professional profiles in Ecuadorian context based on guide of Knowledge SWEBOK and ontological model

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 obtain the necessary information to establish the relationship, and the criteria to evaluate the profiles based on the guide of knowledge

Secure software engineering: A new teaching perspective based on the SWEBOK

Lack of a suitable set of controls during the development life cycle of software will lead to mistakes in the requirements, design, or code of software and, therefore, result in significant security vulnerabilities. This paper proposes a software engineering course from the security perspective, which can be taught at both the undergraduate and graduate levels. It will prepare students to successfully cope with the technical challenges as well as the non technical issues associated with the software development process, while integrating security into each phase of the process. The course materials are derived from the Guide to the Software Engineering Body of Knowledge (SWEBOK) published by the IEEE Computer Society with the support of a consortium of industrial sponsors

Evaluation of occupational and professional profiles in Ecuadorian context based on guide of Knowledge SWEBOK and ontological model

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 obtain the necessary information to establish the relationship, and the criteria to evaluate the profiles based on the guide of knowledge