2011Unpublished venueRequires access

Web Engineering Requirements in Web Application Development

Paula Yadranka Žitinski Elias, Darko Agić, Lidija Mandić, Maja Strgar Kurečić, Ante Poljičak

Open publisher page 0 citations

Abstract

Web applications are considered complex applications, and, as such, they deal with a lot of interlaced concerns which can be divided into functional and nonfunctional requirements, for example, simultaneous access, response time, etc. Thus, to create a good working web application, with little margin for errors, one has to have a well structured development system that can create an application with no functional errors. The other issue to be considered in the area of web application development is the time to market, as a constant battle to produce in the less time possible. Hence, web application development is often standardized by workflows, with aid of patterns, Use Case Scenarios, sometimes even using metamodels. The objective of this paper is to show the different options when developing web applications and the upsides and downsides of each of them, and how combining them can result in a more efficient solution.

About this research paper

What this paper is about

Web applications are considered complex applications, and, as such, they deal with a lot of interlaced concerns which can be divided into functional and nonfunctional requirements, for example, simultaneous access, response time, etc. Thus, to create a good working web application, with little margin for errors, one has to have a well structured development system that can create an application with no functional errors. The other issue to be considered in the area of web application development is the time to market, as a constant battle to produce in the less time possible. Hence, web application development is often standardized by workflows, with aid of patterns, Use Case Scenarios, sometimes even using metamodels. The objective of this paper is to show the different options when developing web applications and the upsides and downsides of each of them, and how combining them can result in a more efficient solution.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Web applications are considered complex applications, and, as such, they deal with a lot of interlaced concerns which can be divided into functional and nonfunctional requirements, for example, simultaneous access, response time, etc. Thus, to create a good working web application, with little margin for errors, one has to have a well structured development system that can create an application with no functional errors. The other issue to be considered in the area of web application development is the time to market, as a constant battle to produce in the less time possible. Hence, web application development is often standardized by workflows, with aid of patterns, Use Case Scenarios, sometimes even using metamodels. The objective of this paper is to show the different options when developing web applications and the upsides and downsides of each of them, and how combining them can result in a more efficient solution.

Key concepts: Computer science, Web modeling, Web application development, Web application, Web engineering, Web development, Workflow, Web standards

Related papers

Back to paper searchBrowse research topicsOriginal source
Web Engineering Requirements in Web Application Development — Research Paper | ScholarLens