MARC details
| 000 -LEADER |
|---|
| fixed length control field |
06931cam a2200325 i 4500 |
| 001 - CONTROL NUMBER |
|---|
| control field |
223809823 |
| 005 - DATE AND TIME OF LATEST TRANSACTION |
|---|
| control field |
20201220133642.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
080618s2010 maua b 001 0 eng |
| 010 ## - LIBRARY OF CONGRESS CONTROL NUMBER |
|---|
| LC control number |
2008027309 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9780763754204 (pbk.) |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
076375420X (pbk.) |
| 040 ## - CATALOGING SOURCE |
|---|
| Original cataloging agency |
DLC |
| Transcribing agency |
DLC |
| Modifying agency |
BTCTA |
| -- |
BAKER |
| -- |
YDXCP |
| -- |
UKM |
| -- |
C#P |
| -- |
BWX |
| -- |
CDX |
| Description conventions |
rda |
| 082 04 - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Edition number |
22 |
| Classification number |
005.12 |
| Item number |
S |
| 245 00 - TITLE STATEMENT |
|---|
| Title |
Software architecture and design illuminated / |
| Statement of responsibility, etc |
Kai Qian ... [et al.] |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
|---|
| Place of publication, distribution, etc |
Sudbury, Mass. : |
| Name of publisher, distributor, etc |
Jones and Bartlett Publishers, |
| Date of publication, distribution, etc |
c2010. |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
xiv, 387 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 |
| 490 1# - SERIES STATEMENT |
|---|
| Series statement |
Jones and Bartlett illuminated series. |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc |
Includes bibliographical references and index. |
| 505 ## - FORMATTED CONTENTS NOTE |
|---|
| Formatted contents note |
Table of Contents<br/> Preface <br/>1 Introduction to Software Architecture <br/>1.1 Overview <br/>1.2 Software Architecture: Bridging Software Requirement<br/> and Software Implementation <br/>1.3 Architectural Styles <br/>1.4 Quality Attributes <br/>1.5 Guidelines for Software Architectural Design <br/>1.6 Summary <br/>1.7 Self-Review Questions <br/>2 Software Architecture Design Space <br/>2.1 Overview <br/>2.2 Types of Software Structures <br/> 2.2.1 Software Code Structure <br/> 2.2.2 Software Runtime Structure <br/> 2.2.3 Software Management Structure <br/>2.3 Software Elements <br/>2.4 Software Connectors <br/>2.5 An Agile Approach to Software Architecture Design <br/>2.6 Summary <br/>2.7 Self-Review Questions <br/>3 Models for Software Architecture <br/>3.1 Overview <br/>3.2 UML for Software Architecture <br/> 3.2.1 Structural Diagrams <br/> 3.2.2 Behavioral Diagrams <br/>3.3 Architecture Views <br/>3.4 Architectural Description Languages (ADL) <br/>3.5 Summary <br/>3.6 Self-Review Questions <br/>3.7 Exercises <br/>3.8 Design Exercises <br/>4 Object Oriented Paradigm <br/>4.1 Overview <br/>4.2 Introducing Object Oriented Paradigm <br/> 4.2.1 Classes and Objects <br/> 4.2.2 Relationships <br/>4.3 OO Analysis <br/> 4.3.1 Step 1: Design of UML Use Case Diagram <br/> 4.3.2 Step 2: Develop Analysis Class Diagram via Noun Extraction <br/>4.4 OO Design <br/> 4.4.1 Step 1: Identify Classes - CRC Card <br/> 4.4.2 Step 2: Construct Interaction Diagram <br/> 4.4.3 Step 3: Build State Machine Diagram<br/> <br/> 4.4.4 Step 4: Class Specification <br/>4.5 Design Principles<br/> 4.5.1 Principle of Decoupling<br/> 4.5.2 Ensuring Cohesion<br/> 4.5.3 Open-Closed Principle<br/>4.6 Summary<br/>4.7 Self-Review Questions <br/>4.8 Exercises <br/>4.9 Design Exercises <br/>4.10 Challenging Exercises<br/>5 Data Flow Architecture <br/>5.1 Overview <br/>5.2 Batch Sequential <br/>5.3 Pipe & Filter Architecture <br/>5.4 Process-Control Architecture <br/>5.5 Summary <br/>5.6 Self-Review Questions <br/>5.7 Exercises <br/>5.8 Design Exercises <br/>6 Data Centered Software Architecture <br/>6.1 Overview <br/>6.2 Repository Architecture Style <br/>6.3 Blackboard Architecture Style <br/>6.4 Summary <br/>6.5 Self-Review Questions <br/>6.6 Exercises <br/>6.7 Design Exercises <br/>7 Hierarchy Architecture <br/>7.1 Overview <br/>7.2 Main/Subroutine <br/>7.3 Master/Slave <br/>7.4 Layered<br/>7.5 Virtual Machine <br/>7.6 Summary <br/>7.7 Self-Review Questions <br/>7.8 Exercises <br/>7.9 Design and Exercises <br/>8 Implicit Asynchronous Communication Software Architecture <br/>8.1 Overview <br/>8.2 Non-Buffered Event-Based Implicit Invocations <br/>8.3 Buffered Message-Based Software Architecture <br/>8.4 Summary <br/>8.5 Self-Review Questions <br/>8.6 Exercises <br/>8.7 Design and Exercises <br/>9 Interaction Oriented Software Architecture <br/>9.1 Overview <br/>9.2 Model-View-Controller(MVC) <br/>9.2.1 MVC-I <br/>9.2.2 MVC-II <br/>9.3 Presentation-Abstraction-Control (PAC) <br/>9.4 Summary <br/>9.5 Self-Review Questions <br/>9.6 Exercises <br/>9.7 Design Exercises <br/>10 Distributed Architecture <br/>10.1 Introduction <br/>10.2 Client/Server <br/>10.3 Multi-tiers <br/>10.4 Broker Architectural Style <br/> 10.4.1 Broker Implementation in Common Object Request<br/> Broker Architecture (CORBA) <br/> 10.4.2 Message Broker Architecture <br/>10.5 Service-Oriented Architecture (SOA) <br/> 10.5.1 SOA Implementation in Web Services <br/> 10.5.2 SOA Implementation for Grid Service Computing <br/>10.6 Summary <br/>10.7 Self-Review Questions <br/>10.8 Exercises <br/>10.9 Design Exercises <br/>11 Component-Based Software Architecture <br/>11.1 Overview <br/>11.2 What is a Component <br/>11.3 Principles of Component-Based Design <br/> 11.3.1 Connections of Components <br/> 11.3.2 Component-Level Design Guidelines <br/>11.4 Summary <br/>11.5 Self-Review Questions <br/>11.6 Exercises <br/>11.7 Design Exercises <br/>12 Heterogeneous Architecture <br/>12.1 Overview <br/>12.2 Methodology of Architecture Decision <br/>12.3 Quality Attributes <br/>12.4 Selection of Architectural Styles <br/>12.5 Evaluation of Architecture Designs <br/>12.6 Case Study: Online Computer Vendor <br/> 12.6.1 Overall Architecture Design of OCVS <br/> 12.6.2 Architecture Design of Order Processing Component <br/> 12.6.3 Architecture Design of Inventory Management <br/> 12.6.4 Architecture Design of Manufacture & Shipping Component <br/>12.7 Summary <br/>12.8 Self-Review Questions <br/>12.9 Exercises <br/>12.10 Design Exercises <br/>12.11 Challenging Exercises<br/>13 Architecture of Graphical User Interfaces<br/>13.1 Overview<br/>13.2 Evolution of User Interfaces<br/>13.3 Look-and-Feel (Syntax) of User Interfaces<br/> 13.3.1 Static Style of User Interfaces<br/> 13.3.2 Dynamic Style of User Interfaces<br/> 13.3.3 Tailorable Style of User Interfaces<br/> 13.3.4 No User Interfaces<br/>13.4 Usability (Semantics) of User Interfaces<br/>13.5 Design Considerations of User Interfaces<br/>13.6 Enabling Technology<br/> 13.6.1 Containers<br/> 13.6.2 Layout Managers<br/> 13.6.3 Major UI Components<br/> 13.6.4 Event Listeners<br/> 13.6.5 A Case Study<br/>13.7 Direct Manipulation<br/>13.8 Evaluation of User Interfaces<br/>13.9 Summary<br/>13.10 Self-Review Questions<br/>13.11 Exercises<br/>13.12 Design Exercises<br/>14 Product Line Architectures <br/>14.1 Overview<br/>14.2 Introduction and Motivation<br/> 14.2.1 Software reuse and product lines<br/> 14.2.2 Methodologies, processes, and tools<br/>14.3 Domain Engineering: Institutionalizing Software Reuse<br/> 14.3.1 Domain Analysis: Reference Requirements And Architectures<br/> 14.3.2 Domain Design: Design-For-Commonality And Control-Of-Variability<br/> 14.3.3 Domain Implementation: Configuration Model, Component Base.<br/> 14.3.4 Types of components<br/> 14.3.5 Heuristics<br/> 14.3.6 Software Technology for Systematic Reuse<br/> 14.3.7 Applications Engineering<br/>14.4 Product Line Architectures (PLA)<br/> 14.4.1 Elements of a PLA<br/> 14.4.2 Costs and Benefits of Producing a PLA<br/> 14.4.3 Attribute-Driven Design Method<br/> 14.4.4 Process for Producing a PLA<br/>14.5 A Product Line Analysis Example<br/> 14.5.1 WHY: mission and strategic goals<br/> 14.5.2 WHAT: Product Families<br/> 14.5.3 HOW: asset base<br/>14.6 Summary<br/>14.7 Self-Review Questions<br/>14.8 Exercises<br/>14.9 Design exercises |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software architecture. |
| 9 (RLIN) |
33243 |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Qian, Kai. |
| 9 (RLIN) |
33244 |
| 830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE |
|---|
| Uniform title |
Jones and Bartlett illuminated series. |
| 9 (RLIN) |
33245 |
| 856 ## - ELECTRONIC LOCATION AND ACCESS |
|---|
| Materials specified |
Abstract |
| Uniform Resource Identifier |
<a href="http://repository.fue.edu.eg/xmlui/handle/123456789/3441">http://repository.fue.edu.eg/xmlui/handle/123456789/3441</a> |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) |
|---|
| Koha item type |
Books |
| Source of classification or shelving scheme |
Dewey Decimal Classification |