Increasing the Quality of Web systems By inserting requirements of accessibility and usability Ana Luiza Dias, Renata Pontin de Mattos Fortes and Paulo Cesar Masiero Instituto de Ciências Matemáticas e de Computação – ICMC Universidade de São Paulo – USP, São Carlos, Brazil {anadias, renata, masiero}@icmc.usp.br : e-mail address if desired Abstract—The traditional software development is not entirely suitable for development of Web systems. These systems must be developed supported by a fast life cycle, considering users´ characteristics. In this context, this paper describes how to improve the quality of Web systems including accessibility and usability non-functional requirements during development. For this propose, this paper explains how to extends the requirements engineering phase of a process of Web development with activities related to users´ profile and needs. Keywords - Requirements elicitation; Quality of Web systems; Software Engineering; Non-functional requirements specification; Web Accessibility; Usability I. INTRODUCTION Quality is defined by ISO 8402 [23], as the totality of characteristics of an entity that gives it the ability to satisfy explicit and implied needs. Entity is the product itself, the explicit needs are the own conditions and objectives proposed by the producer and the implied needs are conditions, more subjective, such as differences between the users’ needs, the time evolution, the implicit ethical, security issues and others. The quality of software, according to Pressman [20], is compliance about functional and performance requirements explicitly declared, the development patterns clearly documented and implicit characteristics that are expected of all professionally developed software. The software industry is becoming increasingly important and complex, requiring that the software organizations to invest in quality of their development processes. The requirements elicitation is one of the activities that can help software organizations to deal with this scenario, especially the definition of initiatives that can improve the requirements elicitation and activities analysis [26]. Thus, to collaborate with this context and considering the importance of human resources for software development, this paper presents a list of non-functional requirements that must be considered on Web engineering, during the development of all types of Web systems. The list of requirements was developed in accordance with accessibility guidelines of the WCAG (Web Content Accessibility Guidelines) [27] [28] and usability heuristics formalized by Nielsen and Molich [16]. This list of accessibility and usability non-functional requirements is proposed to be used in the process of software development, more specifically, the Framework of Web engineering process [21]. In addition to these requirements, we propose the extension of this Framework so that accessibility and usability are considered from the beginning of development. This paper is organized as follows: Section 2 presents a theoretical background, which contains basic information to understand the purpose of this work. In Section 3 related work presented in this paper are presented. In Section 4, the proposed evolution of requirements elicitation activity with tasks that should be considered in all projects of Web systems is shown, followed by Section 5, which sees the application of these requirements in case study. Finally, in Section 6 the conclusions and future work are presented. II. THEORETICAL BACKGROUND A. Web Engeneering Web Engineering emerged as a disciplined initiative aims to support and optimizes efforts often required in development processes, management, maintenance and quality control of the Web systems. It refers to the establishment and use of solid scientific and engineering concepts, management principles and disciplined and systematic ways to develop, make available and evolve high-quality Web systems [8]. To carry out the activities that are part of Web engineering, it is necessary to perform them in accordance with a process or development method. More recently, Pressman and Lowe [21] proposed a process known as Framework of Web engineering process that begins with the communication phase (business needs and description of the objectives are identified), followed by the planning phase (the total cost of project is estimated, the associated risks are assessed and timelines for initial and subsequent phases are defined), modeling phase (helps the developer and user better understand the system requirements that are established Web), construction phase (tools for building Web systems are used, interface, architecture and navigation designs producing executable pages that can be tested in order to reveal errors in the code are defined), ending with the implementation phase (the increment Web system is delivered to the user and he may request changes that will be