SYSTEM AND METHOD FOR APPLYING DEVELOPMENT PATTERNS FOR COMPONENT BASED APPLICATIONS

• US 20100131922A1
• Filed: 12/04/2009
• Published: 05/27/2010
• Est. Priority Date: 03/14/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Mateescu, Daniel, Shenfield, Michael, Goring, Bryan R.
• Granted Patent: US 8,132,149 B2
• Time in Patent Office: Days
• US Class Current: 717/107
• CPC Class Codes: G06F 8/20 Software design

Abstract

“A computing device and method for coordinating the development of a client application including application components comprising one or more of at least one of a data component, a message component or a screen component, having corresponding component definitions, or a workflow component comprising a series of instructions. A first development pattern module configured for interaction with a development environment is provided by a computer user interface, the first development pattern module configured for selecting a first pattern from a plurality of patterns based on an application component type central to the client application, the first development pattern module for guiding a user interface with a plurality of predefined steps to coordinate a development of the application components through user input events via the user interface in accordance with the first pattern.”

Claims

1-41. -41. (canceled)

42. A designer tool for developing a client application comprising application components, the tool comprising:

a user facing module selected from a group consisting of an editor, a viewer, a wizard module, a dialog module and a combination thereof;

the editor module interacting with a user of the tool;

the viewer used to create and modify definitions of the application components, and relationships between the application components;

the wizard module assisting the operation of the editor and the viewer, and guiding the development of the client application, the wizard module being step-driven by the dialog after gathering information from the user of the tool via a user interface;

a data model selected from a group consisting of a design time data model, a runtime data model and a combination thereof, the design time data model representing a state of the client application under development, accepting a set of commands included in the user facing module that affect a state of the design time data model, and interacting with the user facing module by notifying user facing module when the state of the design time data model;

the runtime data model representing the state of an emulated application under development;

a service module selected from a group consisting of a model validator, an application generator, a build service, a skin manager, a backend connector, a localization service a deployment service, a security service and a combination thereof;

the model validator validating a representation of the client application by the design time data model;

the application generator collaborating with the design time data model to obtaining a content of the application components, the application generator further utilizing the model validator to check definitions of the application components and mapping description information;

the build service building the client application in a deployable form, the build service further preparing and packaging a resource bundle with the client application in the deployable form;

the skin manager loading visual elements defined by a screen component of the data model;

the backend connector building a suitable application message and data set for, and communicating with backend data sources;

the localization service supporting a build time localization of user visible strings and creating the resource bundle file;

a deployment service deploying the client application; and

a security service signing the client application;

wherein the user facing module observes and responds to changes in the data model of the client application and wherein the service module provides facilities to the user facing module.

43. The designer tool according to claim 42, wherein the designer tool is executed in a computer processor.

44. The designer tool according to claim 42, further comprising a user interface layer including the user facing module, a model layer including the data model and a service layer including the service.

45. The designer tool according to claim 42, wherein the editor module is a graphical editor providing an edit space for draw objects or a text editor implementing line based text editing.

46. The designer tool according to claim 42, wherein the viewer is a resource viewers or a graphical editing framework viewer providing an edit space to view objects.

47. The designer tool according to claim 42, wherein the user facing module triggers validation actions on the design time data model.

48. The designer tool according to claim 42, wherein the design time data model defines an item selected from the group consisting of:

a data component definition, a global variable definition, a message component definition, a resource definition, a screen component definition, a script, a style definition, a backend data source mapping descriptor, and a combination thereof.

49. The designer tool according to claim 42, wherein the design time data model sends events to the user facing module in response to changes in the design time data model.

50. The designer tool according to claim 42, wherein the runtime data model notifies the user facing module with changes made to runtime data model.

51. The designer tool according to claim 42, wherein the model validator checks the that the representation of the client application by the design time data model is in line with the backend data source presentation of messaging operations.

52. The designer tool according to claim 42, wherein the model validator checks a consistency of parameters and field level mappings of the application components, or screen control mappings and screen refresh messages of a screen component.

53. The designer tool according to claim 42, wherein the model validator validates the design time data model'"'"'s representation of messaging relationships of the backend data source.

54. The designer tool according to claim 42, wherein a generation process of the application generator is started through a generate application interface accessed by the developer using the user interface.

55. The designer tool according to claim 42, wherein the build service provides generates a manifest file a jar file of the client application in the deployable form.

56. The designer tool according to claim 42, wherein the skin manager instantiates a new environment for construct the screen elements according to the screen component of the data model.

57. The designer tool according to claim 42, wherein the backend connector generates appropriate messaging component and data component sets the client application.