LEADER 03868nam  22006975  450 
001 9910299837803321
005 20200703120946.0
010   $a3-319-18344-3
024 7 $a10.1007/978-3-319-18344-2
035   $a(CKB)3710000000402864
035   $a(EBL)2096854
035   $a(SSID)ssj0001501241
035   $a(PQKBManifestationID)11830219
035   $a(PQKBTitleCode)TC0001501241
035   $a(PQKBWorkID)11522219
035   $a(PQKB)10879839
035   $a(DE-He213)978-3-319-18344-2
035   $a(MiAaPQ)EBC2096854
035   $a(PPN)185489990
035   $a(EXLCZ)993710000000402864
100   $a20150423d2015      u|         0
101 0 $aeng
135   $aur|n|---|||||
181   $ctxt
182   $cc
183   $acr
200 10$aNon-functional Requirements in Systems Analysis and Design /$fby Kevin MacG. Adams
205   $a1st ed. 2015.
210  1$aCham :$cSpringer International Publishing :$cImprint: Springer,$d2015.
215   $a1 online resource (276 p.)
225 1 $aTopics in Safety, Risk, Reliability and Quality,$x1566-0443 ;$v28
300   $aDescription based upon print version of record.
311   $a3-319-18343-5 
320   $aIncludes bibliographical references and index.
327   $aPart I Introduction -- Part II Sustainment Concerns -- Part III Design Concerns -- Part IV Adaptation Concerns -- Part V Viability Concerns -- Part VI Conclusion.
330   $aThis book will help readers gain a solid understanding of non-functional requirements inherent in systems design endeavors. It contains essential information for those who design, use, and maintain complex engineered systems, including experienced designers, teachers of design, system stakeholders, and practicing engineers. Coverage approaches non-functional requirements in a novel way by presenting a framework of four systems concerns into which the 27 major non-functional requirements fall: sustainment, design, adaptation, and viability. Within this model, the text proceeds to define each non-functional requirement, to specify how each is treated as an element of the system design process, and to develop an associated metric for their evaluation. Systems are designed to meet specific functional needs. Because non-functional requirements are not directly related to tasks that satisfy these proposed needs, designers and stakeholders often fail to recognize the importance of such attributes as availability, survivability, and robustness. This book gives readers the tools and knowledge they need to both recognize the importance of these non-functional requirements and incorporate them in the design process.
410  0$aTopics in Safety, Risk, Reliability and Quality,$x1566-0443 ;$v28
606   $aEngineering design
606   $aComputational complexity
606   $aQuality control
606   $aReliability
606   $aIndustrial safety
606   $aEngineering Design$3https://scigraph.springernature.com/ontologies/product-market-codes/T17020
606   $aComplexity$3https://scigraph.springernature.com/ontologies/product-market-codes/T11022
606   $aQuality Control, Reliability, Safety and Risk$3https://scigraph.springernature.com/ontologies/product-market-codes/T22032
615  0$aEngineering design.
615  0$aComputational complexity.
615  0$aQuality control.
615  0$aReliability.
615  0$aIndustrial safety.
615 14$aEngineering Design.
615 24$aComplexity.
615 24$aQuality Control, Reliability, Safety and Risk.
676   $a620
676   $a620.0042
676   $a658.56
700   $aAdams$b Kevin MacG$4aut$4http://id.loc.gov/vocabulary/relators/aut$0447835
906   $aBOOK
912   $a9910299837803321
996   $aNon-functional Requirements in Systems Analysis and Design$92522103
997   $aUNINA