160 likes | 290 Views
SOFTWARE LIFECYCLE. What functions would ISEES perform?. Functions, Services and Activities:. Marketing, Outreach Benefits of OSS Value of “Software Management Plans” Crowdsourced swag development Training Software best practices, bootcamps , more focused training courses
E N D
Functions, Services and Activities: • Marketing, Outreach • Benefits of OSS • Value of “Software Management Plans” • Crowdsourced swag development • Training • Software best practices, bootcamps, more focused training courses • Community Building • Promote software reuse as an indicator of successful science • Industry links • Consulting Services • Consulting for any point of project lifecycle • Call-based proposals (or nominations) and community selection • Technical Services • Software certification programs • Software system preservation • Software Registry: quality, evaluation results, reuse
How would ISEES uniquely provide value to enable {efficient|reproducible|scalable|impactful} science?
Providing Value • Science via integrated software • Training
Providing value: science via integrated s/w • Scalable, interoperable, integratable software solutions • Cultural change • Synthetic science
Providing value: training • Learn software best practices and how to leverage software • Cultural change
ISEES should pursue: • Creating and engaging the community • Developing products for the community
Pursue: community creation and engagement • Active community promotion • Hackathons • Working groups • Evangelism
Pursue: develop products • Development services e.g. hardening • Materials covering principles, best practices • Pointers and resources
Logic models: science / software integration • Hackathon-style working groups, co-led by a scientist and a developer, to address one or more SWLC problems that presently impede a grand challenge science question • Would need support for 2+ meetings pear year, 2+ years, ~12 people • Would deliver software solutions to the problems. Publications. • Enables things that can’t be done now • Publications and adoption would be measures of success
Logic models: science / software integration • Standards Workshops • 3-4 per year • Best practices, coding standards, policies, documentation, standards, quality metrics • Deliver concrete results
Logic models: community tools • Online tools and infrastructure to create community • Resources: development of, and running of courses. delivery mechanisms for online courses, facilities to host the workshop • Outputs: multi-day workshops or multi-step courses, sample datasets • Impact: better trained scientists and developers. software being used in the community • Assess: participation and follow-on courses. Surveys, usage statistics, engagement w/ open source
Logic models: community building and engaging • Engaging as large a community as we can • Building, then engaging the community, and leaders • Resources: community and online management people (~4FTE) • Outputs, Measurement: community ownership of effort, more volunteers, higher quality of collaboration