Managing complexity of information systems : the value of simplicity / Pirmin Lemberger, Médéric Morel.

Lemberger, Pirmin, author.
1st edition
London : ISTE ; Hoboken, NJ : Wiley, 2012.
1 online resource (245 p.)
Management information systems.
Technological complexity.
Information technology.
Electronic books.
System Details:
text file
This book is about complexity in Information Systems (IS). The subject is addressed from both conceptual and applied perspectives. Concepts are drawn from information theory, industrial design and software engineering. Its content capitalizes on experiences gathered by the authors during various contracting jobs involving software architecture, modeling and IS architecture that were conducted for large organizations in the banking and industry sectors, as well as in the public sector.The authors develop the point of view according to which mastering complexity involves two essential steps:
Cover; Managing Complexity of Information Systems; Title Page; Copyright Page; Table of Contents; Foreword; Preface; Chapter 1. Why Simplicity?; 1.1. Solving conflicting requirements; 1.2. Three periods in IS management; 1.2.1. Management driven by technology; 1.2.2. Management through cost reduction; 1.2.3. Management through value creation; 1.3. And now ... simplicity!; 1.3.1. Technology, cost reduction, value creation ... So what's next?; 1.4. Plan of the book; Chapter 2. Complexity, Simplicity, and Abstraction; 2.1. What does information theory tell us?; 2.1.1. Shannon's entropy
2.1.2. Kolmogorov complexity2.1.2.1. Complexity of objects versus complexity of binary strings; Relation to Shannon's entropy; Can we compute K-complexity?; 2.1.3. Bennett's logical depth; 2.1.4. Abstraction in light of scale and depth; 2.1.5. Harvesting information theory; 2.2. What does the design tell us?; 2.2.1. Simplicity by reduction; 2.2.2. Simplicity by hiding complexity; Customers; Business analysts; IT personnel; 2.2.3. Simplicity through organization; 2.2.4. Simplicity through learning Learning obviates the need to hide complexity2.2.4.2. Learning allows complexity transformation; 2.2.5. Simplicity implies time saving; Lack of time; How simplicity saves time; 2.2.6. Simplicity needs trust; 2.2.7. What does software architecture tell us?; The complexity of code and of IS architecture; 2.2.8. Abstraction in software engineering; Abstraction is everywhere in software; Depth and scale revisited; Chapter 3. Value or Values?; 3.1. Who is concerned?; 3.1.1. Internal stakeholders; 3.1.2. External stakeholders
3.2. Concepts of value for an IS3.2.1. Book value; 3.2.2. Net worth; 3.2.3. Use value; Functional criterion; Non-functional criteria; 3.2.4. Strategic value; 3.2.5. Sustainability value; 3.3. Are these values sufficient and independent?; 3.3.1. IT chaos; 3.3.2. Tech academy; 3.3.3. Alignment trap; 3.3.4. Users are unimportant; 3.3.5. Business-user tyranny; 3.3.6. Wrong direction; 3.3.7. Architecture is a waste of money; 3.3.8. IS heaven; Chapter 4. Promoting Value Through Simplicity; 4.1. Growing technical heterogeneity; 4.1.1. Openness; Why complexity increases Implementing simplicity4.1.2. Rapid obsolescence of IT; Why complexity increases; Implementing simplicity; 4.1.3. Absence of technological vision and leadership; Why complexity increases; Implementing simplicity; 4.2. Changing requirements; 4.2.1. Why complexity increases; 4.2.2. Implementing simplicity; Technical answers; Organizational answers; 4.3. Human factors; 4.3.1. Multidisciplinarity; Why complexity increases; Implementing simplicity; 4.3.2. Disempowerment of IT Skills; Why complexity increases Implementing simplicity
Description based upon print version of record.
Includes bibliographical references and index.
Description based on print version record.
Morel, Médéric, author.
Location Notes Your Loan Policy
Description Status Barcode Your Loan Policy