Tag Archives: technical debt

Coming November 3-6, 2014, Pgh. Pa.: TSP Symposium 2014

We at the SEI are excited about the Team Software Process (TSP) Symposium, which we are holding in Pittsburgh, Pa. November 3-6, 2014. The theme of the symposium is “Going Beyond Methodology to Maximize Performance.”

By this, we mean that the technical program goes beyond the core methodology of TSP to encompass a broader range of complementary practices that contribute to peak performance on system and software projects.

As part of our strategy to expand the scope of the symposium and bring in more architectural thinking to those who have adopted TSP and are using it, we’ve added several architecture-related sessions to the technical program. We at the SEI have seen how successful combining TSP and architecture-centric engineering approaches can be in the project we undertook with Bursatec, the technology subsidiary of the Mexican stock exchange.

Continue reading

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

Exciting Events Added to SATURN 2014 Program

The international software architecture community has responded to this year’s SATURN technical program with another year of strong registration for the SEI Architecture Technology User Network (SATURN) Conference. SATURN, now in its 10th year, will be held at the Marriott Downtown Waterfront in Portland, Oregon, from May 5 through 9, 2014, and registration is still open. Currently 180 people are registered to attend, and it is likely that this year’s conference will come close to or exceed the record attendance of 207 in Minneapolis in 2013.

We are excited to inform you about two late additions to the technical program.

Continue reading

SATURN 2014 Line-up of Tutorials

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.

Continue reading

The Importance of Software Architecture in Big Data Systems

Many types of software systems, including big data applications, lend them themselves to highly incremental and iterative development approaches. In essence, system requirements are addressed in small batches, enabling the delivery of functional releases of the system at the end of every increment, typically once a month. The advantages of this approach are many and varied. Perhaps foremost is the fact that it constantly forces the validation of requirements and designs before too much progress is made in inappropriate directions. Ambiguity and change in requirements, as well as uncertainty in design approaches, can be rapidly explored through working software systems, not simply models and documents. Necessary modifications can be carried out efficiently and cost-effectively through refactoring before code becomes too “baked” and complex to easily change. This blog post at the SEI Blog by Ian Gorton of the SEI, the second in a series addressing the software engineering challenges of big data, explores how the nature of building highly scalable, long-lived big data applications influences iterative and incremental design approaches.

Using Scenario-Based Architecture Analysis to Inform Code Quality Metrics

As the pace of software delivery increases, organizations need guidance on how to deliver high-quality software rapidly, while simultaneously meeting demands related to time to market, cost, productivity, and quality. In practice, demands for adding new features or fixing defects often take priority. However, when software developers are guided solely by project-management measures, such as progress on requirements and defect counts, they ignore the impact of architectural dependencies, which can impede the progress of a project if not properly managed.

This blog post at the SEI blog by Rod Nord and Ipek Ozkaya of the SEI describes a first step toward an approach they developed that aims to use qualitative architectural measures to better inform quantitative code-quality metrics.

Best of SATURN: A Curated Selection from Jeromy Carriere (Google)

Jeromy Carriere of Google, member of the SATURN 2014 Program Committee and previously featured speaker at SATURN, dug through presentations from previous years at SATURN and put together a list of some he found valuable:

Invited talk: Games Software Architects Play (Phillippe Kruchten)
“The life of a software architect is a long (and sometimes painful) succession of suboptimal decisions made partially in the dark.” Phillippe takes us on a tour of some of the ways that we make bad decisions: cognitive biases, reasoning fallacies, political games. Sadly, each example resonates with me, and not just because I’ve seen them in other people. Architects have to rely on intuition, but we also need to know when and how it fails us.

Continue reading

Webinar: Architecture Practices for Agile at Scale: Managing Technical Debt to Improve System Quality

Architecture Practices for Agile at Scale: Strategically Managing Technical Debt to Improve System Quality

The Cyber Security and Information Systems Information Analysis Center (CSIAC) invites you to attend this webinar. This event requires registration.

Presenter: Robert L. Nord
Date and Time: Wednesday, December 11th, 2013; 12-1 pm EDT
Registration Required

Practices designed to expedite system delivery, such as prototyping or agile development, can paradoxically lead to unexpected rework costs that ultimately slow down later deliverables and degrade value over time, especially as the scale of the system grows. The term “technical debt” describes an aspect of this tradeoff between short-term and long-term value in the software development cycle.

Continue reading

Workshop on Software Architecture Metrics at WICSA 2014 – Call for Papers

First International Workshop on Software Architecture Metrics at WICSA 2014
Sydney, Australia, April 7, 2014
Submission deadline: January 12, 2014

http://www.sei.cmu.edu/community/sam2014/

Architecting complex software systems faces the challenge of how best to assess the achievement of quality attributes and other key drivers, how to reveal issues and risks early, and how to make decisions on architecture improvement. Software architecture quality has a large impact on this effort but is usually not assessed with quantitative measures. As the pace of software delivery and technology churn increases, organizations need guidance on how to meet business goals of their software. There is an increasing need to provide ongoing insights into the quality of the system being developed.

Continue reading

SATURN 2014 Call for Submissions

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.

Continue reading