Software Engineering Body of Knowledge (v3) (2014) (811503), страница 96
Текст из файла (страница 96)
26513-2010 Standard Adoption of ISO/IEC 26513:2009Systems and Software Engineering—Requirements for Testers andReviewers of DocumentationIEEE Std. 26514-2010 Standard Adoption of ISO/IEC 26514:2008Systems and Software Engineering—Requirements for Designers andDevelopers of User DocumentationISO/IEC/IEEE 26515:2012 Systems and Software Engineering—Developing User Documentation in an Agile EnvironmentISO/IEC 29110 [several parts] Software Engineering—LifecycleProfiles for Very Small Entities (VSE)ISO/IEC/IEEE 29119 [four parts] (Draft) Software and SystemsEngineering—Software TestingISO/IEC/IEEE 29148:2011 Systems and Software Engineering—LifeCycle Processes—Requirements EngineeringISO/IEC/IEEE 42010:2011 Systems and Software Engineering—Architecture DescriptionIEEE Std. 90003:2008 Guide—Adoption of ISO/IEC 90003:2004Software Engineering—Guidelines for the Application of ISO9001:2000 to Computer SoftwareMost Relevant KASW QualitySW QualitySW QualitySW EngineeringManagementSW EngineeringManagementSW TestingSW DesignSW EngineeringModels and MethodsSW EngineeringProcessSW TestingSW RequirementsSW DesignSW QualityAPPENDIX CCONSOLIDATED REFERENCE LISTThe Consolidated Reference List identifies allrecommended reference materials (to the level ofsection number) that accompany the breakdownof topics within each knowledge area (KA).
ThisConsolidated Reference List is adopted by thesoftware engineering certification and associatedprofessional development products offered by theIEEE Computer Society. KA Editors used the references allocated to their KA by the ConsolidatedReference List as their Recommended References.Collectively this Consolidated Reference List is• Complete: Covering the entire scope of theSWEBOK Guide.• Sufficient: Providing enough information todescribe “generally accepted” knowledge.• Consistent: Not providing contradictoryknowledge nor conflicting practices.• Credible: Recognized as providing experttreatment.• Current: Treating the subject in a manner thatis commensurate with currently generallyaccepted knowledge.• Succinct: As short as possible (both in number of reference items and in total pagecount) without failing other objectives.[1*] J.H.
Allen et al., Software SecurityEngineering: A Guide for ProjectManagers, Addison-Wesley, 2008.[2*] M. Bishop, Computer Security: Art andScience, Addison-Wesley, 2002.[3*] B. Boehm and R. Turner, Balancing Agilityand Discipline: A Guide for the Perplexed,Addison-Wesley, 2003.[4*] F. Bott et al., Professional Issues inSoftware Engineering, 3rd ed., Taylor &Francis, 2000.[5*] J.G. Brookshear, Computer Science: AnOverview, 10th ed., Addison-Wesley, 2008.[6*] D. Budgen, Software Design, 2nd ed.,Addison-Wesley, 2003.[7*] E.W. Cheney and D.R.
Kincaid, NumericalMathematics and Computing, 6th ed.,Brooks/Cole, 2007.[8*] P. Clements et al., Documenting SoftwareArchitectures: Views and Beyond, 2nd ed.,Pearson Education, 2010.[9*] R.E. Fairley, Managing and LeadingSoftware Projects, Wiley-IEEE ComputerSociety Press, 2009.[10*] D. Galin, Software Quality Assurance:From Theory to Implementation, PearsonEducation Limited, 2004.[11*] E. Gamma et al., Design Patterns:Elements of Reusable Object-OrientedSoftware, 1st ed., Addison-WesleyProfessional, 1994.[12*] P. Grubb and A.A. Takang, SoftwareMaintenance: Concepts and Practice, 2nded., World Scientific Publishing, 2003.[13*] A.M.J. Hass, Configuration ManagementPrinciples and Practices, 1st ed., AddisonWesley, 2003.C-1C-2 SWEBOK® Guide V3.0[14*] E. Horowitz et al., Computer Algorithms,2nd ed., Silicon Press, 2007.[15*] IEEE CS/ACM Joint Task Force onSoftware Engineering Ethics andProfessional Practices, “SoftwareEngineering Code of Ethics andProfessional Practice (Version 5.2),” 1999;www.acm.org/serving/se/code.htm.[16*] IEEE Std.
828-2012, Standard forConfiguration Management in Systems andSoftware Engineering, IEEE, 2012.[17*] IEEE Std. 1028-2008, Software Reviewsand Audits, IEEE, 2008.[18*] ISO/IEC 14764 IEEE Std. 14764-2006,Software Engineering—Software Life CycleProcesses—Maintenance, IEEE, 2006.[19*] S.H. Kan, Metrics and Models in SoftwareQuality Engineering, 2nd ed., AddisonWesley, 2002.[20*] S. McConnell, Code Complete, 2nd ed.,Microsoft Press, 2004.[21*] J.
McGarry et al., Practical SoftwareMeasurement: Objective Informationfor Decision Makers, Addison-WesleyProfessional, 2001.[22*] S.J. Mellor and M.J. Balcer, ExecutableUML: A Foundation for Model-DrivenArchitecture, 1st ed., Addison-Wesley,2002.[23*] D.C. Montgomery and G.C. Runger,Applied Statistics and Probability forEngineers, 4th ed., Wiley, 2007.[24*] J.W. Moore, The Road Map to SoftwareEngineering: A Standards-Based Guide, 1sted., Wiley-IEEE Computer Society Press,2006.[25*] S. Naik and P. Tripathy, Software Testingand Quality Assurance: Theory andPractice, Wiley-Spektrum, 2008.[26*] J. Nielsen, Usability Engineering, 1st ed.,Morgan Kaufmann, 1993.[27*] L. Null and J.
Lobur, The Essentials ofComputer Organization and Architecture,2nd ed., Jones and Bartlett Publishers,2006.[28*] M. Page-Jones, Fundamentals of ObjectOriented Design in UML, 1st ed., AddisonWesley, 1999.[29*] K. Rosen, Discrete Mathematics and ItsApplications, 7th ed., McGraw-Hill, 2011.[30*] A. Silberschatz, P.B. Galvin, and G.Gagne, Operating System Concepts, 8thed., Wiley, 2008.[31*] H.M. Sneed, “Offering SoftwareMaintenance as an Offshore Service,” Proc.IEEE Int’l Conf.
Software Maintenance(ICSM 08), IEEE, 2008, pp. 1–5.[32*] I. Sommerville, Software Engineering, 9thed., Addison-Wesley, 2011.[33*] S. Tockey, Return on Software:Maximizing the Return on Your SoftwareInvestment, 1st ed., Addison-Wesley, 2004.[34*] G. Voland, Engineering by Design, 2nded., Prentice Hall, 2003.[35*] K.E. Wiegers, Software Requirements, 2nded., Microsoft Press, 2003.[36*] J.M. Wing, “A Specifier’s Introduction toFormal Methods,” Computer, vol. 23, no. 9,1990, pp. 8, 10–23..
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
