000			03707nam a2200361 i 4500
999			_c397969 _d397969 _x1
001			397969
003			ES-MaUEC
005			20240314174500.0
006			a|||||o|||| 00| 0
007			cr nn 008mamaa
008			230427s2023 sz | o |||| 0|eng d
020			_a9783031168628
024	7		_a10.1007/978-3-031-16862-8 _2doi
040			_aES-MaUEC _bspa _cES-MaUEC _dES-MaUEC
050		4	_aQA76.758 _b2023 EB
100	1		_aBrock, Bert de _eautor _4http://id.loc.gov/vocabulary/relators/aut _9689460
245	1	0	_aDeveloping Information Systems Accurately : _bA Wholistic Approach _cby Bert de Brock
250			_a1st ed 2023
264		1	_aCham _bSpringer International Publishing _c2023
300			_a1 recurso en línea
336			_atexto _btxt _2rdacontent
337			_aelectrónico _bc _2rdamedia
338			_arecurso electrónico _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 an IS-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. .
988			_aSpringer_Computer_2023
650		7	_2embne _9152630 _aIngeniería del software
856	4	0	_uhttps://go.openathens.net/redirector/universidadeuropea.es?url=https://doi.org/10.1007/978-3-031-16862-8 _zAcceso a este recurso digital (usuarios Universidad Europea de Madrid)
942			_2lcc _cLE
998			_b01/2024 _dz _eb _zSI