國立高雄大學圖資館 |

Language: English

Back

Hardware and software projects troubleshootinghow effective requirements writing can save the day /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Hardware and software projects troubleshootingby George Koelsch.
Reminder of title:	how effective requirements writing can save the day /
Author:	Koelsch, George.
Published:	Berkeley, CA :Apress :2023.
Description:	xxv, 562 p. :ill., digital ;24 cm.
Contained By:	Springer Nature eBook
Subject:	Requirements engineering.
Online resource:	https://doi.org/10.1007/978-1-4842-9830-5
ISBN:	9781484298305$q(electronic bk.)

Hardware and software projects troubleshootinghow effective requirements writing can save the day /
Koelsch, George.

Hardware and software projects troubleshootinghow effective requirements writing can save the day /[electronic resource] :by George Koelsch. - Second edition. - Berkeley, CA :Apress :2023. - xxv, 562 p. :ill., digital ;24 cm.

Learn how to create good requirements when designing hardware and software systems. While this book emphasizes writing traditional "shall" statements, it also provides guidance on use case design and creating user stories in support of agile methodologies. The book surveys modelling techniques and various tools that support requirements collection and analysis. You'll learn to manage requirements, including discussions of document types and digital approaches using spreadsheets, generic databases, and dedicated requirements tools. Good, clear examples are presented, many related to real-world work the author has performed during his career. More importantly, you will learn how these techniques can prevent the problems that occur during requirements development. Most of all, you will learn how good requirements governance will greatly increase the success of development projects by getting all people involved to eliminate the adverse impacts to requirements throughout the development lifecycle. Hardware and Software Projects Troubleshooting covers techniques for defining user needs, so you can determine which combination of approaches to use for your projects. You'll also learn how to analyze the different development methodologies so that you can determine the advantages and disadvantages of different requirements approaches and implement them correctly as your needs evolve. Unlike most requirements books, this one teaches writing both hardware and software requirements because many projects include both areas. To exemplify this approach, two example projects are developed throughout the book, one focusing on hardware, and the other on software. You will: Focus on how to eliminate or mitigate requirements problems Understand the 14 techniques for capturing all requirements Address software and hardware needs; because most projects involve both Ensure all statements meet the 16 attributes of a good requirement Differentiate the 19 different functional types of requirements, and the 31 non-functional types Write requirements properly based on extensive examples of good 'shall' statements, user stories, and use cases Employ modelling techniques to mitigate the imprecision of words Install requirements governance to significantly improve project success.

ISBN: 9781484298305$q(electronic bk.)

Standard No.: 10.1007/978-1-4842-9830-5doiSubjects--Topical Terms:

696400
Requirements engineering.

LC Class. No.: TA180

Dewey Class. No.: 624.068

Hardware and software projects troubleshootinghow effective requirements writing can save the day /
LDR:03336nmm a2200325 a 4500 001 653556
003 DE-He213
005 20231207132547.0
006 m d
007 cr nn 008maaau
008 240426s2023 cau s 0 eng d
020 $a 9781484298305$q(electronic bk.)
020 $a 9781484298299$q(paper)
024 7 $a 10.1007/978-1-4842-9830-5 $2 doi
035 $a 978-1-4842-9830-5
040 $a GP $c GP
041 0 $a eng
050 4 $a TA180
072 7 $a UMZ $2 bicssc
072 7 $a COM051230 $2 bisacsh
072 7 $a UMZ $2 thema
082 0 4 $a 624.068 $2 23
090 $a TA180 $b .K77 2023
100 1 $a Koelsch, George. $3 761737
245 1 0 $a Hardware and software projects troubleshooting $h [electronic resource] : $b how effective requirements writing can save the day / $c by George Koelsch.
250 $a Second edition.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2023.
300 $a xxv, 562 p. : $b ill., digital ; $c 24 cm.
520 $a Learn how to create good requirements when designing hardware and software systems. While this book emphasizes writing traditional "shall" statements, it also provides guidance on use case design and creating user stories in support of agile methodologies. The book surveys modelling techniques and various tools that support requirements collection and analysis. You'll learn to manage requirements, including discussions of document types and digital approaches using spreadsheets, generic databases, and dedicated requirements tools. Good, clear examples are presented, many related to real-world work the author has performed during his career. More importantly, you will learn how these techniques can prevent the problems that occur during requirements development. Most of all, you will learn how good requirements governance will greatly increase the success of development projects by getting all people involved to eliminate the adverse impacts to requirements throughout the development lifecycle. Hardware and Software Projects Troubleshooting covers techniques for defining user needs, so you can determine which combination of approaches to use for your projects. You'll also learn how to analyze the different development methodologies so that you can determine the advantages and disadvantages of different requirements approaches and implement them correctly as your needs evolve. Unlike most requirements books, this one teaches writing both hardware and software requirements because many projects include both areas. To exemplify this approach, two example projects are developed throughout the book, one focusing on hardware, and the other on software. You will: Focus on how to eliminate or mitigate requirements problems Understand the 14 techniques for capturing all requirements Address software and hardware needs; because most projects involve both Ensure all statements meet the 16 attributes of a good requirement Differentiate the 19 different functional types of requirements, and the 31 non-functional types Write requirements properly based on extensive examples of good 'shall' statements, user stories, and use cases Employ modelling techniques to mitigate the imprecision of words Install requirements governance to significantly improve project success.
650 0 $a Requirements engineering. $3 696400
650 0 $a Systems engineering. $3 182491
650 1 4 $a Software Engineering. $3 274511
650 2 4 $a Project Management. $3 515728
650 2 4 $a Software Management. $3 715554
650 2 4 $a Computer System Implementation. $3 276333
650 2 4 $a IT Operations. $3 913145
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-9830-5
950 $a Professional and Applied Computing (SpringerNature-12059)