Software Architecture. (Record no. 25650)

MARC details
000 -LEADER
fixed length control field 05784nam a22003493i 4500
001 - CONTROL NUMBER
control field EBC5127467
003 - CONTROL NUMBER IDENTIFIER
control field MiAaPQ
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20190107152053.0
006 - FIXED-LENGTH DATA ELEMENTS--ADDITIONAL MATERIAL CHARACTERISTICS--GENERAL INFORMATION
fixed length control field m o d |
007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION
fixed length control field cr cnu||||||||
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 181231s2009 xx o ||||0 eng d
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9788131742112
Qualifying information (electronic bk.)
035 ## - SYSTEM CONTROL NUMBER
System control number (MiAaPQ)EBC5127467
035 ## - SYSTEM CONTROL NUMBER
System control number (Au-PeEL)EBL5127467
035 ## - SYSTEM CONTROL NUMBER
System control number (CaONFJC)MIL266301
035 ## - SYSTEM CONTROL NUMBER
System control number (OCoLC)1024276458
040 ## - CATALOGING SOURCE
Original cataloging agency MiAaPQ
Language of cataloging eng
Description conventions rda
-- pn
Transcribing agency MiAaPQ
Modifying agency MiAaPQ
082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER
Edition number 23
Classification number 005.1
100 1# - MAIN ENTRY--PERSONAL NAME
Personal name Varma, vasudeva.
245 10 - TITLE STATEMENT
Title Software Architecture.
300 ## - PHYSICAL DESCRIPTION
Extent 1 online resource (280 pages)
505 0# - FORMATTED CONTENTS NOTE
Formatted contents note Cover -- A Case Based Approach -- Copyright -- Contents -- Foreword -- Preface -- Acknowledgements -- About the Author -- Software Architecture Primer -- The Discipline of Software Architecture -- The Rise and fall of Netscape (or the Browser War 1994-1999) -- The Growing Demands on Software Development -- What is software architecture? -- The Importance of Software Architecture -- Role of a Software Architect -- Some Important Terms used in Software Architecture -- Software Architecture Concepts -- Types of Architectures -- Architectural Drivers -- Software Architecture Frameworks -- Architectural Styles or Architectural Patterns -- Software Architecture as A Problem-Solving Activity -- Polya's How to Solve It-A Problem-Solving Guide -- Systems Thinking Approach to Problem Solving -- Further Reading -- Where is the Architecture? Story of a Sick Health Insurance Application -- Background -- Case Study: Assure-Health-Story of a Sick Health InsuranceApplication -- Postmortem -- Why is Software Architecture Important? -- Role of Architecture in Software Development -- The use Case Analysis -- The Technical Process of Designing Architectures -- Case Analysis -- Conclusions -- Best Practices and Key Lessons from the Case Study -- Further Reading -- Refining and Re-factoring Architecture-Story of McCombbs Call Centre -- Background -- Case Study: Technical Architecture of McCombbs Call CentreSoftware -- Postmortem -- Software Architecture Goals and Drivers -- Software Architecture Patterns and Anti-Patterns -- Performance-Oriented Design -- Performance Objectives -- Performance Improvement -- Understanding Architecture -- Identifying Key Scenarios -- Identifying Problem Areas or Bottlenecks -- Refining the System -- Case Analysis -- Step 1: 4 + 1 View Model of the Proposed Architecture -- Step 2: Prepare for the Evaluation.
505 8# - FORMATTED CONTENTS NOTE
Formatted contents note Step 3: Execute the Evaluation -- Step 4: Reflect the Evaluation -- Conclusions -- Best Practices and Key Lessons from the Case Study -- Further Reading -- Architecture Evaluation-Developing a Futuristic Travel Search Engine -- Background -- What Is Architectural Evaluation? -- Why Should Architecture Be Evaluated and Reviewed? -- When to Evaluate and Review? -- Who Should Evaluate and Review? -- What Should Be Reviewed? -- How to Review Architectures? -- Case Study: Evluating the Architecture of a Futuristic Traval Search Engine -- Postmortem -- Techniques for Evaluation and Review -- A Review Method for Architectural Description and Architecting Process -- Scenario-Based Review Methods -- Case Analysis -- Which Method to use? -- Software Architecture Analysis Method -- Conclusion -- Best Practices and Key Lessons from the Case Study -- Further Reading -- Moving from Software Architecture to Software Design-Building a Mobile Trading System -- Background -- What is Design? -- Design Notations -- Case Study: Mobile Trading System -- Postmortem -- The Design Process -- Moving from Architecture to Design -- Step 1: Defi ning System Context -- Step 2: Identifying the Modules -- Step 3: Describing the Components and Connectors -- Characteristics of a Good Design -- Case Analysis -- Use Case Specification -- Sequence Diagrams -- Class Diagrams -- Conclusions -- Best Practices and Key Lessons from the Case Study -- Further Reading -- Component-based Development: Portal of Universal Bank -- Background -- Why Component-Based Development? -- Origin of CDB -- Some Examples of Cost of 'From the Scratch' Development -- Case Study: Component-Based Development for Universal Bank Portal -- Postmortem -- The Component-Based Development Approach -- Success Factors of CDB -- Challenges to Adopting CDB -- Conclusions -- Best Practices and Key Lessons from the Case Study.
505 8# - FORMATTED CONTENTS NOTE
Formatted contents note Further Reading -- Emerging Trends in Software Architecture -- Software Architecture Discipline-Past, Present and Future -- Reusability and Reusable Services -- Service-Oriented Architecture -- Dimensions of Future Software Architecture -- Critical Software Architecture Elements -- Conclusions -- Further Reading -- References -- Index.
520 ## - SUMMARY, ETC.
Summary, etc This book discusses the discipline ofSSoftware Architecture using real-world case studies and posing pertinent questions that arouse objective thinking. It encourages the reader to think about the subject in the context of problems that software architects solve, the tools they use and the constraints under which they operate. To this end, a case study is provided at the beginning of most chapters, followed by an in-depth analysis that delves into the core issues and challenges of software architecture.
590 ## - LOCAL NOTE (RLIN)
Local note Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2018. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
655 #4 - INDEX TERM--GENRE/FORM
Genre/form data or focus term Electronic books.
776 08 - ADDITIONAL PHYSICAL FORM ENTRY
Display text Print version:
Main entry heading Varma, vasudeva
Title Software Architecture: A Case Based Approach
Place, publisher, and date of publication Noida : Pearson India,c2009
797 2# - LOCAL ADDED ENTRY--CORPORATE NAME (RLIN)
Corporate name or jurisdiction name as entry element ProQuest (Firm)
856 40 - ELECTRONIC LOCATION AND ACCESS
Uniform Resource Identifier <a href="https://ebookcentral.proquest.com/lib/cethalassery/detail.action?docID=5127467">https://ebookcentral.proquest.com/lib/cethalassery/detail.action?docID=5127467</a>
Public note Click to View
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Source of classification or shelving scheme Dewey Decimal Classification
Koha item type Books
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Materials specified (bound volume or other part) Damaged status Not for loan Home library Current library Shelving location Date acquired Total Checkouts Full call number Barcode Date last seen Price effective from Koha item type
    Dewey Decimal Classification Online access     CENTRAL LIBRARY Digital Library Digital Library 07/01/2019   005.1 VAR-S E0179 07/01/2019 07/01/2019 E- Books
Powered by Koha ILS
Page Design & Customization: Library Web Team CE Thalassery