【中英雙語】513關(guān)于計算機專業(yè)app應(yīng)用html設(shè)計的畢業(yè)設(shè)計論文英文英語外文文獻(xiàn)翻譯成品資料：面向?qū)ο蟮膚eb應(yīng)用程序開發(fā)（中英文雙語對照）

1、本文是中英雙語對照畢業(yè)設(shè)計論文外文文獻(xiàn)翻譯，下載之后無需調(diào)整復(fù)雜的格式直接可用！一輩子也就一次的事！外文標(biāo)題：OBJECT- ORIENTED WEB APPLICATION DEVELOPMENT外文作者：HAN S-W. GELLERSEN AN D M ARTIN GAEDKE文獻(xiàn)出處: IEEE Internet Computing 3(1):60 - 68,2018 (如覺得年份太老，可改為近 2 年，畢竟很多畢業(yè)生都這樣做)

2、英文 4015 單詞，26661 字符(字符就是印刷符)，中文 6698 漢字。 （如果字?jǐn)?shù)多了，可自行刪減，大多數(shù)學(xué)校都是要求選取外文的一部分內(nèi)容進(jìn)行翻譯的。 ）OBJECT- ORIENTED WEB APPLICATION DEVELOPMENTThe Web has evolved into a global environment for delivering all kinds of applications, rangin

3、g from small-scale and short-lived services to large-scale, enterprise workflow systems distributed over many servers. Applications that use HTML-based front ends benefit from the pervasive distribution of Web browsers f

4、or universal, cross-platform access. Another striking advantage of Web delivery lies in the concept of thin clientsand centralized maintenance, facilitating instantaneous deployment of software updates at minimal cost. W

5、hile the popularity of the Web and its advantages as a client-server platform have led to countless HTML-based applications, the development of Web applications is still mostly ad hoc. There is no rigorous, systematic ap

6、proach, and most current Web application development and management practices rely on the knowledge and experience of individual developers.One reason for the lack of a structured approach may be in the Web’s legacy as a

7、n information medium rather than an application platform. Web development is seen primarily as an authoring problem rather than a software development problem to which well-established software engineering principles sho

8、uld apply.We believe another reason is that the Web implementation model does not relate well General Softw are Development Conventional software processes usually address four development phases: analysis, design,

9、implementation, and maintenance/evolution. During analysis, developers build a model of an application in terms of the domain. Ideally, this analysis concentrates on the application’s problem space—separate from softwar

10、e considerations, which are part of the solution space. Accordingly, this phase should not be affected by whether or not the application is to be delivered over the Web. Based on the analysis, a model of the software sol

11、ution is defined during the design phase. Obviously, the Web application development process— in contrast to a general software process—assumes a Web-based software solution and must accommodate this.The implementation t

12、ransforms the design into actual software. For Web applications, this phase has to rely on available Web implementation technology. Finally, maintenance is concerned with modifications to the software, which may occur at

13、 the implementation, design, or even analysis levels. General software processes are hard to relate to the Web implementation model, as will be discussed below. The Web implementation model is based on flat decomposition

14、 of applications into resources. Resources have a unique address, and they are delivered on request from Web server to Web client. They can be static or dynamically generated from a script, but they are inherently specif

15、ic, which means that they cannot capture abstractions.Document Delivery ApplicationsThe World Wide Web was originally designed as an information medium for distributed research teams.4 A key objective was to make it as e

16、asy as possible for authors to deliver documents, and the notion of Web application development essentially boiled down to document development by an author or small group of authors. For this kind of development, the li

17、fe cycle comprises informal analysis of what is to be presented, informal design of how to structure it into hyper-linked chunks of information, and implementation through markup. Following implementation, the doc