Tag Archives: software engineering

Register Now for SATURN 2014 Conference

Registration for the tenth annual SEI Architecture Technology User Network (SATURN ) 2013 software architecture conference is now open. SATURN 2014 will take place at the Portland Downtown Waterfront Hotel in Portland, Oregon, from May 5-9 and will feature keynote presentations by leaders in the field of software architecture:

  • Joe Justice of Scrum Inc., and Team Wikispeed, which built a 100+ mpg car in less than three months for the X-Prize using Agile, Lean, and Scrum: (see http://tedxtalks.ted.com/video/TEDxRainier-Joe-Justice-WikiSpe)
  • Jerome Pesenti, Vice President of Watson Core Technology at IBM and former co-founder of Vivisimo, the innovate search solutions company
  • Bill Opdyke, Architecture Lead (Corporate Internet Group) at J.P. Morgan Chase, who is best known for having done the first in-depth study of code re-factoring as a software engineering technique

Also participating in SATURN this year will be Diana Larsen (http://futureworksconsulting.com), who will facilitate an Open Space event that will run concurrently with the conference and provide a valuable forum for networking and sharing of ideas and solutions.

Register now for the SATURN 2014 software architecture conference.

Continue reading

1st ACM International Conference on Mobile Software Engineering and Systems (MobileSoft 2014)

1st ACM International Conference on Mobile Software Engineering and Systems
MobileSoft 2014

http://www.sigsoft.org/mobilesoft2014

June 2-3, 2014 Hyderabad, India

Co-located with ICSE 2014 May 31- June 7, 2014

http://2014.icse-conferences.org

Important Dates
!!! EXTENDED !!!
Submission: January 27, 2014
Notification: February 24, 2014
Camera: March 3, 2014
Conference: June. 2-3, 2014

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.

7 Tips for Writing a Great Submission Proposal for SATURN 2014

7 Secret Proposal-Writing Tips that Make Conference Program Committees go Wild!

Writing a great session proposal for a practitioners’ conference can be difficult, even for experienced public speakers and authors. Proposal writing is a distinct skill, different from writing great papers and giving amazing presentations. Since your session proposal is what the reviewers will use to decide whether your session might be a good fit for the SATURN 2014 technical program, it’s also an important skill.

With the final submission deadline for SATURN 2014 quickly approaching on January 17, 2014, here are 7 tips for writing a great submission proposal. Continue reading

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

Why Participatory Sessions at SATURN 2014?

Experience reports and case studies are some of the most effective learning tools available to professional software engineers today. For decades, software engineers have improved the state of practice by sharing stories of their harrowing adventures and triumphant successes. Taking the time to share lessons from our past experiences not only helps us to avoid repeating the mistakes of the past but also spreads the most effective practices widely. This is why SATURN has included experience reports in the main conference program since the start.

While hearing about others’ experiences is important, there is only so much that you can learn by listening to others talk about what they did and what they learned. Learning from experiences of your own is an essential part of growing as a professional software engineer. This is especially true for software architecture, an area that requires a broad understanding of theory and practice.

Continue reading

1st ACM International Conference on Mobile Software Engineering and Systems (MobileSoft 2014)

Everyone can be part of the mobile adventure! Visit our website for more details: http://www.sigsoft.org/mobilesoft2014

1st ACM International Conference on Mobile Software Engineering and Systems (MobileSoft 2014)
http://www.sigsoft.org/mobilesoft2014
June 2-3, 2014 Hyderabad, India
Co-located with ICSE 2014 May 31- June 7, 2014 (http://2014.icse-conferences.org)

Important Dates
===============
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