Call for Submissions

Submissions for the SATURN 2016 technical program are now closed.
Learn more about the technical program for SATURN 2016.

 SATURN 2016 Copyright Clearance and Authorization to Record

Speakers at SATURN 2016 are required to complete and submit a "Copyright Clearance and Authorization to Record" form. Links to the form for both U.S. government employees and non-U.S.. government employees appear below. Please contact us if you have questions or need more information.

U.S. Government Employees ONLY Form Non-U.S. Government Employees Form

What’s New for 2016?

SATURN 2016 will feature the Internet of Things (IoT) as a theme for one of its four tracks. This theme is intended to inspire the SATURN architecture community to cut through the hype and discuss real architecture challenges and solutions to building IoT reference architectures, products, and services.

Conference Tracks

This year’s technical program is organized into four tracks: (1) Architecting for the Internet of Things, (2) Architecture Methods and Design Patterns, (3) Technology and Tools, and (4) Leadership and Business. A session might touch on more than one of these tracks, but successful sessions will identify a primary track. We provide suggested topics for each track below, but proposals need not be limited to these topics.

1. Architecting for the Internet of Things
This track focuses on designing, building, testing, and securing IoT solutions in the real world. While sessions that highlight real-world implementations are preferred, submissions providing practical information that attendees can directly apply in building their own IoT solutions are also sought. Live or video demonstrations are welcomed.

  • Concerns related to specific industries including consumer, entertainment, smart cities, manufacturing, transportation, energy, supply-chain logistics, health care, defense, intelligence, banking, or financial markets
  • Architecture patterns and tactics for IoT solutions 
  • Machine-to-machine connectivity challenges (e.g., reliability, privacy, availability) 
  • Time-series data management (e.g., data velocity, cleansing, storage)
  • Big-data analytics approaches (e.g., data size and volume, diagnostics, prognostics)
  • Cyber-physical security (e.g., forensics, detection, software-defined security) 
  • User experience with connected things 
  • Containerization and cloud technologies driving IoT solutions
  • Quality attributes of Platform-as-a-Service (Paas) offerings for IoT  
  • Integration solutions for connecting traditionally disconnected, unintelligent devices such as home appliances, cars, or heavy machinery

2.  Architecture Methods and Design Patterns
This track focuses on experiences tailoring and using software architecture analysis, design, and evaluation methods or patterns and supporting tools. Innovative new methods and tools are just as important as fundamental principles, practices, and methods of software architecture. Anecdotes and evidence-based experiences are welcomed.

  • Architecture design, patterns, tactics, and evaluation techniques
  • Microservices architecture and new approaches to service orientation 
  • Architecting to enable continuous delivery and DevOps  
  • Cloud adoption of Infrastructure as a Service (IaaS), PaaS, and Software as a Service (SaaS) focusing on architecture concerns and solutions 
  • Architecting within agile development environments and managing technical debt 
  • Addressing quality attribute concerns such as performance, privacy, scalability, connectivity, and interoperability  
  • Improving user experience of new form factors (e.g., voice, vision, touch, wearables, augmented reality) through better architecture 
  • Lessons from success and failure using classic and new design, problem definition, documentation, and evaluation methods

3.  Technology and Tools
This track focuses on technology and tools in the context of software architecture. Specific examples with technical details and stories (success or failure) that demonstrate how system properties are promoted or inhibited by technology or tool choices are a good fit for this track. Diagrams and code are welcomed.

  • Architecture considerations of development platforms for cloud, mobile, web, social, and embedded solutions
  • Big- and small-data (structured and unstructured) analytics frameworks such as the Hadoop family of technologies and tools 
  • Container-based technology platforms such as Docker, Mesos, OpenStack, Kubernetes, and CoreOS 
  • Cyber-physical security solutions addressing both the physical and cyber sides of systems  
  • Connectivity and networking architectures addressing determinism, global reach, harsh/remote environments, and message-passing frameworks 
  • Programming languages and frameworks that promote specific architecture patterns

4.  Business and Leadership
This track focuses on the software architect’s role in leading teams and influencing business decisions. Topics relevant to both organizations and professionals that address the human and business elements of software architecture are a good fit.

  • Leadership roles and growth opportunities for software architects within different types of organizations
  • Experiences developing and maintaining communities of practices both within organizations and as a broader design community 
  • Providing architecture coaching, and offering architecture certification, training, and education 
  • Architecture in the context of project management activities such as estimation, planning, and tracking
  • Understanding risk and assessing business value in the context of legacy-system modernization and greenfield development 
  • Architecture within self-organizing teams including agile teams and open-source projects

Session Types

When deciding what kind of a session to propose, choose a session type that you are comfortable presenting or facilitating and that also helps you to effectively share your wisdom, knowledge, and experience with your audience.

  • 15-Minute (maximum) DEV@SATURN Talk—New this year at SATURN, a DEV (Design, Engineering, Vision) @SATURN talk is similar to a TED talk and concisely shares a single breakthrough technique, lesson, or experience in a passionate and inspiring way. We have a few slots available for these presentations. For more information about these talks, see Giving a TED-Style Talk? Here's How They're Different from Business Presentations and the SATURN blog post New This Year at SATURN: DEV@SATURN Talks.
  • 30-Minute Experience Report—Presentation that describes a first-hand experience, lessons learned, or practitioner-focused research. Generally a slide-based presentation that tells a story about something that you did.
  • Participatory Session—90-minute facilitated workshop with attendees spending at least 50% of the time dedicated to hands-on, active-learning activities, such as writing code, applying a design technique, or practicing an architecture-leadership activity. Please tune the activities to work with groups of 10 to 50 people.
  • Technical Talks and Tutorials—30- or 90-minute sessions, often lecture-based, focused on in-depth teaching of specific topics based on your knowledge and expertise in those topics. Look for opportunities to package longer content as multiple independent sessions rather than parts that presume former sessions as prerequisites.

Submission Guidelines

All proposals must be submitted to the online submission system no later than January 15, 2016. Presenters whose proposals are accepted will receive free or discounted admission to the conference depending on the submission type.

For tips on how to submit a winning proposal, see SATURN 2016 Proposal Guidelines on the SATURN blog.

To help ensure that your proposal is clear and gets a fair review, please be sure to fill in all of the information requested in the online submission form.

The SATURN 2016 Technical Committee looks forward to reviewing your submissions.