Chapter 8: Software Engineering Process - Revision history

Daniel Robbins: /* Software Process Definition */

2015-08-25T17:14:57Z

‎Software Process Definition

Daniel Robbins at 17:14, 25 August 2015

2015-08-25T17:14:01Z

Daniel Robbins at 17:10, 25 August 2015

2015-08-25T17:10:43Z

Daniel Robbins at 16:57, 25 August 2015

2015-08-25T16:57:58Z

Daniel Robbins: /* Software Engineering Process Tools */

2015-08-25T16:50:59Z

‎Software Engineering Process Tools

Daniel Robbins: /* Software Engineering Process Tools */

2015-08-25T16:48:57Z

‎Software Engineering Process Tools

Daniel Robbins: /* Software Measurement */

2015-08-25T16:48:30Z

‎Software Measurement

Show changes

Daniel Robbins: /* Continuous and Staged Software Process Ratings */

2015-08-25T16:43:24Z

‎Continuous and Staged Software Process Ratings

Daniel Robbins: /* Continuous and Staged Software Process Ratings */

2015-08-25T16:42:40Z

‎Continuous and Staged Software Process Ratings

Daniel Robbins: /* Software Process Assessment and Improvement */

2015-08-25T16:40:47Z

‎Software Process Assessment and Improvement

Show changes

@@ Line 84: / Line 84: @@
 process, software process management, and
 software process infrastructure.
 As stated above, a software process is a set of

