Net.Orange App Development

1. Net.Orange App Development • Net.Orange Version 1.0.0 | September 20, 2013

2. Experience Framework (XDm) Team XDm Framework Manager Framework Developer Framework Designer Framework Architect iCOS API Expert Component Developers Framework Quality Device Specialist Component Developers Framework Community Support Framework Training Framework Documentation Framework Quality: The framework quality team is responsible for ensuring the quality of the framework, integration points, components, and documentation required to implement the framework. Net.Orange App Ecosystem

3. The Team Customer Customer: The business owner of the app who will be taking the app to market either independently or as part of a solution. Product Manager: The functional owner of the map, responsible for gathering requirements from the customer and subject matter experts and managing the overall delivery process for the app. Subject Matter Expert: The subject area expert that provides requirements for the app. Can be functional (clinical/financial) or market expert (US/UK) iCOS API Expert: Expert in consuming iCOS API and determines possibilities of functionality of the app based on existing APIs and provides requirements to the iCOS for enhancement and new API creation. Experience Architect: Works with the Product Manager, Customer, and Subject Experts on architecting the user experience of the app. Provides detailed wireframes of exhaustive functionality to the Experience Designer. Experience Designer: Uses the wireframes derived by the Experience Architect to create visual UI comps and create CSS to style the app as architected and designed. Experience Developer: Uses technology (HTML, JavaScript, iOS, Droid, etc.) to build the architected and designed experience. Responsible for working with the iCOS API Expert on integrating iCOS-based data into the resulting app. App Product Manager Experience Developer Experience Designer Experience Architect iCOS API Expert Subject Matter Expert cOS XDm SCRUM Master Quality Assurance: Using this methodology, functional QA is the responsibility of all members of the team during the development process, with the QA leads being the Subject Experts and the Experience Architect. The thought is that those generating the requirements are best fit to ensure those requirements are being met in a usable manner. Browser, platform, and data scenario testing are done by a 3rd party centralized QA department after initial development has been completed. SCRUM Master: Project Management is accomplished using an Agile/SCRUM approach with project self-governance, led by a SCRUM Master assigned to the app. Net.Orange App Ecosystem

4. The Process Process Summary Primary Team Members Market Analysis: A documented and vetted business opportunity assessment looking at market forces, cost to develop, and revenue potential. Business Requirements: The documented business requirements to be satisfied by the app (e.g. Reduce cost of readmissions). Functional Requirements: The documented functional requirements of the app (e.g. Workflow to transition patients across care settings to help satisfy the business requirements). Experience Architecture: The wire-framed interaction and process that satisfies the functional requirements. Experience Design: The visual design of the wire-framed interaction and process determined during the Experience Architecture phase. Experience Development: The coding of the technology used to enliven the architected and designed solution that satisfies the functional requirements within the chosen framework of deployment. iCOS API Integration: The process of selecting existing iCOS APIs, requesting API enhancements, and requesting new APIs within the iCOS to leverage in “lighting up” the app with iCOS-based data and interaction. Quality Assurance: While quality assurance will be assured by the entire app team through the development process, this is the process of enlisting a 3rd party to provide QA on the selected platforms, devices, browsers, etc.. Release: The process of releasing the app, including updating marketing collateral, publishing to app stores, release notes, user documentation, etc.. Implementation: Implementing the app, such as deploying published app to user devices, etc.. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

5. The Process: Market Analysis Team Responsibilities Primary Team Members Customer: The business owner of the app who will be taking the app to market either independently or as part of a solution. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

6. The Process: Business Requirements Team Responsibilities Primary Team Members Customer: Communicates market analysis and works with assigned Product Manager on building the Business Requirements. Reviews and signs off on Business Requirements proposed by the Product Manager. Product Manager: Works with the Customer to develop the Business Requirements document. Upon signoff of the Business Requirements, assembles the App Team to begin the Functional Requirements phase. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

7. The Process: Functional Requirements Team Responsibilities Primary Team Members Customer: Observation, feedback, review and signoff on the Functional Requirements. Product Manager: Works with Customer and Subject Matter Expert (consulting with the remainder of the team) on developing the Functional Requirements. Subject Matter Expert: Works with the Product Manager to provide insight into the functional area they are an expert in (clinical, financial, market, etc.) to determine Functional Requirements. iCOS API Expert: Observation and feedback on API abilities and requirements. Experience Architect: Observation and feedback on possible workflows. Experience Designer: Observation on possible visual aspects. Experience Developer: Observation on possible technology requirements. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

