asp技术外文翻译

asp技术外文翻译内容摘要：

s logic, to hundreds or thousands of machines has bee 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 puters that are out of IT control. There are many estimates available that the cost of Client/Server puting is eight or more times the cost of the equipment alone. Several panies offer large, expensive systems that have the sole purpose of maintaining corporate software spread out all over the corporation. The issue here is not personalproductivity 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 orderentry 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 departmentlevel 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 splitup of the corporate applications is different for Browser/Server . The user interface and the data interaction ponents 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 ponents do run on the Client, but they are not ultimately stored there. They are most probably Java applets stored in a corpora te Intra Web Server, and they are automatically loaded into the Browser software on the user machine as they are needed. If a newer version bees 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 workcentric puting that optimizes the performance of mission critical enterprise applications deployed via the corporate intra and/or World Wide Web. Browser/Server acplishes these performance gains with customized multitiered infrastructure and application designs that produce production solutions with reduced work requests and increased user interaction. （二） SOFTWARE QUALITY ASSURANCE The activity of software quality assurance is closely related to verification and validation activities carried out at each stage of the software life cycle[1]． Indeed， in many anizations there is no distinction made between these activities． However，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 development[2]． An 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 cycle[3]； and without specific prescribed standards， quality assurance entails ensuring that a product meets or exceed a minimal industrial and / or mercially acceptable level of excellence． This definition is， of course[4]， 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 estimated． The 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， anization， etc.， which the developed product must attain[5]． At the time of writing， some software standards have been developed by the IEEE， ANSI and military anizations． These standards describe configuration management plans， documentation，specification practices， software parisons， etc． Other standards which are currently under development include standards for reliability， measurement， the use of Ada as PDL[6]， software testing and others． Bransta 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 characteristics． Effective quality assurance within an anization thus requires the development of more specific anizational standards． Of course， the problem which arises in developing software standards for quality assurance a。