How to get from idea to prototype (and to a deliverable solution): Part 2
Note on legacy behavior: 'Service' renamed to 'Application'
What previously was called Services within the BRYTER platform is now renamed to Applications making it more self-explanatory and convenient for our customers.
Further, Service Frontends are now referred to as Publish Applications.
Great BRYTER Services are providing value, offer a comprehensive solutions and create memorable experiences. When planning a BRYTER Service, the typical process entails research, definition, development, validation and implementation of the service. In this webinar series, we will draw on several scientifically proven frameworks to outline the best way from idea to prototype (and implemented Service).
Based on the Phases outlined in the Software Development Lifecycle (SDLC), we are offering a step-by-step guide on how to plan Services starting from Planning and Ideation (Part 1) until Delivery and Maintenance (Part 7) of your final published Service.
In this second installment of Best Practice Webinar series: From idea to prototype (to Service), we present our suggested approach on how to perform a requirement analysis.
We discussed:
- Creating a list of requirements (input, output, processing)
- Estimating delivery dates for module content, prototype, and testing
- Laying the groundwork for the design and prototype phase (Part 3)