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.
Informative sessions share meaningful insights with lessons that attendees will be able to apply directly with their teams after the conference.
- Is the information proposed relevant to one of the topic themes in this year’s conference?
- Are there succinct lessons supported by real-world examples, research, or direct experience?
- Is the topic of broad or general interest?
- Can the lessons be applied beyond small sub-communities of practice?
Engaging sessions create an active learning environment that promotes information retention and generally gets attendees excited about the topics discussed.
- Did the speakers have an impact on their organization related to the lessons or insights proposed?
- Do the speakers appear to be knowledgeable of the topics proposed?
- Do the speakers have a history of successful, engaging, educational, energetic, passionate, or entertaining presentations?
- Have the speakers shown an attention to detail in preparing their proposal?
- For participative sessions and tutorials, will the proposed session create an effective learning experience for attendees?
Lasting sessions have appeal beyond current fads and attempt to weave new ideas into our overall understanding of how we develop software systems.
- Does the proposed session advance the current state of practice?
- Does the proposed session improve our depth of understanding in software architecture?
- Does the proposed session present a unique or novel project experience?
- Does the proposed session offer a unique or fresh perspective on “classic” topics?
Our intent in sharing this information is to help you to write the best proposal possible. Use these evaluation guidelines to tailor your proposals and help create the best SATURN Conference yet. Strong proposals will have some “yes” answers in each of the guidelines. Also note that these are only guidelines and not hard-and-fast rules. We are excited to see all the great ideas that are proposed!
– George Fairbanks
– Michael Keeling
SATURN 2015 Co-Technical Chairs
SATURN 2015 will be held in Baltimore, Maryland, April 27-30, 2015. See the SATURN 2015 Call for Submissions to learn how you can submit an abstract to present your ideas at SATURN 2015. Please submit proposals for 15-, 30-, and 90-minute sessions to the online submission system no later than January 16, 2015. Proposals will be reviewed and accepted monthly. Proposals not accepted early will receive feedback from a committee of software-architecture community leaders that can be used to refine the proposal before the final deadline. The technical committee plans to offer heavily discounted conference attendance to those selected to be part of the program; specific compensation details will be posted on the SATURN 2015 website soon.