毕业设计选题及成绩管理开题报告和英文翻译

题目（中文）毕业设计选题及成绩管理

（英文）Graduating the design chooses and result management 课题类型技术开发课题来源教师指定

学生姓名专业班级

指导教师职称

填写日期：年月日一、本课题研究的主要内容、目的和意义

在Internet飞速发展的今天,互联网成为人们快速获取、发布和传递信息的重要渠道,它在人们政治、经济、生活等各个方面发挥着重要的作用。我国各大院校也加快了信息化进程,这为我们网络现代化教育提供了必备的物质基础。毕业设计是大学四年教学工作中的重要一环,毕业设计管理工作具有工作量大,灵活性强、时间要求紧等特点。在技术和需求的推动下,毕业生以班级为单位的原始手工报送的选题方式,暴露出很多缺点和不足,例如,消耗时间长、工作效率不高,可能出现不公平现象等。

本课题提出了一种网上选题及成绩管理系统,它能很好的解决.而且通过本次设计可以让学生更加熟练掌握软件开发的一般过程，并对所学知识做一个全面的总结。同时，选择这一课题，第一，可以让我知道架构一个网站所需掌握的基本技术。毕竟，要想研究web 数据库系统的网络应用与深层次管理，能够设计出一个实际的系统是非常好的。这个“毕业设计选题及成绩管理”能够实现用户登录，查看毕业课题详细情况并选题，成绩管理等这些基本功能，它具备一个网站的基本要素。通过设计这个系统，可以让我掌握一些设计一个完整网站的基本技术。

本系统可实现让在籍学生可以在线选题，了解有关课题的信息，教师可以在线进行信息查询。管理员进行课题、用户维护及成绩管理等。并且具有操作方便，响应快捷等优点。

二、文献综述（国内外相关研究现况和发展趋向）

系统分为学生、教师和管理员维护三部分功能模块。采用ASP.net结合sql数据库实现该基于Web的毕业设计选题及成绩管理系统

系统利用了ASP.NET这一具有强大功能、用于Web开发的全新框架。ASP.NET在系统重处于操作系统内核与应用程序之间，使得应用程序可以更好地利用操作系统提供的功能，并使得应用程序的开发更快、更简单。

本系统采用B/S模式，其最根本的目的是让在籍学生可以在线选题，了解有关论文的信息，教师可以在线进行论文信息输入、论文信息查询等，并且具有操作方便，响应快捷等优点。.

毕业设计管理及信息管理是一个复杂的计算机网络信息系统，本系统采用基于浏览器/服务器（B/C）,客户端/服务器（C/S）混合的应用的体系结构来建设高校的.毕业设计管理及信息管理系统，使毕业设计管理及信息管理系统真正实现信息资源的高度集成与共享、实现信息资源的集中管理和统一调度。

系统的可行性研究：

技术可行性：为了方便交互式应用和数据的大型存储，毕业设计管理系统必须采用B-S框架模式而且支持大型的后台数据库，而Asp.net+SQL SERVER数据库正好满足了交互与大型存取两方面。可见使用Asp.net毕业设计管理系统在技术上是可行的。

操作可行性：毕业设计管理系统是一个集成了选课.审核.学生与老师的交流的网站，用户只要会上网就应该会使用本网站，网站各个部分都有说明和提示，引导用户达到他们的目的。

三、拟采取的研究方法（方案、技术路线等）和实现的可行性论证

系统分为学生、教师和管理员维护三部分功能模块。采用ASP.net结合sql数据库实现该基于Web的毕业设计选题及成绩管理系统

系统利用了ASP.NET这一具有强大功能、用于Web开发的全新框架。ASP.NET在系统重处于操作系统内核与应用程序之间，使得应用程序可以更好地利用操作系统提供的功能，并使得应用程序的开发更快、更简单。

本系统采用B/S模式，其最根本的目的是让在籍学生可以在线选题，了解有关论文的信息，教师可以在线进行论文信息输入、论文信息查询等，并且具有操作方便，响应快捷等优点。.毕业设计管理及信息管理是一个复杂的计算机网络信息系统，本系统采用基于浏览器/服务器（B/C）,客户端/服务器（C/S）混合的应用的体系结构来建设高校的.毕业设计管理及信息管理系统，使毕业设计管理及信息管理系统真正实现信息资源的高度集成与共享、实现信息资源的集中管理和统一调度。

