 |
Software Engineering Technologies
Goal and Product: The goal of the workshop is to develop an assessment report on software engineering technology needs and gaps for NASA, with a primary focus for code T (the new exploration code) but also informed by requirements from other parts of NASA and related agencies, such as the FAA. Technologies include tools and methods for the full span of the software lifecycle – e.g., requirements analysis through maintenance and execution monitoring, configuration management, and also tools to facilitate adherence to software process. The assessment will represent customer (stakeholder) pull, though with software technologist input in order to shape it into a forward-looking vision. The survey results and material from past efforts will be the starting point for the report. The first day of the workshop will be a plenary session providing background material, a summary of the survey, and presentations on capability requirements from selected NASA organizations. The second day of the workshop will be breakout sessions for different NASA domains (manned space, robotic space, and other NASA domains). The result of the second day will be drafts for domain-oriented capability requirements. The morning of the third day of the workshop will be breakout sessions devoted to a technology gap analysis along major capability lines, resulting in drafts for the assessment report. The afternoon of third day will be a plenary session summarizing the workshop findings and organizing the process for finishing the assessment report over the two weeks following the workshop through email. Workshop participants are invited to bring laptops and USB storage devices (e.g., jump drives) in order to help develop and share written and presentation material. Please bring relevant electronic documents. Each breakout session will have a facilitator and a scribe, who will be primarily responsible for integrating material into sections of the draft report.Agenda
April 21, 2004 Lunar Planetary Institute 8:00 to 8:30 Continental breakfast (Great Room) The objective of Wednesday’s breakout sessions is to develop a draft of capability requirements in software engineering technologies for NASA domains. Each session will have a facilitator and a scribe, and will be given an electronic version of the survey results. Projectors, easels and other material for brainstorming and group discussions will be provided. Breakout Sessions:
Suggested itinerary: Introductions Workshop participants are invited to develop their individual versions of a twenty-year vision prior to Wednesday morning’s breakout sessions. Twenty year vision:
Result: first drafts of twenty-year vision statements, group and/or individual. 10:00 to 10:30 Morning Break (Great Room) Organization and refinement of capability categories. Definition of capabilities. Result: outlines or lists of capabilities. 12:00 to 1:00 Lunch (Great Room) Prioritization of capabilities. Ten year vision statements. Result: drafts of prioritized capabilities with ten and twenty year vision statements. 3:30 to 4:00 Afternoon Break (Great Room) 4:00 to 5:00 Plenary session – presentation of breakout sessions. (Berkner A-F) 5:00 Adjourn
April 22, 2004 Technology Gap Analysis Breakout Sessions Lunar Planetary Institute The objective of Thursday morning breakout sessions is to develop a draft of technology gaps in software engineering technologies for NASA. Each session will have a facilitator and a scribe, and will be given an electronic version of the survey results. Projectors, easels and other material for brainstorming and group discussions will be provided. The breakout sessions will be organized according to the major capability requirements developed Wednesday. The breakout sessions will cut across the domains of manned space, robotic space, and other NASA/aerospace domains. Possible organization could be according to software lifecycle (e.g., requirements, design/develop, test-monitor-maintenance) or according to workshop survey (dependability, cost &schedule, system-software interface). 8:00 to 8:30 Continental breakfast (Great Room) Suggested itinerary: Define current state of technology for the capabilities. Describe gap with ten and twenty year visions. Score criticality of the gaps. 12:00 to 1:00 lunch (Great Room) Plenary session: (Berkner A-F) Technology gap presentations (Breakout session leaders). Process for finishing the draft report. (Organizing committee)
3:00 Adjourn
|
|
||||||||||||||||||||||||||||||||||||
