000 04088nam a22004935i 4500
001 978-3-031-16862-8
003 DE-He213
005 20240423125024.0
007 cr nn 008mamaa
008 230427s2023 sz | s |||| 0|eng d
020 _a9783031168628
_9978-3-031-16862-8
024 7 _a10.1007/978-3-031-16862-8
_2doi
050 4 _aQA76.76.A65
072 7 _aUB
_2bicssc
072 7 _aCOM005000
_2bisacsh
072 7 _aUX
_2thema
082 0 4 _a005.3
_223
100 1 _ade Brock, Bert.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
245 1 0 _aDeveloping Information Systems Accurately
_h[electronic resource] :
_bA Wholistic Approach /
_cby Bert de Brock.
250 _a1st ed. 2023.
264 1 _aCham :
_bSpringer International Publishing :
_bImprint: Springer,
_c2023.
300 _aXXV, 252 p. 141 illus., 25 illus. in color.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
520 _aThis textbook shows how to develop the functional requirements of (information) systems. It emphasizes the importance to consider the complete development path of a functional requirement, i.e. not only the individual development steps but also their proper combination and their alignment. The book consists of two parts: Part I presents the underlying theory while Part II contains various illustrative case studies. Part I starts with an introduction to the topic (Chapter 1). Then it explains how to develop functional requirements that represent the conceptual dynamics of an information system (Chapters 2 and 3). Chapters 4 and 5 explain how to model the conceptual statics of an information system. Chapter 6 gives some directions for implementation. Finally, Chapter 7 explains how a ‘technical manager’ can organize and manage the development process. As an illustration of the theory, Part II contains three substantial case studies. The first one (Chapter 8) presents a stepwise development starting from an informal situation sketch via a simple domain model towards a precisely specified, full-fledged conceptual data model, which finally is translated to an SQL database. In the second case study (Chapter 9) the author converts the well-known non-trivial use case Process Sale from Larman into a textual System Sequence Description (SSD). For validation purposes, that textual SSD is subsequently translated into natural language and into a graphical SSD. The third case study (Chapter 10) shows the applicability of the author’s approach to a control system and also illustrates the typical situation that the requirements are constantly changing during development. This book is written for (under)graduate students in software engineering or information systems who want to learn how to carry out adequate problem analysis, to make good system specifications, and/or to understand how to organize and manage anIS-development process. It also targets practitioners who want to improve their problem analysis abilities and/or their ability to make good system specifications. To this end, it includes more than 150 explanatory figures and is accompanied by a Web site which provides additional course material such as slides, additional exercises, solutions to exercises, and the code for the figures used in the book. .
650 0 _aApplication software.
650 0 _aSoftware engineering.
650 0 _aBusiness information services.
650 1 4 _aComputer and Information Systems Applications.
650 2 4 _aSoftware Engineering.
650 2 4 _aBusiness Information Systems.
710 2 _aSpringerLink (Online service)
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783031168611
776 0 8 _iPrinted edition:
_z9783031168635
856 4 0 _uhttps://doi.org/10.1007/978-3-031-16862-8
912 _aZDB-2-SCS
912 _aZDB-2-SXCS
942 _cSPRINGER
999 _c173338
_d173338