Access the full text.
Sign up today, get DeepDyve free for 14 days.
There are a significant number of proposals for modelling and developing web applications, but very few of them rigorously deal with how to elicit and represent requirements, and how to go from the Requirements Model to the Conceptual Model with a sound methodological basis. This work presents an approach to capture web application requirements. The main goal of this approach is to provide analysts with techniques that allow them to specify not only the functional and data requirements of a web application but also the navigational ones at early stages. These techniques make it possible to identify, specify and describe every task that must be achieved by web application users. In addition, we introduce a strategy based on graph transformations that allow us to automate the derivation of the navigational model of the OOWS method from early requirements specifications. Finally, by using the OOWS automatic code capabilities, we show how this graph transformations-based strategy allows us to obtain web applications prototypes from early requirements specifications.
International Journal of Web Engineering and Technology – Inderscience Publishers
Published: Jan 1, 2007
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.