SATURN 2014 Call for Submissions

Submit a proposal for the 10th annual SATURN software architecture conference by January 17, 2014.

Submissions for the 10th annual SATURN software architecture conference are now closed.

The SATURN technical program will include 30-minute experience-report presentations, 90-minute participatory sessions, and half-day tutorials. The following is the Call for Submissions, which closed on January 17, 2014:

Submitting a session proposal is as easy as 1-2-3.

SATURN 2014 - Submitting a session proposal is as easy as 1-2-3.

Step 1—Choose a Theme

This year’s technical program will cover a variety of subjects organized into three themes: (1) Technology, (2) Methods and Tools, and (3) Leadership and Business. A session might touch on more than one of these themes, but successful sessions will have a primary theme that will be the main focus.

Technology

This theme comprises topics related to technology in the context of software architecture. Specific examples and stories (success or failure) that explore how system properties are promoted or inhibited by technology choices are a good fit. Diagrams and code are welcome.  

Suggested topics include, but are not limited to, the following:

  • Choosing and using back-end or front-end technologies and frameworks. For example,
    • Web: Ruby on Rails, ASP.Net, Sinatra, jQuery, HTML5/CSS3, Boilerplate, etc.
    • Mobile: Android, Cocoa, Windows Modern/Metro, etc.
    • Server / back-ends: JEE, .Net, JRuby, Node.js, JBoss, etc.
    • Testing: xUnit, Cucumber, Fitnesse, Watir, Selenium, JasmineBDD, etc.
    • Data management: Hibernate, Spring, ADO.Net, LINQ, Object Relational Mappers, etc.
  • Architecting for modern information-management systems and computing styles—big data, NoSQL, MapReduce, stream-based computing, information discovery, indexing/search, or data warehousing

  • Architecting for specific engineering paradigms including
    • Virtualization, multi-tenant, cloud, or stand-alone/dedicated systems
    • Embedded or real-time systems
    • Legacy systems
    • Service-oriented architectures (SOAs), concurrent systems, or event-driven systems
    • High-scale, high-volume systems such as web applications, enterprise resource planning (ERP) packages, and control systems
    • Continuous delivery (e.g., monitoring, predicting faults, managing parallel feature branches for phased rollouts or A/B testing)

Methods and Tools

This theme comprises topics related to experiences tailoring and using software architecture analysis, design, and evaluation methods and supporting tools. Innovative new methods and tools are just as important as variants and lessons from the field using existing methods and tools. Evidence-based experiences and anecdotes are welcome.

Suggested topics include, but are not limited to, the following:

  • 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, or design for operations
  • Architecting in uncertainty, delaying decisions while remaining effective, or dealing with volatile and quickly changing requirements
  • Model-driven approaches

Leadership and Business

This theme comprises topics related to the software architect's role in leading teams and making business decisions. Topics relevant to both organizations and individuals that address the human elements of software architecture are a good fit.

Suggested topics include, but are not limited to, the following:

  • Leveraging architecture for project management activities such as estimation, planning, and tracking; planning agile pre-games, conducting architectural spikes and sprint zeros; managing technical risk; supporting make-or-buy decisions
  • Providing architectural coaching, establishing communities of practice, architecture certification, training, and education
  • Succeeding in hard-sell situations; for example, risk identification or assessing business value of refactoring and legacy-system modernization
  • Adopting agile collaboration practices when working with stakeholders
  • Software development on self-organizing teams including highly agile teams or open source projects; enabling effective architectural refactoring and evolution
  • Developing leaders, teams, and organizations that are architecturally aware "systems thinkers" prepared to lead and build the next wave of innovative software systems

Step 2—Choose a Session Type

When deciding what kind of 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.

  • Experience-Report Presentation: 30-minute presentation that describes a first-hand experience, lessons learned, or practitioner-focused research; generally a slide-based presentation
  • Participatory Session: 90-minute facilitated workshops with at least 50% of the time dedicated to hands-on, active learning activities with attendees, such as writing code or practicing techniques
  • Tutorial: Half-day sessions focused on teaching specific topics in depth

Step 3—Submit Your Proposal

All proposals must be submitted to the online submission system no later than January 17, 2014.

Proposals will undergo peer review by a program committee of software architecture experts. This year, the program committee will provide feedback on proposals received before November 22, 2013. This feedback can then be used to refine the proposal before the final deadline.

The following information must be included in your proposal:

  • Title for your proposed session
  • Abstract (250 words or less): think "elevator pitch"
  • Session theme: technology, methods and tools, or leadership and business
  • Session type: experience-report presentation, participatory session, or tutorial
  • Session mechanics: How will the session be conducted? Include information such as an outline, timing, and description of activities (for participatory sessions) of no more than 700 words.
  • Learning outcomes: What will attendees learn and be able to apply with their teams after the conference?
  • Target audience and assumed knowledge of the audience
  • Names and bios for all speakers. Bios should be 100 words or fewer.
  • Has this content been presented before? Please list. For experience-report presentations, originality of content is preferred but not essential. Prior presentation of participatory sessions and tutorials, which demonstrates some maturity of the material, is preferred.
  • Speaking experience: Have you presented at previous conferences? Please describe.

You may submit the same or similar topics to multiple session types; however please note this in your proposals and tailor your proposals accordingly. A maximum of four proposals may be submitted by the same person including proposals in which you are a co-presenter.

30-minute experience-report and 90-minute participatory-session presenters may register for the conference at a 40% discounted registration fee.

Tutorial presenters receive a $500 honorarium if their tutorials are attended by 10 or more paid registrants, and they may register for the conference and for other tutorials for free.

Compensation for Presenters

30-minute experience-report and 90-minute participatory-session presenters may register for the conference at a 40% discounted registration fee.

Tutorial presenters receive a $500 honorarium if their tutorials are attended by 10 or more paid registrants, and they may register for the conference and for other tutorials for free.

Important News
Important Dates
SATURN 2015
April 27--May 1, 2015
Baltimore, Md.
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, #SATURN14), 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.