For the projects that I am involved in, I use the term Mobile Framework to define the process and “upfront” questions that should be asked on any mobile project. These questions (and answers) establish a framework for the mobile strategy at either an enterprise level or for a specific project. The “process” includes a number of steps which eventually lead through the architecture and to the deployment of the mobile application(s). The Framework helps define the required infrastructure (via architectural decisions) and should include decisions on
- Alignment to the enterprise mission
- Platforms / Devices
- Application design etc
The questions that are asked during the first few steps help you understand what you will need to develop and why. The answers to these questions are critical as you start to develop an architecture.
This framework is used to guide an organization through the development and deployment process.. The framework helps answer the question “How mobile technology supports the organizations' mission”. The questions that should be asked center around
· Who (is going to use the application),
· What Data (is being accessed and stored)
· Where (is the application being used)
These questions are then balanced by security, economics and risk (Financial, Policy, Legal, technical, Operational, Privacy and security). The answers to the questions lead directly to an architectural approach in developing the mobile strategy. The answers become input to a set of architectural decisions.. the architecture is framed within the context of a reference architecture. It is at this point the strategy can be implemented. Applications can then be designed and deployed.
Below is a depiction of the steps. Each step will be discussed in more detail in my next post