Goal oriented Requirement Analysis for Web Applications

Abstract

Web applications have mushroomed a great deal from static web pages to interactive web services. It has thus become important to engineer these applications methodologically. Goal integration from the early stages maximizes the product quality and prevents giving "requirements" amiss. We propose a Goal based Requirement Analysis for creating the web application. Both functional and non-functional requirements have been studied specific to the web applications. The requirements can be analysed according to the type of application being constructed. The web classification model aids in the understanding of web applications.

A Solution Proposal for Complex Web Application Modeling with the I-Star Framework

“…In the proposal of [4], the authors illustrates how to use goal-oriented requirements analysis to define hypermedia specific requirements that may be effectively used in Web conceptual design and usability evaluation. Another proposal for using a goaloriented requirement analysis language is the one presented in [5], this proposal uses the WebGRL and, similar to our previous work [3], the A-OOH Web engineering method and proposes a model transformation approach extending the GOREWEB framework from the requirements phase to the design phase. Unfortunately, any of these works have the mature level for being used in industrial projects since the modularity issue is not covered, thus, the implementation of its tools does not provide well support (i.e., at usability level) for the Web application designer, making the requirements analysis stage difficult to maintain due to the goal-oriented diagrams in real projects trends to grow up accordingly the requirements evolution.…”

“…In the context of WE, several approaches currently exist that use different goal-oriented requirements analysis languages for requirements stage, being the most commonly used the i* modeling framework [3][4][5] by the reason of it focuses on the description and evaluation of alternatives and their relationships to the organizational objectives. Unfortunately, the robustness of the Web application modeling, i.e., the requirements model, becomes very complex (big size).…”