asp技术外文翻译.docx

原文：（一）an active server page (asp)1. this paper firstly introduces multi-tier b/s architecture and web-related technology .based on them , this paper presents system objection, system demand, main feather and system design solution ,particularly describes system design and implement in detail. in system design and implement，and key points in other sub-system are also analyzed further .this paper also introduces mostly technology of system . lastly, this paper makes a summery and figures out some problem which need to be improved.2. computing has brought about a whole new standard of corporate computing productivity, but at the same time it has introduced many new problems for corporate it organizations. the advent of low-cost desktop computers makes b/s possible. no longer is it necessary for users to wait even seconds to interact with their corporate data. with their own computer on their desktop they do not need to wait for the mainframe to respond. all of this cheap computer power has also made it possible to support computation- intensive graphical interfaces, which are much easier for users to understand. in order for b/s to work, the application program which used to reside entirely on the mainframe has been split into two pieces, the client piece and the server piece. the portion of the application that resides in the client personal computer includes logic for the presentation of information to the user and mechanisms for accepting user input. it also includes logic for data interaction at the client, such as changing the appearance of the graphical interface as the user make various choices. the client software often includes corporate business rules that allow data to be validated before it is sent to the server. the portion of the application that remains on the server is usually just the portion that stores data at a central location, accessible to other users. the once mighty mainframes have been reduced to database servers, while the rest of the application has migrated out to the clients. this migration has caused many problems. the client machines have become fat. as the complexity of applications has risen it has become necessary to supply users with more and more powerful computers with faster processors, more disk storage, and more ram. it is true that personal computer manufacturers have been able to deliver better and better computers for the same amount of money, but the constant upgrades required are costly for corporations. it takes more people and time to upgrade hundreds or thousands of personal computers than it used to take to just upgrade the mainframes. setting aside the cost of client equipment, the proliferation of corporate applications, including business logic, to hundreds or thousands of machines has become a major cost factor for corporations. where it staffs used to be able to maintain all the corporate software assets in one central location, they now need to maintain corporate software spread all across the corporation, often housed in computers that are out of it control. there are many estimates available that the cost of client/server computing is eight or more times the cost of the equipment alone. several companies offer large, expensive systems that have the sole purpose of maintaining corporate software spread out all over the corporation. the issue here is not personal-productivity software such as word processors and spreadsheets. personal software products have enabled knowledge workers to attain new heights of productivity. the issue is the maintenance of corporate software, such as order-entry and accounting. imagine the difficulty of making a schema change in a corporate database, and synchronizing that change with the updating of thousands of copies of the corresponding client software. it is true that the use of department-level lans can bring down the number of copies that need to be updated to hundreds, instead of thousands. the size of the lans must be limited, because the large size of the fat client software requires a responsive lan or else the users will just copy the enterprise software to their own machines, bringing us back to thousands of copies to be maintained. the task of making simultaneous changes to even hundreds of copies of client software is still a daunting one.3. which in turn serves it back to the client in your personal computer, which displays the information for you. the client/server model has become one of the central ideas of network computing. most business applications being written today use the client/server model. so does the internets main program, tcp/ip. in marketing, the term has been used to distinguish distributed computing by smaller dispersed computers from the monolithic centralized computing of mainframe computers. but this distinction has largely disappeared as mainframes and their applications have also turned to the client/server model and become part of network computing. in the usual client/server model, one server, sometimes called a daemon, is activated and awaits client requests. typically, multiple client programs share the services of a common server program. both client programs and server programs are often part of a larger program or application. relative to the internet, your web browser is a client program that requests services (the sending of web pages or files) from a web server (which technically is called a hypertext transport protocol or http server) in another computer somewhere on the internet. similarly, your computer with tcp/ip installed allows you to make client requests for files from file transfer protocol (ftp) servers in other computers on the internet. other program relationship models included master/slave, with one program being in charge of all other programs, and peer-to-peer, with either of two programs able to initiate a transaction.asp is also an abbreviation for application service provider. an active server page (asp) is an html page that includes one or more scripts (small embedded programs) that are processed on a microsoft web server before the page is sent to the user. an asp is somewhat similar to a server-side include or a common gateway interface (cgi) application in that all involve programs that run on the server, usually tailoring a page for the user. typically, the script in the web page at the server uses input received as the result of the users request for the page to access data from a database and then builds or customizes the page on the fly before sending it to the requestor. asp is a feature of the microsoft internet information server (iis), but, since the server-side script is just building a regular html page, it can be delivered to almost any browser. you can create an asp file by including a script written in vbscript or javascript in an html file or by using activex data objects (ado) program statements in the html file. you name the html file with the .asp file suffix. microsoft recommends the use of the server-side asp rather than a client-side script, where there is actually a choice, because the server-side script will result in an easily displayable html page. client-side scripts (for example, with javascript) may not work as intended on older browsers. for web service applications, microsoft provides a new version of asp support called asp.net.4. browser/server is a trademark for the new paradigm of corporate computing that is now possible using technology developed for the world wide web. at the present time the web is used by the many corporations to distribute marketing materials. the corporate web server is usually just a brochure server for the marketing department. the potential exists for using web browsers and severs for much more, especially behind the corporate firewall. browser/server technology can be used to enhance most corporate computing systems, not just the system used for marketing. to understand the important new role that browser/server technology can play within a company it is useful to examine the previous paradigms that have paved the way for browser/server computing. computers were first used in batch mode. end users had little interaction with the corporate computing systems. inputs would be gathered in a batch and keyed into punch cards, which were fed by operators into the mainframe computer when the computer was done running previous batch jobs. when the mainframe processed the job it usually produced printed output which eventually made its way to the end user. the batch process included no user interaction, and the only recourse a user had after discovering errors in the batch run was to go through the cycle, which often took hours or even days, again and again. the addition of dumb terminals to the mainframe gave the users direct, hands-on, connections to the corporate computer. users no longer had to wait for a computer operator to run their jobs, they could enter the data and initiate processing themselves. there were still delays involved. dumb terminals were useful for inputting and displaying information, but because they had no processing ability it was necessary for the user to interact with the mainframe in order to interact with their data. batch jobs previously could be run one-by-one if necessary, but mainframes had to deal with all attached terminals seemingly at once. this lead to delays as users waited for the mainframe to turn around their terminal messages while they interacted with their data. still, the delays were now down to seconds or minutes, instead of hours or days. client/server computing has brought about a whole new standard of corporate computing productivity, but at the same time it has introduced many new problems for corporate it organizations. the advent of low-cost desktop computers makes client/server possible. no longer is it necessary for users to wait even seconds to interact with their corporate data. with their own computer on their desktop they do not need to wait for the mainframe to respond. all of this cheap computer power has also made it possible to support computation- intensive graphical interfaces, which are much easier for users to understand. in order for client/server to work, the application program which used to reside entirely on the mainframe has been split into two pieces, the client piece and the server piece. the portion of the application that resides in the client personal computer includes logic for the presentation of information to the user and mechanisms for accepting user input. it also includes logic for data interaction at the client, such as changing the appearance of the graphical interface as the user make various choices. the client software often includes corporate business rules that allow data to be validated before it is sent to the server. the portion of the application that remains on the server is usually just the portion that stores data at a central location, accessible to other users. the once mighty mainframes have been reduced to database servers, while the rest of the application has migrated out to the clients. this migration has caused many problems. the client machines have become fat. as the complexity of applications has risen it has become necessary to supply users with more and more powerful computers with faster processors, more disk storage, and more ram. it is true that personal computer manufacturers have been able to deliver better and better computers for the same amount of money, but the constant upgrades required are costly for corporations. it takes more people and time to upgrade hundreds or thousands of personal computers than it used to take to just upgrade the mainframes. setting aside the cost of client equipment, the proliferation of corporate applications, including business logic, to hundreds or thousands of machines has become a major cost factor for corporations. where it staffs used to be able to maintain all the corporate software assets in one central location, they now need to maintain corporate software spread all across the corporation, often housed in computers that are out of it control. there are many estimates available that the cost of client/server computing is eight or more times the cost of the equipment alone. several companies offer large, expensive systems that have the sole purpose of maintaining corporate software spread out all over the corporation. the issue here is not personal-productivity software such as word processors and spreadsheets. personal software products have enabled knowledge workers to attain new heights of productivity. the issue is the maintenance of corporate software, such as order-entry and accounting. imagine the difficulty of making a schema change in a corporate database, and synchronizing that change with the updating of thousands of copies of the corresponding client software. it is true that the use of department-level lans can bring down the number of copies that need to be updated to hundreds, instead of thousands. the size of the lans must be limited, because the large size of the fat client software requires a responsive lan or else the users will just copy the enterprise software to their own machines, bringing us back to thousands of copies to be maintained. the task of making simultaneous changes to even hundreds of copies of client software is still a daunting one. the split-up of the corporate applications is different for browser/server . the user interface and the data interaction components are still run on the user machine, but the business logic usually remains on the server, usually in a special server called an application server.the user interface and data interaction components do run on the client, but they are not ultimately stored there. they are most probably java applets stored in a corporate intranet web server, and they are automatically loaded into the browser software on the user machine as they are needed. if a newer version becomes available, then that version is automatically loaded.we have achieved the same benefits as with client/server, but without the enormous distribution and maintenance problem. the only software that the user machine needs, besides an operating system and personal productivity software, is a web browser that runs java applets. since much of the fat of the application resides in the business logic application server, the need to constantly upgrade the user machines is greatly reduced. there is no need to spend precious time and hard disk space installing corporate software on thousands of user machines, or hundreds of departmental lans. corporate software assets now all reside in corporate servers, under it control. updates to systems are now easily coordinated.so exactly what is browser/server technology? browser/server is an important adaptation of modern network-centric computing that optimizes the performance of mission critical enterprise applications deployed via the corporate intranet and/or world wide web. browser/server accomplishes these performance gains with customized multi-tiered infrastructure and application designs that produce production solutions with reduced network requests and increased user interaction.（二）software quality assurancethe activity of software quality assurance is closely related to verification and validation activities carried out at each stage of the software life cycle1indeed，in many organizations there is no distinction made between these activitieshowever，quality assurance and other verification and validation activities are actually quite separate，with quality assurance being a management function and verification and validation being part of the process of software development2an appropriate definition of software quality assurance is provided by bersoff（1984）：quality assurance consists of those procedures，techniques and tools applied by professionals to ensure that a product meets or exceeds prespecified standards during a products development cycle3；and without specific prescribed standards，quality assurance entails ensuring that a product meets or exceed a minimal industrial and / or commercially acceptable level of excellence this definition is，of course4，a fairly general one and it suggests that，firstly，software standards can be established and，secondly，the level of excellence of a software product can be estimatedthe development of software engineering project standards is an extremely difficult process. a standard is some abstract representation of a product which defines the minimal level of performance，robustness，organization，etc.，which the developed product must attain5at the time of writing，some software standards have been developed by the ieee，ansi and military organizationsthese standards describe configuration management plans，documentation，specification practices，software comparisons，etcother standards which are currently under development include standards for reliability，measurement，the use of ada as pdl6，software testing and othersbransta d and powell（1984）describe both existing and planned software standards as well as discussing standardization in more general terms the problem with national software standards is that they tend to be very general in nature. this is inevitable as，unlike hardware，we are not yet capable of quantifying most software characteristicseffective quality assurance within an organization thus requires the development of more specific organizational standardsof course，the problem which arises in developing software standards for quality assurance and which makes the assessment of the level of excellence of a software product difficult to assess is the elusive nature of s