128計算機專業(yè)相關有關畢業(yè)設計外文文獻翻譯成品web網(wǎng)站開發(fā)方法 4萬字符

1、<p>　　此文檔是畢業(yè)設計外文翻譯成品（ 含英文原文+中文翻譯），無需調整復雜的格式！下載之后直接可用，方便快捷！本文價格不貴,也就幾十塊錢！一輩子也就一次的事！</p><p>　　外文標題：Web Site Development Methodologies</p><p>　　外文作者：Pedro Isaias，Tomayess Issa</p><p

2、>　　文獻出處:High Level Models and Methodologies for Information Systems ,2014,pp 63-81</p><p>　　英文7215單詞，40895字符，中文11278漢字。</p><p>　　Web Site Development Methodologies</p><p>　　Intro

3、duction</p><p>　　The progress of the World Wide Web appears to be an inexorable process, constantly presenting new challenges and opportunities. With the need to accompany a society that is increasingly dedi

4、cated to new technologies, while at the same time reducing costs and improving information systems, entities must equip themselves with the means to attract more customers and users. Thus, a Web site is no longer seen me

5、rely as a means to present informative content. Today, it is also a platform for business,</p><p>　　With the evolution of the World Wide Web and the increasing need to innovate Web sites, researchers have at

6、tempted to propose different methods and techniques to aid and improve the development of Web pages. Many Web developers base their work on existing software development methodologies; however, there are speci?c aspects

7、of Web development that have lead researchers to propose that speci?c methodologies are needed. Here, we will discuss some of those methodologies by reviewing existing liter</p><p>　　The W3DT Methodology<

8、/p><p>　　The World Wide Web Design Technique, commonly known as W3DT, is a pioneering approach used for the design of Web-based hypermedia applications (Bichler and Nusser 1996). Developed by Bichler and Nusser

9、 (1996), it was conceptualized particularly for the development of large Web sites. It is a technique focused on the collaborative development of distributed Web pages, allowing for the modeling of highly structured, dat

10、abase-like information-domains, and conventional hypertext. Thus, it facilitate</p><p>　　The W3DT methodology comprises an intuitive graphical model suitable for the use of Web pages, which describes design

11、components such as sites, pages, index, forms, menus, links, dynamic links, etc. (Enguix and Davis 1999).</p><p>　　According to Bichler and Nusser (1996), the process of developing a Web site within this fra

12、mework is divided into two stages:</p><p>　　First, the developers outline a graphical representation of the Web site and respective pages, which will account not just for the aesthetic presentation of the We

13、b site but also its navigational structure. This is accomplished by building one or more diagrams. These diagrams consist of at least one page, with optional links, and a layout, which will de?ne formatting speci?cations