系统的可行性研究：

技术可行性：为了方便交互式应用和数据的大型存储，毕业设计管理系统必须采用B-S框架模式而且支持大型的后台数据库，而Asp.net+SQL SERVER数据库正好满足了交互与大型存取两方面。可见使用Asp.net毕业设计管理系统在技术上是可行的。

操作可行性：毕业设计管理系统是一个集成了选课.审核.学生与老师的交流的网站，用户只要会上网就应该会使用本网站，网站各个部分都有说明和提示，引导用户达到他们的目的。

四、预期结果（或预计成果）

预期目标：通过对毕业设计管理系统的需求分析，分析其可行性及重要性，进而对系统的各个模块进行分析、设计。教师和学生可在任何地方进行选题和申报课题。满足外出实习学生的选题需求。

本课题进行了系统分析、系统的总体设计和数据库设计,最后用ASP.net结合sql数据库实现了该系统。该系统实现的详细功能预计如下

(1)用户类别：登录系统的身份定为三种，一是超级管理员(领导)，二是普通老师，三是学生，只有被授权的用户才可以使用本系统的资源。

(2)权限管理：系统需要经过有效的身份验证可以登录。用户的身份不同，使用的系统资源也不同。学生只可以选择毕业设计，重选毕业设计，及修改自己的密码和查看所获成绩。普通教师为查看所有设计课题被哪些学生所选中及学生所获成绩功能。管理员(领导)拥有整个系统学生、教师、课题、成绩等全部管理功能。

(3)教师管理：领导才有此功能，可添加教师，及教师信息编辑。

(4)学生管理：领导才有此功能，可添加学生，及学生信息编辑。

(5)课题管理：领导才有此功能，可添加课题，及课题信息编辑

(6)成绩管理：领导才有此功能，可录入成绩，及成绩信息编辑

(7)老师查询学生所选课题设计：可根据查询所有设计课题被哪些学生所选中。

(8)学生选课题设计：学生可根据普通老师所出的设计题目，进行选择（修改）。但只能选一个作

为自己的设计题目。

(9)设计成绩查询设计：学生和老师可查寻设计成绩信息

五、研究进度安排

第4周 3.17-3.23搜集相关资料、课题调研，初拟开发计划；

第5周 3.24-3.30写需求规格说明书，设计校园新闻管理系统的总体构架；

第6周 3.31-4.6翻译英文文献，撰写开题报告，初步完善系统的大体模块功能；第7周 4.7-4.13提交开题报告，并根据指导老师意见修改开题报告；

第8周 4.14-4.20对校园新闻管理系统进行详细设计；

第9周 4.21-4.27完成校园新闻管理系统的详细设计，根据导师的意见修改；

第10周 4.28-5.4拟出系统的基本构架，对系统进行编码；

第11周 5.5-5.11对系统中各个模块进行详细的设计；

第12周 5.12-5.18对每一功能模块进行测试，在导师的指导下进行修改；

第13周 5.19-5.25对系统进行测试，并写出测试分析报告；

第14周 5.26-6.1再次对所设计的系统进行全面的检测；

第15周 6.2-6.8撰写毕业设计论文；

第16周 6.9-6.15完成毕业设计论文，根据指导老师的意见对其进行修改和完善；第17周 6.16-6.22提交毕业设计论文，进行毕业设计答辩。

六、主要参考文献

1、参考文献目录

[1]David Buser、John Kauffman著《ASP初级编程》机械工业出版社

[2]萨师煊、王珊著《数据库系统概论（第四版）》高等教育出版社

[3]宣小平、但正刚、张文毅著《ASP数据库系统开发实力导航》人民邮电出版社

[4]李樱、王会英、廖建华著《ASP+SQL Server2005项目开发》人民邮电出版社

[5]吴玉新著《网站ASP后台解决方案》人民邮电出版社

