Software architecture in practice / (Record no. 41027)

MARC details
000 -CABECERA
Campo de control de longitud fija 05627nam a2200325 a 4500
003 - IDENTIFICADOR DEL NÚMERO DE CONTROL
Identificador del número de control AR-sfUTN
008 - DATOS DE LONGITUD FIJA--INFORMACIÓN GENERAL
Códigos de información de longitud fija 170717b ||||| |||| 00| 0 d
020 ## - NÚMERO INTERNACIONAL ESTÁNDAR DEL LIBRO
ISBN 0201199300
040 ## - FUENTE DE LA CATALOGACIÓN
Centro transcriptor AR-sfUTN
041 ## - CÓDIGO DE LENGUA
Código de lengua del texto eng
080 ## - NÚMERO DE LA CLASIFICACIÓN DECIMAL UNIVERSAL
Clasificación Decimal Universal 004.41 B293 1998
Edición de la CDU 2000
100 1# - ENTRADA PRINCIPAL--NOMBRE DE PERSONA
Nombre personal Bass, Len
245 10 - MENCIÓN DE TÍTULO
Título Software architecture in practice /
Mención de responsabilidad Len Bass, Paul Clements, Rick Kazman.
260 ## - PUBLICACIÓN, DISTRIBUCIÓN, ETC.
Lugar de publicación, distribución, etc. Reading:
Nombre del editor, distribuidor, etc. Addison-Wesley,
Fecha de publicación, distribución, etc. 1998
300 ## - DESCRIPCIÓN FÍSICA
Extensión 452 p.
336 ## - TIPO DE CONTENIDO
Fuente rdacontent
Término de tipo de contenido texto
Código de tipo de contenido txt
337 ## - TIPO DE MEDIO
Fuente rdamedia
Nombre del tipo de medio sin mediación
Código del tipo de medio n
338 ## - TIPO DE SOPORTE
Fuente rdacarrier
Nombre del tipo de soporte volumen
Código del tipo de soporte nc
490 ## - MENCIÓN DE SERIE
Mención de serie SEI Series in Software Engineering
505 80 - NOTA DE CONTENIDO CON FORMATO
Nota de contenido con formato CONTENIDO<br/>Part One Envisioning Architecture 1<br/>CHAPTER 1 The Architecture Business Cycle 3<br/>1.1 Where Do Architectures Come From? 6<br/>1.2 Software Processes and the Architecture Business Cycle 12<br/>1.3 What Makes a Good Architecture? 17<br/>CHAPTER 2 What Is Software Architecture? 21<br/>2.1 What Software Architecture Is and What It Isn't 21<br/>2.2 Architectural Styles, Reference Models, and Reference Architectures 25<br/>2.3 Other Viewpoints 26<br/>2.4 Why Is Software Architecture Important? 28<br/>2.5 Architectural Structures 36<br/>CHAPTER 3 A-7E: A Case Study in Utilizing Architectural Structures 45<br/>3.1 Relationship to the Architecture Business Cycle 45<br/>3.2 Requirements and Qualities 47<br/>3.3 Architectural Approach 50<br/>3.4 Architecture for the A-7E Avionics System 57<br/>Part Two Creating and Analyzing an Architecture 73<br/>CHAPTER 4 Quality Attributes 75<br/>4.1 Architectures and Quality Attributes 76<br/>4.2 Architectural Means for Achieving Qualities 88<br/>CHAPTER 5 Moving From Qualities to Architecture: Architectural Styles 93<br/>5.1 Introducing Architectural Styles 94<br/>5.2 Organizing Architectural Styles 104<br/>5.3 Refinements of Styles 107<br/>5.4 Using Styles in System Design 113<br/>5.5 Achieving Quality Goals with Architectural Styles 117<br/>CHAPTER 6 Unit Operations 123<br/>6.1 Introducing Unit Operations 123<br/>6.2 Applying Unit Operations to User-Interface Software 130<br/>6.3 Ramifications of Addressing Quality Attributes 142<br/>CHAPTER 7 The World Wide Web: A Case Study in Interoperability 145<br/>7.1 Relationship to the Architecture Business Cycle 145<br/>7.2 Requirements and Qualities 147<br/>7.3 Architectural Approach 152<br/>7.4 Architectural Solution 152<br/>7.5 Architecture Business Cycle Today 160<br/>CHAPTER 8 CORBA: A Case Study of an Industry Standard Computing Infrastructure 165<br/>8.1 Relationship to the Architecture Business Cycle 166<br/>8.2 Requirements and Qualities 169<br/>8.3 Architectural Approach 171<br/>8.4 Architectural Solution 174<br/>8.5 The Web and CORBA 184<br/>CHAPTER 9 Analyzing Development Qualities at the Architectural Level: The Software Architecture Analysis Method 189<br/>9.1 The How and Why of Analyzing Software Architecture 190<br/>9.2 Overview of Software Architecture Analysis Method 193<br/>9.3 A Small Example of SAAM Application 198<br/>9.4 SAAM Applied to a Financial Management System 202<br/>9.5 SAAM Applied to a Revision-Control System 210<br/>9.6 Observations on SAAM 216<br/>CHAPTER 10 Architecture Reviews 221<br/>10.1 Costs and Benefits 222<br/>10.2 Review Techniques 225<br/>10.3 The Review Practice 230<br/>CHAPTER 11 Air Traffic Control: A Case Study in Designing for High Availability 239<br/>11.1 Relationship to the Architecture Business Cycle 242<br/>11.2 Requirements and Qualities 243<br/>11.3 Architectural Approach 244<br/>11.4 Architectural Solution 245<br/>11.5 Assessing the Architecture for Maintainability 259<br/>Part Three Moving From Architectures to Systems 265<br/>CHAPTER 12 Architecture Description Languages 267<br/>12.1 Architecture Description Languages Today 269<br/>12.2 Capturing Architectural Information in an ADL 271<br/>12.3 How Do ADLs Help System Development? 273<br/>12.4 Choosing an ADL 274<br/>12.5 An Example of an ADL 277<br/>CHAPTER 13 Architecture-Based Development 285<br/>13.1 Forming the Team Structure 285<br/>13.2 Creating a Skeletal System 288<br/>13.3 Exploiting Patterns in Software Architecture 291<br/>13.4 Ensuring Conformance to an Architecture 297<br/>13.5 Building Domain-Specific Languages 299<br/>CHAPTER 14 Flight Simulation: A Case Study in Architecture for Integrability 303<br/>14.1 Relationship to the Architecture Business Cycle 304<br/>14.2 Requirements and Qualities 305<br/>14.3 Architectural Approach 307<br/>14.4 Architectural Solution 308<br/>14.5 Achievement of Goals 325<br/>Part Four Reusing Architectures 329<br/>CHAPTER 15 Product Lines: Reusing Architectural Assets within an Organization 331<br/>15.1 Creating Products and Evolving a Product Line 333<br/>15.2 Organizational Implications of a Product Line 334<br/>15.3 Component-Based Systems 337<br/>CHAPTER 16 CelsiusTech: A Case Study in Product Line Development 345<br/>16.1 Relationship to the Architecture Business Cycle 345<br/>16.2 Requirements and Qualities 363<br/>16.3 Architectural Approach 365<br/>CHAPTER 17 Communitywide Reuse of Architectural Assets 375<br/>17.1 Reference Architectures 375<br/>17.2 Open Systems 380<br/>17.3 The Process of Engineering an Open System 383<br/>17.4 Standards 385<br/>CHAPTER 18 The Meteorological Anchor Desk System: A Case Study in Building a Web-Based System from Off-the-Shelf Components 395<br/>18.1 Relationship to the Architecture Business Cycle 397<br/>18.2 Requirements and Qualities 398<br/>18.3 Architectural Approach 402<br/>18.4 Architectural Solution 404<br/>CHAPTER 19 Software Architecture in the Future 417<br/>19.1 The Architecture Business Cycle Revisited 418<br/>19.2 Architecture and Legacy Systems 419<br/>19.3 Achieving an Architecture 422<br/>19.4 From Architecture to System 427
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia INGENIERIA DEL SOFTWARE
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia ARQUITECTURA DE SOFTWARE
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia ATAM
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia CBAM
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia SOFTWARE ARCHITECTURE
700 1# - PUNTO DE ACCESO ADICIONAL--NOMBRE DE PERSONA
Nombre personal Clements, Paul
700 1# - PUNTO DE ACCESO ADICIONAL--NOMBRE DE PERSONA
Nombre personal Kazman, Rick
942 ## - ELEMENTOS DE PUNTO DE ACCESO ADICIONAL (KOHA)
Tipo de ítem Koha Libros
Esquema de clasificación Clasificación Decimal Universal
999 ## - NÚMEROS DE CONTROL DE SISTEMA (KOHA)
-- 41027
-- 41027
Holdings
Estado Estado perdido Tipo de préstamo Localización permanente Ubicación/localización actual Fecha de adquisición Número de inventario Total Checkouts ST completa de Koha Código de barras Date last seen Número de copias Tipo de ítem Koha
      Facultad Regional Santa Fe Facultad Regional Santa Fe 02/02/2018 9320   004.41 B293 1998 9320 02/02/2018 02/02/2018 Libros
      Facultad Regional Santa Fe Facultad Regional Santa Fe 02/02/2018 9321   004.41 B293 1998 9321 02/02/2018 02/02/2018 Libros