Mockup‐driven fast‐prototyping methodology for Web application development

Abstract

Web application development can be very complicated without an appropriate framework, architecture and application model. A good implementation model can help application developers communicate with clients, consolidate the design before starting the development, speed up the development, and make the code highly reusable. This paper proposes a mockup-driven fast prototyping methodology (MODFM) for the development of Web applications. It is built on the most recent Web technologies: EJB, JSP, Servlet, XML, Struts, and Web application server. A two-tier Model-View-Controller (MVC) architecture is proposed as the underlying backbone and a supporting environment is tailored specifically in order to enable development. Two basic supporting tools are provided: the dynamic menu generator and the generic code generator, which produce code for front-end, back-end and database schemas. MODFM helps to generate fully functional mockup systems for the client to review at an early analysis stage, and continues to provide guidance throughout follow-on development phases. Real-life experiences on the use of this methodology in industry are presented as examples.

Service-level agreement-based QoS analysis for web services discovery and composition

“…Our previous research creates a Web application code generator WebGen (Zhang and Chung, 2003), which we will adopte it in this work as a SLA document parser.…”

Toward a Service-Oriented Development Through a Case Study

“…5, each Web-service component in the repository exhibits another three-tier structure. Based upon the typical three-tier architectural model and some most recent Web technology, such as The Java 2 Platform, Enterprise Edition (J2EE) [16], our previous research yielded a Web-application architecture that is oriented to exposing Web services [44], [45]. As shown in Fig.…”

“…[44], [45], which was used in this project to automatically generate significant part of code, both in the front-end and the back-end. The back-end in-memory simulation templates help generate in-memory back-end support for the front-end tier; so that, the front-end can be tested independent of the back-end development.…”

“…In contrast with their work focusing on conceptual modeling, our project proposes a practical services-oriented architectural model to guide the design and development of services-oriented Web applications. We used our own code generator (WGenerator) [44], [45] to generate services-oriented code.…”

A Double-Model Approach to Achieve Effective Model-View Separation in Template Based Web Applications

“…As for future research lines we propose to relate our work to others such us [33], where a similar adaptation process occurs between the fornt-end and the back-end of a two-tier MVC based architecture that supports the MODFM methodology for the development of web applications; or [4] that presents the dual-mvc approach, in which the controller of a MVC application is split between the client and the server. The approach reduces client/server interactions in web applications by returning to the client more data than strictly necessary for page visualization, but that can be used in response to certain user actions.…”