The initial idea for a science gateway is often driven by requirements in research and/or teaching; however, the knowledge about implementing an extensible, scalable, easy-to-use, and sustainable science gateway is not necessarily in the knowledge portfolio of the researcher behind the idea. On the development side, someone knowledgeable on the topic of creating science gateways may not necessarily be an expert in the research area serviced by an envisioned science gateway. The close collaboration between researchers and science gateway creators is crucial to gather all necessary information and requirements on a science gateway. This is usually an underestimated design task, and the exact layout for the science gateway is a continuous and iterative process. Suggestions come from developers for the design and layout while feedback and comments come from the user community. While each community and its requirements for a science gateway are unique, the
questions that need to be answered for planning and designing a particular science gateway are very similar for any domain. The panel will discuss effective checklists to support developers communicating with diverse domain experts. Such checklists may be the basis for starting a Software Requirement Specification for an envisioned science gateway.
This panel will be useful for both software developers creating gateways and researchers/educators who specialize in the content of a gateway, as it will illuminate both sides of the process. Additional questions for the panelists will be accepted in advance during the
Tuesday afternoon Learning Labs. More details will follow.
