Software Engineering Body of Knowledge (v3) (2014) (811503), страница 85
Текст из файла (страница 85)
ISO/IEC12207:2008) Standard for Systems andSoftware Engineering—Software Life CycleProcesses, IEEE, 2008 [3].This standard is considered the key standardregarding the definition of life cycle processes andhas been adopted by the two main standardizationbodies in software engineering: ISO/IEC JTC1/SC7 and the IEEE Computer Society Softwareand Systems Engineering Standards Committees.It also has been designated as a pivotal standardby the Software and System Engineering Standards Committee (S2ESC) of the IEEE.Even though we do not intend that the Guide tothe Software Engineering Body of Knowledge befully 12207-conformant, this standard remains akey input to the SWEBOK Guide, and special carewill be taken throughout the SWEBOK Guideregarding the compatibility of the Guide with the12207 standard.3.
J.W. Moore, The Road Map to SoftwareEngineering: A Standards-Based Guide,Wiley-IEEE Computer Society Press, 2006.[4*]This book describes the scope, roles, uses, anddevelopment trends of the most widely used software engineering standards. It concentrates onimportant software engineering activities—quality and project management, system engineering, dependability, and safety. The analysis andregrouping of the standard collections exposesthe reader to key relationships between standards.Even though the SWEBOK Guide is not a software engineering standard per se, special carewill be taken throughout the document regardingthe compatibility of the Guide with the currentIEEE and ISO/IEC Systems and Software Engineering Standards Collection.4. Software Engineering 2004: CurriculumGuidelines for Undergraduate DegreePrograms in Software Engineering, IEEEComputer Society and Association forComputing Machinery, 2004; http://sites.computer.org/ccse/SE2004Volume.pdf.
[5]This document describes curriculum guidelinesfor an undergraduate degree in software engineering. The SWEBOK Guide is identified as being“one of the primary sources” in developing thebody of knowledge underlying these guidelines.5. ISO/IEC/IEEE 24765:2010 Systems andSoftware Engineering—Vocabulary, ISO/IEC/IEEE, 2010; www.computer.org/sevocab. [6]A-6 SWEBOK® Guide V3.0The hierarchy of references for terminology isMerriam Webster’s Collegiate Dictionary (11thed.) [7], IEEE/ISO/IEC 24765 [6], and new proposed definitions if required.6.
“Certification and Training for SoftwareProfessionals,” IEEE Computer Society,2013; www.computer.org/certification. [8]Information on the certification and associatedprofessional development products developedand offered by the IEEE Computer Society forprofessionals in the field of software engineering can be found on this website. The SWEBOKGuide is foundational to these products.STYLE AND TECHNICAL GUIDELINES• KA Descriptions should conform to theWord template available at www.computer.org/portal/web/cscps/formatting.• KA Descriptions are expected to follow theIEEE Computer Society Style Guide (www.computer.org/portal/web/publications/styleguide).• Files are to be submitted in Microsoft Wordformat.• All citations of reference material are to beproduced using EndNote Web as indicatedin the instructions provided to KA Editors inthis regard.OTHER DETAILED GUIDELINESWhen referencing the Guide to the SoftwareEngineering Body of Knowledge, use the title“SWEBOK Guide.”For the purpose of simplicity, avoid footnotesand try to include their content in the main text.Use explicit references to standards, as opposedto simply inserting numbers referencing items inthe bibliography.
We believe this approach allowsthe reader to be better exposed to the source andscope of a standard.The text accompanying figures and tablesshould be self-explanatory or have enough relatedtext. This would ensure that the reader knowswhat the figures and tables mean.To make sure that some information in theSWEBOK Guide does not become rapidly obsolete and due to its generic nature, please avoiddirectly naming tools and products.
Instead, tryto name their functions.EDITINGEditors of the SWEBOK Guide as well as professional copy editors will edit KA Descriptions.Editing includes copy editing (grammar, punctuation, and capitalization), style editing (conformance to the Computer Society style guide), andcontent editing (flow, meaning, clarity, directness, and organization).
The final editing willbe a collaborative process in which the Editorsof the SWEBOK Guide and the KA Editors worktogether to achieve a concise, well-worded, anduseful KA Description.RELEASE OF COPYRIGHTAll intellectual property rights associated withthe SWEBOK Guide will remain with the IEEE.KA Editors must sign a copyright release form.It is also understood that the SWEBOK Guidewill continue to be available free of charge in thepublic domain in at least one format, provided bythe IEEE Computer Society through web technology or by other means.For more information, see www.computer.org/copyright.htm.Appendix A A-7REFERENCES[1] Project Management Institute, A Guide to theProject Management Body of Knowledge(PMBOK(R) Guide), 5th ed., ProjectManagement Institute, 2013.[2] Integrated Software and SystemsEngineering Curriculum (iSSEc) Project,Graduate Software Engineering 2009(GSwE2009): Curriculum Guidelinesfor Graduate Degree Programs inSoftware Engineering, Stevens Institute ofTechnology, 2009; www.gswe2009.org.[3] IEEE Std.
12207-2008 (a.k.a. ISO/IEC12207:2008) Standard for Systems andSoftware Engineering—Software Life CycleProcesses, IEEE, 2008.[4*] J.W. Moore, The Road Map to SoftwareEngineering: A Standards-Based Guide,Wiley-IEEE Computer Society Press, 2006.[5] Joint Task Force on Computing Curricula,IEEE Computer Society and Associationfor Computing Machinery, SoftwareEngineering 2004: Curriculum Guidelinesfor Undergraduate Degree Programs inSoftware Engineering, 2004; http://sites.computer.org/ccse/SE2004Volume.pdf.[6] ISO/IEC/IEEE 24765:2010 Systems andSoftware Engineering—Vocabulary, ISO/IEC/IEEE, 2010.[7] Merriam-Webster’s Collegiate Dictionary,11th ed., 2003.[8] IEEE Computer Society, “Certification andTraining for Software Professionals,” 2013;www.computer.org/certification.APPENDIX BIEEE AND ISO/IEC STANDARDS SUPPORTINGTHE SOFTWARE ENGINEERING BODY OFKNOWLEDGE (SWEBOK)Some might say that the supply of software engineering standards far exceeds the demand.
Oneseldom listens to a briefing on the subject withoutsuffering some apparently obligatory joke thatthere are too many of them. However, the existence of standards takes a very large (possiblyinfinite) trade space of alternatives and reducesthat space to a smaller set of choices—a hugeadvantage for users. Nevertheless, it can still bedifficult to choose from dozens of alternatives, sosupplementary guidance, like this appendix, canbe helpful.
A summary list of the standards mentioned in this appendix appears at the end.To reduce tedium in reading, a few simplifications and abridgements are made in this appendix:• ISO/IEC JTC 1/SC 7 maintains nearly twohundred standards on the subject. IEEEmaintains about fifty. The two organizationsare in the tenth year of a systematic programto coordinate and integrate their collections.In general, this article will focus on the standards that are recognized by both organizations, taking this condition as evidence thatwide agreement has been obtained.
Otherstandards will be mentioned briefly.• Standards tend to have long, taxonomicaltitles. If there were a single standard forbuilding an automobile, the one for yourCamry probably would be titled somethinglike, “Vehicle, internal combustion, fourwheel, passenger, sedan.” Also, modern standards organizations provide their standardsfrom databases. Like any database, thesesometimes contain errors, particularly for thetitles.
So this article will often paraphrase theB-1title of the standard or simply use its number.In obtaining a standard of interest, the readershould rely on the number, not the title, givenin this article. For reasons of consistency, thearticle will use the IEEE’s convention for thecapitalization of titles—nouns, pronouns,adjectives, verbs, adverbs, and first and lastwords have an initial capital letter—despitethe fact that IEEE and ISO/IEC use differingconventions.• Because these standards are being continually revised to take account of new technologies and usage patterns, this article will beobsolescent before it is published.
Therefore,it will occasionally discuss standards thathave not yet been published, if they are likelyto assume significant importance.• Explicit trademarks are omitted. Suffice it tosay that IEEE places a trademark on all of itsstandards’ designations.There are some other conventions of interest:• In both IEEE and ISO/IEC, standards forsystems engineering are maintained by thesame committee as those for software engineering. Many of the standards apply to both.So, instead of making fine distinctions, thisarticle will deal with both.• On the other hand, both S2ESC and SC 7(see below for descriptions of these organizations) are responsible for standardsthat don’t qualify as “engineering.” In theUS and many other countries, the servicesof a licensed engineer are required when aproduct might affect public safety, health,B-2 SWEBOK® Guide V3.0and welfare as opposed to affecting merelythe pocketbook of the client. This appendixwill respect that distinction and ignore standards that appear to be merely economic inconsequence.• User documentation is assumed to be developed similarly to software.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
