Abstract

Two years ago, the Object Management Group (OMG) adopted a new standard method named Interaction Flow Modeling Language (IFML) for web engineering domain. IFML is designed to express the content, user interaction, and control behavior of the front end of applications. There are number lacks in web engineering methods, because each of them is defined to particular specifications, one of which is the open issue of supporting the whole lifecycle in process development. In this paper, we analyze IFML models in the process development lifecycle to show capability of the method used in the process development. We then make a comparison between IFML and other methods in lifecycle phases. Finally, we add IFML to the web engineering lifecycle’s map. It is anticipated that the result of this paper will be to become a guide for developers for using IFML in the development of new applications.

Highlights

  • Model Driven Web Engineering (MDWE) methods such as WebML [1], UWE [2] or OOHDM [3] have become mature solutions for developing Web Applications

  • We analyzed the actions of Interaction Flow Modeling Language (IFML) in the process development life cycle

  • Results showed that IFML is a good method with best practice but cannot fully support the web development lifecycle

Read more

Summary

INTRODUCTION

Model Driven Web Engineering (MDWE) methods such as WebML [1], UWE [2] or OOHDM [3] have become mature solutions for developing Web Applications. The advantages of engaging MDWE are evident from diverse perceptions like software quality, team output or adjustment to improving technologies [13,14] Of these diverse MDWE methods, it is worth describing the IFML [15], an object management group condition for the establishment of data-intensive utilization becoming a key reference within the industry growth [16,17]. We will analyze IFML in respect to process development web applications This will involve demonstrating the capability of IFML to support whole phases of web engineering in a lifecycle to determine IFML’s location in the lifecycle map. We present some concluding remarks and suggestions for future research

RELATED WORK
MDWE LIFE CYCLE
General Overview
IFML Artifacts
Metamodels
IFML Development Process
RESULT
Process Model
Content Model
CONCLUSION AND FUTURE WORK
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.