By Jeff Garland
ISBN-10: 0470848499
ISBN-13: 9780470848494
ISBN-10: 0470856386
ISBN-13: 9780470856383
Meant as a consultant for software program architects, their managers, and different improvement workforce participants engaged on large-scale software program improvement tasks similar to firm platforms and massive dispensed platforms, this e-book covers crucial details on defining the software program structure of huge initiatives. suggestions mentioned is additionally utilized to smaller initiatives and embedded platforms. insurance progresses from roles of the software program architect and the improvement approach via UML, subsystem layout, and structure options. The authors are skilled software program architects.
Read or Download Large-Scale Software Architecture: A Practical Guide using UML PDF
Similar design & architecture books
Chip multiprocessors - often known as multi-core microprocessors or CMPs for brief - at the moment are the single method to construct high-performance microprocessors, for numerous purposes. huge uniprocessors aren't any longer scaling in functionality, since it is simply attainable to extract a constrained quantity of parallelism from a standard guide move utilizing traditional superscalar guideline factor strategies.
Principles of Data Conversion System Design by Behzad Razavi PDF
This complex textual content and reference covers the layout and implementation of built-in circuits for analog-to-digital and digital-to-analog conversion. It starts off with simple ideas and systematically leads the reader to complex themes, describing layout concerns and methods at either circuit and approach point.
William J. Dally (auth.)'s A VLSI Architecture for Concurrent Data Structures PDF
Concurrent information constructions simplify the improvement of concurrent courses by way of encapsulating well-known mechanisms for synchronization and commu nication into information buildings. This thesis develops a notation for describing concurrent information buildings, provides examples of concurrent info buildings, and describes an structure to help concurrent information buildings.
- Ansible Configuration Management
- Storage Area Networking Essentials: A Complete Guide to Understanding & Implementing SANs
- The cloud at your service : the when, how, and why of enterprise cloud computing
- Principles of Modern Operating Systems
- Sun Certified Enterprise Architect for Java EE Study Guide (Exam 310-051)
Additional resources for Large-Scale Software Architecture: A Practical Guide using UML
Example text
The Deployment View shows the mapping of hardware and software for distributed systems. The Physical Database View illustrates the physical deployment structures of databases. The Process View shows the execution threads of the system and often the mapping to components. The Process State View shows the dynamic states for a process. 3 Environment/Physical viewpoint summary Viewpoint UML diagram type Description Chapter Deployment Deployment Mapping of software to hardware for distributed systems.
Relationship to Software Architect: The software architect must communicate the overall software design to the system architect. This includes interfaces between development teams, external interfaces, requirements-related issues, and dependencies from other organizations that may impact the software development. In addition, the software architect will work closely with the chief engineer to identify and resolve significant technical issues. Role: chief software engineer Description: In some organizations, a role of chief software engineer (CSE) is separate from the software architect.
Each individual can then focus on what they do best, leaving the release management tasks to the manager and the technical issues to be worked out by the technical lead. This lead is responsible for technical aspects of the interfaces, defects, building, testing, and delivery of the software. These technical leads will often participate in the definition of and modifications to the software architecture. Relationship to Software Architect: First, the software architect must deliver a set of architecture views to the technical lead that clearly communicates the system under development and test for that release.
Large-Scale Software Architecture: A Practical Guide using UML by Jeff Garland
by Brian
4.1