[6]黄明、梁旭著《ASP信息系统设计与开发实例》机械工业出版社

[7]郑人杰著《实用软件工程》清华大学出版社

[8]英文参考文献

[9]《Micosoft.NET编程语言：C#教程》，沉舟，崔培枝，何荣辉等。

[10]《ASP.NET数据库高级编程》，C#篇李应伟，姚素霞，景利。人民邮电出版社。

[11]《计算机网络基础及应用》，白以恩，哈尔滨工业大学出版社，2000年1月。

[12]《ASP.NET2.0的web 2.0应用-Blog.Tags.Rss.NAS.XML.Ajax Mail》郑耀东编注，民邮电出版社。

[13]《系统分析与设计》，王勇领，清华大学出版社

外文参考文献翻译（译文大于5000汉字）

见附件“毕业设计（论文）外文参考文献翻译”

七、审核意见

指导教师对开题的意见：

指导教师签字：年月日

系（院）审核意见：

审核人签字：年月日

说明：1、该表每生一份，系（院）妥善存档；

2、课题来源填：“自选”或“教师指定”或“其它”，课题类型填：“理论研究”或“应用研究”或

“技术开发”或“实验设计”或“其它”。

附件：

毕业设计（论文）外文参考文献翻译

计算机科学与信息工程系（院）2008届

题目（英文）（一）An Active Server Page(ASP)

（二）SOFTWARE QUALITY ASSURANCE

(三)SOFTWARE TESTIN

（中文）（一）asp

（二）软件质量保证

（三）软件测试

学生姓名专业班

指导老师职称

完成日期：年月日原文：

（一）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 Internet's 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 user's 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 theserver-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 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 organizations 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 commercially 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 excellenceof 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，organization，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 organizations．These standards describe configuration management plans，documentation，specification practices，software comparisons，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 organization thus requires the development of more specific organizational standards．Of 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 software quality．Boehm et al．（1978）suggest that quality criteria include but are not limited to：Economy Correctness Resilience

Integrity Reliability Usability

Documentation Modifiability Clarity

Understandability Validity Maintainability

Flexibility Generality Portability

Interoperability Testability Efficiency

Modularity Reusability

Exactly how some of these criteria may be quantified is not clear．Furthermore，as Buckley and Poston（1984）point out，parts of this definition may have no value for a particular product．It may be possible to transfer a system from a microcomputer to a large mainframe but this is often a nonsensical thing to do．Assessment of software quality thus still relies on the judgement of skilled individuals although this does not mean that it is necessarily inferior to quantitative assessment．After all，we cannot assess a painting or a play quantitatively yet this does not preclude a judgement of its quality．

Within an organization，quality assurance should be carried out by an independent software quality assurance team who reports directly to management above the project manager level．The quality assurance team should not be associated with any particular development group but should be responsible for quality assurance across all project groups in an organization．

The activity of quality assurance involves sitting in on design reviews[7]，program walkthroughs，etc.，and reporting on the overall quality of the product as it is developed．It also involves checking that the finished product and its associated documentation conform to those standards which exist．The quality assurance team mayalso assess if the different representations of a product（requirements，design，code）are consistent and complete．

Notice that quality assurance is not the same as system testing．It is the development or testing team’s responsibility to validate the system，with the quality assurance team reporting on both the validation and the adequacy of the validation effort．This naturally involves quality assurance being closely associated with the final integration testing of the system．

Software quality assurance is now an emerging subdiscipline of software engineering[8]．As Buckly and Poston point out，effective software quality assurance is likely to lead to an ultimate reduction in software costs．However，the major hurdle in the path of software management in this area is the lack of usable software standards．The development of accepted and generally applicable standards should be one of the principal goals of research in software engineering．

（三）SOFTWARE TESTING

1.Purpose of Testing

No matter how capably we write programs，it is clear front the variety of possible errors that we should check to insure that our modules are coded correctly．Many programmers view testing as a demonstration that their programs perform properly．However，the idea of demonstrating correctness is really the reverse of what testing is all about．We test a program in order to demonstrate he existence of an error．Because our goal is to discover errors，we can consider a test successful only when an error is discovered．Once an error is found，“debugging”or error correction is the process of determining what causes the error and of making changes to the system so that the error no longer exists．

