Einar Landre and Jørn Ølmheim, Statoil
by Jacob Tate, Mount St. Mary’s University
Einar Landre presented an experience report at the last morning session titled “Systems of Action: A Stack Model for Capability Classification.” The subject matter of this presentation delved into the importance of structuring a class of systems that can observe phenomena or processes and then interpret this data and make intelligent decisions.
WICSA/CompArch 2015 – 12th Working IEEE / IFIP Conference on Software Architecture and 9th Federated Conference Series Component-Based Software Engineering and Software Architecture
Call for Workshop Papers
May 4-8, 2015 Montreal, Canada
WICSA | CompArch 2015 workshops provide a unique forum for researchers and practitioners to present and discuss the latest R&D results, experiences, trends, and challenges in the field of software architecture, component-based software engineering, and software system qualities.
Software Architecture Modeling
Coding Is Not the New Literacy: In a recent blog post, Chris Granger argues, “We build mental models of everything—from how to tie our shoes to the way macro-economic systems work. With these, we make decisions, predictions, and understand our experiences. If we want computers to be able to compute for us, then we have to accurately extract these models from our heads and record them. Writing Python isn’t the fundamental skill we need to teach people. Modeling systems is.” Continue reading
Posted in Architecture-Centric Engineering, Architecture-Centric Practices, Link Roundup, SATURN Conference
Tagged architecture modeling, model-based engineering, SATURN 2015, SATURN Conference, software architecture, software architecture requirements, software design, software development, software engineering
Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim
Expanding Legacy Systems Using Model-Driven Engineering (MDE)
William Smith, Northrop Grumman
Kevin Nguyen, Northrop Grumman
Kevin Nguyen and his fellow engineers faced a common problem of dealing with legacy systems. At their environment (Northrop Grumman), they are dealing with rigid defense systems. Kevin tried to adapt a model-driven engineering approach in his work to achieve his goals. The team used conceptual software architecture to help understand customer requirements. Next, they refined the requirements into a CSCI architecture of software and hardware. Then, they tried to expand the CSCI architecture into CSC architecture (more detailed and lower level models). Finally, the team tried to convert that into a detailed design for the software unit. They went through these steps following a basic procedure of software-design life cycle.
by Neil Ernst, SATURN 2014 Tutorials Chair
We have a great tutorial line-up this year that I would like to share. Since tutorials at SATURN are half-day sessions, they provide the presenters time for an in-depth exploration. I think attendees of SATURN 2014 will be particularly impressed by the breadth and depth of our program.
On Tuesday, May 6, we have five tutorials scheduled.
- George Fairbanks, Google, and author of Just Enough Software Architecture, will cover “Architecture Hoisting” (T1), techniques for moving responsibility from the code to the architecture.
- Stephany Bellomo and Rick Kazman, from the Software Engineering Institute, in Tutorial T2, will introduce deployability and DevOps techniques, then discuss architectural approaches and patterns to reduce build time and shorten the feedback cycle.
- In the afternoon sessions, Len Bass, of Australia’s National IT Research Centre, will discuss the implications of DevOps on system design (T3). For example, how does moving to a continuous-deployment approach change how the architecture is designed and implemented? This makes a nice complement to the earlier tutorial from Bellomo and Kazman for those desiring a full menu of deployability fare.
- Pradyumn Sharma (@PradyumnSharma) of Pragati Software will cover NoSQL databases (T4). If you’ve been hearing this term for a few years now and need to really get a good sense for the landscape, Pradyumn will cover the fundamentals for you, basing the session on real-world examples.
- Finally on Tuesday, Eltjo Poort (@eltjopoort) of CGI will cover the CGI Risk and Cost-Driven Architecture approach (RCDA) in T5. He will discuss how CGI has used RCDA to implement lean and agile architectures in their global software business. RCDA is a recognized architecture method in The Open Group’s architect certification program.
Posted in Architecture and Agile, Architecture-Centric Engineering, Architecture-Centric Practices, Conferences and Events, Quality Attribute Analysis, SATURN Conference
Tagged agile release planning, architecture evaluation, model-based engineering, non-functional requirements, release planning, SATURN 2014, SATURN Conference, SEI, software architecture, software architecture requirements, software architecture review, software design, software engineering, Software Engineering Institute, technical debt
SATURN 2014 marks the 10th Software Engineering Institute (SEI) Architecture Technology User Network (SATURN) conference—the largest conference dedicated to software architecture in North America. Since 2003, an international audience of practicing software architects, industry thought leaders, developers, technical managers, and researchers have gathered at SATURN to share ideas, insights, and experiences about effective architecture-centric practices for developing and maintaining software-intensive systems.
SATURN 2014 will take place in Portland, Oregon from May 5—May 9, 2014.
Posted in Architecture-Centric Engineering, Architecture-Centric Practices, Conferences and Events, SATURN Conference
Tagged AADL, architecture evaluation, architecture review, Architecture Tradeoff Analysis Method, ATAM, attribute-driven design, cloud computing, model-based engineering, non-functional requirements, SATURN 2014, SATURN Conference, SATURN Network, SEI, software architecture, software architecture evaluation, software architecture review, software design, software development, software engineering, Software Engineering Institute, technical debt, testing
Notes by Brendan Foote
How to Build, Implement, and Use an Architecture Metamodel
Chris Armstrong, Armstrong Process Group, Inc.
Armstrong discussed the architecture-description standard UML model, showing how an architecture description expresses an architecture, fulfills the concerns of stakeholders, and more. He uses the difference between raw accounting data and the common views the way, say, a CFO would need to because of the way that an architecture is standardized by the RFC 42010 (that is, what subset of the entire UML model is particularly useful?). This leads to his refined viewpoint metamodel. His process group has added the “architecture scenario” to the metamodel, which he points out is not in conflict with the standard. This scenario is defined by a stakeholder, and it contextualizes an architectural concern. He goes on to show how stakeholders and concerns are also connected by architecture viewpoints, of which there are several types. Those types are defined differently depending on whether you talk to TOGAF, DoDAF, etc., but a modeling system should allow you to render your viewpoints in different ways for different consumers (e.g., a grid, diagram, catalog, or dashboard).
As program chairs for SATURN 2013, we would like to provide you an overview of the presentation program (note: information about keynotes by Stephan Murer, Scott Berkun, and Mary Poppendieck, the invited talk by Philippe Kruchten, and tutorial highlights is already available in other blog posts).
We received many high quality submissions covering the topics of front-end architecture, back-end architecture, methods and tools, and technical leadership. In total we got contributions from more than 40 companies and organizations across three continents.
On Wednesday morning you have the tough choice to decide between three great sessions. For example, Harald Wesenberg from Statoil speaks about architecting for the long term in Session 1. In Session 2, Chris Armstrong presents ISO/IEC/IEEE 42010 in action, while Session 3 deals with agile practices at scale.
Posted in Architecture and Agile, Architecture-Centric Engineering, Architecture-Centric Practices, Cloud Computing, Conferences and Events, Quality Attribute Analysis, SATURN Conference, Secure and Assured Mobile Computing Components, Service-Oriented Architecture
Tagged AADL, agile release planning, architecture evaluation, architecture review, Architecture Tradeoff Analysis Method, ATAM, cloud computing, model-based engineering, non-functional requirements, release planning, SATURN 2013, SATURN Conference, SEI, SOA, software architecture, software architecture evaluation, software architecture requirements, software architecture review, software design, software development, software engineering, Software Engineering Institute
To help developers make the most of the Architecture Analysis and Design Language (AADL), two SEI researchers published Model-Based Engineering with AADL (Addison-Wesley Professional 2012), about which we blogged here in October.
The book has been selected for Intel Corporation’s Recommended Reading List for the first half of 2013.
Our Recommended Reading Program provides technical professionals a simple and handy reference list of what to read to stay abreast of new technologies. Dozens of industry technologists, corporate fellows, and engineers have helped by suggesting books and reviewing the list. This is the most comprehensive reading list available for professional computer Developers.
International Workshop on the Engineering of Mobile-Enabled Systems (MOBS 2013)
Co-located with the 35th International Conference on Software Engineering (ICSE 2013)
May 25, 2013 — San Francisco, CA USA
Submission Deadline: February 7, 2013
Acceptance Notification: February 28, 2013
Camera-Ready Version: March 7, 2013
Mobile apps are becoming important parts of enterprise and mission-critical systems that make use of contextual information to optimize resource usage and drive business and operational processes. Mobile technology is also reaching people in the field across multiple domains to help with various tasks such as speech and image recognition, natural language processing, decision-making, and mission planning.