Software Engineering Body of Knowledge (v3) (2014) (811503), страница 38
Текст из файла (страница 38)
Data providersand measurement users should participatein reviewing the data to ensure that they aremeaningful and accurate and that they canresult in reasonable actions.• Communicate results. Information productsshould be documented and communicated tousers and stakeholders.6.4. Evaluate Measurement[7*, c1, c2]• Evaluate information products and the measurement process against specified evaluation criteria and determine strengths andweaknesses of the information products orprocess, respectively. Evaluation may beperformed by an internal process or an external audit; it should include feedback frommeasurement users. Lessons learned shouldbe recorded in an appropriate database.• Identify potential improvements.
Suchimprovements may be changes in the formatof indicators, changes in units measured, orreclassification of measurement categories.The costs and benefits of potential improvements should be determined and appropriateimprovement actions should be reported.• Communicate proposed improvements to themeasurement process owner and stakeholders for review and approval. Also, lack ofpotential improvements should be communicated if the analysis fails to identify anyimprovements.7. Software Engineering Management Tools[3*, c5, c6, c7]Software engineering management tools are oftenused to provide visibility and control of softwareengineering management processes.
Some toolsare automated while others are manually implemented. There has been a recent trend towardsthe use of integrated suites of software engineering tools that are used throughout a project toplan, collect and record, monitor and control, and7-12 SWEBOK® Guide V3.0report project and product information.
Tools canbe divided into the following categories:Project Planning and Tracking Tools. Projectplanning and tracking tools can be used to estimate project effort and cost and to prepare projectschedules. Some projects use automated estimation tools that accept as input the estimated sizeand other characteristics of a software productand produce estimates of the required total effort,schedule, and cost.
Planning tools also includeautomated scheduling tools that analyze the taskswithin a work breakdown structure, their estimated durations, their precedence relationships,and the resources assigned to each task to produce a schedule in the form of a Gantt chart.Tracking tools can be used to track projectmilestones, regularly scheduled project statusmeetings, scheduled iteration cycles, productdemonstrations, and/or action items.Risk Management Tools. Risk managementtools (see section 2.5, Risk Management) canbe used to track risk identification, estimation,and monitoring. These tools include the use ofapproaches such as simulation or decision treesto analyze the effect of costs versus payoffsand subjective estimates of the probabilities ofrisk events.
Monte Carlo simulation tools canbe used to produce probability distributions ofeffort, schedule, and risk by combining multipleinput probability distributions in an algorithmicmanner.Communications Tools. Communication toolscan assist in providing timely and consistentinformation to relevant stakeholders involved in aproject. These tools can include things like emailnotifications and broadcasts to team membersand stakeholders. They also include communication of minutes from regularly scheduled projectmeetings, daily stand-up meetings, plus chartsshowing progress, backlogs, and maintenancerequest resolutions.Measurement Tools.
Measurement tools support activities related to the software measurement program (see topic 6, Software Engineering Measurement). There are few completelyautomated tools in this category. Measurementtools used to gather, analyze, and report projectmeasurement data may be based on spreadsheetsdeveloped by project team members or organizational employees.Software Engineering Management 7-131. Initiation and ScopeDefinition1.1. Determination andNegotiation of Requirements1.2. Feasibility Analysis1.3. Process for the Review andRevision of Requirements2. Software Project Planning2.1. Process Planning2.2. Determine Deliverables2.3. Effort, Schedule, and CostEstimation2.4. Resource Allocation2.5. Risk Management2.6. Quality Management2.7. Plan Management3. Software Project Enactment3.1. Implementation of Plans3.2. Software Acquisition andSupplier Contract Management3.3. Implementation ofMeasurement Process3.4. Monitor Process3.5. Control Process3.6. Reporting4. Review and Evaluation4.1. Determining Satisfaction ofRequirements4.2. Reviewing and EvaluatingPerformancec3c4c3c2, c3, c4, c5c4, c5, c6c1c6c5, c10, c11c9c4c4c5c24c2c3, c4c7c8c7, c8c11c8, c10McGarry et al.
2001[7*]Boehm and Turner 2003[5*]Sommerville 2011[4*]Fairley 2009[3*]MATRIX OF TOPICS VS. REFERENCE MATERIALMcGarry et al. 2001[7*]Boehm and Turner 2003[5*]Sommerville 2011[4*]Fairley 2009[3*]7-14 SWEBOK® Guide V3.05. Closure5.1. Determining Closure5.2. Closure Activities6. Software EngineeringMeasurement6.1. Establish and SustainMeasurement Commitment6.2. Plan the MeasurementProcess6.3. Perform the MeasurementProcess6.4. Evaluate Measurement7. Software EngineeringManagement Toolsc1, c2c1, c2c1, c2c1, c2c5, c6, c7Software Engineering Management 7-15FURTHER READINGSREFERENCESA Guide to the Project Management Body ofKnowledge (PMBOK® Guide) [1].[1] Project Management Institute, A Guide to theProject Management Body of Knowledge(PMBOK(R) Guide), 5th ed., ProjectManagement Institute, 2013.The PMBOK® Guide provides guidelines formanaging individual projects and defines projectmanagement-related concepts.
It also describesthe project management life cycle and its relatedprocesses, as well as the project life cycle. It isa globally recognized guide for the project management profession.Software Extension to the Guide to theProject Management Body of Knowledge(PMBOK® Guide) [2].SWX provides adaptations and extensions tothe generic practices of project managementdocumented in the PMBOK® Guide for managing software projects. The primary contributionof this extension to the PMBOK® Guide is adescription of processes that are applicable formanaging adaptive life cycle software projects.IEEE Standard Adoption of ISO/IEC 15939 [6].This international standard identifies a processthat supports defining a suitable set of measuresto address specific information needs.
It identifies the activities and tasks that are necessary tosuccessfully identify, define, select, apply, andimprove measurement within an overall projector organizational measurement structure.J. McDonald, Managing the Development ofSoftware Intensive Systems, Wiley, 2010 [8].This textbook provides an introduction to projectmanagement for beginning software and hardware developers plus unique advanced materialfor experienced project managers. Case studiesare included for planning and managing verification and validation for large software projects,complex software, and hardware systems, as wellas inspection results and testing metrics to monitor project status.[2] Project Management Institute and IEEEComputer Society, Software Extension tothe PMBOK® Guide Fifth Edition, ProjectManagement Institute, 2013.[3*] R.E.
Fairley, Managing and LeadingSoftware Projects, Wiley-IEEE ComputerSociety Press, 2009.[4*] I. Sommerville, Software Engineering, 9thed., Addison-Wesley, 2011.[5*] B. Boehm and R. Turner, Balancing Agilityand Discipline: A Guide for the Perplexed,Addison-Wesley, 2003.[6] IEEE Std. 15939-2008 Standard Adoption ofISO/IEC 15939:2007 Systems and SoftwareEngineering—Measurement Process,IEEE, 2008.[7*] J.
McGarry et al., Practical SoftwareMeasurement: Objective Informationfor Decision Makers, Addison-WesleyProfessional, 2001.[8] J. McDonald, Managing the Development ofSoftware Intensive Systems, John Wiley andSons, Inc., 2010.CHAPTER 8SOFTWARE ENGINEERING PROCESSACRONYMSBPMNCASECMCMMIGQMIDEF0LOEODCSDLCSPLCUMLprocess” will be referred to as “software process”in this KA.
In addition, please note that “softwareprocess” denotes work activities—not the execution process for implemented software.Software processes are specified for a numberof reasons: to facilitate human understanding,communication, and coordination; to aid management of software projects; to measure andimprove the quality of software products in anefficient manner; to support process improvement; and to provide a basis for automated support of process execution.SWEBOK KAs closely related to this Software Engineering Process KA include SoftwareEngineering Management, Software Engineering Models and Methods, and Software Quality;the Measurement and Root Cause Analysis topicfound in the Engineering Foundations KA is alsoclosely related. Software Engineering Management is concerned with tailoring, adapting, andimplementing software processes for a specificsoftware project (see Process Planning in theSoftware Engineering Management KA).
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
