Category Archives: Architecture-Centric Engineering

Sixth International Workshop on Managing Technical Debt

Sixth International Workshop on Managing Technical Debt
Co-located with 30th International Conference on Software Maintenance and Evolution (ICSME 2014)
Victoria, British Columbia, Canada
September 30, 2014
http://www.sei.cmu.edu/community/td2014/

Technical debt is a metaphor that software developers and managers increasingly use to communicate key tradeoffs related to release and quality issues. The Managing Technical Debt workshop series has, since 2010, brought together practitioners and researchers to discuss and define issues related to technical debt and how they can be studied. Workshop participants reiterate the usefulness of the metaphor each year, share emerging practices used in software development organizations, and emphasize the need for more research and better means for sharing emerging practices and results.

Continue reading

SATURN 2014 Team Collaboration Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

Transparency: An Architecture Principle for Socio-Technical Ecosystems
Felix Bachmann and Linda Northrop, Software Engineering Institute

Felix and Linda shared their experience as a team in the XSEDE project. They presented compelling evidence of the need to have transparent architecture and architectural practices in socio-technical ecosystems like XSEDE. XSEDE is a virtual, high-performance computer system that allows interactivity for scientists (e.g., biologists, mechanical engineers, environmentalists) all over the world to run their experiments. Experiments are usually of the types that need super-powerful computing capabilities. The system is distributed over a wide distance, and engineers or developers have different global and local priorities. Due to the size of the project and the high complexity, architectural guidance was necessary to ensure the success of the project. Felix’s and Linda’s team responsibilities are to help the team make the right architectural decisions, coach the team on how to incorporate architectural practices, and research missions.

Continue reading

SATURN 2014 Promoting Quality Attributes: Lessons Learned from the Trenches Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

Can You Hear Me Now? The Art of Applying Communication Protocols When Architecting Real-Time Control Systems
Todd Farley, BAE Systems, Inc.

BAE Systems deals with architecting real-time control systems. These systems are usually complicated and distributed. Also, the lifetimes of projects are usually very long. So BAE must always answer this question: Which process should they adapt? The problems they face tend to fall into three categories:

  • motion control systems (~robots)
  • computation-intensive algorithms
  • user interfaces

Continue reading

SATURN 2014 Art and Science of Scalability Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

BI/Big Data Reference Architectures and Case Studies
Serhiy Haziyev and Olha Hrytsay, SoftServe, Inc.

Serhiy and Olha shared their experience with the tradeoff between modern and traditional (non-relational and relational) reference architectures. They looked into the challenges associated with each approach and gave tips from real-life case studies on how to deal with big data reference architecture. As a reminder, they visited some of the known big data challenges:

  • Data is generated from many and different sources.
  • As data grows, it becomes complicated and heterogeneous (velocity and volume) until it’s no longer manageable.

Continue reading

SATURN 2014 The Business of Software Architecture Session (notes)

Notes by Ziyad Alsaeed, edited by Tamara Marshall-Keim

Under N: Acceptance to Delivery in N Hours
Umashankar Velusamy, Verizon Communications, Inc.

Umashankar started the presentation with a simple question: Are all deliveries the same? Humans take about 9 months to “deliver” babies. Cats and dogs take about 2 months to do so. So not all deliveries are the same. In the software industry, the same thing applies—different deliveries take different amounts of time. However, we tend to apply a one-size-fits-all solution to everything. Umashankar asked another question: Does it make since to wait 2 weeks or even 2 months for something to deliver, when it takes only 12 hours to deliver? It’s definitely doesn’t make sense, Umashankar answers.

Continue reading

SATURN 2014 Architecting in the Enterprise Session (notes)

Notes by Scott Shipp, edited by Tamara Marshall-Keim

CORBA to Web Services Migration Using Model-Driven Approaches and Offshoring
Georg Huettenegger, Credit Suisse

Huettenegger discussed challenges and lessons learned from migrating one of the world’s largest and most successful CORBA SOAs to a web services SOA.

Credit Suisse is an integrated global bank. It delivers all the possible services that a bank could offer. Credit Suisse employs more than 45,000 people from 160 nations.

The current Credit Suisse SOA is “nice, yet limited.” Where it is headed is not good. It has over 2,500 CORBA service operations, there are 20–30 Mill CORBA calls per day, and there are about 400 consuming applications. With such a large scale and with such widely distributed employees, maybe Agile is not the way to go.

Continue reading

SATURN 2014 DevOps and Delivery Session (notes)

Notes by Scott Shipp, edited by Tamara Marshall-Keim

Impact of Architecture on Continuous Delivery
Russell Miller, SunView Software, Inc.

First, context: This was a greenfield, from-scratch project for a nontrivial social-monitoring tool. It was also their first attempt at the native cloud. It was a pilot for a truly agile project. Go to http://livepulse.co to see a beta version.

Miller uses the term “continuous delivery” (CD) as defined in Jez Humble’s book Continuous Delivery. It leverages continuous integration, automated testing, and automated deployment. Releases are frequent, small, and predictable.

For example, take Amazon drone delivery. It eliminates waste, and customers do not have time to cancel the order. It also provides quicker feedback from the customer. So CD vs. the traditional release model is similar to drone delivery vs. freight train delivery. “This is a good metaphor for lean vs. legacy.”

Continue reading

SATURN 2014 Architectural Modeling Session (notes)

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.

Continue reading

SATURN 2014 Building a Community of Practice Session (notes)

Notes by Scott Shipp, edited by Tamara Marshall-Keim

Creating a Sustainable Architecture Organization
William Beshilas, PwC

Opening question: How many of you lead or manage architects? (show of hands: about 50%)

Agenda:

  1. Intro
  2. Reasons to mature
  3. Office of architect
  4. Rollout approach
  5. Making change stick

Continue reading

SATURN 2014 Growing Great Architects Session (notes)

Notes by Scott Shipp, edited by Tamara Marshall-Keim

Metrics for Simplifying and Standardizing Enterprise Architecture: An Experience Report for an Oil and Gas Organization
Alexis Ocampo (Ecopetrol)
Jens Heidrich (Fraunhofer IESE)
Constanza Lampasona (Fraunhofer IESE)
Victor Basili (University of Maryland, Fraunhofer CESE)

Some data about Ecopetrol S.A.

  • largest petroleum company in Colombia
  • One of four largest Latin American oil and gas companies
  • 1M barrels will be produced 2015
  • Top 40 world oil and gas companies

How can IT contribute?

They have been working on answering this question for several years.

Continue reading