MARC details
| 000 -LEADER |
|---|
| fixed length control field |
05186cam a2200337 i 4500 |
| 001 - CONTROL NUMBER |
|---|
| control field |
15688592 |
| 005 - DATE AND TIME OF LATEST TRANSACTION |
|---|
| control field |
20201220134003.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
090406s2010 njua b 001 0 eng |
| 010 ## - LIBRARY OF CONGRESS CONTROL NUMBER |
|---|
| LC control number |
2009013890 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
0321357485 (pbk. : alk. paper) |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9780321357489 (pbk. : alk. paper) |
| 040 ## - CATALOGING SOURCE |
|---|
| Original cataloging agency |
DLC |
| Transcribing agency |
DLC |
| Modifying agency |
UKM |
| -- |
C#P |
| -- |
BWX |
| -- |
CDX |
| -- |
DLC |
| Description conventions |
rda |
| 050 00 - LIBRARY OF CONGRESS CALL NUMBER |
|---|
| Classification number |
QA76.754 |
| Item number |
.E35 2010 |
| 082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
005.12 |
| Edition number |
22 |
| Item number |
E.P.P |
| 100 1# - MAIN ENTRY--PERSONAL NAME |
|---|
| Personal name |
Eeles, Peter, |
| Dates associated with a name |
1962- |
| 245 14 - TITLE STATEMENT |
|---|
| Title |
The process of software architecting / |
| Statement of responsibility, etc |
Peter Eeles, Peter Cripps. |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
|---|
| Place of publication, distribution, etc |
Upper Saddle River, NJ : |
| Name of publisher, distributor, etc |
Addison-Wesley, |
| Date of publication, distribution, etc |
c2010. |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
xxv, 405 pages. : |
| Other physical details |
illustration; |
| Dimensions |
24 cm. |
| 336 ## - CONTENT TYPE |
|---|
| Source |
rdacontent |
| Content type term |
text |
| 337 ## - MEDIA TYPE |
|---|
| Source |
rdamedia |
| Media type term |
unmediated |
| 338 ## - CARRIER TYPE |
|---|
| Source |
rdacarrier |
| Carrier type term |
volume |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc |
Includes bibliographical references and index. |
| 505 0# - FORMATTED CONTENTS NOTE |
|---|
| Formatted contents note |
Foreword xvii<br/>Preface xix<br/>Acknowledgments xxiii<br/>About the Authors xxv<br/><br/>Chapter 1: Introduction 1<br/>Applying the Process 2<br/>The Process in Brief 2<br/>Scope 8<br/>Summary 8<br/><br/>Chapter 2: Architecture, Architect, Architecting 9<br/>Architecture 9<br/>Architect 21<br/>The Benefits of Architecting 35<br/>Summary 40<br/><br/>Chapter 3: Method Fundamentals 43<br/>Key Concepts 43<br/>Method Content 46<br/>Process 50<br/>Summary 59<br/><br/>Chapter 4: Documenting a Software Architecture 61<br/>The End Game 62<br/>Key Concepts 64<br/>Viewpoints and Views 65<br/>Models 72<br/>Characteristics of an Architecture Description Framework 75<br/>An Architecture Description Framework 81<br/>The Software Architecture Document 87<br/>Summary 88<br/><br/>Chapter 5: Reusable Architecture Assets 89<br/>Sources of Architecture 89<br/>An Architecture Asset Metamodel 90<br/>Asset Types 94<br/>Attributes of an Architecture Asset 103<br/>Other Reuse Considerations 106<br/>Summary 106<br/><br/>Chapter 6: Introduction to the Case Study 107<br/>Applying the Process 107<br/>Scope of the Case Study 110<br/>Application Overview 115<br/>The YourTour Vision 118<br/>Summary 123<br/><br/>Chapter 7: Defining the Requirements 125<br/>Relating Requirements to Architecture 128<br/>Functional and Non-Functional Requirements 130<br/>Techniques for Documenting Requirements 131<br/>Applying the Process 132<br/>Understanding the Task Descriptions 133<br/>Define Requirements: Activity Overview 134<br/>Task: Collect Stakeholder Requests 136<br/>Task: Capture Common Vocabulary 141<br/>Task: Define System Context 143<br/>Task: Outline Functional Requirements 149<br/>Task: Outline Non-Functional Requirements 156<br/>Task: Prioritize Requirements 160<br/>Task: Detail Functional Requirements 164<br/>Task: Detail Non-Functional Requirements 171<br/>Task: Update Software Architecture Document 174<br/>Task: Review Requirements with Stakeholders 175<br/>Summary 176<br/><br/>Chapter 8: Creating the Logical Architecture 179<br/>Moving from Requirements to Solution 182<br/>How Much Logical Architecture? 185<br/>Applying the Process 188<br/>Create Logical Architecture: Activity Overview 188<br/>Task: Survey Architecture Assets 192<br/>Task: Define Architecture Overview 194<br/>Task: Document Architecture Decisions 200<br/>Task: Outline Functional Elements 204<br/>Task: Outline Deployment Elements 222<br/>Task: Verify Architecture 228<br/>Task: Build Architecture Proof-of-Concept 232<br/>Task: Detail Functional Elements 234<br/>Task: Detail Deployment Elements 245<br/>Task: Validate Architecture 251<br/>Task: Update Software Architecture Document 256<br/>Task: Review Architecture with Stakeholders 258<br/>Summary 260<br/><br/>Chapter 9: Creating the Physical Architecture 261<br/>Moving from Logical to Physical Architecture 263<br/>Applying the Process 265<br/>Creating the Physical Architecture: Activity Overview 266<br/>Task: Survey Architecture Assets 269<br/>Task: Define Architecture Overview 270<br/>Task: Document Architecture Decisions 273<br/>Task: Outline Functional Elements 274<br/>Task: Outline Deployment Elements 289<br/>Task: Verify Architecture 292<br/>Task: Build Architecture Proof-of-Concept 293<br/>Task: Detail Functional Elements 294<br/>Task: Detail Deployment Elements 296<br/>Task: Validate Architecture 300<br/>Task: Update Software Architecture Document 301<br/>Task: Review Architecture with Stakeholders 301<br/>Summary 302<br/><br/>Chapter 10: Beyond the Basics 303<br/>The Architect and the Project Team 303<br/>The Architect and External Influences 313<br/>Architecting Complex Systems 318<br/>Summary 330<br/>In Conclusion: A Note from the Authors 331<br/><br/>Appendix A: Software Architecture Metamodel 333<br/>Definition of Metamodel Terms 335<br/><br/>Appendix B: Viewpoint Catalog 339<br/>Stakeholder Summary 340<br/>Basic Viewpoints 341<br/>Cross-Cutting Viewpoints 344<br/>View Correspondence 347<br/><br/>Appendix C: Method Summary 351<br/>Roles 351<br/>Work Products 354<br/>Activities 356<br/>Tasks 356<br/>Phases 362<br/><br/>Appendix D: Architectural Requirement Checklist 365<br/>Functional Requirements 366<br/>Usability Requirements 366<br/>Reliability Requirements 367<br/>Performance Requirements 367<br/>Supportability Requirements 368<br/>Constraints 368<br/><br/>Glossary 373<br/>References 379<br/>Index 385 |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software architecture. |
| 9 (RLIN) |
33243 |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
System design. |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Cripps, Peter, |
| Dates associated with a name |
1958- |
| 856 41 - ELECTRONIC LOCATION AND ACCESS |
|---|
| Materials specified |
Table of contents only |
| Uniform Resource Identifier |
<a href="http://www.loc.gov/catdir/toc/fy1002/2009013890.html">http://www.loc.gov/catdir/toc/fy1002/2009013890.html</a> |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) |
|---|
| Koha item type |
Books |
| Source of classification or shelving scheme |
Dewey Decimal Classification |