2．Stages of Testing

In the development of a large system，testing involves several stages．First，each program module is tested as a single program，usually isolated from the other programs in the system．Such testing，known as module testing or unit-testing，verifies that the module functions properly with the types of input expected from studying the module design．Unit testing is done in a controlled environment whenever possible so that the test team can feed a predetermined set of data to the module being tested and observe what output data are produced[1]．In addition，the test team checks the internal data structures，the logic，and the boundary conditions for the input and output data．

When collections of modules have been unit-tested，the next step is to insure that the interfaces among the modules are defined and handled properly．Integration testing is the process of verifying that the components of a system work together as described in the program design and system design specifications．When collections of modules have been unit-tested，the next step is to insure that the interfaces among the modules are defined and handled properly．Integration testing is the process of verifying that the components of a system work together as described in the program design and system design specifications．

Once we are sure that information is passed among modules according to the designprescriptions，we test the system to assure that it has the desired functionality．A function test evaluates the system to determine if the functions described by the requirements specification are actually performed by the integrated system[2]．The result，then，is a functioning system．

Recall that the requirements were specified in two ways：first in the customer’s terminology and again as a set of software and hardware requirements．The function test compares the system being built with the functions described in the software and hardware requirements．Then，a performance test compares the system with the remainder of the software and hardware requirements．If the test is performed in the customer’s actual working environment，a successful test yields a validated system．However，if the test must be performed in a simulated environment，the resulting system is a verified system．

When the performance test is complete，we as developers are certain that the system functions according to our understanding of the system description．The next step is to confer with the customer to make certain that the system works according to the customer’s expectations．We join with the customer to perform an acceptance test in which the system is checked against the customer’s requirements description．When the acceptance test is complete，the accepted system is installed in the environment in which it will be used；a final I nstallation test is performed to make sure that the system still functions as it should．

Fig.8-2illustrates the several stages of testing．Although systems may differ in size，the type of testing described in each stage is necessary for assuring the proper performance of any system being developed．

译文：

（一）asp技术

1.本文首先介绍了课题研究所用的技术:浏览器/服务器结构以及Web应用的相关数据库访问技术。在此基础上，论述了系统的研究目标、系统需求、主要特色和总体设计方案，较详细地论述了详细设计与实现。并且对其它子系统实现中遇到的一些主要问题进行了分析。给出了系统设计和实现中所涉及的主要关键技术。最后，对系统进行了总结并提出了还需要改进的问题。

2.浏览器/服务器计算带来了一个全新的标准，企业计算的生产力，但在同一时间，又推出了许多新的问题，为企业的IT组织。来临的低成本台式电脑，使浏览器/服务器的可能。不再是必要的，为用户的等待，甚至秒的相互作用，他们的公司数据。用自己的电脑在自己的桌面上，他们并不需要等待大型机作出回应。所有这一切都便宜的电脑电源，也使人们有可能以支持计算密集型的图形界面，这是用户更容易理解。为了让浏览器/服务器的工作，应用程序，其中用于居住的完全是对主机已被成两块，一块浏览器和服务器一块。这部分的应用程序是居住在客户端的个人电脑，包括逻辑陈述的信息给用户和机制，以接受用户输入。它也包括逻辑数据交互在客户端，如更改外观的图形界面，为用户作出不同的选择.客户端软件通常包括企业的业务规则，使数据得到验证之前，它是发送到服务器上。这部分的应用仍然在服务器上，通常只是部分和存储数据，在一个位置，方便其他用户。一度浩浩荡荡主机已减少到数据库服务器，而其余的应用迁移到客户。这种迁移，造成了很多问题。由于复杂的应用已上升，它已成为必要的，以供应用户更多和更强大的电脑，速度更快的处理器，更多的磁盘存储，并需要更多的内存。这是事实的个人电脑生产商已经能够为市民提供更佳，更好地为电脑相同数额的钱，但不断升级所需的费用高昂，为公司。它需要更多的人，时间，以提升数以百计或数以千计的个人电脑比以前要到刚刚升级大型机。撇开成本的客户端设备，扩散的企业应用软件，包括业务逻辑，向数百或数千台计算机已成为一个主要的成本因素，为公司。那里的工作人员用，才能保持各企业的软件资产，可以在一个中心位置，他们现在需要维持企业软件蔓延全美各地的公司，往往是住在电脑上出了它的控制。有许多估计可用的成本客户机/服务器计算是8次或者更多次设备的费用。有好几家公司提供庞大，昂贵的系统，有其唯一目的是保持公司软件分散全国各地的公司。这里的问题不是个人生产力的软件，如文字处理和电子表格。个人软件产品，使知识工作者，以达到新的高度的生产力。这个问题，是维持企业软件，如为了收及结算的。困难度可想而知作模式改变公司数据库，并同步这种改变与更新的数千份相应的客户端软件。这是事实，认为利用厅级局域网，可以把拷贝的数量需要加以更新，以数百人，而不是数千人。规模的局域网必须加以，因为体积较大的脂肪客户端软件，需要一个负责任的局域网，否则用户将刚刚复制的企业软件，以自己的机器，把我们带回数千份继续保持。任务是制定同步变化，甚至上百份的客户端软件仍然是一个艰巨的。

