Chapter 7: Software Engineering Management - Revision history

Daniel Robbins at 16:17, 25 August 2015

2015-08-25T16:17:29Z

Daniel Robbins at 16:14, 25 August 2015

2015-08-25T16:14:58Z

Show changes

Daniel Robbins: /* Software Engineering Management Tools */

2015-08-25T16:06:48Z

‎Software Engineering Management Tools

Daniel Robbins: /* Software Engineering Management Tools */

2015-08-25T15:59:04Z

‎Software Engineering Management Tools

Daniel Robbins: /* Software Engineering Management Tools */

2015-08-25T15:58:33Z

‎Software Engineering Management Tools

Daniel Robbins: /* Software Engineering Management Tools */

2015-08-25T15:52:45Z

‎Software Engineering Management Tools

Daniel Robbins: /* Software Engineering Measurement */

2015-08-25T15:51:56Z

‎Software Engineering Measurement

Daniel Robbins: /* Closure */

2015-08-25T15:45:12Z

‎Closure

Daniel Robbins: /* Review and Evaluation */

2015-08-25T15:44:40Z

‎Review and Evaluation

Daniel Robbins: /* Software Project Enactment */

2015-08-25T15:43:57Z

‎Software Project Enactment

@@ Line 242: / Line 242: @@
 This leads to the determination of project scope in
 order to meet objectives and satisfy constraints.
 === Feasibility Analysis ===

@@ Line 851: / Line 851: @@
 employees.
 {{EndSection|title=References|body=
 {{reference

@@ Line 920: / Line 920: @@
 |part=
 |link=http://resources.sei.cmu.edu/library/asset-view.cfm?assetID=9661
-}}}}
+}}{{ReferenceList}}}}

← Older revision		Revision as of 15:58, 25 August 2015
Line 850:		Line 850:
	developed by project team members or organizational		developed by project team members or organizational
	employees.		employees.
		+
		+	{{EndSection\|title=References\|body=
		+	{{reference
		+	\|number=1
		+	\|author=
		+	\|article=
		+	\|publication=ISO/IEC/IEEE 24765:2010 Systems and Software Engineering—Vocabulary
		+	\|edition=
		+	\|publisher=ISO/IEC/IEEE
		+	\|issue=
		+	\|date=2010
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=2
		+	\|author=
		+	\|article=
		+	\|publication=IEEE Std. 828-2012, Standard forConfiguration Management in Systems and Software Engineering
		+	\|edition=
		+	\|publisher=IEEE
		+	\|issue=
		+	\|date=2012
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=3
		+	\|author=A.M.J Hass
		+	\|article=
		+	\|publication=Configuration Management
		+	Principles and Practices
		+	\|edition=1st ed.
		+	\|publisher=Addison Wesley
		+	\|issue=
		+	\|date=2003
		+	\|part=
		+	\|link=
		+	}}
		+	{{reference
		+	\|number=5
		+	\|author=I. Sommerville
		+	\|article=
		+	\|publication=Software Engineering, 9th ed.
		+	\|edition=9th ed.
		+	\|publisher=Addison Wesley
		+	\|issue=
		+	\|date=2011
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=6
		+	\|author=S.P. Berczuk and B. Appleton
		+	\|article=
		+	\|publication=Software Configuration Management Patterns: Effective Teamwork, Practical Integration
		+	\|edition=
		+	\|publisher=Addison Wesley Professional
		+	\|issue=
		+	\|date=2003
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=7
		+	\|author=CMMI Product Team
		+	\|article=CMMI for Development, Version 1.3
		+	\|publication=
		+	\|edition=
		+	\|publisher=Software Engineering Institute
		+	\|issue=
		+	\|date=2010
		+	\|part=
		+	\|link=http://resources.sei.cmu.edu/library/asset-view.cfm?assetID=9661
		+	}}}}

← Older revision		Revision as of 15:52, 25 August 2015
Line 786:		Line 786:

	== Software Engineering Management Tools ==		== Software Engineering Management Tools ==
		+
		+	Software engineering management tools are often
		+	used to provide visibility and control of software
		+	engineering management processes. Some tools
		+	are automated while others are manually implemented.
		+	There has been a recent trend towards
		+	the use of integrated suites of software engineering
		+	tools that are used throughout a project to
		+	plan, collect and record, monitor and control, and
		+	report project and product information. Tools can
		+	be divided into the following categories:
		+
		+	Project Planning and Tracking Tools. Project
		+	planning and tracking tools can be used to estimate
		+	project effort and cost and to prepare project
		+	schedules. Some projects use automated estimation
		+	tools that accept as input the estimated size
		+	and other characteristics of a software product
		+	and produce estimates of the required total effort,
		+	schedule, and cost. Planning tools also include
		+	automated scheduling tools that analyze the tasks
		+	within 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 project
		+	milestones, regularly scheduled project status
		+	meetings, scheduled iteration cycles, product
		+	demonstrations, and/or action items.
		+
		+	Risk Management Tools. Risk management
		+	tools (see section 2.5, Risk Management) can
		+	be used to track risk identification, estimation,
		+	and monitoring. These tools include the use of
		+	approaches such as simulation or decision trees
		+	to analyze the effect of costs versus payoffs
		+	and subjective estimates of the probabilities of
		+	risk events. Monte Carlo simulation tools can
		+	be used to produce probability distributions of
		+	effort, schedule, and risk by combining multiple
		+	input probability distributions in an algorithmic
		+	manner.
		+
		+	Communications Tools. Communication tools
		+	can assist in providing timely and consistent
		+	information to relevant stakeholders involved in a
		+	project. These tools can include things like email
		+	notifications and broadcasts to team members
		+	and stakeholders. They also include communication
		+	of minutes from regularly scheduled project
		+	meetings, daily stand-up meetings, plus charts
		+	showing progress, backlogs, and maintenance
		+	request resolutions.
		+
		+	Measurement Tools. Measurement tools support
		+	activities related to the software measurement
		+	program (see topic 6, Software Engineering
		+	Measurement). There are few completely
		+	automated tools in this category. Measurement
		+	tools used to gather, analyze, and report project
		+	measurement data may be based on spreadsheets
		+	developed by project team members or organizational
		+	employees.

@@ Line 719: / Line 719: @@
 == Software Engineering Measurement ==
 === Establish and Sustain Measurement Commitment ===
 === Plan the Measurement Process ===
 === Perform the Measurement Process ===
 === Evaluate Measurement ===
 == Software Engineering Management Tools ==

@@ Line 677: / Line 677: @@
 == Closure ==
 === Determining Closure ===
 === Closure Activities ===
 == Software Engineering Measurement ==

@@ Line 626: / Line 626: @@
 == Review and Evaluation ==
 === Determining Satisfaction of Requirements ===
 === Reviewing and Evaluating Performance ===
 == Closure ==

@@ Line 489: / Line 489: @@
 == Software Project Enactment ==
 === Implementation of Plans ===
 === Software Acquisition and Supplier Contract Management ===
 === Implementation of Measurement Process ===
 === Monitor Process ===
 === Control Process ===
 === Reporting ===
 == Review and Evaluation ==