[雙語(yǔ)翻譯]計(jì)算機(jī)外文翻譯--網(wǎng)絡(luò)工程方法的需求分析系統(tǒng)性文獻(xiàn)綜述（英文）

1、WEB ENGINEERING APPROACHES FOR REQUIREMENT ANALYSIS A Systematic Literature Review Jose Alfonso Aguilar, Irene Garrigós, Jose-Norberto Mazón and Juan Trujillo Lucentia Research Group, University of Alicante,

2、 Spain jaac12@alu.ua.es, igarrigos@dlsi.ua.es, jnmazon@dlsi.ua.es, jtrujillo@dlsi.ua.es Keywords: Requirement Analysis, Web Engineering, Systematic Review. Abstract: Web engineering software development is facing con

3、tinuous changes in technology implementation. This involves analysts, developers and designers to provide extra effort in the design and maintenance of Web applications in order to adapt them to changes in requirements

4、 and implementation technologies. In this paper, a systematic review is presented in order to obtain, in a formal way, the current state-of-the-art about approaches for modeling, analysis and specification of Web engin

5、eering requirements, supported with a formal and well defined strategy. 1 INTRODUCTION One of the most important factors of success in the software development is the elicitation, management, and analysis of requi

6、rements. This is especially true in Web engineering due to the heterogeneous audience of the Web, which may lead to websites difficult to comprehend by visitors and complex to maintain by designers (Garrigós, Ma

7、zón et al. 2009). Importantly, Web applications have certain characteristics that make them different from traditional software or information systems such as the amount of information they offer (content), the

8、 access to the different scenarios where they offer this information (navigational) and how providing this information to the user or the groups of users (functionality) of the website. These unique characteristics o

9、f Web applications enforced new Web engineering methodologies to cope with those new requirements and Web developers need to adopt it. The goal of this work is to make a comprehensive review and synthesis of the cu

10、rrent state-of-the-art in the literature related to the specification of Web engineering requirements with the purpose of showing gaps in current research and shed light on potential future research lines. In this p

11、aper, we expect to study methods and techniques that propose the specification of Web requirements and bring some kind of support to generate several models of the website from the requirements. The main objective

12、of this work has been achieved through a systematic review using the approach of Kitchenham (Kitchenham 2004) and taking into account Mark Staples experiences (Staples and Niazi 2007). 2 BACKGROUND Web Engineering (

13、WE) is a branch of Software Engineering (SE) that defines techniques, processes and specific models for the Web environment. WE has a sub-discipline that refers to the phase in application development in which requir

14、ements of different stakeholders are gathered and processed, resulting in a requirements specification, this phase is called Requirements Engineering (RE) (Almeida, van Eck et al. 2006). In this sense, one problem

15、associated with RE is that requirements should be fully completed. To this aim, it is necessary that users and stakeholders can see that it has completed the transformation of their requirements in the final work pro

16、duct and be able to distinguish which one belongs to a certain requirement, this will help determining which requirements will be impacted due to the modification of a work product or vice versa. Furthermore,

17、requirements engineering needs to ensure Requirements Traceability (RT), RT refers to the ability to describe and follow the life of a 187Table 1: Summary of methodological approaches. Approach Techniques Traceabi

18、lity Support Tools Support Requirements A. Traceability NDT Use cases, textual templates Yes NDT-Tool NDT-Tool NDT-Suite WebML Use cases,activity diagrams No WebRatio No No WSDM Concept maps, data dictiona

19、ry No No No No UWE Use cases, UML profiles No ArgoUWE MagicUWE ArgoUWE No OOWS Use cases, Task diagrams, FRT Yes OlivaNova OlivaNova OOWS-Suite AGG TaskTracer A-OOH Use cases, i*,UML profiles No VisualWade

20、Eclipse Plugin No requirements specification demonstrates the limitations of this approach. OOWS: An Object-Oriented Approach for Web Solutions Modeling. This approach provides a gathering requirements phase thro

21、ugh a series of strategies that implement FRT (Function Refinement Tree), use cases and a set of diagrams (tasks, task specification and data description) for navigation requirements. This approach has traceability s

22、upport (Valderas and Pelechano 2009), this is done through a set of transformations rules defined by graph theory. In regard to tool support, this approach has an environment called OOWS-Suite (Valverde, Valderas et

23、 al. 2007), which is integrated with the OlivaNova tool to provide support for requirements gathering phase. For the traceability tool support, this approach uses two tools, the first one is the open source tool call

24、ed AGG (Attributed Graph Grammar System) and the second is TaskTracer developed by the authors to generate traceability reports. A-OOH (Adaptive Object Oriented Hypermedia). It is an extension of the OOH modeling met

25、hod (Object Oriented Hypermedia) addressed to the user. The techniques used in this approach for the requirements specification are the i* framework and UML-Profiles. The requirements model is specified by the desig

26、ner using i* models, specifically the SR (Strategic Relationship) model and the SD (Strategic Dependency) model. Next, the conceptual models are generated by means of QVT transformations, thus are considering the goa

27、ls and needs of stakeholders that will meet the expectations of users thereby reducing errors that may appear on the final implementation. The traceability between the models generated by this approach could be deriv

28、ed from the transformations rules. The requirements specification phase in A-OOH has been implemented using the Eclipse development platform (Garrigós, Mazón et al. 2009). Next, a brief analys

29、is about the approaches described above is presented, to facilitate this analysis Table 1 is shown. Table 1 shows a tendency towards the application of UML profiles as a technique used by the approaches studied in t

30、his systematic review and the persistence of other one, the use cases. Moreover, although traceability is a very important success factor for software engineering, a common problem in Model-Driven Web development

31、 processes is that most of the approaches lack support for traceability (except NDT and OOWS). Except WSDM, each approach has a tool to support it. In the requirements phase, only NDT, UWE, OOWS and A-OOH have a to

32、ol support. In terms of traceability, the two approaches that have implemented traceability have a tool support. It is worth noting that OOWS combines two tools to achieve this support. In this context, the approach

33、es explored in this systematic review do not consider the real user expectations of the website as well as stakeholders from an early stage of requirements analysis. A- OOH is the exception, as it considers these exp

34、ectations through the i * framework where requirements are modeled based in the user goals and objectives, thus avoiding the requirement specification in textual form (with the effort involved to do it this way) and

35、the based on tasks (depending in most cases the analyst's experience). Is worth mentioning the support offered by the approaches WSDM, NDT, UWE and WebML through its website, they offer examples, published paper

36、s and their respective tools for everyone who visits their website, except WSDM which only offers the download of published papers due to that is a tool that has proprietary licence. In the particular case of UWE and