8. The Process: Experience Architecture Team Responsibilities Primary Team Members Customer: Observation, feedback, review and signoff on the Experience Architecture (wireframes). Product Manager: Coordinates and oversees the Experience Architecture process. Subject Matter Expert: Observation, feedback, review, and signoff on the Experience Architecture wireframes. iCOS API Expert: Observation and feedback on API abilities and requirements. Suggestions on how to match iCOS abilities with the workflows being designed. Experience Architect: Works with the Customer, Product Manager, Subject Matter Expert (consulting with remainder of team). Experience Designer: Observation and feedback on possible visual aspects. Experience Developer: Observation and feedback on possible technology requirements. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

9. The Process: Experience Design Team Responsibilities Primary Team Members Customer: Observation, feedback, review and signoff on the Experience Design. Product Manager: Coordinates and oversees the Experience Design process. Subject Matter Expert: Observation, feedback, review, and signoff on the Experience Design. iCOS API Expert: Observation on the Experience Design and feedback on any possible collisions with the iCOS capabilities. Experience Architect: Observation, feedback, and review on the Experience Design. Experience Designer: Utilizes wireframes to generate the look and feel and visual aspects of the app using a variety of visual design tools. Experience Developer: Observation and feedback on possible technology requirements. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

10. The Process: Experience Development Team Responsibilities Primary Team Members Customer: Observation, feedback, review and signoff on the Experience Development. Product Manager: Coordinates and oversees the Experience Development process. Subject Matter Expert: Observation, feedback, review, and signoff on the Experience Development. iCOS API Expert: Works with the Experience Developer to identify exact iCOS data interactions and data needed. Uses JSON/XML developed by the Experience Developer as a blueprint to develop iCOS-enabled versions of the same. Experience Architect: Observation, feedback, and review on the Experience Development. Experience Designer: Observation, feedback, and review on the Experience Development. Remains engaged during the development process to provide CSS and HTML styling support. Experience Developer: Takes the Experience Architecture and Experience Design to craft the technology solution required. Data points are developed against JSON/XML files. Publishes development project frequently for review with other team members. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

11. The Process: iCOS API Integration Team Responsibilities Primary Team Members Customer: Observation, feedback, review and signoff on the iCOS API Integration. Product Manager: Coordinates and oversees the iCOS API Integration process. Subject Matter Expert: Observation, feedback, review, and signoff on the iCOS API Integration. iCOS API Expert: Works with the iCOS API documentation and App Support team to develop iCOS-enabled versions of the app’s data and interactions. Experience Architect: Observation, feedback, and review on the iCOS API Integration process and to ensure the architecture is minimally impacted by the iCOS API usage. Experience Designer: Observation, feedback, and review on the iCOS API Integration process and to ensure the design is minimally impacted by the iCOS API usage. Experience Developer: Work with the iCOS API Expert on integrating the iCOS-based data and interactions, and strive to reduce impact to the experience technology. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

12. The Process: Quality Assurance Team Responsibilities Primary Team Members Customer: Participation, observation, feedback, review and signoff on the Quality Assurance process. Product Manager: Participate in coordinate and oversee the Quality Assurance process. Subject Matter Expert: Participate in the Quality Assurance process to ensure their subject area’s needs are met. iCOS API Expert: Participate in the Quality Assurance process to ensure the iCOS API interaction is optimal. Experience Architect: Participate in the Quality Assurance process to ensure the architected experience is maintained. Experience Designer: Participate in the Quality Assurance process to ensure the product’s design principals are met. Experience Developer: Participate in the Quality Assurance process to ensure the experience technology is optimal and bug-free. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

13. The Process: Release Team Responsibilities Primary Team Members Customer: Participation, observation, feedback, review and signoff on the Release process. Product Manager: Participate in coordinate and oversee the Release process. Working with Marketing on updating and releasing collateral. Work with documentation on generation of any required documentation. Experience Developer: Publish, package and submit app for the implementation process. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem

14. The Process: Implementation Team Responsibilities Primary Team Members Customer: Work with end customers and users on implementing the application for their use. Market Analysis Business Requirements Functional Requirements Experience Architecture Experience Design* XDm Experience Development iCOS API Integration cOS Quality Assurance Release Implementation * Required only for custom apps Net.Orange App Ecosystem