- Introduction to Software Security
- Nov 2, 2001
- The root of most security problems is software that fails in unexpected ways. Although software security as a field has much maturing to do, it has much to offer to those practitioners interested in striking at the heart of security problems.
|
- Modeling and Analysis with the AADL: The Basics
- Nov 1, 2012
- In this chapter, the authors illustrate the development of basic AADL models and present general guidance on the use of some of the AADL’s core capabilities in order to provide a basic understanding of architectural modeling and analysis and start you on your way in applying the AADL to more complex software-dependent systems.
|
- On Architecture: From Small to Gargantuan
- Jul 5, 2006
- In their innovative book A Pattern Language, Christopher Alexander and his colleagues describe the patterns that breathe life into civil architectures, from intimate spaces to buildings to entire towns. No matter where you look along this spectrum of size, you’ll find common structures and common behaviors. At each point in the spectrum, the patterns therein form the architecture of each instance.
Across the software landscape, you’ll find a similar spread, from small programs to systems to systems of systems. Each instance has an architecture, be it intentional or accidental, and the forces that work upon each system—from small to gargantuan—vary accordingly.
|
- Organizational Savvy: The Missing Piece in Software Architecture Education
- Apr 19, 2002
- Today, more and more software professionals assume the role and title of software architect. Like building architects, software architects need to draw on a broad range of disciplines to be effective, and like their earlier namesakes, organizational savvy is also an important part of this skill set.
|
- Paradoxes of Software Architecture
- Nov 6, 2012
- Many of the ideals we strive for in software architecture ultimately contribute to the system's demise. Kirk Knoernschild, author of Java Application Architecture: Modularity Patterns with Examples Using OSGi, explores the paradoxes of software architecture, examining how "architecture all the way down" and modularity can help.
|
- Patterns: An Antidote for "Best" Practices Gone Bad
- May 10, 2002
- Incorporating innovative approaches remains critical to an organization's survival. How can this be done without encountering the pitfalls of one-size-fits-all best practice efforts? Patterns provide an alternative approach to incorporating practices in appropriate situations successfully.
|
- Preface to 12 More Essential Skills for Software Architects
- Jul 30, 2014
- Dave Hendricksen introduces his book, 12 More Essential Skills for Software Architects; learn the three sets of skills that will have the greatest impact on your ability to succeed and ascend.
|
- Prologue: Software Architectures and Documentation
- Nov 11, 2010
- This prologue to Documenting Software Architectures: Views and Beyond, 2nd Edition begins with short overviews of software architecture and architecture documentation and then discusses architecture views, architecture styles and rules for sound documentation.
|
- Service Oriented Architecture with Apache Axis
- Nov 22, 2006
- Service oriented architecture has moved beyond hype and into implementation. Apache Axis provides a compelling solution in terms of TCO, standards-compliance, manageability, and ease of use. So, how good is Axis? Read Stephen Morris' article to find out.
|
- So Now I'm A Software Architect. What Do I Actually Do?
- Oct 6, 2005
- A key part of the software architect's job is producing an architectural description of the system that defines the architecture's key functions, features, and characteristics for its stakeholders. Where do you start? What do you need to know? Nick Rozanski and Eóin Woods provide detailed answers to these questions, with useful suggestions on how to attack this fundamental document that underpins any development project.
|
- SOA Project Planning Aspects
- Nov 18, 2005
- This chapter takes the next step toward execution by focusing on how to plan an SOA project. The topics in this chapter constitute the best practices the authors have uncovered for forming a project office, how to define the phases of SOA adoption, the need for and mechanisms of SOA governance, and finally, the various project roles and how they interact with each other.
|
- Software Architecture in Practice: the Luther Architecture
- Jun 20, 2003
- Discover the role of Luther in the rapid building of customer support systems for Inmedius. You will see examples of wearable computers used by workers in the field and how the system based on J2EE is working toward continual innovation.
|
- Software Architecture: Basic Training
- Apr 16, 2004
- This chapter introduces the fundamental concepts of object orientation, open systems, and object-oriented architectures. It also discusses object orientation in terms of isolating changes in software systems by combining the data and processing into modules called objects.
|
- Software Architecture: The Difference between Marketecture and Tarchitecture
- Jun 6, 2003
- Luke Hohmann clarifies how the marketing and technical aspects of the software architecture system must work together to achieve business objectives.
|
- Software Architecture: The What and Why
- Jan 11, 2016
- This chapter from Practical Software Architecture: Moving from System Context to Deployment provides some background on the discipline of software architecture and some of the time-tested value drivers that justify its adoption.The chapter ends by laying some groundwork for the essential elements of the discipline.
|
- Software Futures: Architecture
- Mar 25, 2005
- Network management specialist Stephen Morris discusses the growing trend toward architecture orientation in software development and how this trend relates to the general area of software engineering.
|
- Software Systems Architecture: Viewpoints and Views
- Nov 10, 2011
- Capturing the essence and the detail of the whole architecture in a single model is just not possible for anything other than simple systems. By far the best way of managing this complexity is to produce a number of different representations of all or part of the architecture, each of which focuses on certain aspects of the system, showing how it addresses some of the stakeholder concerns.
|
- Strategies for Real-Time System Specification: Creating the System Architecture Model
- Oct 2, 2013
- The authors of Strategies for Real-Time System Specification explain how to use the architecture model to map the enhanced requirements model allocations to architecture modules.
|
- Surviving Product Management
- Mar 3, 2006
- In his years as product manager for a wide variety of tech products, Louis Columbus has learned several useful lessons regarding what strategies work best to support the products and, ultimately, the company's bottom line. Share his knowledge in this article.
|
- The Accidental Architecture
- Jun 2, 2006
- Every interesting software-intensive system has an architecture. While some of these architectures are intentional, most appear to be accidental. Grady Booch explains.
|