Method and system for task modeling of mobile phone applications
First Claim
1. A method for modeling interactive sequential applications for smart mobile devices, comprising the steps of:
- a) generating in a central processing unit (CPU) a static model describing all goals of target applications using their screens, Screen Input Elements (SIEs), transitions between screens, sub-goals and the links between them;
b) building in said CPU a dynamic model based on said static model by tracking the use of the application screens over an actual device while using an inheritance mechanism whereby model entities having a parent-child relationship are reusable in different models;
c) creating instances of said static and dynamic models specifically generated for a variety of devices;
d) storing said static and dynamic models with their instances into a passive Task Model database, being in data communication with said CPU;
e) downloading relevant passive Task Models to user'"'"'s device according its type and the application supported by said user'"'"'s device;
f) tracking in real-time user'"'"'s actions during user-system interactions and generating a unique identifier for each application'"'"'s screen that is visited by the user of said mobile device by choosing an identifier that matches a signature of each application'"'"'s screen, wherein created identifiers are used for generating an active model of the user'"'"'s actual usage;
g) storing said tracked model into an active Task Model database being in data communication with said CPU; and
h) comparing said active Task Model to said passive Task Model and generating usage patterns for said user;
wherein the static and dynamic models are in the form of an Entity Relationship Diagram (ERD), and implemented in a relational database.
3 Assignments
0 Petitions
Accused Products
Abstract
A system for task modeling interactive sequential applications for one or more mobile devices has a software tool for defining a generic meta-model of the target applications. The generic meta-model has a static model of application components, and a dynamic model of identifiers of application screens and connections; a passive Task Model database for storing the generic meta-model for future reuse, which further comprises static instances of the generic meta-model specifically generated for a variety of mobile devices; a tracker module for real-time monitoring and creating unique identifier for each application'"'"'s screen visited by the user of the mobile device, wherein created identifiers are used for generating active models of the user actual use; and an active Task Model database for storing the active models, wherein data transferring and storing is minimized to screen identifier numbers.
31 Citations
15 Claims
-
1. A method for modeling interactive sequential applications for smart mobile devices, comprising the steps of:
-
a) generating in a central processing unit (CPU) a static model describing all goals of target applications using their screens, Screen Input Elements (SIEs), transitions between screens, sub-goals and the links between them; b) building in said CPU a dynamic model based on said static model by tracking the use of the application screens over an actual device while using an inheritance mechanism whereby model entities having a parent-child relationship are reusable in different models; c) creating instances of said static and dynamic models specifically generated for a variety of devices; d) storing said static and dynamic models with their instances into a passive Task Model database, being in data communication with said CPU; e) downloading relevant passive Task Models to user'"'"'s device according its type and the application supported by said user'"'"'s device; f) tracking in real-time user'"'"'s actions during user-system interactions and generating a unique identifier for each application'"'"'s screen that is visited by the user of said mobile device by choosing an identifier that matches a signature of each application'"'"'s screen, wherein created identifiers are used for generating an active model of the user'"'"'s actual usage; g) storing said tracked model into an active Task Model database being in data communication with said CPU; and h) comparing said active Task Model to said passive Task Model and generating usage patterns for said user; wherein the static and dynamic models are in the form of an Entity Relationship Diagram (ERD), and implemented in a relational database. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system for task modeling interactive sequential applications for one or more mobile devices, comprising:
-
a) a central processing unit (CPU) having a software tool for defining a generic meta-model of the target applications, wherein said generic meta-model consists of a static model of application components, and a dynamic model of identifiers of application screens and connections that are based on an inheritance mechanism whereby model entities having a parent-child relationship are reusable in different models; b) a passive Task Model database, being in data communication with said CPU, for storing said generic meta-model for future reuse, which further comprises static instances of the generic meta-model specifically generated for a variety of mobile devices; c) a tracker module in said processing unit for; c1) real-time tracking and monitoring user'"'"'s actions during user-system interactions and creating a screen unique identifier for each application'"'"'s screen visited by the user of said mobile device by choosing an identifier that matches a signature of each application'"'"'s screen, wherein created identifiers are used for generating active models of the user'"'"'s actual usage; and c2) generating a unique identifier for each captured screen that is presented to said user; d) an active Task Model database, being in data communication with said processing unit, for storing said active model, wherein data transferring and storing is minimized to screen unique identifier and; e) an analyzer for comparing said active Task Model to said passive Task Model and for generating usage patterns for said user. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15)
-
Specification