@@ Line 68: / Line 68: @@
 software processes.
 }}
 {{IntroSection|title=Breakdown of Topics for Software Engineering Process|body=
 As illustrated in Figure 8.1, this KA is concerned

@@ Line 77: / Line 77: @@
 == Software Process Definition ==
+{{RightSection|{{referenceLink|number=1|parts=p177}} {{referenceLink|number=2|parts=p295}} {{referenceLink|number=3|parts=p28-29, p36, c5}}
 This topic is concerned with a definition of software
 process, software process management, and
@@ Line 154: / Line 155: @@
 === Software Process Management ===
+{{RightSection|{{referenceLink|number=3|parts=s26.1}} {{referenceLink|number=4|parts=p453-454}}
 Two objectives of software process management
 are to realize the efficiency and effectiveness that
@@ Line 195: / Line 197: @@
 === Software Process Infrastructure ===
+{{RightSection|{{referenceLink|number=2|parts=p183,p186}} {{referenceLink|number=4|parts=p437-438}}
 Establishing, implementing, and managing software
 processes and software life cycle models
@@ Line 241: / Line 244: @@
 == Software Life Cycles ==
+{{RightSection|{{referenceLink|number=1|parts=c2}} {{referenceLink|number=2|parts=p190}}
 This topic addresses categories of software processes,
 software life cycle models, software
@@ Line 297: / Line 301: @@
 === Categories of Software Processes ===
+{{RightSection|{{referenceLink|number=1|parts=Preface}} {{referenceLink|number=2|parts=p294-295}} {{referenceLink|number=3|parts=c22-c24}}
 Many distinct software processes have been
 defined for use in the various parts of the software
@@ Line 333: / Line 338: @@
 === Software Life Cycle Models ===
+{{RightSection|{{referenceLink|number=1|parts=c2}} {{referenceLink|number=2|parts=s3.2}} {{referenceLink|number=3|parts=s2.1}}{{referenceLink|number=5}}
 The intangible and malleable nature of software
 permits a wide variety of software development
@@ Line 398: / Line 404: @@
 === Software Process Adaptation ===
+{{RightSection|{{referenceLink|number=1|parts=s2.7}} {{referenceLink|number=2|parts=p51}}
 Predefined SDLCs, SPLCs, and individual software
 processes often need to be adapted (or
@@ Line 419: / Line 426: @@
 === Practical Considerations ===
+{{RightSection|{{referenceLink|number=2|parts=p188-190}}
 In practice, software processes and activities are
 often interleaved, overlapped, and applied concurrently.
@@ Line 448: / Line 456: @@
 == Software Process Assessment and Improvement ==
+{{RightSection|{{referenceLink|number=2|parts=p188, p194}} {{referenceLink|number=3|parts=c26}} {{referenceLink|number=4|parts=p397, c15}}
 This topic addresses software process assessment
 models, software process assessment methods,
@@ Line 508: / Line 517: @@
 === Software Process Assessment Models ===
+{{RightSection|{{referenceLink|number=2|parts=s4.5, s4.6}} {{referenceLink|number=3|parts=s26.5}} {{referenceLink|number=4|parts=p44-48}}
 Software process assessment models typically
 include assessment criteria for software processes
@@ Line 519: / Line 529: @@
 === Software Process Assessment Methods ===
+{{RightSection|{{referenceLink|number=1|parts=p322-331}} {{referenceLink|number=3|parts=s26.3}} {{referenceLink|number=4|parts=p44-48, s16.4}}{{referenceLink|number=6}}
 A software process assessment method can be
 qualitative or quantitative. Qualitative assessments
@@ Line 567: / Line 578: @@
 value.
-=== Software Process Improvement Methods ===
+=== Software Process Improvement Models ===
+{{RightSection|{{referenceLink|number=2|parts=p187-188}} {{referenceLink|number=3|parts=s26.5}} {{referenceLink|number=4|parts=s2.7}}
 Software process improvement models emphasize
 iterative cycles of continuous improvement.
@@ Line 588: / Line 600: @@
 === Continuous and Staged Software Process Ratings ===
+{{RightSection|{{referenceLink|number=1|parts=p28-34}} {{referenceLink|number=3|parts=s26.5}} {{referenceLink|number=4|parts=p39-45}}
 Software process capability and software process
 maturity are typically rated using five or six levels
@@ Line 680: / Line 693: @@
 == Software Measurement ==
+{{RightSection|{{referenceLink|number=3|parts=s26.2}} {{referenceLink|number=4|parts=s18.1.1}}
 This topic addresses software process and product
 measurement, quality of measurement results,
@@ Line 702: / Line 716: @@
 === Software Process and Product Measurement ===
+{{RightSection|{{referenceLink|number=1|parts=s6.3, p273}} {{referenceLink|number=3|parts=s26.2, p638}}
 Software process and product measurement are
 concerned with determining the efficiency and
@@ Line 834: / Line 849: @@
 === Quality of Measurement Results ===
+{{RightSection|{{referenceLink|number=4|parts=s3.4-3.7}}
 The quality of process and product measurement
 results is primarily determined by the reliability
@@ Line 852: / Line 868: @@
 === Software Information Models ===
+{{RightSection|{{referenceLink|number=1|parts=p310-311}} {{referenceLink|number=3|parts=p712-713}} {{referenceLink|number=4|parts=s19.2}}
 Software information models allow modeling,
 analysis, and prediction of software process and
@@ Line 924: / Line 941: @@
 === Software Process Measurement Techniques ===
+{{RightSection|{{referenceLink|number=1|parts=c8}}
 Software process measurement techniques are
 used to collect process data and work product
@@ Line 940: / Line 958: @@
 ==== Quantitative Process Measurement Techniques ====
+{{RightSection|{{referenceLink|number=4|parts=s5.1, s5.7, s9.8}}
 The purpose of quantitative process measurement
 techniques is to collect, transform, and analyze
@@ Line 996: / Line 1,015: @@
 ==== Qualitative Process Measurement Techniques ====
+{{RightSection|{{referenceLink|number=1|parts=s6.4}}
 Qualitative process measurement techniques—
 including interviews, questionnaires, and expert
@@ Line 1,006: / Line 1,026: @@
 == Software Engineering Process Tools ==
+{{RightSection|{{referenceLink|number=1|parts=s8.7}}}}
 Software process tools support many of the notations
 used to define, implement, and manage

@@ Line 1,107: / Line 1,107: @@
 define the requirements and procedures for performing
 process assessments.
 }}

← Older revision		Revision as of 16:50, 25 August 2015
Line 1,057:		Line 1,057:
	are within control limits and those needing corrective		are within control limits and those needing corrective
	action.		action.
		+
		+	{{EndSection\|title=Further Readings\|body=
		+
		+	''Software Extension to the Guide to the Project
		+	Management Body of Knowledge®'' (SWX)
		+	[5].
		+
		+	SWX provides adaptations and extensions to the
		+	generic practices of project management documented
		+	in the PMBOK® Guide for managing
		+	software projects. The primary contribution of
		+	this extension to the PMBOK® Guide is description
		+	of processes that are applicable for managing
		+	adaptive life cycle software projects.
		+
		+	D. Gibson, D. Goldenson, and K. Kost,
		+	“Performance Results of CMMI-Based
		+	Process Improvement” [6].
		+
		+	This technical report summarizes publicly available
		+	empirical evidence about the performance
		+	results that can occur as a consequence of CMMIbased
		+	process improvement. The report contains
		+	a series of brief case descriptions that were created
		+	with collaboration from representatives
		+	from 10 organizations that have achieved notable
		+	quantitative performance results through their
		+	CMMI-based improvement efforts.
		+
		+	''CMMI® for Development, Version 1.3'' [7].
		+
		+	''CMMI® for Development, Version 1.3'' provides an
		+	integrated set of process guidelines for developing
		+	and improving products and services. These
		+	guidelines include best practices for developing
		+	and improving products and services to meet the
		+	needs of customers and end users.
		+
		+	''ISO/IEC 15504-1:2004 Information technology—
		+	Process assessment—Part 1:
		+	Concepts and vocabulary'' [8].
		+
		+	This standard, commonly known as SPICE
		+	(Software Process Improvement and Capability
		+	Determination), includes multiple parts. Part 1
		+	provides concepts and vocabulary for software
		+	development processes and related businessmanagement
		+	functions. Other parts of 15504
		+	define the requirements and procedures for performing
		+	process assessments.
		+	}}

← Older revision		Revision as of 16:48, 25 August 2015
Line 1,006:		Line 1,006:

	== Software Engineering Process Tools ==		== Software Engineering Process Tools ==
		+
		+	Software process tools support many of the notations
		+	used to define, implement, and manage
		+	individual software processes and software life
		+	cycle models. They include editors for notations
		+	such as data-flow diagrams, state charts, BPMN,
		+	IDEF0 diagrams, Petri nets, and UML activity
		+	diagrams. In some cases, software process tools
		+	allow different types of analyses and simulations
		+	(for example, discrete event simulation). In
		+	addition, general purpose business tools, such as
		+	a spreadsheet, may be useful.
		+
		+	Computer-Assisted Software Engineering
		+	(CASE) tools can reinforce the use of integrated
		+	processes, support the execution of process definitions,
		+	and provide guidance to humans in performing
		+	well-defined processes. Simple tools
		+	such as word processors and spreadsheets can
		+	be used to prepare textual descriptions of processes,
		+	activities, and tasks; these tools also support
		+	traceability among the inputs and outputs of
		+	multiple software processes (such as stakeholder
		+	needs analysis, software requirements specification,
		+	software architecture, and software detailed
		+	design) as well as the results of software processes
		+	such as documentation, software components,
		+	test cases, and problem reports.
		+
		+	Most of the knowledge areas in this Guide
		+	describe specialized tools that can be used to
		+	manage the processes within that KA. In particular,
		+	see the Software Configuration Management
		+	KA for a discussion of software configuration
		+	management tools that can be used to manage the
		+	construction, integration, and release processes
		+	for software products. Other tools, such as those
		+	for requirements management and testing, are
		+	described in the appropriate KAs.
		+
		+	Software process tools can support projects
		+	that involve geographically dispersed (virtual)
		+	teams. Increasingly, software process tools are
		+	available through cloud computing facilities as
		+	well as through dedicated infrastructures.
		+
		+	A project control panel or dashboard can display
		+	selected process and product attributes for
		+	software projects and indicate measurements that
		+	are within control limits and those needing corrective
		+	action.

@@ Line 606: / Line 606: @@
 {| class="wikitable"
 |-
-! colspan="3"
+!colspan="3"|Table 8.1. Software Process Rating Levels
 | Table 8.1. Software Process Rating Levels
 |-
 | '''Level'''

@@ Line 605: / Line 605: @@
 {| class="wikitable"
-|- colspan="3"
+|-
 | Table 8.1. Software Process Rating Levels
 |-
@@ Line 619: / Line 620: @@
 | Performed
 | Initial
 |}