[雙語翻譯]計算機外文翻譯--網(wǎng)絡(luò)工程方法的需求分析系統(tǒng)性文獻綜述

1、2200 英文單詞， 英文單詞，12500 英文字符，中文 英文字符，中文 3600 字文獻出處： 文獻出處：Aguilar J A, Garrigós I, Mazón J N, et al. Web engineering approaches for requirement analysis: a systematic literature review[J]. Investigación, 2010

2、:187-190.WEB ENGINEERING APPROACHES FOR REQUIREMENT ANALYSIS:A Systematic Literature ReviewJose Alfonso Aguilar, Irene Garrigós, Jose-Norberto Mazón and Juan TrujilloAbstractWeb engineering software development

3、 is facing continuous 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

4、requirements 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

5、 Web engineering requirements, supported with a formal and well defined strategy.Keywords: Requirement Analysis, Web Engineering, Systematic Review1 INTRODUCTIONOne of the most important factors of success in the softwa

6、re development is the elicitation, management, and analysis of requirements. This is especially true in Web engineering due to the heterogeneous audience of the Web, which may lead to websites difficult to comprehend by

7、 visitors and complex to maintain by designers (Garrigós, Mazón et al. 2009). Importantly, Web applications have certain characteristics that make them different from traditional software or information systems

8、 such as the amount of information they offer (content), the access to the different scenarios where they offer this information (navigational) and how providing this information to the user or the groups of users (funct

9、ionality) of the website. These unique characteristics of 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 ma

10、ke a comprehensive review and synthesis of the current 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 o

11、n potential future research lines. In this paper, 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

12、 the requirements.The main objective 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)

13、.2 BACKGROUNDWeb Engineering (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 d

14、evelopment in which requirements 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

15、sense, one problem 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

16、 final work product and be able to models.Navigational Development Techniques (NDT). In requirements analysis phase NDT applies use case diagrams and a set of templates for requirements with a textual description (Escalo

17、na and Aragon 2008). Traceability is supported through a set of traceability matrices that keeps the relationship between a requirement and their respective artifact that satisfies it (Escalona, Mejías et al. 2004).

18、 Requirements analysis phase and traceability is supported by the NDT-Suite tool (NDT-Profile, NDT-Driver-Quality NDT) using profiles to work with the CASE tool Enterprise Architect. In (Escalona and Koch 2007), the auth

19、ors of NDT and UWE have developed an UML profile for Web requirements called WebRE. In combination of both approaches, the conceptual models can be derived from requirements specification; the main drawback of this appro

20、ach is the lack of tool support for model-to-model transformations.Web Modeling Language (WebML). This is a method for designing websites that allow high-level modeling (Ceri, Fraternali et al. 2000). The requirements an

21、alysis phase is not described in detail, but in (WebML 2009) the author proposes the use of UML (Unified Modeling Language) using use case and activity diagrams for its specification. This approach does not have traceabi

22、lity support.WSDM: Web Site Design Method. The initial two phases of this approach (Mission Statement and User Modeling) are responsible for managing requirements through techniques such as concept maps (of roles and act

23、ivities) and the data dictionary for the definition of functional and security requirements (De Troyer and Leune 1998). The requirements in this approach are specified in a textual form. The lack of transformations betwe

24、en models and support for traceability as well as the lack of a prototype tool which supports the requirements specification demonstrates the limitations of this approach.OOWS: An Object-Oriented Approach for Web Solutio

25、ns Modeling. This approach provides a gathering requirements phase through a series of strategies that implement FRT (Function Refinement Tree), use cases and a set of diagrams (tasks, task specification and data descrip

26、tion) for navigation requirements. This approach has traceability support (Valderas and Pelechano 2009), this is done through a set of transformations rules defined by graph theory. In regard to tool support, this approa

27、ch has an environment called OOWS-Suite (Valverde, Valderas et al. 2007), which is integrated with the OlivaNova tool to provide support for requirements gathering phase. For the traceability tool support, this approach

28、uses two tools, the first one is the open source tool called AGG (Attributed Graph Grammar System) and the second is TaskTracer developed by the authors to generate traceability reports.A-OOH (Adaptive Object Oriented Hy

29、permedia). It is an extension of the OOH modeling method (Object Oriented Hypermedia) addressed to the user. The techniques used in this approach for the requirements specification are the i* framework and UML-Profiles.

30、The requirements model is specified by the designer 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 t

31、ransformations, thus are considering the goals 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 g