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.
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.
The early acceptance deadline for SATURN 2014 is quickly approaching on November 22, 2013. Now is the time to prepare and submit your abstracts! By submitting your proposal early, it is eligible for the first round of reviews and your talk, tutorial, or participatory session could be accepted before the final deadline of January 10, 2014.
Thanks to the great community participation we had at SATURN 2013 in Minneapolis this year, we are able to keep SATURN affordable in 2014. As in 2013, we will have three registration periods for SATURN, priced as follows:
- Super-early-bird (early February through mid-March): $750
- Early-bird (mid-March through early April): $850
- Regular: $1100
One of our goals every year with SATURN is to create a solid technical program that is informative, engaging, and lasting. When evaluating proposals for the program, the review committee uses the following guidelines to help decide whether a proposal is a good match for this year’s conference. In these guidelines, the term “session” is used generically to describe any talks, workshops, tutorials, and so on in the conference program.
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.
Everyone can be part of the mobile adventure!
Visit our website for more details:
1st ACM International Conference on Mobile Software Engineering and Systems (MobileSoft 2014) June 2-3, 2014 Hyderabad, India Co-located with ICSE 2014 May 31- June 7, 2014 (http://2014.icse-conferences.org)
First International Workshop on Software Architecture Metrics at WICSA 2014
Sydney, Australia, April 7, 2014
Submission deadline: January 12, 2014
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.