Software Engineering Body of Knowledge (v3) (2014) (811503), страница 84
Текст из файла (страница 84)
These commonthemes are measurement, quality (in general), and security.i)The breakdown of topics should be at mosttwo or three levels deep. Even though noupper or lower limit is imposed on the number of topics within each KA, a reasonableand manageable number of topics is expectedto be included in each KA. Emphasis shouldalso be put on the selection of the topicsthemselves rather than on their organizationin an appropriate hierarchy.j)Topic names must be significant enoughto be meaningful even when cited outside theSWEBOK Guide.k)The description of a KA will include a chart(in tree form) describing the knowledgebreakdown.CRITERIA AND REQUIREMENTS FORDESCRIBING TOPICSTopics need only be sufficiently described so thereader can select the appropriate reference material according to his/her needs.
Topic descriptions must not be prescriptive.CRITERIA AND REQUIREMENTS FORREFERENCE MATERIALa)KA Editors are instructed to use the references (to the level of section number) allocated to their KA by the Consolidated Reference List as their Recommended References.b)There are three categories of referencematerial:»» Recommended References. The set ofRecommended References (to the levelof section number) is collectively knownas the Consolidated Reference List.»» Further Readings.»» Additional references cited in the KADescription (for example, the sourceof a quotation or reference material insupport of a rationale behind a particularargument).Appendix A A-3c)The SWEBOK Guide is intended by definition to be selective in its choice of topicsand associated reference material.
The list ofreference material should be clearly viewedas an “informed and reasonable selection”rather than as a definitive list.d)Reference material can be book chapters,refereed journal papers, refereed conference papers, refereed technical or industrialreports, or any other type of recognized artifact. References to another KA, subarea, ortopic are also permitted.e)Reference material must be generally available and must not be confidential in nature.f)Reference material must be in English.g)Criteria and requirements for recommendedreference material or Consolidated Reference List:»» Collectively the list of RecommendedReferences should bei. complete: covering the entirescope of the SWEBOK Guideii.
sufficient: providing enoughinformation to describe “generally accepted” knowledgeiii. consistent: not providing contradictory knowledge nor conflicting practicesiv. credible: recognized as providingexpert treatmentv. current: treating the subject ina manner that is commensuratewith currently generally acceptedknowledgevi. succinct: as short as possible(both in number of referenceitems and in total page count)without failing other objectives.»» Recommended reference material mustbe identified for each topic. Each recommended reference item may of coursecover multiple topics.
Exceptionally, atopic may be self-descriptive and not citea reference material item (for example, atopic that is a definition or a topic forwhich the description itself without anycited reference material is sufficient forthe objectives of the SWEBOK Guide).»» Each reference to the recommendedreference material should be as preciseas possible by identifying what specificchapter or section is relevant.»» A matrix of reference material (to thelevel of section number) versus topicsmust be provided.»» A reasonable amount of recommendedreference material must be identifiedfor each KA. The following guidelinesshould be used in determining howmuch is reasonable:i.
If the recommended referencematerial were written in a coherent manner that followed the proposed breakdown of topics and ina uniform style (for example, in anew book based on the proposedKA description), an average target across all KAs for the numberof pages would be 750. However,this target may not be attainablewhen selecting existing referencematerial due to differences instyle and overlap and redundancybetween the selected referencematerials.ii. In other words, the target for thenumber of pages for the entirecollection of recommended references of the SWEBOK Guide isin the range of 10,000 to 15,000pages.iii.
Another way of viewing this isthat the amount of recommendedreference material would bereasonable if it consisted of thestudy material on this KA for asoftware engineering licensingexam that a graduate would passafter completing four years ofwork experience.h)Additional reference material can beincluded by the KA Editor in a “FurtherReadings” list:A-4 SWEBOK® Guide V3.0»» These further readings must be related tothe topics in the breakdown rather than,for example, to more advanced topics.»» The list must be annotated (within 1paragraph per reference) as to why thisreference material was included in thelist of further readings. Further readingscould include: new versions of an existing reference already included in therecommended references, alternativeviewpoints on a KA, or a seminal treatment of a KA.»» A general guideline to be followed is 10or fewer further readings per KA.»» There is no matrix of the referencematerials listed in further readings andthe breakdown of topics.i)Criteria and requirements regarding additional references cited in the KA Description:»» The SWEBOK Guide is not a researchdocument and its readership will be varied.
Therefore, a delicate balance mustbe maintained between ensuring a highlevel of readability within the documentwhile maintaining its technical excellence. Additional reference materialshould therefore only be brought in bythe KA Editor if it is necessary to thediscussion. Examples are to identify thesource of a quotation or to cite referenceitem in support of a rationale behind aparticular and important argument.COMMON STRUCTUREKA descriptions should use the following structure:• Acronyms• Introduction• Breakdown of Topics of the KA (including afigure describing the breakdown)• Matrix of Topics vs. Reference Material• List of Further Readings• ReferencesWHAT DO WE MEAN BY “GENERALLYRECOGNIZED KNOWLEDGE”?The Software Engineering Body of Knowledgeis an all-inclusive term that describes the sumof knowledge within the profession of softwareengineering.
However, the SWEBOK Guide seeksto identify and describe that subset of the bodyof knowledge that is generally recognized or, inother words, the core body of knowledge. To better illustrate what “generally recognized” knowledge is relative to other types of knowledge,Figure A.1 proposes a three-category schema forclassifying knowledge.The Project Management Institute in its Guideto the Project Management Body of Knowledgedefines “generally recognized” knowledge forproject management as being:that subset of the project managementbody of knowledge generally recognizedas good practice.
“Generally recognized”means the knowledge and practicesdescribed are applicable to most projectsmost of the time, and there is consensusabout their value and usefulness. “Goodpractice” means there is general agreementthat the application of these skills, tools,and techniques can enhance the chancesof success over a wide range of projects.“Good practice” does not mean that theknowledge described should always beapplied uniformly to all projects; the organization and/or project management teamis responsible for determining what isappropriate for any given project. [1]“Generally accepted” knowledge could also beviewed as knowledge to be included in the studymaterial of a software engineering licensing exam(in the USA) that a graduate would take aftercompleting four years of work experience.
Thesetwo definitions should be seen as complementary.KA Editors are also expected to be somewhatforward looking in their interpretation by taking into consideration not only what is “generally recognized” today and but what they expectwill be “generally recognized” in a 3- to 5-yeartimeframe.SpecializedPractices Used Only forCertain Types of SoftwareAppendix A A-5Generally RecognizedEstablished traditional practices recommended by manyorganizationsAdvanced and ResearchInnovative practices testedand used only by some organizations and concepts stillbeing developed and tested inresearch organizationsFigure A.1.
Categories of KnowledgeLENGTH OF KA DESCRIPTIONKA Descriptions are to be roughly 10 to 20 pagesusing the formatting template for papers published in conference proceedings of the IEEEComputer Society. This includes text, references,appendices, tables, etc. This, of course, does notinclude the reference materials themselves.IMPORTANT RELATED DOCUMENTS1. Graduate Software Engineering 2009(GSwE2009): Curriculum Guidelines forGraduate Degree Programs in SoftwareEngineering, 2009; www.gswe2009.org.
[2]This document “provides guidelines and recommendations” for defining the curricula of aprofessional master’s level program in softwareengineering. The SWEBOK Guide is identifiedas a “primary reference” in developing the bodyof knowledge underlying these guidelines. Thisdocument has been officially endorsed by theIEEE Computer Society and sponsored by theAssociation for Computing Machinery.2. IEEE Std. 12207-2008 (a.k.a.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
