CN106445539A - IFML-based Android developing modeling method - Google Patents
IFML-based Android developing modeling method Download PDFInfo
- Publication number
- CN106445539A CN106445539A CN201610874410.8A CN201610874410A CN106445539A CN 106445539 A CN106445539 A CN 106445539A CN 201610874410 A CN201610874410 A CN 201610874410A CN 106445539 A CN106445539 A CN 106445539A
- Authority
- CN
- China
- Prior art keywords
- android
- interface
- ifml
- event
- control
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 66
- 230000008569 process Effects 0.000 claims abstract description 40
- 230000002452 interceptive effect Effects 0.000 claims abstract description 29
- 230000000694 effects Effects 0.000 claims description 56
- 230000009471 action Effects 0.000 claims description 13
- 238000011161 development Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 7
- 230000010354 integration Effects 0.000 claims description 2
- 238000009434 installation Methods 0.000 claims 1
- 230000003993 interaction Effects 0.000 abstract description 14
- 230000005012 migration Effects 0.000 description 5
- 238000013508 migration Methods 0.000 description 5
- 230000000007 visual effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000000875 corresponding effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000011435 rock Substances 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to an IFML-based Android developing modeling method which comprises the following steps: 1) when IFML is expanded for a moving platform, firstly expanding an Android platform on the basis of the expanding requirement of the moving platform, and confirming and extracting an overall running process of the Android platform application; 2) utilizing the expansion of the IFML (Interaction Flow Modeling Language) for the moving platform to perform initially interactive flow modeling on the overall running process of the Android platform application in the step 1); 3) for the expansion of the moving platform, adopting IFML for further expanding the Android platform application, adopting the IFML for the expansion of the Android platform application for performing realization-oriented interactive flow modeling, performing IFML expansion for the Android platform, and after expanding, describing the running process of the Android application, thereby acquiring the model information and helping the Android developer to develop the application.
Description
Technical field
The present invention relates to soft project, belong to model-driven field of engineering technology.The invention particularly relates to a kind of be based on mould
Type drives and Android Mobile solution is carried out with abstract extraction interaction flow model, using IFML pair extended for Android platform
It is modeled.
Background technology
Nowadays flourish in Mobile solution market, development speed is extremely rapid, and mobile terminal and its application thoroughly change
Become the life style of people, Mobile solution presents multi-platform, multi version situation in itself, it is many to have a platform, version evolving
How fast feature, more preferably and efficiently support that multi-platform, multi version exploitation is a problem receiving much concern.Android
Be to be issued by Google, be the open Mobile Development platform that mobile terminal is made, between a few years the primary system of Android just from
1.1 versions develop 5.1 versions in (in May, 2016) up till now, increase the fast short-term training with intelligent terminal market with the market demand
Long, the renewal iteration speed of android system also can accordingly be accelerated to better adapt to the market demand, additionally, being based on Android
The secondary development that system source code is carried out, the mobile platform operating system that depth customizes correcting is also one of Android development and shows
Work trend, version evolving fast numerous and diverse of therefore visible android system, the diversity between each version is extremely complex, Android
Mobile solution is constantly updated developing as well as the change of system.Model is abstract to the one kind implementing, can
Effectively shield the diversity between each system version, a Mobile solution is taken out with model and is carved using suitable modeling language
Draw description, thus helping developer to complete Android Mobile solution from a version to the migration of another one version.
The exploitation of Android Mobile solution is to design pattern, Mobile solution project based on MVC (model-view-controller)
In source code, all objects are also to be divided into three parts according to this three class, view layer mainly be responsible for application content viewable present with
And the place of user operation is provided；Controller layer and view layer set up contact, are responsible for processing the operation of user in view layer, model
The data of whole application is deposited in layer.
The maximum feature of Mobile solution is exactly visualization and frequently man-machine interaction, and Mobile solution is based on UI event-driven
, event-driven that whole service flow process is mainly based upon on interface completes, and all has this in each version of android system
Individual feature.The overall operation control flow of this application is contained in the interface of Mobile solution, if application is all made up of dry interface,
Exist between interface certain redirect relation, have some visual control elements, user and these visual controls in each interface
Element carries out man-machine interaction, and by this trigger event, system completes to process thus completing the interaction intention of user to monitoring of event,
Processing or completing certain service logic computing of event, or triggers redirecting between interface.
IFML (The Interaction Flow Modeling Language) interactive stream modeling language, by OMG
The content for describing software application front end, user mutual and the behavior that (Object Management Group) formulates
Modeling language.IFML is as OMG standard interactive stream modeling language, there is provided extension mechanism, can be more by extending IFML
It is used for well describing user interface and the interbehavior of Mobile solution.
The interactive flow model that IFML sets up is merely able to describe front end interaction stream information the most general, the pin later it being carried out
Extension to mobile platform, can be used for portraying the description model related to mobile platform, the related model of mobile platform can
General information in preliminary description mobile platform.For this reason, it may be necessary to further the extension for Android platform be carried out to it, from
And set up the related model of Android platform, developer based on the Android platform correlation model shielding difference in version,
In conjunction with Android version during exploitation, complete the exploitation of Android application, the later stage, can be complete based on model with version evolving
Cheng Congyi version is to the migration of another one version.
Content of the invention
Goal of the invention, has the characteristics that version evolving fast for current Mobile solution development field, and the depth of evolution can body
Now arrive api layer time, or even cause the situation that the API between new early version cannot be compatible, this to the exploitation of programmer to realize bringing
Huge challenge.The present invention seeks to, extend IFML for Android platform, and the IFML based on extension is to Android
Application carries out abstract foundation interaction flow model, shields the complicated diversity of each android system different editions, describes Android
The overall operation control flow of Mobile solution, developer based on the interactive flow model set up, in conjunction with actual development demand and
The concrete version information of Android, completes Android application and development.The main object of the present invention also resides in, based on model-driven,
Framework feature for Android platform extends IFML modeling specification, and proposes one kind for Android shifting based on this extension
The method that dynamic exploitation is modeled.In a word, new technology and method is provided to adapt to the rapid evolution of this system platform rank,
Become the problem that academia and industrial quarters are all paid close attention to jointly.Traditional software development scheme is supported not to this, and MDE passes through to divide not
Model with abstraction hierarchy can support the evolution between version and migration effectively.IFML interactive stream modeling language is that OMG proposes
Front end interactive stream modeling specification.
Present invention Android developer first determine the Android that will develop application be made up of how many interfaces and
Redirect relation between interface, determine in each interface, included which Android control, which control need binding event and
Carry out event handling, after event handling is complete, whether carry out redirecting between interface.The overall operation flow process of Android application is determined
Afterwards；In the overall operation flow process preliminarily using standard IFML, Android applied, various elements set up interaction flow model, this
Model is coarseness and is high abstraction, we are extended for mobile platform to standard IFML, after extension
IFML refines to model again, and the model so obtaining just is provided with the concept of mobile platform, embodies the spy of mobile platform
Point.The element information comprising in this model is insufficient to support Android exploitation, Android platform therefore to be further directed to
Carry out the extension of IFML, after extension, Android application operational process is described and portrays, the model information energy that this step obtains
Enough help the exploitation that Android developer is applied.
For completing above-mentioned purpose, the technical solution used in the present invention is as follows：A kind of Android exploitation modeling based on IFML
Method, is characterized in that comprising the steps：
1) when IFML is extended for mobile platform, the extension based on mobile platform needs to put down first against Android
Platform is extended, and determines and take out the overall operation flow process of Android platform application；
11) determine overall operation flow process number of interfaces in Android platform application, between interface, redirect relation；
12) determine the control type constituting each interface of overall operation flow process；
13) determine whether described control binds event, and determine event type；
14) determine and redirect to be completed by which control trigger event between described interface；
2) use interactive stream modeling language IFML be directed to mobile platform extension, to step 1) in Android platform application
Middle overall operation flow process carries out preliminary interactive stream modeling；
21) interface to overall operation flow process in Android platform application, using ViewContainer in extension IFML
The Screen obtaining represents；
22) to the control in overall operation flow process interface, obtained using ViewComponent in extension IFML
MobileComponent represents；
23) to the control Mobile Component representing in overall operation flow process interface, if control
Event is bound on MobileComponent, in extension IFML, Event obtains MobileSystemEvent, right further
MobileSystemEvent extension obtains concrete event type, such as Click, is placed on using concrete event type
On MobileComponent element border；
24) on the MobileComponent of the control from overall operation flow process interface, the event of binding draws one
Navigation Flow, points to the Action element in IFML, the service logic that expression event is carried out after triggering, then from
Action element continues to draw Navigation Flow, points to purpose interface Screen, represents and redirects after having processed service logic
To which interface；
3) IFML is directed to mobile platform and extends, and Android platform application is further expanded, using being directed to
The IFML of Android platform application extension, carries out the interactive stream modeling of realization oriented；
31) to the interface in Android platform application, the Activity element being obtained using the Screen that IFML extends
Represent；
32) to the control in interface, expanded based on MobileComponent element using in Android application platform
Open up each concrete Android control obtaining to represent, including Button, TextView；
33) bound event on described Android control, using for Android based on MobileSystemEvent
Element extends each concrete Android event obtaining to represent, including Click, Touch, LongPress；
34) from described Android control, the event of binding draws a Navigation Flow, points to expression event
The Action element of processing business logic, draws Navigation Flow from Aciton element and points to purpose Activity；
35) redirect relation between interface A ctivity element to show using the IFML extending, interface
If necessary to relate to the source Activity that redirects and purpose Activity is given birth to when being redirected between Activity element
The coding of life cycle methods, adds expression source between the Navigation Flow of source Activity and purpose Activity
The uml class figure of Activity and purpose Activity；
4) to step 3) in Android platform application interactive flow model, integration project demand and Android version are believed
Breath, completes application and development；
41) to the Activity element representing interface in model, add a java class in the project, be inherited from
Activity class in Android SDK；Activity element in model is used to indicate that the interface in Android application, gives
This represents that the element at interface is named as Activity；And Activity Lei Shi Android official here be supplied to developer,
The out and out java class having existed；
Project refers to Android App to be developed, and according to model median surface, correspondingly adds one in this project
Individual java class rather than java class program；
42) to the Android control in interface, project layout Resource TOC adds the topology file at each interface, that is,
Add Android control in interface layout files；
43) step 41) in java class, complete in its life cycle methodology onCreate () interface load and initialize
The coding works such as setting, obtain Android control, are Android control bundle event, complete transaction processing service logic, add
Plus interface redirects code.
Beneficial effect：The IFML extended model based on Android Mobile solution for the present invention, in conjunction with different Android platform
The information of version, completes the exploitation of Android application clear and intuitively, is also readily able to complete from an Android version
Evolution migration to another one version.Model of the present invention can shield the complicated diversity between each version of Android platform, with
Intuitive way shows the overall operation control flow of Android Mobile solution, and developer can be different based on this models coupling
Android platform version carry out Android application and development it is also possible to easily Android Mobile solution can be completed
From a version to the migration of another one version.
The present invention, by carrying out the abstract method setting up model to Mobile solution, not only can be used for shielding Android system
Diversity between system different editions, equally can be used for shielding the diversity between different mobile platforms, thus helping through from one
Individual mobile platform model is changed to another one mobile platform model, carries out code building further according to model.
Brief description
Fig. 1 show the IFML meta-model for Android platform extension；
Fig. 2 show the model that an Android application example uses IFML to set up；
Fig. 3 show the model that same Android application example is set up using the IFML for mobile platform extension；
Fig. 4 show the interactive flow model that the IFML for Android platform extension sets up for Android application example.
Specific embodiment
Below the present invention is described in further details.
First Android developer determine the Android that will develop application be made up of how many interfaces and interface between
Redirect relation, determine in each interface, included which Android control, which control need binding event and enter act
Part is processed, and whether carries out redirecting between interface after event handling is complete.After the overall operation flow process determination of Android application, just
In the overall operation flow process that step ground is applied to Android using standard IFML, various elements set up interaction flow model, this model
It is coarseness and is high abstraction, standard IFML is extended for mobile platform, right again using the IFML after extension
Model is refined, and the model so obtaining just is provided with the concept of mobile platform, embodies the feature of mobile platform.This mould
The element information comprising in type is insufficient to support Android exploitation, and Android platform therefore to be further directed to carries out IFML's
Extension, is described to Android application operational process after extension and portrays, the model information that this step obtains can help
The exploitation that Android developer is applied.
1) determine and take out the overall operation flow process that Android applies.
Android application is UI and event driven, and Android developer is when developing an Android application, first
The overall operation flow process of first application to be determined, carries out abstract understanding to Android application and can learn that Android applies with interface
For unit, carry out redirecting the operational process completing to apply between each interface, in each interface, place suitable visual control unit
Element presents to user, and user can be interacted with control element in interface, and the interactive operation that application can process user completes work(
, effect can be realized, redirecting of interface in interaction, may be triggered.
It is to be developed using object oriented language Java, based on mould that Android developer both knows about Android application
The MVC architecture mode of type-controller-view is designed, any object in application, broadly fall into after all model object,
One of view object and controller object.View object is used for assuming visual content to user, and enters with user
Row interaction, the input of response user, but view object can not process the event of user mutual initiation it is necessary to by view object
All kinds of event informations of triggering are sent to controller object, entrust controller object to go to process all kinds of events.
Controller layer in Android is to be responsible for completing by Activity, and each Activity corresponds to a Java
File.The function of Activity is mainly：1. load the view of its association and present to user；2. obtain the view of its association
In each control, and be responsible for processing the operation that control responds user and widget interaction.In application each page have associated
Activity, Activity specifically combine Android API by Java programming language and realize, and Activity is as Android
In one of four big assemblies, android system is provided for 7 life cycle methodologies, when the state of application changes,
Android system can call the corresponding life cycle methodology of Activity automatically, and developer can be in each life cycle side
In body of laws finishing service logic coding just can realize when life cycle methodology is called by system expected from function or effect.
In Mobile solution, view and controller are inseparable, and Activity is responsible for loading view associated with it, if should
With needing control and user to interact, in Activity, event-handling method will be arranged to this control, Android is to thing
The treatment mechanism of part is all identical：Monitoring event source, is that an event-handling method is bound in event source, event occurs then corresponding
Event-handling method complete event handling.Additionally, event may cause redirecting between interface.Android application be UI and
Event driven, by for being supplied to the visual control binding event that user interacts, system can capture user to developer
The event of interaction generation is simultaneously processed to it.
All interfaces, the control in interface, control bundle event and the event handling of Android application, redirects between interface
Relation, these information just can clearly give expression to the overall operation flow process of Android application, the step for the operation control that obtains
Flow process processed and concrete Android version are unrelated, shield the complicated diversity of each version.
2) use IFML to be directed to the extension of mobile platform, Android application overall operation flow process in step 1 is carried out tentatively
Interactive stream models.
IFML is general interactive stream modeling language, can not be in step 1 through the IFML of extension using standard
Run control flow to be modeled, but this model only rests on the abstract interactive stream level of most original it is impossible to embody mobile flat
The feature of platform, nor describe the information of application in detail, the help to developer is little.The IFML of standard mainly employ with
Lower element interacts stream modeling：ViewContainer represents a view container, can be used to accommodate visualized elements；
ViewComponent represents the visualized elements that can deposit in ViewContainer, visible to user and user is permissible
Interact；Event represents the event in interactive stream, is commonly attached to represent on ViewComponent and is somebody's turn to do
ViewComponent can produce event, be closely connected with Event together be Action and Navigation Flow,
Action represent event produce after the service logic that can carry out, what Navigation Flow illustrated interactive stream redirects direction.When
When Android application overall operation flow process being interacted with stream modeling using standard IFML, in IFML, ViewContainer represents
Interface in Android application, the Android control in interface represents using ViewComponent, control is if necessary to bind
Event, then add Event on ViewComponent, draw Navigation Flow from Event, if event-handling method
Need finishing service logic, then a Navigation Flow and Action is associated, otherwise point to purpose
ViewContainer.Fig. 1 show an Android application example use IFML set up model, this model more abstract and
And coarseness describe Android application interface between redirect relation, how many constitution element in interface, part constitution element
Bind event, event or trigger redirecting of interface, or complete a part of service logic.
IFML is carried out with extending so that IFML can carry out the modeling related to mobile platform for mobile platform, expands
Mainly in terms of the control with mobile platform distinguishing feature and event type, the event type of mobile platform mainly divides exhibition emphasis
For three major types：1. the event that sensor specific to mobile terminal causes, such as rocks, accelerator etc.；2. user is using shifting
The event that the peripheral hardware of dynamic terminal causes, such as photographic head is taken pictures, mike etc.；3. control initiation in the direct operation interface of user
Event, such as clicks on, slide etc., MobileSystemEvent can be expanded based on Event, be expanded based on ViewContainer
Open up Screen, so statement is compared mobile platform feature, and Screen represents the interface of Mobile solution, ViewComponent
Expand to the control MobileComponent with mobile platform related notion, represent that this is the control of mobile platform.Using pin
When the IFML that mobile platform is extended interacts stream modeling to Android application, the interface of Android application uses
Screen represents, the Android control in interface is represented using MobileComponent, the event then basis of binding on control
Concrete event type, to represent, such as clicks Click.Fig. 2 show same Android application example using for mobile flat
The model that the IFML of platform extension sets up, the extension of this part can describe the information of mobile platform concept.
3) the mobile platform extension being directed to IFML is further directed to Android platform and is extended, using for Android
The IFML of extension carries out the interactive stream modeling of realization oriented.
Step 2) in interactive flow model Mobile solution related operation interactive stream process can be depicted, we are further
Extension makes it possible to set up the related interactive flow model of Android platform for the IFML of mobile platform.The contrast each version of Android
Control type in this and event type, find that control and event type there is no change, therefore we can extend
MobileComponent in IFML, expands the control of Android, such as Button, TextView etc. in IFML.
The relation of MobileComponent and Android control, similar to the relation of parent in object oriented language and subclass, works as exploitation
When which control personnel do not know to need in certain interface using, can first be replaced using MobileComponent completely, etc.
MobileComponent is replaced with concrete Android control again when final exploitation determines.Extension MobileSystemEvent adds
Plus the such as Click of the event type in Android, Touch etc..In Android, Activity and view layer are closely connected,
The service logic of view layer all transfers to controller Activity process, and therefore Screen is expanded to Activity by us.In step
In rapid 1), we mention, and when Activity switches over, and application state changes, android system can automatically be called and carry
Supply Activity 7 life cycle methodologies, developer can in life cycle methodology body finishing service logic coding
Just expectation function can be realized when life cycle methodology is called by system.Model in step 2 cannot describe this part with
The information that Android platform is closely related, for this, we need interpolation new element to portray this partial information.IFML is to combine
UML (Unified Modeling Language) modeling language complete application in can not directly by interface or interactive stream come table
The part stated.We select the class figure being used in UML and collaboration diagram to correspond to as mentioning Activity in new element, step 1
Java file, can represent the life cycle methodology in Activity using uml class figure and collaboration diagram completely in IFML.With
Sample ground, the event-handling method being caused due to the event of Android control bundle, it is possible to use uml class figure and collaboration diagram
New element is stated.
After the IFML extension for Android platform, we can so describe the entirety fortune of Android application
Row control flow：Represent the interface in application using Activity, add Android control in Activity, tie up to control
Determine Android event, event is connected by Navigation Flow and Action, Action part is had by developer
Body goes to realize, after completing Action, or the original interface of Navigation Flow sensing represents and achieving function, complete to imitate
Really, or pointing to Activity, if pointing to other Activity, need to add Activity life cycle methodology, raw
Content in life cycle methods body transfers to developer to decide whether to add.By these steps, the entirety of Android application is handed over
Mutually operational process just models and completes.The IFML that Fig. 3 show for Android platform extension sets up for Android application example
Interactive flow model.
4) be based on step 3) in Android interact flow model, in conjunction with the concrete version of Android, if needed only right
Android control type is adjusted, and developer's comparison model can directly complete to apply in Android project source code
All interfaces, control in interface, the corresponding Activity in interface, the event of control bundle, how interface redirects and redirects pass
System.Android developer sees the Activity in model, adds a java class in the project for this Activity, sees
Control in the Activity in model can be added in the interface of Activity association, and control in model is bound
Event and carried out event handling, directly can capture control in Activity and carry out event binding to control.
Term synopsis
English term Chinese
ViewContainer view container；
Screen mobile terminal screen container；
ViewComponent view control；
MobileComponent mobile terminal view control；
Event event；
MobileSystemEvent mobile end system event；
Navigation Flow guiding stream；
Action logic processing operations；
Activity Android platform screen container；
Button Android platform button control；
TextView Android platform Input；
Click Andorid platform click event；
Touch Android platform touch event；
LongPress Android platform length presses event.
Claims (1)
1. a kind of Android exploitation modeling method based on IFML, is characterized in that comprising the steps：
1) when IFML is extended for mobile platform, the extension based on mobile platform needs to enter first against Android platform
Row extension, determines and takes out the overall operation flow process of Android platform application；
11) determine overall operation flow process number of interfaces in Android platform application, between interface, redirect relation；
12) determine the control type constituting each interface of overall operation flow process；
13) determine whether described control binds event, and determine event type；
14) determine and redirect to be completed by which control trigger event between described interface；
2) use interactive stream modeling language IFML be directed to mobile platform extension, to step 1) in Android platform application in whole
Running body flow process carries out preliminary interactive stream modeling；
21) interface to overall operation flow process in Android platform application, is obtained using ViewContainer in extension IFML
Screen represent；
22) to the control in overall operation flow process interface, obtained using ViewComponent in extension IFML
MobileComponent represents；
23) to the control Mobile Component representing in overall operation flow process interface, if control MobileComponent
On bound event, in extension IFML, Event obtains MobileSystemEvent, further MobileSystemEvent is expanded
Exhibition obtains concrete event type, such as Click, is placed on MobileComponent element border using concrete event type；
24) on the MobileComponent of the control from overall operation flow process interface, the event of binding draws one
Navigation Flow, points to the Action element in IFML, the service logic that expression event is carried out after triggering, then from
Action element continues to draw Navigation Flow, points to purpose interface Screen, represents and redirects after having processed service logic
To which interface；
3) IFML is directed to mobile platform and extends, and Android platform application is further expanded, puts down using for Android
The IFML of platform application extension, carries out the interactive stream modeling of realization oriented；
31) to the interface in Android platform application, the Activity list of elements being obtained using the Screen that IFML extends
Show；
32) to the control in interface, extended based on MobileComponent element using in Android application platform
To each concrete Android control to represent, including Button, TextView；
33) bound event on described Android control, using for Android based on MobileSystemEvent element
Extend each concrete Android event obtaining to represent, including Click, Touch, LongPress；
34) from described Android control, the event of binding draws a Navigation Flow, points to and represents event handling
The Action element of service logic, draws Navigation Flow from Aciton element and points to purpose Activity；
35) redirect relation between interface A ctivity element to show using the IFML extending, interface A ctivity unit
If necessary to relate to the source Activity that redirects and purpose Activity carries out life cycle methodology when being redirected between element
Coding, add expression source Activity and purpose between the Navigation Flow of source Activity and purpose Activity
The uml class figure of Activity；
4) to step 3) in Android platform application interactive flow model, integration project demand and Android version information,
Complete application and development；
41) to the Activity element representing interface in model, add a java class in the project, be inherited from Android
Activity class in SDK；Activity element in model is used to indicate that the interface in Android application, to this expression
The element at interface is named as Activity；And Activity Lei Shi Android official here is supplied to developer, has existed
A java class；
Project refers to Android App to be developed, and according to model median surface, correspondingly adds one in this project
Java class rather than java class program；
42) to the Android control in interface, project layout Resource TOC adds the topology file at each interface, that is, on boundary
Add Android control in the topology file of face；
43) step 41) in java class, complete in its life cycle methodology onCreate () interface load and Initialize installation
Deng coding work, obtain Android control, be Android control bundle event, complete transaction processing service logic, add boundary
Face redirects code.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610874410.8A CN106445539A (en) | 2016-09-30 | 2016-09-30 | IFML-based Android developing modeling method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610874410.8A CN106445539A (en) | 2016-09-30 | 2016-09-30 | IFML-based Android developing modeling method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106445539A true CN106445539A (en) | 2017-02-22 |
Family
ID=58172836
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610874410.8A Withdrawn CN106445539A (en) | 2016-09-30 | 2016-09-30 | IFML-based Android developing modeling method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106445539A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107133042A (en) * | 2017-05-04 | 2017-09-05 | 南京大学 | A kind of iOS exploitation modeling methods based on IFML |
| CN107766161A (en) * | 2017-09-29 | 2018-03-06 | 湖北天禾立方智能科技发展有限公司 | MVC frameworks for elevator long-distance monitorng platform |
| CN112463142A (en) * | 2020-11-25 | 2021-03-09 | 昆明理工大学 | Android mobile user interface modeling and converting method based on MDA |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544005A (en) * | 2013-09-10 | 2014-01-29 | Tcl集团股份有限公司 | Expansion developing method and device for Android custom control |
| CN105955718A (en) * | 2016-04-20 | 2016-09-21 | 深圳青虹数据技术有限公司 | Software customization method and system |
| CN106126213A (en) * | 2016-06-16 | 2016-11-16 | 南京大学 | A kind of Android based on IFML develops modeling method |
-
2016
- 2016-09-30 CN CN201610874410.8A patent/CN106445539A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544005A (en) * | 2013-09-10 | 2014-01-29 | Tcl集团股份有限公司 | Expansion developing method and device for Android custom control |
| CN105955718A (en) * | 2016-04-20 | 2016-09-21 | 深圳青虹数据技术有限公司 | Software customization method and system |
| CN106126213A (en) * | 2016-06-16 | 2016-11-16 | 南京大学 | A kind of Android based on IFML develops modeling method |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107133042A (en) * | 2017-05-04 | 2017-09-05 | 南京大学 | A kind of iOS exploitation modeling methods based on IFML |
| CN107766161A (en) * | 2017-09-29 | 2018-03-06 | 湖北天禾立方智能科技发展有限公司 | MVC frameworks for elevator long-distance monitorng platform |
| CN112463142A (en) * | 2020-11-25 | 2021-03-09 | 昆明理工大学 | Android mobile user interface modeling and converting method based on MDA |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102221993B (en) | The declarative definition of complex user interface Status Change | |
| Hamon et al. | Formal description of multi-touch interactions | |
| US20170262262A1 (en) | Application platform for designing and executing applications | |
| Spano et al. | A compositional model for gesture definition | |
| EP2697715A1 (en) | System and method for mobile application development | |
| Allen et al. | Beginning Android 4 | |
| Bernaschina et al. | Formal semantics of OMG’s Interaction Flow Modeling Language (IFML) for mobile and rich-client application model driven development | |
| Barnett et al. | Supporting multi-view development for mobile applications | |
| Bishop et al. | Developing principles of GUI programming using views | |
| Raffaillac et al. | Polyphony: Programming interfaces and interactions with the entity-component-system model | |
| CN106445539A (en) | IFML-based Android developing modeling method | |
| CN106126213B (en) | A kind of Android exploitation modeling method based on IFML | |
| CN107133042A (en) | A kind of iOS exploitation modeling methods based on IFML | |
| Bishop | Multi-platform user interface construction: a challenge for software engineering-in-the-small | |
| Lewis et al. | Native mobile development: a cross-reference for iOS and Android | |
| Sousa et al. | Operationalizing the integration of user interaction specifications in the synthesis of modeling editors | |
| CN113010168A (en) | User interface generation method based on scene tree | |
| Blouin et al. | Interacto: A Modern User Interaction Processing Model | |
| Samaan et al. | Task models and interaction models in a multiple user interfaces generation process | |
| Gill | Using React Native for mobile software development | |
| Kasik et al. | Reflections on using a UIMS for complex applications | |
| Ruiz | Mastering Android Application Development | |
| CN103902274A (en) | Platform for developing smart television UI (user interface) | |
| Yuen | Mastering Windows Presentation Foundation: Build responsive UIs for desktop applications with WPF | |
| Palanque et al. | Interactive cooperative objects: an object-oriented formalism based on petri nets for user interface design |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20170222 |