{"product_id":"cognitive-dynamics-of-computer-science-costeffective-large-scale-software-development-wiley-ieee-9780471970477","title":"Cognitive Dynamics of Computer Science","description":"\u003cb\u003eBook Synopsis\u003c\/b\u003e\u003cbr\u003eThis book has three major objectives: * To propose an ontology for computer software. * To provide a methodology for development of large software systems to cost and schedule that is based on the ontology. * To offer an alternative vision regarding the development of truly autonomous systems.\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTrade Review\u003c\/b\u003e\u003cbr\u003e\"The book is outstanding on almost every aspect…might become one of the classics and [I] hope you enjoy reading it.\" (\u003ci\u003eACM Software Engineering Notes\u003c\/i\u003e, January 2007)  \u003cp\u003e\"…this book is worthwhile.\" (\u003ci\u003eSoftware Quality Professional\u003c\/i\u003e, December 2006)\u003c\/p\u003e \u003cp\u003e\"This book is a 'must-have' for all computer scientists and software professionals.\" (\u003ci\u003eUbiquity\u003c\/i\u003e, September 19, 2006)\u003c\/p\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTable of Contents\u003c\/b\u003e\u003cbr\u003e\u003cb\u003eList of Figures.\u003c\/b\u003e  \u003cp\u003e\u003cb\u003eAcknowledgments.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 1. Introduction.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e1.1 The Retention of Software Jobs.\u003c\/p\u003e \u003cp\u003e1.2 Depth of Experience.\u003c\/p\u003e \u003cp\u003e1.3 The Scope of This Book.\u003c\/p\u003e \u003cp\u003e1.4 The Nature of Computer Science.\u003c\/p\u003e \u003cp\u003e1.5 The Future of Computer Science.\u003c\/p\u003e \u003cp\u003e1.6 The Essence of Philosophy.\u003c\/p\u003e \u003cp\u003e1.7 Why Autonomy?\u003c\/p\u003e \u003cp\u003e1.8 An Architecture for Autonomy.\u003c\/p\u003e \u003cp\u003e1.9 Other Notes.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 2. Prologue.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e2.1 How This Book Originated.\u003c\/p\u003e \u003cp\u003e2.2 The Importance of Management.\u003c\/p\u003e \u003cp\u003e2.3 The Tie-in with Autonomy.\u003c\/p\u003e \u003cp\u003e2.4 Major Themes of This Book.\u003c\/p\u003e \u003cp\u003e2.5 The Challenge of a New Idea.\u003c\/p\u003e \u003cp\u003e2.6 The Importance of Visualization.\u003c\/p\u003e \u003cp\u003e2.7 The Move Toward Autonomy.\u003c\/p\u003e \u003cp\u003e2.8 Why I Wrote This Book.\u003c\/p\u003e \u003cp\u003e2.9 Merging Theory and Practice.\u003c\/p\u003e \u003cp\u003e2.10 The Pace of Computer Science.\u003c\/p\u003e \u003cp\u003e2.11 The Importance of Cognitive Dynamics.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 3. The Philosophical Foundations of Computer Software Design.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e3.1 The Philosophical Origins of Computer Science.\u003c\/p\u003e \u003cp\u003e3.2 Influence of the Cognitive Philosophers.\u003c\/p\u003e \u003cp\u003e3.3 Abstracting the Human Thought System.\u003c\/p\u003e \u003cp\u003e3.4 The Philosophical Foundations of Software Development.\u003c\/p\u003e \u003cp\u003e3.5 The Phenomenon of Reality.\u003c\/p\u003e \u003cp\u003e3.6 The Phenomenon of Subjectivity.\u003c\/p\u003e \u003cp\u003e3.7 Low-Cost Software Development.\u003c\/p\u003e \u003cp\u003e3.8 \"On Budget and On Schedule.\"\u003c\/p\u003e \u003cp\u003e3.9 The Time to Completion: Schedule.\u003c\/p\u003e \u003cp\u003e3.10 Philosophy and Successful Design.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 4. The Philosophical Imperatives of Architectural Design.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e4.1 The Manager as Architect.\u003c\/p\u003e \u003cp\u003e4.2 The Manager as Teacher.\u003c\/p\u003e \u003cp\u003e4.3 The Manager as Social Worker.\u003c\/p\u003e \u003cp\u003e4.4 The Manager as Axman.\u003c\/p\u003e \u003cp\u003e4.5 The Philosophical Imperatives of Architectural Design.\u003c\/p\u003e \u003cp\u003e4.6 Availability of the Manager.\u003c\/p\u003e \u003cp\u003e4.7 Project Manager: 10 Key Attributes and Responsibilities.\u003c\/p\u003e \u003cp\u003e4.8 Philosophical Aspects of Engineering.\u003c\/p\u003e \u003cp\u003e4.9 The Importance of Finishing the Job.\u003c\/p\u003e \u003cp\u003e4.10 Visualizing an Architecture.\u003c\/p\u003e \u003cp\u003e4.11 The Role of Intuition in Design.\u003c\/p\u003e \u003cp\u003e4.12 ‘‘Sufficient Reality’’ and Inference in the Design Process.\u003c\/p\u003e \u003cp\u003e4.13 Dialectics in the Achievement of Sufficient Reality.\u003c\/p\u003e \u003cp\u003e4.14 The Relationship of Logic to Software Architectures.\u003c\/p\u003e \u003cp\u003e4.15 The Logic of the Systems Design.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 5. Project and Task Organization.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e5.1 The Role of Organization.\u003c\/p\u003e \u003cp\u003e5.2 The Ability to Organize.\u003c\/p\u003e \u003cp\u003e5.3 The Difficulty of Communication.\u003c\/p\u003e \u003cp\u003e5.4 The Title of \"Manager.\"\u003c\/p\u003e \u003cp\u003e5.5 The Flat, Nonhierarchical Organization.\u003c\/p\u003e \u003cp\u003e5.6 Projects, Tasks, and Work Units.\u003c\/p\u003e \u003cp\u003e5.7 Large Organizations and Staffing.\u003c\/p\u003e \u003cp\u003e5.8 Staffing Up: The Initial Team.\u003c\/p\u003e \u003cp\u003e5.9 Balancing Hardware and Software.\u003c\/p\u003e \u003cp\u003e5.10 Incremental Deliveries.\u003c\/p\u003e \u003cp\u003e5.11 Functional Organization.\u003c\/p\u003e \u003cp\u003e5.12 Interface Protocols of the Organization.\u003c\/p\u003e \u003cp\u003e5.13 Completion of the Task.\u003c\/p\u003e \u003cp\u003e5.14 Detecting the \"Fraud.\"\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 6. The Philosophy of Communication.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e6.1 \"Sanity Is an Achievement!\"\u003c\/p\u003e \u003cp\u003e6.2 Gauging Understanding.\u003c\/p\u003e \u003cp\u003e6.3 Internal Team Communication Protocols.\u003c\/p\u003e \u003cp\u003e6.4 External Team Communication Protocols.\u003c\/p\u003e \u003cp\u003e6.5 Technical English as the Medium.\u003c\/p\u003e \u003cp\u003e6.6 Engineers as Technical Writers.\u003c\/p\u003e \u003cp\u003e6.7 Documentation: Articulation of the Requirements and Design.\u003c\/p\u003e \u003cp\u003e6.8 The SRD: Software Requirements Document.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 7. Software Management Standards.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e7.1 Three Good Standards.\u003c\/p\u003e \u003cp\u003e7.2 Aspects Addressed by a Standard.\u003c\/p\u003e \u003cp\u003e7.3 Preparing to Select the Standard.\u003c\/p\u003e \u003cp\u003e7.4 Standards for Implementation.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 8. The Estimation of Software Cost.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e8.1 Sponsor Costing Issues.\u003c\/p\u003e \u003cp\u003e8.2 Types of Cost Estimates.\u003c\/p\u003e \u003cp\u003e8.3 ‘‘Lines of Code’’ Metrics.\u003c\/p\u003e \u003cp\u003e8.4 The Major Work Areas, Functions, and Tasks that Must be Included in the Estimation of Cost.\u003c\/p\u003e \u003cp\u003e8.5 The Detailed Cost Estimate.\u003c\/p\u003e \u003cp\u003e8.6 The SRD as a Contract.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 9. The Exercise of Project Control.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e9.1 The Functions of Project Control and Oversight.\u003c\/p\u003e \u003cp\u003e9.2 The Requirements Phase.\u003c\/p\u003e \u003cp\u003e9.3 Contents of the Software Requirements Document.\u003c\/p\u003e \u003cp\u003e9.4 The Design Phase.\u003c\/p\u003e \u003cp\u003e9.5 The Implementation Phase.\u003c\/p\u003e \u003cp\u003e9.6 The Test and Integration Phase.\u003c\/p\u003e \u003cp\u003e9.7 Personnel Issues.\u003c\/p\u003e \u003cp\u003e9.8 The Hacker and Other Personalities.\u003c\/p\u003e \u003cp\u003e9.9 The Buck Stops at the Top.\u003c\/p\u003e \u003cp\u003e9.10 How People Think, Pay Attention, and Remember.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 10. The Development Process Methodology.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e10.1 The \"Design Hub\" as Implementation Tool.\u003c\/p\u003e \u003cp\u003e10.2 The Architecture Definition Process.\u003c\/p\u003e \u003cp\u003e10.3 The Use of Large-Scale Representations.\u003c\/p\u003e \u003cp\u003e10.4 Design Team Meetings.\u003c\/p\u003e \u003cp\u003e10.5 Rapid Development versus Prototyping.\u003c\/p\u003e \u003cp\u003e10.6 The Traditional Development Methodology.\u003c\/p\u003e \u003cp\u003e10.7 Action Items, Change Requests, and Software Discrepancy Reports.\u003c\/p\u003e \u003cp\u003e10.8 Resolving Problems and Impasses.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 11. The Development of System Architectures.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e11.1 Pushing the Architecture.\u003c\/p\u003e \u003cp\u003e11.2 The Point of \"Acceptable Reality.\"\u003c\/p\u003e \u003cp\u003e11.3 The Importance and Imperative of Visualizing Phenomena.\u003c\/p\u003e \u003cp\u003e11.4 Traditional Architectures.\u003c\/p\u003e \u003cp\u003e11.5 The Inferred Architecture.\u003c\/p\u003e \u003cp\u003e11.6 The Redesign or Upgrading of Existing Systems.\u003c\/p\u003e \u003cp\u003e11.7 The Approach to New Systems.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 12. The Impact of Leadership on Software Development.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e12.1 Recognizing Good Leadership.\u003c\/p\u003e \u003cp\u003e12.2 The Concepts of Management and Leadership.\u003c\/p\u003e \u003cp\u003e12.3 Rewarding Failure.\u003c\/p\u003e \u003cp\u003e12.4 The Leader’s Subordinate.\u003c\/p\u003e \u003cp\u003e12.5 Indications of Poor Leadership.\u003c\/p\u003e \u003cp\u003e12.6 Leadership and Ethics.\u003c\/p\u003e \u003cp\u003e12.7 The Attributes of Leadership.\u003c\/p\u003e \u003cp\u003e12.8 The Ramifications of Failure.\u003c\/p\u003e \u003cp\u003e12.9 The Absence of Leadership.\u003c\/p\u003e \u003cp\u003e12.10 The Basis in Leadership for Failure.\u003c\/p\u003e \u003cp\u003e12.11 The impact of Poor or Nonexistent Leadership.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 13. Management of Software Systems Development.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e13.1 Self-Respect in the Manager.\u003c\/p\u003e \u003cp\u003e13.2 The Ethical Workplace.\u003c\/p\u003e \u003cp\u003e13.3 Narcotics Use in the Workforce.\u003c\/p\u003e \u003cp\u003e13.4 Spotting Narcotics Addicts.\u003c\/p\u003e \u003cp\u003e13.5 Courage and Dynamic Energy in Management.\u003c\/p\u003e \u003cp\u003e13.6 The Traveling Manager.\u003c\/p\u003e \u003cp\u003e13.7 The Manager as Architect.\u003c\/p\u003e \u003cp\u003e13.8 The Phenomenon of Decision Making.\u003c\/p\u003e \u003cp\u003e13.9 The Concept of \"Ability.\"\u003c\/p\u003e \u003cp\u003e13.10 Manager: Administrator or Leader?\u003c\/p\u003e \u003cp\u003e13.11 Authority, Responsibility, and Accountability.\u003c\/p\u003e \u003cp\u003e13.12 The Issue of Contempt.\u003c\/p\u003e \u003cp\u003e13.13 Management: The Fulcrum of Project Execution.\u003c\/p\u003e \u003cp\u003e13.14 The Ascendance of Mediocrity.\u003c\/p\u003e \u003cp\u003e13.15 The Pitfalls of Staffing Up.\u003c\/p\u003e \u003cp\u003e13.16 Salary Issues.\u003c\/p\u003e \u003cp\u003e13.17 Contracting Out Work.\u003c\/p\u003e \u003cp\u003e13.18 Evaluating Proposals.\u003c\/p\u003e \u003cp\u003e13.19 Cost Bidding too Early.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 14: Four Case Studies of Low-Cost Systems.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e14.1 Case Study One: The Joint Theater Level Simulation (JTLS).\u003c\/p\u003e \u003cp\u003e14.2 Case Study Two: The Global Decision Support System (GDSS).\u003c\/p\u003e \u003cp\u003e14.3 Case Study Three: The Topex TCCS System.\u003c\/p\u003e \u003cp\u003e14.4 Case Study Four: The Jason 1 TCCS System (JTCCS).\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 15. Operations, Operators, and Users: Their Impact on Cost.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e15.1 The Operational Requirement.\u003c\/p\u003e \u003cp\u003e15.2 The Lack of an Operational Requirement.\u003c\/p\u003e \u003cp\u003e15.3 The Operations Scenario.\u003c\/p\u003e \u003cp\u003e15.4 The Cost of Operators and Analysts.\u003c\/p\u003e \u003cp\u003e15.5 The Voyager Project Operations Center.\u003c\/p\u003e \u003cp\u003e15.6 War Gaming.\u003c\/p\u003e \u003cp\u003e15.7 The Value of Simulation.\u003c\/p\u003e \u003cp\u003e15.8 Funds: A Perspective.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eChapter 16. The Autonomous Cognitive System.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e16.1 Introduction.\u003c\/p\u003e \u003cp\u003e16.2 The Scale of Autonomy.\u003c\/p\u003e \u003cp\u003e16.3 \"I Will, Because I Can.\"\u003c\/p\u003e \u003cp\u003e16.4 Toward Cognitive Dynamics.\u003c\/p\u003e \u003cp\u003e16.5 Building an Autonomous System.\u003c\/p\u003e \u003cp\u003e16.6 An Appropriate Model.\u003c\/p\u003e \u003cp\u003e16.7 System-Level Requirements for Autonomy.\u003c\/p\u003e \u003cp\u003e16.8 Architectural Domains for Autonomy.\u003c\/p\u003e \u003cp\u003e16.9 In Summary.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eEpilogue.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eThe Science of Computer Science.\u003c\/p\u003e \u003cp\u003eThe Professional Software Manager.\u003c\/p\u003e \u003cp\u003eCognitive Philosophy in a Modern Technical Context.\u003c\/p\u003e \u003cp\u003eCognitive Dynamics is the Unifying Theory.\u003c\/p\u003e \u003cp\u003eThe Issue of Software Cost.\u003c\/p\u003e \u003cp\u003eThe Paradigm Shift of Cognitive Dynamics.\u003c\/p\u003e \u003cp\u003e\u003cb\u003eGlossary of Acronyms.\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003eIndex.\u003c\/b\u003e\u003c\/p\u003e","brand":"John Wiley \u0026 Sons Inc","offers":[{"title":"Default Title","offer_id":49402700988759,"sku":"9780471970477","price":999.99,"currency_code":"GBP","in_stock":false}],"url":"https:\/\/bookcurl.com\/products\/cognitive-dynamics-of-computer-science-costeffective-large-scale-software-development-wiley-ieee-9780471970477","provider":"Book Curl","version":"1.0","type":"link"}