| 000 | 05784nam a22003493i 4500 | ||
|---|---|---|---|
| 999 |
_c25650 _d25650 |
||
| 001 | EBC5127467 | ||
| 003 | MiAaPQ | ||
| 005 | 20190107152053.0 | ||
| 006 | m o d | | ||
| 007 | cr cnu|||||||| | ||
| 008 | 181231s2009 xx o ||||0 eng d | ||
| 020 |
_a9788131742112 _q(electronic bk.) |
||
| 035 | _a(MiAaPQ)EBC5127467 | ||
| 035 | _a(Au-PeEL)EBL5127467 | ||
| 035 | _a(CaONFJC)MIL266301 | ||
| 035 | _a(OCoLC)1024276458 | ||
| 040 |
_aMiAaPQ _beng _erda _epn _cMiAaPQ _dMiAaPQ |
||
| 082 |
_223 _a005.1 |
||
| 100 | 1 | _aVarma, vasudeva. | |
| 245 | 1 | 0 | _aSoftware Architecture. |
| 300 | _a1 online resource (280 pages) | ||
| 505 | 0 | _aCover -- 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 | _aStep 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 | _aFurther 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 | _aThis 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 | _aElectronic 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 | _aElectronic books. | |
| 776 | 0 | 8 |
_iPrint version: _aVarma, vasudeva _tSoftware Architecture: A Case Based Approach _dNoida : Pearson India,c2009 |
| 797 | 2 | _aProQuest (Firm) | |
| 856 | 4 | 0 |
_uhttps://ebookcentral.proquest.com/lib/cethalassery/detail.action?docID=5127467 _zClick to View |
| 942 |
_2ddc _cBK |
||