PhD Research Student
Room 3xx, General Purpose South Building (building 78)
School of Information Technology and Electrical Engineering
The University of Queensland
Queensland 4072 AUSTRALIA
Phone: +61 7 3365 xxxx; Fax: +61 7 3365 4999
email: eescott@itee.uq.edu.au
Research Interests: Model-Driven Software Development, Model-Based Testing, Web Engineering
Research
Architecture-Centric Model-Driven Web Engineering
To be adopted by architects, modelling approaches must provide a means to leverage the software patterns and architectural styles that are relevant to development practice, instead of those proscribed by black-box CASE tools. Architecture-Centric Model-Driven Software Development (AC-MDSD) is a modelling approach that provides architectural control of the generated application. However, AC-MDSD primarily focuses on generating infrastructure code. We apply AC-MDSD to web engineering and contribute a technique to define and generate system behaviour that goes beyond the create/read/update/delete infrastructure functionality. We use UML profiles augmented with OCL to specify the behaviour. We provide an example to illustrate the approach and outcomes.
Form validation is an integral part of a web application. Web developers must ensure that data input by the user is validated for correctness. Given the importance of form validation it is therefore equally important to consider it as part of a model-driven solution to web development. Existing model-driven approaches typically have not addressed form validation as part of the model. In this paper, we present an approach that allows validation constraints to be captured within a model. Our approach covers three common types of validation: single element, multiple element, and entity association. These categories, alongside an architecture-driven philosophy, make use of UML and OCL to specify form validation constraints in a model-driven solution.
Traditionally, it has been recommended not to reuse developments model for model-based testing. If the same model is used for both development and testing, a defect that exists in the development model will be replicated in the testing model and potentially go undetected. If the model used for testing is independent of the development model then this issue is avoided. Whilst this argument has validity it must be considered in the context of the entire project. Code generation completeness and the project team structure must be taken into consideration. In this paper we present a model-driven approach whereby we justify the reuse of development models for model-based testing. We provide an example to illustrate the approach and outcomes.
Advisors
Prof. Paul Stooper Dr Jim Steel Dr Paul King
Publications
Escott, E., Strooper, P., King, P., and Hayes, I. J.: Model-Driven Web Form Validation using UML and OCL, 7th Model-Driven Web Engineering Workshop (ICWE 2011).
Escott, E., Strooper, P., Süß, J. G., and King, P.: Architecture-Centric Model-Driven Web Engineering, The 18th Asia-Pacific Software Engineering Conference (APSEC 2011).
Escott, E., Strooper, P., Steel, J., and King, P.: Integrating Model-Based Testing in Model-Driven Web Engineering, The 18th Asia-Pacific Software Engineering Conference (APSEC 2011).
Current thesis status.