3.客户机/服务器描述之间的关系两个计算机程序，其中一个程序，客户端，使得服务请求从另一个程序，服务器，其中符合要求。虽然客户机/服务器的想法可以利用程式在一个单一的计算机，它是一个更重要的思想，在一个网络。在网络，客户机/服务器模型提供了一种便捷的途径来互联的程序分配效率不同地点。电脑交易采用客户机/服务器模型是非常普遍的现象。例如，要检查你的银行帐户从您的计算机，客户端程序在您的计算机前锋你的要求，一台服务器计划于银行。这一计划可能反过来提出请求，以自己的客户端程序发出了一个请求到一个数据库服务器在另外一间银行的电脑检索你的帐户余额。平衡是返回到该银行的客户数据，进而回给客户端，在你的个人电脑，显示器的信息向你提供。

客户机/服务器模式已成为其中的中心思想的网络计算。大多数的商业应用正在写今天使用的客户机/服务器模型。.那么在互联网上的主程序，TCP/IP协议。在市场营销中，这个词已被用来区分分布式计算所规模较小的分散电脑从"铁板一块"集中运算的电脑主机。但这种区分已基本上消失了，因为大型主机及其应用，还拒绝向客户机/服务器模型，并成为部分网络计算。

在通常的客户机/服务器模式，一台服务器，有时被称为守护进程，是激活，并等待客户端的请求。通常情况下，多个客户端程序共享服务的一个共同的服务器程序。这两个客户端程序和服务器程序通常是其中的一部分的一个更大的程式或应用程式。相对到网际网路，你的网络浏览器是一个客户端程序请求服务（发送网页或文件）从一台网络服务器（这在技术上被称为超文本传输协议或HTTP服务器），在另一台计算机上互联网某处。同样地，如果你的电脑与TCP/IP协议安装的，你可以据此要求客户档案，从文件传输协议（FTP）服务器，在其他计算机上互联网。其他计划的关系模式，包括主/从，同一个程序正在负责其他所有节目，而点对点，有两种程序能够启动交易。

积极服务器网页（ASP）的是一个HTML网页，包括一个或多个脚本（小型嵌入式节目），这是处理对微软网络服务器前一页发送给用户。一个ASP的，是有点类似服务器端包括或公共网关接口（CGI）应用在所有涉及程序上运行的服务器，通常剪裁一个网页，为用户手中。通常情况下，脚本在网页上的服务器用途的投入收到了由于用户的请求页面访问数据从一个数据库，然后再建立或定制该网页上飞，然后递交给申请者。

