The design process aims at analyzing the application integration needs, designing the information architecture (IA), and creating comprehensive requirements for the development phase.
In this document:
Wireframes of all UI screens
Leverage the effect of this document by complying with the following prerequisites:
Will, as the product manager, starts with gathering description of the cloud application that he is going to integrate with the OSS/BSS platform. Key points:
Which services and sub-services are you going to provide and sell?
Which services does the application provide per customer and which per user?
Which configuration sets can the providers offer to parameterize resources acquired by customers?
Does the application need services from other applications, for example, domain registration or anti-virus?
Are there other applications your application can integrate with?
A sales model usually contains the following minimal set:
Services for sale - offers
Included resources and add-ons
Resource types and service templates
The documents that help understand and build the application resource model:
Resource model diagram as demonstrated in the APS Resource Model document.
Detailed description of each service including properties and operations to be implemented.
Corrected sales model as demonstrated in the APS Resource Model document and represented by:
Service template with application resources
Service plan with resource rates
Description of the application services to be delivered to customers
Sales model presented by the service template and service plan with respective descriptions
Resource model with description
The designed sales model and resource model allow Roger to proceed with the following steps.
Identify customer personas that are consumers of the application services
- List of customer owner, administrative personnel, and service use employees
- Detailed description of each persona
Identify integration points of the application on the OSS/BSS platform
Persona based list of touchpoints with brief description of the communication area where these touchpoints are used
Design user scenarios
Design the information architecture
Tables and diagrams presenting details of UI screens and APS types
Design UI wireframes
Approved UI wireframes with interaction calls of backend and frontend methods
The hosting platform implies the simplified customer team that will manage and consume application services as described in the Customer Personas document:
Samantha - SOHO owner and simultaneously the administrative staff
Emily - SOHO employee that is the typical consumer (service user) of application resource
Get more details about this step in the Customer Personas document.
In the considered OSS/BSS platform, there is a predefined set of integration points that Roger can use in his project. Analyzing the sales model, resource model, and the list of available integration points, Roger defines the set of integration points his application needs to implement.
The User scenarios should be oriented on the personas defined earlier. Roger gets familiar with the typical Customer Scenarios to develop user scenarios for his application. The scenarios must walk the respective users through the integration points defined at the previous step.
Get more details about this step in the Customer Scenarios document.
In this step, Roger should compile the data gathered and built at the previous steps in the format suitable for developers as described in the Information Architecture document. Preferably, it should be a set of tables and diagrams with detailed description of all APS types involved into development.
Get more details about this step in the Information Architecture document.
Refer to more detailed description: