Planning Pre-Work
Before initiating app development on the Vizion Platform, thorough pre-planning is crucial. This phase involves defining the app's purpose, outlining its functionalities, and understanding how it will operate within the Vizion Platform. Such planning is critical for ensuring that the final application meets user needs and business objectives effectively.
Planning Pre-Work Considerations
Vision Statement: What problem are we solving and what value should this solution provide?
On this page: |
|---|
Stakeholder Analysis: Identify who will be interacting with the business process on a daily basis, and who will benefit from the information provided?
Business/System Process Flow: Document both business activities and system logic, including how various Vizion Platform components (triggers, workflows, data processes) will interact within the app.
User Requirements: Collect detailed requirements from users and stakeholders, focusing on user stories and use cases specific to the platform's capabilities.
System Hierarchy: Define the structure of the system within the app, including user roles, permissions, and data ownership.
Examples of Reports: Gather sample reports that demonstrate the kind of output the app should produce, including data visualizations and analytics.
Test Cases: Document the tests that must be passed to gain acceptance.
Case Study
In this course we will develop a new Equipment Checkout application, which will track the location and status of all assets assigned to a specific location. The following outlays the pre-work done for our case study.
Vision Statement
Our vision for the Equipment Checkout application is to create an intuitive, comprehensive system for real-time tracking and management of assets. This application will support asset management by enhancing operational efficiency and promoting accountability in asset usage and maintenance.
Business/System Process Flows
User Requirements
System Hierarchy
Below is a visual depiction of the planned Trackor Types and their relations to each other. All of these relations are a 1 to Many relationship from Parent to Child. For example, one Home Location record can have one or many Asset Items records.
Continue Training