ASP的是一个特点，微软的因特息服务器（IIS），但是，由于服务器端的脚本是刚刚建立一个经常性的HTML页面，它可以提供几乎任何浏览器。您可以创建一个ASP 的文件包括一个脚本写的VBScript或者JavaScript是HTML文件或用ActiveX数据对象（ADO 的）计划报表，在HTML文件。你的名字HTML文件与"ASP的"文件后缀。微软建议使用服务器端的ASP，而不是一个客户端脚本，那里其实是一个选择，因为服务器端的脚本将导致一个很容易Displayable的HTML网页。客户端脚本（例如，在JavaScript）可能无法正常工作打算对旧版本的浏览器。

为Web Service的应用程序，微软提供了一个新版本的ASP支持所谓asp.net

4.浏览器/服务器TM是一个商标为新的范式企业计算的，就是现在要尽可能利用技术的发展，为世界万维网。在目前这个时间在网上使用的是由许多企业派发的营销资料。该公司的网络服务器通常只是一本小册子，服务器市场营销部。

可能存在使用Web浏览器和断绝，为更多的，特别是背后的企业防火墙浏览器/服务器TM技术，可以用来提高大多数企业计算系统，不只是用系统营销。

了解了新的重要作用，浏览器/服务器TM技术，可以发挥一个公司，它是有用的研究范式前已经铺平了道路，为浏览器/服务器计算技术备忘录。

计算机最初是用来在批处理模式。最终用户很少互动，与企业的计算机系统。投入都将聚集在一个"间歇"，并有一套成穿孔卡片，饲养，由经营者到大型主机电脑的时候，电脑是做跑前一批就业机会。当主机处理工作，它通常是生产印刷输出，最终作出了自己的方式向最终用户。

间歇过程主要包括没有用户交互的，仅仅诉诸一个用户后发现错误，在间歇运行，是要经过周期，而往往需数小时甚至几天，一次又一次。

加上哑终端，以大型机给用户直接的，实际操作上，连接到公司的电脑。用户已不再等待一个电脑操作员管理自己的工作，他们可以将数据输入，并着手处理。

但还是有一些延误。哑终端被用于输入和显示信息，而是因为他们没有处理能力，因此有必要为用户进行互动与主机，以互动，他们的个人资料。一批职位以前可以运行一个接一个，如果有必要，但主机已处理一切与附码头看似售磬。这导致延误用户等待大型机到"掉头"，其终端的讯息，而他们互动，他们的个人资料。

尽管如此，拖延，现在下降到秒或分钟，而不是数小时或数天。客户机/服务器计算带来了一个全新的标准，企业计算的生产力，但在同一时间，并推出了许多新的问题，为企业的IT组织。

来临的低成本台式电脑，使客户机/服务器的可能。不再是必要的，为用户的等待，甚至秒的相互作用，他们的公司数据。用自己的电脑在自己的桌面上，他们并不需要等待大型机作出回应。所有这一切都便宜的电脑电源，也使人们有可能以支持计算密集型的图形界面，这是用户更容易理解。

为了让客户机/服务器的工作，应用程序，其中用于居住的完全是对主机已被成两块，一块客户端和服务器一块。

这部分的应用程序是居住在客户端的个人电脑，包括逻辑陈述的信息给用户和机制，以接受用户输入。它也包括逻辑数据交互在客户端，如更改外观的图形界面，为用户作出不同的选择。

客户端软件通常包括企业的业务规则，使数据得到验证之前，它是发送到服务器上。

这部分的应用仍然在服务器上，通常只是部分和存储数据，在一个位置，方便其他用户。一度浩浩荡荡主机已减少到数据库服务器，而其余的应用迁移到客户。

这种迁移，造成了很多问题。由于复杂的应用已上升，它已成为必要的，以供应用户更多和更强大的电脑，速度更快的处理器，更多的磁盘存储，并需要更多的内存。这是事实的个人电脑生产商已经能够为市民提供更佳，更好地为电脑相同数额的钱，但不断升级所需的费用高昂，为公司。它需要更多的人，时间，以提升数以百计或数以千计的个人电脑比以前要到刚刚升级大型机。

撇开成本的客户端设备，扩散的企业应用软件，包括业务逻辑，向数百或数千台计算机已成为一个主要的成本因素，为公司。,那里的工作人员用，才能保持各企业的软件资产，可以在一个中心位置，他们现在需要维持企业软件蔓延全美各地的公司，往往是住在电脑上出了它的控制。