14、 for each page. The underlying structure of each page is composed of three elements: form, index, and menu (Bichler a</p><p>　　Second, the developers produce and run prototypes using a computer-based environ

15、ment. This stage utilizes a computer-based design environment that the authors called WebDesigner, giving the developer the opportunity to create a running prototype of the Web site. WebDesigner is W3DT’s CASE tool, prov

16、iding this methodology with an intuitive browser that allows the developers to graphically represent the Web site as it is being developed, and to draw and edit all features of its constructs (Bichler</p><p>

17、;　　W3DT combines a modeling technique with a computer-based design environment. It was primarily created to support the requirements of unstructured, hierarchical domains. It is a visual, high-level methodology that harn

18、esses the functionality of HTML, its fundamental language (Burner 2002).</p><p>　　The Web Site Design Method</p><p>　　The WSDM was ?rst proposed by De Troyer and Leune in 1998. Originally, the a

19、cronym WSDM stood for Web Site Design Method, and only concerned Web sites providing information. With the evolution of the World Wide Web, WSDM has developed to encompass not only traditional Web applications but also s

20、emantic Web applications, which lead to it being renamed as Web Semantics Design Method (Troyer et al. 2008).</p><p>　　The Web Site Design Method is primarily a user-centered methodology, placing the user at

21、 the center of the development of the Web site. It focuses on an audience- driven design philosophy, where the product is design with the audience in mind. Thus, the developer must take into consideration the different p

22、otential target audiences (visitors and users). Their necessities and preferences must be the starting point for the design process. This means that the key structure of the Web site is derive</p><p>　　Its u

23、ltimate purpose is to break down multiple design problems by offering a systematic, multiphase approach to Web design. Therefore, each design phase focuses on one speci?c feature of the Web design cycle, such as requirem

24、ents and task analysis, data and functionality modeling, navigation modeling, presentation modeling and implementation (Plessers et al. 2005).</p><p>　　WSDM is a methodology which not only offers modeling pr

25、imitives, allowing Web developers to design and develop models that portray the Web site/application from different perspectives and at different levels of abstraction, but, in addition, it also proposes a systematic way

26、 to develop the Web application (Troyer et al. 2008).</p><p>　　Since this methodology is not merely attached to a technology, it does not entail the design and structure of the data. Its main concern is to i

27、dentify potential users and their information necessities (Burner 2002). Thus, it can be asserted that the management of information is at the center of this methodology.</p><p>　　The WSDM comprises ?ve fund

28、amental stages (Troyer and Leune 1998), which are summarized in Fig. 4.1. There is a preliminary stage, the mission statement speci?cation, during which the purpose and goals of the Web site are outlined, as well as its

29、subject and target users (Plessers et al. 2005). The second stage is user modeling. Here, it is crucial to focus on the potential users of the Web site. This stage is divided into two phases: user classi?cation and user

30、class description, where the user</p><p>　　The purpose is to produce a reliable, enjoyable, and ef?cient “l(fā)ook” for the conceptual design made in prior stages. The fourth stage is implementation, the actual

31、completion of the Web site, and its placement online. When developing an application with this methodology, the developer must follow a well-de?ned design philosophy that will aid him/her with the necessary support to or

32、ganize the Web site. With the WSDM, development comprises a chain of successive stages. Each stage has a well-de?ned</p><p>　　The implementation of WSDM guarantees that autonomic computing elements can be ac

33、cessed in a regular way and have well-de?ned life cycles. Furthermore, each of the elements is regarded as a resource that is addressable through the Web Services Addressing Standard (Litoiu et al. 2008). Burner (2002) a

34、rgues that “WSDM is good to design front-ends and design the ‘look and feel,’ but it does not either explicitly design, or manage dynamic data. It is advisable to combine it with a second methodology</p><p>

35、　　Relationship Management Methodology (RMM)</p><p>　　The Relationship Management Methodology (RMM) was originally developed in the 1990s, as a framework for the design and construction of hypermedia applicat

36、ions. It is thus called because it focuses on hypermedia applications as a vehicle for the relationships between information objects (Isakowitz et al. 1995). RRM is a structured methodology. The design stages of the proc

37、ess are preceded by a number of studies focusing on such things as the objectives of the Web site, market and user analysis, i</p><p>　　After needs, goals, and requirements of the project are well de?ned, th

38、ere follows a process of seven stages, as illustrated in Fig. 4.2.</p><p>　　R Design The information domain of the application is represented via an Entity–Relationship (E-R) diagram. According to Isakowitz

39、et al. (1995), this ?rst step of the design process represents a study of the relevant entities and relation- ships of the application domain.</p><p>　　Entity Design This step establishes how the information

40、 in the selected entities will be presented to users and how they may access it. The resulting concept is described as an E-R+diagram. It involves dividing an entity into meaningful pieces and organizing these into a hyp

41、ertext network.</p><p>　　Navigational Design The course that will enable hypertext navigation is outlined and designed. Each associative relationship appearing in the E-R+ diagram is examined and represented

42、 in a Relationship Management (RM) diagram. Conversion Protocol Design Developers use a group of conversion rules to convert each element of the Relationship Management Data Model (RMDM) diagram into an object in the tar

43、get platform.</p><p>　　User Interface Design Design of screen layouts for every object appearing in the diagram acquired in Step 3. Run time Behavior Design At this point, developers make decisions about whi

44、ch link traversal, history, backtracking, and navigational mechanisms are to be applied.</p><p>　　It is important to consider the instability and the dimension of the domain in order to choose whether node c

45、ontents and link endpoints are to be developed during application, or dynamically computed on demand at run time.</p><p>　　Construction and Testing This last step consists on the implementation of the applic

46、ation and testing. Applications designed with this methodology are represented in RMDM, based on the E-R model and the Hypermedia Design Method (HDM), which was one of the ?rst methods created to identify the structure a

47、nd interaction of hypermedia applications. RMM combines a top-down and a bottom-up approach (Koch 1999). The Data Models thus created allow the breaking apart of the attributes of a given object o</p><p>　　R

48、MM is particularly adequate to the development and implementation of Web sites focusing on relational databases. It allows for the portrayal and development of the application domain in an abstract way, and it describes

49、all elements of the application domain regarding entity types, attributes, and relationships, through the inclusion of the Relationship Data Models (Antoniol et al. 2000). However，Howcroft and Carroll (2000) have observe

50、d that RRM is exceedingly complex, which makes it less adap</p><p>　　Object-Oriented Hypermedia Design Methodology (OOHDM)</p><p>　　The focus of a hypermedia application is information, and the

51、principle that information can be divided into smaller parts regardless of how it is presented or stored. Schwabe and Rossi (1995a) argue that the Object-oriented Hypermedia Design Method (OOHDM) uses abstraction and com

52、position mechanisms in an object-oriented model, in order to allow for a concise description of complex information items and permit the speci?cation of complex navigation patterns and interface transformations. OOHDM &l

53、t;/p><p>　　the expressiveness of the model (Burner 2002). </p><p>　　Contrary to HDM, OOHDM pre- sents a clearly de?ned method for the development of hypermedia applications (Gaedke and Graef 2000).

54、</p><p>　　Under the OOHDM methodology, the hypermedia application is developed in a four-stage process sustaining an incremental or prototype process model. Each stage emphasizes a particular design concern,

55、 and an object-oriented model is constructed. Classi?cation, aggregation, and generalization/specialization are used throughout the process to improve abstraction power and reuse opportunities (Schwabe and Rossi 1995a).

56、The four stages are described in Table 4.1.</p><p>　　In the conceptual design stage, a conceptual model of the application domain is developed using well-known object-oriented modeling standards. As a result

57、, a class schema is produced, consisting of subsystems, classes, and relationships, with multiple-valued attributes and explicitly indicated directions. The goal, at this point, is to aggregate and summarize the domain s

58、emantics in the widest and most neutral form possible, without particular concerns regarding users and tasks (Schwabe et al. 1</p><p>　　The second stage is navigational design, a description and visualizatio

59、n of the navigational structure of the hypermedia application, based on numerous navigation classes such as nodes, links, indexes, and guided tours. The multivalued attributes described in the conceptual model are corres

60、ponded to different navigation classes. OOHDM posits that navigation objects are the concrete components that give form to conceptual objects. Likewise, links also re?ect conceptual relationships. The resultin</p>

61、<p>　　The third stage is abstract interface design, where an abstract interface model is developed by identifying perceptible objects (such as a picture, a city map…) and interpreting them in terms of interface cla

62、sses. Interface classes are described as aggregations of primitive classes (such as text ?elds and buttons). Because user interface is a fundamental aspect of Web development, it is also an essential stage</p><

63、;p>　　of the OOHDM process. The abstract interface speci?cation will determine the appearance of navigational objects, which objects will activate navigational actions, the synchronization between multimedia elements a

64、nd the context and purpose of interface transformations. This is achieved by means of Abstract Data Views, formal models that describe structural as well as interactive aspects of the interface (Schwabe et al. 1999).<

65、/p><p>　　The fourth and ?nal stage is implementation, and it essentially entails the running of the application. A particular attention is now given to the run time environment. Schwabe et al. (1999) outlined a

66、n appropriate environment named OOHDM-Web, based on the Lua scripting language and the CGI Lua environment. It introduces templates mixing HTML and calls to functions within the navigational library.</p><p>

67、　　These steps are carried out through a combination of incremental, iterative, and prototyped-based development styles. During each step, a set of object-oriented models describing particular design concerns are built or

68、 enriched from previous iterations (Schwabe et al. 1996). OOHDM takes into consideration the very nature of management information systems (MIS), where different users need to access shared data in a way that is adapted

69、for them. A hypermedia application is developed and built as a</p><p>　　Ultimately, the purpose of OOHDM is to aid application designers in the development of single-user hypermedia environments. It is also

70、a methodology oriented toward a perceptive model of hypermedia applications, in which users/ visitors navigate through a hypermedia space that was authored beforehand (Schümmer et al. 1999). As a result of this orie

71、ntation, Schümmer et al. (1999) argue that OOHDM is missing some of the possibilities for the design of editing or authoring functionalities that perm</p><p>　　Therefore, to minimize the lack of editing

72、 and management of the hypermedia environment, these authors present the collaborative OOHDM, aimed at facilitating the design of collaborative hypermedia environments. It introduces an interaction design level to the OO

73、HDM, describing the ways in which users/visitors are able to interact with the hypermedia content and with each other.</p><p>　　Web Engineering</p><p>　　In 1998, a group of researchers establish

74、ed the grounds for Web Engineering, an attempt at creating a new discipline that could introduce sound principles taken from engineering and management into the disorganized panorama of Web development. It was observed t

75、hat there was little methodical discipline in Web development and that most applications were developed through an ad hoc, contingency plan. But the increasing importance of Web applications, as a separate entity of info

76、rmation systems, ca</p><p>　　Web Engineering brings together practices from traditional software engineering methods, adapting them to the more ?exible reality of the Web, and other practices that pertain to

77、 the speci?c nature of Web development in itself. It is de?ned by its creators as “the establishment and use of sound scienti?c, engineering, and management principles and disciplined and systematic approaches to the suc

78、cessful development, deployment and maintenance of high quality Web-based systems and applications” (M</p><p>　　Many developers of Web applications traditionally focused on process logic and data management

79、before moving on to develop the user interface, a practice that derives from the well-established methodologies for software engineering which dated back to the 1960s. But in Web development, user interface is of the utm

80、ost importance, as it provides users with an immediate ?rst impression of the Web site’s purpose. This has introduced an aesthetic component that did not previously exist, attributing m</p><p>　　Building on

81、the notion that the designers must consider issues of usability and HCI principles when creating a Web site, Issa (2008) developed a new methodology, named the Participative Methodology for Marketing Web sites, as a resu

82、lt of an intensive study of existing systems development methodologies, marketing methodologies, and other Web development methodologies (Issa 2008). The concept of usability is central to this approach, due to its focus

83、 on marketing and sales, which transforms the us</p><p>　　This is one of the aspects that pertain to the speci?c nature of Web development as opposed to traditional software development, but there are other

84、aspects such as: The fact that its document-oriented, containing static or dynamic content; its heavy reliance on appearance and visual creativity; a vast, potentially global, user base, with the corresponding variety in

85、 pro?les and preferences; shorter time frames for development than with regular software; a greater variety in the background, expe</p><p>　　Web Engineering is centered on the premise that Web development ha

86、s 6 different dimensions (Deshpande et al. 2002), as illustrated in Fig. 4.3. The authors argue that most existing Web development techniques do not follow all of these stages, starting the project not with planning and

87、management but at a given later stage (Deshpande et al. 2002).</p><p>　　Web Engineering proposes a multidisciplinary approach to development and determines that all of the following stages of development mus

88、t be taken into account for a solid, successful Web product (Murugesan et al. 2001):</p><p>　　1.Requirements speci?cation and analysis</p><p>　　2.Web-based system development techniques</p>

89、;<p>　　3.Integration with legacy systems</p><p>　　4.Migration of legacy systems to Web environments</p><p>　　5.Web-based real-time applications development</p><p>　　6.Testing

90、, veri?cation, and validation</p><p>　　7.Quality assessment, control, and assurance</p><p>　　8.Con?guration and project management</p><p>　　9.“Web metrics” for estimation of develop

91、ment efforts</p><p>　　10.Performance speci?cation and evaluation</p><p>　　11.Update and maintenance</p><p>　　12.Development models, teams, and staf?ng</p><p>　　13.Human

92、 and cultural aspects</p><p>　　14.User-centric development, user modeling, user involvement, and feedback</p><p>　　15.End-user application development</p><p>　　16.Education and trai

93、ning</p><p>　　Web Engineering proponents argue that future development models should build on these principles and good practices. Thus, we can assert that Web Engineering is not a methodology , but it is a

94、set of standards that is designed to in?uence or shape future models of development, making it an important milestone in the evolution of Web development methodologies.</p><p>　　Internet Commerce Development

95、 Methodology (ICDM)</p><p>　　As the focus of applications development shifted from traditional information systems to the Web, there was a particular aspect of Web development that captured the attention of

96、researchers: e-commerce. Standing (1999) thus proposed a methodology that would speci?cally cater to the needs of e-commerce projects within organizational contexts. It was intended as both a management strategy, and a d

97、evelopment strategy, heavily focused on business goals and needs. It presents a holistic, subjectivist</p><p>　　ICDM proposes that the development of a Web site entails three different levels or dimensions:

98、the organizational level, consisting of a Web management team, the development level, consisting of a Web site component production team, and the implementation level, consisting of all the technical aspects of implement