Web Application Classification

Author(s):  
Hsiang-Jui Kung ◽  
Hui-Lien Tung

Many companies use the Web to communicate with the external world as well as within their organizations and to carry out their business processes more effectively. A survey on Web application development shows that 84% of development projects do not meet business needs, 56% do not have the required functionality, 79% are behind schedule, and 63% are over budget (Standish Group, 2002). García-Cabrera, Rodríguez-Fórtiz, and Parets-Llorca (2002) report that the development of a Web application is never finished, and the nature of Web applications is evolutionary. The architecture of Web applications has three layers: conceptual, presentation, and navigation. It also has two perspectives: designer and viewer. Software evolution is “the dynamic behavior of programming systems as they are maintained and enhanced over their life times” (Belady & Lehman, 1976). Web application evolution is of increasing importance as more Web systems are in production.

Author(s):  
Ala M. Abu-Samaha ◽  
Lana S. Al-Salem

The requirements phase of the system/application development process typically involves the activities of requirements elicitation, analysis, validation, and specification. The main goal of such a process is “to develop a requirements speci- fication document which defines the system to be procured and which can act as a basis for the system design” (Sawyer, Sommerville, & Viller, 1996). Hence the underpinning assumption of the requirements engineering (RE) process is to transform the operational needs of an organisation into complete, consistent, and unambiguous system/application specifications through an iterative process of definition and validation (Pohl ,1994). The Web engineering (WE) literature provides a limited number of methods and techniques that can be used to manage the RE process in a Web development context [e3-value framework (Gordijn, Akkermans, & van Vliet, 2000), SOARE approach (Bleistein, Aurum, Cox, & Ray, 2004), e-prototyping (Bleek, Jeenicke, & Klischewski, 2002), AWARE (Bolchini & Paolini, 2004), and SSM/ICDT (Meldrum & Rose, 2004)]. Despite the availability of such a limited number of Web requirements engineering (WRE) methods, many researchers criticised such methods for their failure to address the necessity to align the Web application’ requirements to the organisation’s business strategy. Hence, the recommendation of many researchers (Al-Salem & Abu- Samaha, 2005a; Bleistein 2005; Bleistein, Cox, & Verner, 2004; Vidgen, Avison, Wood, & Wood-Harper, 2002) is to utilise a general WRE framework for the development of Web applications that can align the application’s requirements to the organisation’s business needs and its future vision. The objective of such a WRE framework is to incorporate the elicitation/analysis of business strategy as part of the application’s RE process. This chapter presents a WRE method that extends Sommerville and Kotonya’s viewpoint-oriented requirements definition (VORD) and Kaplan and Norton’s balanced scorecard (BSC) to elicit the Web application’ requirements and to plan/analyze the business strategy, respectively. In addition, eWARE (extended Web application requirements engineering) deploys the concept of “requirements alignment” to attain business objectives during the requirements discovery, elicitation, and formalisation process to identify the services of the Web application that will achieve the business objectives in order to improve the organisation’s profitability and competitiveness. The chapter is organised into a number of sections. The second section of this chapter provides a background to Web applications in terms of defi- nition and differentiating characteristics. The third section provides a discussion of eWARE method in terms of phases and activities. This section is divided into two subsections to cover the activities of the two prominent phases of the eWARE process in more detail. The fourth and fifth sections provide a discussion of possible future trends in WRE and a number of concluding remarks.


Author(s):  
Roberto Paiano ◽  
Anna Lisa Guido ◽  
Andrea Pandurino

As it will be clearer subsequently, two different technologies will be used for realizing the generation of the code; the first one predominantly focused on the generation of code for the Web applications that do not have an underlying business process, and that they do not require, therefore, the management of the relative problems. The second technology has been selected instead, to also keep in mind the business processes. In order to provide support to the designer in the design of the whole complex Web information system, it is essential to provide a suitable tool that hides the intrinsic complexity of the methodology supporting the designer in the application of the same that is often complex, and the tool has to be able to translate the design made up in a machine readable format to be able to use this design in the following automatic code generation of the Web application according to a model-driven approach. In this chapter, we introduce the design and implementation of the editor made up mainly of the architecture presented (and based on Eclipse™ Platform as illustrated in the preceding chapter) and on the methodological steps of integration among the several editors for the design and implementation of these guidelines.


Author(s):  
Rizwan Ur Rahman ◽  
Deepak Singh Tomar

Research into web application security is still in its initial phase. In spite of enhancements in web application development, large numbers of security issues remain unresolved. Login attacks are the most malevolent threats to the web application. Authentication is the method of confirming the stated identity of a user. Conventional authentication systems suffer from a weakness that can compromise the defense of the system. An example of such vulnerabilities is login attack. An attacker may exploit a pre-saved password or an authentication credential to log into web applications. An added problem with current authentication systems is that the authentication process is done only at the start of a session. Once the user is authenticated in the web application, the user's identity is assumed to remain the same during the lifetime of the session. This chapter examines the level login attacks that could be a threat to websites. The chapter provides a review of vulnerabilities, threats of login attacks associated with websites, and effective measures to counter them.


2019 ◽  
Vol 6 (125) ◽  
pp. 121-126
Author(s):  
Liliia Bozhukha ◽  
Oksana Beloborodko

The article presents the results of the analysis of the existing web application architecture design methodologies and the corresponding software development tools and resources.The shortcomings of the existing approaches to application development were identified and conducted the analysis can be used to design the web systems architecture. The practical value of the work is the development of algorithms for creating, deploying and scaling applications using different software. A test system based on several classic approaches has been developed.