有许多估计可用的成本客户机/服务器计算是8次或者更多次设备的费用。.有好几家公司提供庞大，昂贵的系统，有其唯一目的是保持公司软件分散全国各地的公司。

这里的问题不是个人生产力的软件，如文字处理和电子表格。个人软件产品，使知识工作者，以达到新的高度的生产力。

这是事实，认为利用厅级局域网，可以把拷贝的数量需要加以更新，以数百人，而不是数千人。规模的局域网必须加以，因为体积较大的脂肪客户端软件，需要一个负责任的局域网，否则用户将刚刚复制的企业软件，以自己的机器，把我们带回数千份继续保持。

任务是制定同步变化，甚至上百份的客户端软件仍然是一个艰巨的

行动的企业应用软件是不同的浏览器/服务器技术备忘录。用户界面和数据交互部件仍在运行于用户的机器，但业务逻辑通常依然在服务器上，通常是在一个特殊的服务器，称为应用服务器。

用户界面和数据交互部件做运行于客户端，但他们并非最终储存在那里。他们是最有可能的Java小程序存放在一个企业内部网络服务器，它们会自动下载到浏览器软件对用户机器，因为他们需要的。如果一个较新的版本面市，那么这个版本是自动加载。

我们已经实现了同样的利益与客户机/服务器，但没有庞大的分销和维修问题。唯一的软件用户需要的机器，除了作业系统及个人生产力软件，是一个网络浏览器上运行的Java应用程序。

由于大部分的"肥胖"的申请居住在业务逻辑的应用服务器，需要不断的升级，用户的机器是大大减少了。因此没有必要花费宝贵的时间和硬盘空间安装软件企业对数以千计的用户机器，或数百个部门的局域网。

企业软件资产，现在他们都居住在企业服务器，其下控制。.更新系统，现在很容易协调

那么到底什么是浏览器/服务器TM技术？浏览器/服务器TM是一个重要的适应现代网络中心计算优化性能的关键任务企业应用的部署，透过企业内联网和/或万维网。

浏览器/服务器技术备忘录完成这些业绩成果与定制出多层次，基础设施与应用，设计制造生产解决方案，降低网络要求，并增加了用户的互动。

（二）软件质量保证

软件质量保证活动与软件生存周期各阶段的验证和有效性确认活动紧密关联。事实上，在许多组织中这些活动没有明显的区别。尽管如此，质量保证实际上与其他验证和有效性确认活动相差甚远，质量保证是一个管理功能，而验证和有效性确认是软件开发过程的一部分。

Bersoff（1984）给出了软件质量保证的恰当定义：质量保证由在产品开发周期中专业人员要确保产品达到或超过某些预先设定的标准所要用到的那些过程、技术和工具所组成。如果没有具体的规定性的标准，质量保证则需要保证产品达到或超过工商业可接受的优良性能的最低标准。

当然这是一种相当笼统的定义。它首先指出软件标准可以建立；其次软件产品的优良程度可以评测。

软件工程项目标准的开发是一个非常困难的过程。一个标准是一个产品的某种抽象表示，它定义了被开发产品必须达到的最低性能、健壮性、结构等。在写此文章时，一些软件产品标准已经由IEEE，ANSI和一些军事机构制定了。

这些标准描述了配置管理计划、文档、规范实施、软件对照等。其他一些处于开发阶段的标准包括可靠性、测量方法、Ada用作为程序设计语言、软件测试和其他方面的标准。Bransta 和Powell（1984）描述了已有的和已规划的软件标准，用更概括的语言讨论了标准化问题。

软件的国家标准问题在于这些标准过于笼统，这是必然的，因为不像硬件，我们至今尚不能将大多数软件特性进行量化。因此有效的质量保证就要求开发更多特定的组织标准。

当然，为质量保证而开发软件标准所带来的问题及软件产品的优良程度难于评估是软件质量难以把握的本质。Boehm等人（1978）提出的质量准则包括但不局限于：经济性正确性弹性

