國立高雄大學圖資館 |

Language: English

Back

Software development activity cyclescollaborative development, continuous testing and user acceptance /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Software development activity cyclesby Robert F. Rose.
Reminder of title:	collaborative development, continuous testing and user acceptance /
Author:	Rose, Robert F.
Published:	Berkeley, CA :Apress :2022.
Description:	xxxii, 279 p. :ill., digital ;24 cm.
Contained By:	Springer Nature eBook
Subject:	Application softwareDevelopment.
Online resource:	https://doi.org/10.1007/978-1-4842-8239-7
ISBN:	9781484282397$q(electronic bk.)

Software development activity cyclescollaborative 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. - Berkeley, CA :Apress :2022. - xxxii, 279 p. :ill., digital ;24 cm.

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$q(electronic bk.)

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

189413
Application software
--Development.

LC Class. No.: QA76.76.A65 / R67 2022

Dewey Class. No.: 005.1

Software development activity cyclescollaborative development, continuous testing and user acceptance /
LDR:02637nmm a2200325 a 4500 001 627945
003 DE-He213
005 20220720143250.0
006 m d
007 cr nn 008maaau
008 230201s2022 cau s 0 eng d
020 $a 9781484282397$q(electronic bk.)
020 $a 9781484282380$q(paper)
024 7 $a 10.1007/978-1-4842-8239-7 $2 doi
035 $a 978-1-4842-8239-7
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.76.A65 $b R67 2022
072 7 $a KJQ $2 bicssc
072 7 $a BUS083000 $2 bisacsh
072 7 $a KJQ $2 thema
082 0 4 $a 005.1 $2 23
090 $a QA76.76.A65 $b R797 2022
100 1 $a Rose, Robert F. $3 932189
245 1 0 $a Software development activity cycles $h [electronic resource] : $b collaborative development, continuous testing and user acceptance / $c by Robert F. Rose.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2022.
300 $a xxxii, 279 p. : $b ill., digital ; $c 24 cm.
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 Application software $x Development. $3 189413
650 1 4 $a IT Operations. $3 913145
650 2 4 $a Software Management. $3 715554
650 2 4 $a Business Process Management. $3 714086
650 2 4 $a Business Information Systems. $3 274346
650 2 4 $a IT in Business. $3 703717
710 2 $a SpringerLink (Online service) $3 273601
773 0 $t Springer Nature eBook
856 4 0 $u https://doi.org/10.1007/978-1-4842-8239-7
950 $a Professional and Applied Computing (SpringerNature-12059)