國立虎尾科技大學 |

Software Development Activity Cycles = Collaborative Development, Continuous Testing and User Acceptance /

Record Type:	Language materials, printed : Monograph/item
Title/Author:	Software Development Activity Cycles/ by Robert F. Rose.
Reminder of title:	Collaborative Development, Continuous Testing and User Acceptance /
Author:	Rose, Robert F.
Description:	XXXII, 279 p. 55 illus.online resource. :
Contained By:	Springer Nature eBook
Subject:	Electronic data processing—Management. -
Online resource:	https://doi.org/10.1007/978-1-4842-8239-7
ISBN:	9781484282397

Software Development Activity Cycles = Collaborative Development, Continuous Testing and User Acceptance /
Rose, Robert F.

Software Development Activity CyclesCollaborative Development, Continuous Testing and User Acceptance /[electronic resource] :by Robert F. Rose. - 1st ed. 2022. - XXXII, 279 p. 55 illus.online resource.

Chapter 1: The DPAC Model -- Chapter 2: Why Include Support in a Development Model? -- Chapter 3: Inception -- Chapter 4: Elaboration -- Chapter 5: Construction -- Chapter 6: Assembly -- Chapter 7: Evolution -- Chapter 8: Risk Management -- Chapter 9: Engineering SOftware Quality -- Chapter 10: Final Remarks -- Appendix.

The principal benefit this book is to provide a holistic and comprehensible view of the entire software development process, including ongoing evolution and support. It treats development as a collaborative effort with triad communication between a tester, a programmer, and a representative from the user community or a Subject Matter Expert (SME). Progress is measured by user acceptance in each cycle before proceeding to the next step of an activity. There is no test stage in the DPAC model: continuous testing is represented in the backswing (Check Phase) of each activity cycle. This approach posits that there exists some “happy path” that represents the intent of the project as declared by the objectives of a Vision Statement, and that this path can be revealed by an iterative and incremental process of “freeing the statue from the stone.” As the image of this path unfolds, more waste is removed while retaining conceptual integrity. The example presented herein walks the reader through an application of the model. This book should be of great interest to Product and Project Managers new to the concept of a lean agile development effort, and all practitioners of an agile methodology or those considering or just beginning an agile journey.

ISBN: 9781484282397

Standard No.: 10.1007/978-1-4842-8239-7doiSubjects--Topical Terms:

1366260
Electronic data processing—Management.

LC Class. No.: QA76.9.M3

Dewey Class. No.: 004.068

Software Development Activity Cycles = Collaborative Development, Continuous Testing and User Acceptance /
LDR:02931nam a22003855i 4500 001 1088725
003 DE-He213
005 20220720143250.0
007 cr nn 008mamaa
008 221228s2022 xxu| s |||| 0|eng d
020 $a 9781484282397 $9 978-1-4842-8239-7
024 7 $a 10.1007/978-1-4842-8239-7 $2 doi
035 $a 978-1-4842-8239-7
050 4 $a QA76.9.M3
072 7 $a KJQ $2 bicssc
072 7 $a BUS083000 $2 bisacsh
072 7 $a KJQ $2 thema
082 0 4 $a 004.068 $2 23
100 1 $a Rose, Robert F. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1395918
245 1 0 $a Software Development Activity Cycles $h [electronic resource] : $b Collaborative Development, Continuous Testing and User Acceptance / $c by Robert F. Rose.
250 $a 1st ed. 2022.
264 1 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2022.
300 $a XXXII, 279 p. 55 illus. $b online resource.
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
347 $a text file $b PDF $2 rda
505 0 $a Chapter 1: The DPAC Model -- Chapter 2: Why Include Support in a Development Model? -- Chapter 3: Inception -- Chapter 4: Elaboration -- Chapter 5: Construction -- Chapter 6: Assembly -- Chapter 7: Evolution -- Chapter 8: Risk Management -- Chapter 9: Engineering SOftware Quality -- Chapter 10: Final Remarks -- Appendix.
520 $a The principal benefit this book is to provide a holistic and comprehensible view of the entire software development process, including ongoing evolution and support. It treats development as a collaborative effort with triad communication between a tester, a programmer, and a representative from the user community or a Subject Matter Expert (SME). Progress is measured by user acceptance in each cycle before proceeding to the next step of an activity. There is no test stage in the DPAC model: continuous testing is represented in the backswing (Check Phase) of each activity cycle. This approach posits that there exists some “happy path” that represents the intent of the project as declared by the objectives of a Vision Statement, and that this path can be revealed by an iterative and incremental process of “freeing the statue from the stone.” As the image of this path unfolds, more waste is removed while retaining conceptual integrity. The example presented herein walks the reader through an application of the model. This book should be of great interest to Product and Project Managers new to the concept of a lean agile development effort, and all practitioners of an agile methodology or those considering or just beginning an agile journey.
650 0 $a Electronic data processing—Management. $3 1366260
650 0 $a Software engineering—Management. $3 1366259
650 0 $a Information technology—Management. $3 1365950
650 0 $a Business information services. $3 654161
650 1 4 $a IT Operations. $3 1366262
650 2 4 $a Software Management. $3 1069200
650 2 4 $a Business Process Management. $3 1066351
650 2 4 $a Business Information Systems. $3 669204
650 2 4 $a IT in Business. $3 1064965
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer Nature eBook
776 0 8 $i Printed edition: $z 9781484282380
776 0 8 $i Printed edition: $z 9781484282403
856 4 0 $u https://doi.org/10.1007/978-1-4842-8239-7
912 $a ZDB-2-CWD
912 $a ZDB-2-SXPC
950 $a Professional and Applied Computing (SpringerNature-12059)
950 $a Professional and Applied Computing (R0) (SpringerNature-43716)