Tag Archives: systems architecture

Introduction to the Architecture Analysis and Description Language (AADL)

When a system fails, engineers too often focus on the physical components, but pay scant attention to the software. In software-reliant systems ignoring or deemphasizing the importance of software failures can be a recipe for disaster. This blog post at the SEI Blog is the first in a series on recent developments with the Architecture Analysis Design Language (AADL) standard. First published in 2004 by SAE International, AADL is a modeling notation that employs both a textual and graphical representation. AADL provides modeling concepts to describe the runtime architecture of application systems in terms of concurrent tasks, their interactions, and their mapping onto an execution platform. Development organizations use AADL to conduct lightweight, rigorous, yet comparatively inexpensive analyses of critical real-time factors such as performance, dependability, security, and data integrity. Use of AADL helps alleviate mismatched assumptions between the hardware, software, and their interactions that can lead to system failures.

This podcast, an interview with Julien Delange and Peter Feiler of the SEI, covers the latest developments in AADL.

Advertisements

SEI Virtual Tutorial, Feb. 27 (Part 1): Architecture & Design of Service-Oriented Systems

Architecture and Design of Service-Oriented Systems

Date: February 27, 2013 (Part 1)
Time: 
1:30 – 3:00 PM ET
Cost: None

Register now.

About the Tutorial

SOA is not an architecture. SOA is not a system. SOA is a way of designing systems, an approach to system development, an architectural style, a design paradigm.  As an architectural style, SOA can be described in terms of components and connectors. The main components are the services, service consumers, and SOA infrastructure. The connectors are predominantly message-based document exchanges. In essence, SOA is an architectural style and an approach to software development that goes with the style. You do not “build a SOA,” you “build a service-oriented system.”

Continue reading

Available Now: SOA Migration, Adoption, and Reuse Technique (SMART) Resources

The SEI often works to transition mature technologies and processes to the broad software engineering community, and to accelerate the adoption and impact of software engineering improvements. In that spirit, the SEI has made all of its SOA Migration, Adoption and Reuse Technique (SMART) resources freely available. These resources comprise all the SMART training materials, processes, and artifacts. SMART is a family of techniques created by the SEI to help organizations make better decisions about service-oriented architecture (SOA) adoption.

Learn more in this article about SMART on the SEI website.

To download the SEI’s SMART Family resources, please visit http://www.sei.cmu.edu/architecture/tools/smart/index.cfm.

SEI Virtual Event: Architecting in a Complex World

SEI Virtual Event: Architecting in a Complex World

Don’t let complexity defeat your system development effort. This SEI virtual event takes you in depth into three keys to succeed with system development in the midst of complexity.

Date: January 16, 2013
Time: 1:00 – 4:00 PM ET
Cost: Complimentary

Register now.

About the Event

Continue reading

Reflections on 20 Years of Software Architecture: A Presentation by Robert Schwanke

Here is the third in our series of blog posts at the SEI blog that provides lightly edited transcripts of remarks by SATURN 2012 panelists on the theme of “Reflections on 20 Years of Software Architecture.” The session was moderated by Rick Kazman of the SEI, and panelists were Linda Northrop of the SEI, Doug Schmidt of Vanderbilt University, Ian Gorton of Pacific Northwest National Lab, Robert Schwanke of Siemens Corporate Research, and Jeromy Carriere of X.commerce/eBay.

Read the third in the series, Reflections on 20 Years of Software Architecture: A Presentation by Robert Schwanke, who reflected on four general problems in software architecture: modularity, systems of systems, maintainable architecture descriptions, and system architecture.

SEI Blog: Reflections on 20 Years of Architecture: A Presentation by Douglas C. Schmidt

Here is the second in our series of blog posts at the SEI blog that provides lightly edited transcripts of remarks by SATURN 2012 panelists on the theme of “Reflections on 20 Years of Software Architecture.” The session was moderated by Rick Kazman of the SEI, and panelists were Linda Northrop of the SEI, Doug Schmidt of Vanderbilt University, Ian Gorton of Pacific Northwest National Lab, Robert Schwanke of Siemens Corporate Research, and Jeromy Carriere of X.commerce/eBay.

Read the second in the series, Reflections on 20 Years of Software Architecture: A Presentation by Douglas C. Schmidt, who discussed advances in software architecture practice for distributed real-time embedded systems during the past two decades.

SEI Contributes to a National Supercomputing Initiative

For more than 10 years, scientists, researchers, and engineers used the TeraGrid supercomputer network funded by the National Science Foundation (NSF) to conduct advanced computational science. The SEI has joined a partnership of 17 organizations and helped develop the successor to the TeraGrid called the Extreme Science and Engineering Discovery Environment (XSEDE). This post at the SEI blog, which is the first in a multi-part series, describes SEI work on XSEDE that allows researchers open access—directly from their desktops—to the suite of advanced computational tools and digital resources and services provided via XSEDE. This series is not so much concerned with supercomputers and supercomputing middleware, but rather with the nature of software engineering practice at the scale of the socio-technical ecosystem.

SEI Contributes to a National Supercomputing Initiative, at SEI blog.

SATURN 2013, Minneapolis MN April 29-May 3: Call for Submissions

In 2013, the Software Engineering Institute (SEI) Architecture Technology User Network (SATURN) software architecture onference will celebrate its 9th year. Each year SATURN attracts an international audience of practicing software architects, industry thought leaders, developers, technical managers, and researchers to share ideas, insights, and experience about effective architecture-centric practices for developing and maintaining software-intensive systems.

Continue reading

Rapid Lifecycle Development in an Agile Context

This blog post at the SEI blog describes research on providing software and systems architects with a decision-making framework for reducing integration risk with Agile methods, thereby reducing the time and resources needed for related work.

The research explores the implications of decisions made over the course of the software and systems lifecycle. It examines when these decisions are made and the time when the implications surface to validate the following hypotheses:

  1. The fundamental early decisions made during the pre-engineering and manufacturing development (pre-EMD) phase have an impact throughout the lifecycle.
  2. The implications of the early decisions often surface in the final stages of the lifecycle, downstream from development.

Read the full post here.

A New Approach for Handheld Devices in Tactical Networks

The U.S. Department of Defense (DoD) is increasingly interested in having soldiers carry handheld computing devices to support their mission needs in tactical networks. Not surprisingly, however, conventional handheld computing devices (such as iPhone or Android smartphones) for commercial networks differ in significant ways from handheld devices for tactical networks. For example, conventional devices and the software that runs on them do not provide the capabilities and security needed by military devices, nor are they configured to work over DoD tactical networks with severe bandwidth limitations and stringent transmission security requirements.

This post at the new SEI blog describes exploratory research that the SEI is conducting to (1) create software that allows soldiers to access information on a handheld device and (2) program the software to tailor the information for a given mission or situation.