Author(s):  
M. M. Murad ◽  
M. W. Ashraf1

In recent time, the evolution of web applications have gained importance over the web development process and the factor of web evolution cannot be ignored by web developers. Web development has become complex and challengeable for web developers. The process of software evolution played an important role during the development of the software. Millions of web application have been developed every year around the world It has included various approaches, tools, and frameworks to reorganize the web applications with an improved version. Research has been shown that there are no proper and systematic techniques is available for evolving web applications. This special article has been written to make a comparative analysis of WordPress and Django web framework using Lehman’s laws of software evolution. It has been found that the six out of eight Lehman’s laws found valid during the evolution process for web frameworks.


Author(s):  
A. Zh. Kіntonova ◽  
◽  
E. Umbetali ◽  
A. E. Nazyrova ◽  
A. A. Konyrkhanova ◽  
...  

The article is devoted to the issues and design of the web application “Training center”. The article presents the technology of designing the architecture of the web application of online learning. The article presents the interface of the web application “Training center”, modeling of business processes. The article presents the technology of implementation of the architecture of the web application “Training center”.


2019 ◽  
pp. 701-706
Author(s):  
Lilyana Petkova

Nowadays security becomes more important than the content and the SEO of a web application. Due to a lack of protection, the number of attacked websites augments in the past few years. In most of the cases, developers are either uninformed or unqualified to implement security during the application development, which causes a huge amount of data flaws. Supporting the developers and easily managing the workflow, some organizations have developed different kind of guidelines for security integration. Such guide helps handling the security from the outset of the development process, which influence over the protection of the entire application. The one used in this article is a project developed by Open Web Application Security Project (OWASP) Foundation named OWASP Secure Headers Project. Its aim is to show the developers the balance between usability and security implemented through http headers. By giving general data and examples of HTTP response headers usability it is a platform which help increasing the security of the application. In this article, we explain the necessity of HTTP Security Headers and how they can help in preventing a cyber invasion in our web application! We will give details on the most important HTTP headers and will retrieve a basic information for some with a lower need. We will give examples for their implementation in one ASP.NET web application to provide more descriptive perspective of their use! In the recent years, browsers have integrated certain security header controls to support the web application security. Those headers give instructions to the browser how to behave when handling sensitive content and data of the application. If developers enable them in the application, browser will prevent attacks automatically. But not all browsers support them, which brings a compatibility question: what are the alternatives in a case of deprecated header on a specific browser. As a part of the research we will provide an analyze of the use of the HTTP headers in some of the most common sites used in Bulgaria with the help of ALEXA Top 1 Million sites. There have already been developed a lot of applications to show if a certain website has HTTP security headers implemented. Most of them are freely to use and gives detailed information on what was done and what should be done in case that specific layer of security is missing from the web application. The need of security in the web applications become more and more necessary. Along with other security implementations on a programming and on a server level the ones described in the article bring another layer of security management that mitigates certain types of cyberattacks and vulnerabilities.


Author(s):  
Milena Vesić ◽  
◽  
Nenad Kojić ◽  

Web applications are the most common type of application in modern society since they can be accessed by a large number of users at any time from any device. The only condition for their use is an Internet connection. Most applications run using the HTTP protocol and client-server architecture. This architecture is based on the use of API (Application programming interface), most often REST architecture (Representational State Transfer). If there are several different functionalities on the website that fill their content with data from the web server, for most of them a special HTTP request must be generated with one of the existing methods (GET, POST, PUT, DELETE). This way of communication can be a big problem if the connection to the Internet is weak, there are a lot of HTTP requests because you have to wait for each request to be executed and for the web server to return the data. In this paper, one implementation of GraphQL is presented. GraphQL is an open-source data query and manipulation language for APIs. GraphQL enables faster application development and has less server code. The key advantage is the number of HTTP requests because all the desired data of the page is obtained with one request. This paper will show a comparative analysis on the example of a real website in the case of using the REST architecture and GraphQL in the case of different qualities of Internet connections, code complexity and the number of required requests.


2018 ◽  
Vol 7 (2.30) ◽  
pp. 6
Author(s):  
Daljit Kaur ◽  
Dr Parminder Kaur

With the growth of web and Internet, every era of human life has been affected. People want to make their or their organization’s presence globally visible through this medium. Web applications and/or mobile apps are used for the purpose of making their recognition as well as to attract the clients worldwide. With the demand of putting the business or services online faster than anyone else, web applications are developed in hustle and under pressure by developers and most of the times they ignore the few essential activities for securing them from severe attacks, which may be a greater loss for the business. This work is an effort to understand the complex distributed environment of web applications and show the impact of husting the web development process.  


Author(s):  
Hongqing Song ◽  
Stephen Huang

Abstract The purpose of this tool, Rapid Web Application Generator (RWAG), is to allow a user to create a database-driven web application without the knowledge of DBMS and server-side programming. RWAG automatically generates database definitions and ASP pages for manipulating the data. The advantages of using RWAG are as follows: first, a user can create web applications in minutes without ever having to write any code (no need to know ASP, Perl, or Java); secondly, an advanced user can leverage his knowledge of ASP, Perl, Java, JavaScript, HTML, XML and DBMS to expand and customize the web application; thirdly, RWAG allows a user to own a record in the database, which means a record can only be edited by the user who creates it; finally, RWAG provides multiple user access levels. RWAG is ideal for a group of users to share information on the web.


Sign in / Sign up

Export Citation Format

Share Document