Brainstorming on content of Technology section on Services page
Technology section on Services page need some creative input. Please contribute with your ideas, everyone.
Some general questions are (these go beyond the content for section Technology on the Services page but pave the path for precise content for the Services page):
- What is service Technology offering to scientists doing open science?
- How does service Technology assist scientists in their work?
- How does service Technology contribute to HIFIS?
- Which tools/platforms/technology services do we want to offer?
- What is to be done, which prototypes need to be developed and when is it ready for use?
- What do we intend to have developed and finished in one years, two years, etc. time?
- How could a rough phase-oriented milestone-roadmap look like and how to subdivide it into iterations/increments adaptable in a dynamic development process?
- How do we articulate the overall system landscape and what is the big picture?
- Which systems to integrate with each other?
- Which systems need to interoperate via open standards?
- How to collect, categorize, prioritize and rank Use Cases / User Stories / requirements from end-users?
- How to get feedback on functional requirements like functionalities, features and user-interfaces and non-functional requirements like usability, scalability, interoperability/integrability, security and performance for prototypes to be developed?
- What do we need in terms of hardware and third-party software tools for our Technology services?
- What do other Software Services / Platforms / Tools offer and how to integrate / interoperate with them?
- Which already existing Open-Source Software Services / Platforms / Tools serve our purposes in HIFIS and to which shall we contribute?
- Which already existing Open-Source Software Services / Platforms / Tools can be forked and adapted to the needs of HIFIS Software?
- There is more to come ...
Provide your ideas in a list or table or put it in a diagram like UML/SysML, BPMN, mind-map, system-landscape map, etc., if it serves your purpose.