Minneapolis, Minnesota

April 29 to May 3, 2013

SATURN 2013 Software Architecture Conference: Call for Submissions

The submission period closed on January 7, 2013.
Call for Submissions

The SATURN 2013 technical program will cover topics including, but not limited to, the following: 

1. Front-end architectures: impact of living on the edge

  • Deciding between front-end design patterns and platforms such as browser-based user interfaces and native rich clients; tactics to preserve conceptual integrity across user channels
  • Identifying architectural concerns regarding front-end technologies and platforms such as frameworks for mobile client development, HTML5, JSON and WebSockets, and social-networking software
  • Architecting for usability, privacy, and interoperability in handheld devices; dealing with diverse, novel, or unknown user communities

2. Back-end architectures and application hosting: go to the cloud or stay on the ground?

  • Addressing complex integration challenges with service-oriented architectures (SOAs) and systems of systems
  • Evaluating modern information-management and computing styles—big data, NoSQL, MapReduce 
  • Engineering high-scale, high-volume systems such as web applications, enterprise resource planning (ERP) packages, and control systems
  • Establishing guidelines for different deployment and virtualization options such as standalone vs. multi-tenant, cloud-enabled vs. cloud-centric applications, and online vs. offline processing

3. Methods and tools: go with the flow or go your own way?

  • Tailoring analysis, design, and evaluation methods such as Unified Process (UP), Quality Attribute Workshop (QAW), Attribute-Driven Design (ADD), Architecture Tradeoff Analysis Method (ATAM), and others
  • Combining methods from different communities; for example, object-oriented analysis and design techniques, lean and agile practices, and architectural methods and notations
  • Enforcing architectural decisions through architecturally evident coding styles, component interface design principles, or architectural patterns
  • Managing software evolution and technical debt, enterprise architecture frameworks, and design for operations

4. Technical leadership: hard skills and soft skills

  • Adopting agile collaboration practices when working with stakeholders, improvement approaches, and dealing with complicated situations
  • Empowering project management with architecture—planning agile pregames, conducting architectural spikes and sprint zeros, managing technical risk, providing architectural coaching, establishing communities of practice, and supporting make-or-buy decisions
  • Succeeding in hard-sell situations; for example, risk identification or assessing business value of refactoring and legacy-system modernization

There will be three types of proposals for SATURN 2013: (1) 20-minute conference presentations; (2) 5-minute lightning talks; and (3) half-day tutorial sessions.

  1. Conference presentations are based on experience reports, lessons learned, methods, models, or study results.
  2. Lightning talks, included for the first time at SATURN 2013, are 5-minute talks given within a 30-minute session.
  3. Tutorial sessions actively involve participants in applying innovative practices, methods, concepts, models, etc.

Download a PDF of the call for submissions

Sponsors
Stay Connected

Get the latest SATURN news, important dates, and announcements on the SATURN Network blog, sign up for our email updates, follow us on Twitter (@SATURN_News, #SATURN2013), and join the SATURN LinkedIn Group.

SATURN Blog RSS SATURN on LinkedIn Twitter
SEI Customer Relations

Phone: +1 412-268-5800
Toll Free (within the USA):  +1 888-201-4479
FAX: +1 412-268-6257
E-mail:
info@sei.cmu.edu


Help us improve

Visitor feedback helps us continually improve our site.

Please tell us what you
think with this short
(< 5 minute) survey.