完整性可靠性可使用性

文档可修改性明晰性

易理解性合法性可维护性

灵活性通用性可移植性

互操作性可测试性效率

模块性可重用性

如何精确量化其中的某些准则尚不清楚。而且，正如Buckley和Poston（1984）指出的那样，此定义的某些部分对特定产品也许毫无价值。把一个系统从一台微机移到一台大型机上是可能的，但这样做往往是毫无用处的。因此，软件质量的评估仍然依赖于熟练的个人判断。尽管这并不意味着此方法一定比定量评估差。尽管我们不能定量地评价一幅画或一场演出，但这毕竟不能阻止对其质量的判断。

在一个组织内，质量保证应由一个的软件质量保证小组来实施，该小组直接向项目经理层之上的管理层报告。质量保证小组不应与任何开发小组有联系，但要对本组织中所有的项目组的质量保证负责。

质量保证活动包括旁听设计复审、程序走查等，并报告开发过程中产品的整体质量。质量保证也包括检查已完成产品及其有关的文件说明是否与现有标准一致。质量保证小组也可以评估一件产品的不同表示方式（需求、设计、代码）是否一致和完备。

注意，质量保证不同于系统测试。系统有效性确认是开发或测试小组的责任，而质量保证小组要报告确认和确认工作是否充分。这自然意味着质量保证与系统最后阶段的综合测试有着密切的联系。

软件质量保证正成为软件工程的一个新兴分支。正如Buckley和Poston所指出的，有效的软件质量保证很可能导致软件费用的最终降低。然而，在这一领域中软件管理的最主要障碍是缺乏适用的软件标准。为人们所接受和普遍适用的标准的开发应成为软件工程研究的一个主要目标。

（三）软件测试

1．测试的目的

无论我们写程序的能力有多强，从可能出现的各种错误中仍可以看出，应该对程序进行检测以确保模块编码正确。许多程序员把测试视为其程序能够正常运行的展示。然而，展示正确性的想法实际上与测试的目的恰好相反，对程序进行测试是为了展示错误的存在。因为我们的目的是为了发现错误，仅当发现错误后才能认为测试是成功的。一旦发现错误，便要进行“排错”或纠错，确定是什么原因引起的错误并对系统进行修改，以使错误不再出现。2．测试阶段

在大系统开发过程中，测试包含几个阶段。首先，常常将每个程序模块与系统中的其他程序分开，作为单个程序测试，这样的测试称为模块测试或单元测试。它验证模块在设计时期望的输入类型情况下是否正确运行。只要有可能，都要在受控环境下进行模块测试，以便测试小组可以给在测模块输入一个预定的数据集，观察产生什么样的输出数据。另外，测试小组应检查内部数据结构、逻辑和输入、输出数据的边界条件。

当模块集经过单元测试后，下一步是保证模块之间的接口定义和处理得当。完整性测试验证系统的各组成部分是否按照程序设计和系统设计规格说明协同工作。

一旦确信信息按照设计规定在模块之间传递，就可测试整个系统，以确保系统具有希望的功能。功能测试是对系统进行评价，以确定整个系统能否真正实现需求规格说明所描述的各种功能。其结果就是功能正常的系统。

请回忆一下规定需求的两种方法：第一是以用户术语来表述；第二是作为软、硬件要求的集合。功能测试将正建造的系统与软、硬件需求功能进行比较；接着，性能测试是将系统与软硬件需求的其余部分进行比较。如果在用户实际工作环境中进行测试，测试成功就能产生一个有效的系统。但如果在模拟环境下进行测试，产生的结果系统就是一个已验证系统。

当性能测试完成后，作为开发者要确定系统按照我们对系统说明的理解进行工作。下一步就应与用户协商以确保系统按用户的期望进行工作。与用户一起进行验收测试，在此阶段系统按用户需求说明检查。验收测试完成后，此系统就安装在它将被使用的环境中。最后的安装测试用来确保系统仍具有其应有的功能。

图8-2说明了测试的几个阶段。尽管系统大小可能不同，但为确保开发中系统的正确性每一阶段中描述的测试类型都是必要的。