因特网流量管理系统毕业设计(本科论文).doc

大连交通大学信息工程学院2012届本科生毕业设计（论文）实习（调研）报告

大连交通大学信息工程学院
毕业设计(论文)任务书

题 目 世纪家园因特网流量管理系统

任务及要求：
1.设计（研究）内容和要求　
任务：
1、 调查基于世纪家园因特网流量管理系统统，完成实习报告，字数不少于3000，第三周交给指导老师。
2、 结合自己实习情况安排进度，填写进度计划表，第二周完成后交给指导老师签字，并严格执行。
3、 按照软件工程思想，独立完成系统的设计和程序开发，完成代码估计2000行左右。
4、 用JSP实现世纪家园因特网流量管理系统。
5、 程序简洁，算法可行，运行情况良好。

要求：
1、 每周和指导老师至少见面沟通一次，回报课题进展情况，接受老师询问。
2、 接到任务书后，查阅与题目及专业相关的外文资料进行翻译，要求不少于10000个外文字符，译出汉字不得少于3000，于第四周交给指导老师审阅。
3、 毕业设计第13周完成毕业论文的装订，并由指导老师评阅。论文要求12000字以上，包括综述、系统总体设计、系统实现、性能分析、结论等。
4、 教学第13周通过中软及教研室组织进行软件验收，验收时要提供软件使用说明书。
5、 于第13周提出毕业答辩申请并签字。
6、第14 周答辩要求制作PPT

2.原始依据
通过大学几年的学习，已经学习了诸如软件工程、数据库原理及应用、数据结构、C++、Visual Basic、JAVA等多门程序设计语言和网络等基础知识和专业知识，学生有能力而且可以独立完成小中型项目的设计与开发。学校现有设备和环境可以提供给学生实习和上机，而且具有专业老师可以指导学生。

3.参考文献

[1] 刘鲁.信息系统设计原理与应用[M]航天航空大学出版社出版.2006
[2] 朱世欣.智能化住宅小区的设计[J].机械工业出版社.2007.04．
[3] 李劲.SQL Server 2000 数据库设计与系统管理.清华大学出版社.2008
[4] 张静.智能化住宅小区小区因特网流量管理系统软件设计概述[D].中国电子工业出版社.2009.04
[5] 魏茂林.SQL Server 数据库设计与应用案例训练教程.电子工业出版社.20009
[6] 黄璐.高永梅.基于JSP的网络管理系统的设计与实现[J].清华大学出版社.2007
[7] T.Kalinke.C.Tzomakas．A Textture-based object detection and an aduptive model-based classification[J].InProc IEEE Int.lonfonIntelligent Vehicles.1998
[8] 耿祥义.张跃平.Java 2实用教程（第三版）.清华大学出版社.2006.8
[9] 韩利娟.基于MVC模式的Structs框架的研究与实现.电子工业出版社.2008
[10] 黄映霞.Java项目开发案例.北京：清华大学出版社.2010.2
[11] 汪孝宜.Java实战宝典.北京人民大学出版社.2008.7

　指导教师签字：
教研室主任签字：
　　　　　　　　　　　　　　　　　　　　　　 2012年3月26日

大连交通大学信息工程学院
毕业设计(论文)进度计划与考核表
学生姓名
徐桢
专业班级
软件工程
08-2班
指导教师
袁振海
王立娟
本课题其他人员
无
题　目
世纪家园因特网流量管理系统
日　期
计划完成内容
完成情况
指导老师检查签字
第1周
实习调研，查阅课题相关外文资料

第2周
了解行业状况、查阅文献资料，阅读资料，撰写调研报告

第3周
完成10000字符或3000汉字以上的外文翻译资料，准备资料。

第4周
进行需求分析

第5周
进行概要设计

第6周
进行概要设计, 基本框架完成，提交毕业论文提纲

第7周
完成后台数据库的设计并编码，完成部分论文

第8周
完成前台界面的设计并编码，完成部分论文

第9周
继续编码并进行测试，继续编写毕业设计论文

第10周
继续进行程序测试，继续编写毕业设计论文

第11周
整理资料、文档、图表等，修改毕业设计论文

第12周
完成毕业设计论文，打印，按要求装订

第13周
软件验收和准备毕业设计答辩

第14周
毕业设计答辩及成绩评定

指导教师签字：　　　　　　　　　　　 　　年　　月　　日

注：“计划完成内容”由学生本人认真填写，其它由指导教师考核时填写。

大连交通大学信息工程学院
毕业设计(论文)外文翻译

学生姓名 徐桢　 专业班级 软件工程08-2班
指导教师 袁振海 王立娟 职 称 高工　讲师
所在单位 信息科学系软件工程教研室
教研室主任 　 刘瑞杰

完成日期 2012 年 4 月 13 日
SQL SERVER Database Architecture

An SQL SERVER database is a collection of data treated as a unit. The purpose of a database is to store and retrieve related information. A database server is the key to solving the problems of information management. In general, a server reliably manages a large amount of data in a multi-user environment so that many users can concurrently access the same data. All this is accomplished while delivering high performance. A database server also prevents unauthorized access and provides efficient solutions for failure recovery. SQL SERVER Database is the first database designed for enterprise grid computing, the most flexible and cost effective way to manage information and applications. Enterprise grid computing creates large pools of industry-standard, modular storage and servers. With this architecture, each new system can be rapidly provisioned from the pool of components. There is no need for peak workloads, because capacity can be easily added or reallocated from the resource pools as needed. The database has logical structures and physical structures. Because the physical and logical structures are separate, the physical storage of data can be managed without affecting the access to logical storage structures.
Overview of SQL SERVER Grid Architecture
Grid computing is a new IT architecture that produces more resilient and lower cost enterprise information systems. With grid computing, groups of independent, modular hardware and software components can be connected and rejoined on demand to meet the changing needs of businesses.
Grid computing is a new IT architecture that produces more resilient and lower cost enterprise information systems. With grid computing, groups of independent, modular hardware and software components can be connected and rejoined on demand to meet the changing needs of businesses.
The grid style of computing aims to solve some common problems with enterprise IT: the problem of application silos that lead to under utilized, dedicated hardware resources, the problem of monolithic, unwieldy systems that are expensive to maintain and difficult to change, and the problem of fragmented and disintegrated information that cannot be fully exploited by the enterprise as a whole.
Benefits of Grid Computing Compared to other models of computing, IT systems designed and implemented in the grid style deliver higher quality of service, lower cost, and greater flexibility. Higher quality of service results from having no single point of failure, a robust security infrastructure, and centralized, policy-driven management. Lower costs derive from increasing the utilization of resources and dramatically reducing management and maintenance costs. Rather than dedicating a stack of software and hardware to a specific task, all resources are pooled and allocated on demand, thus eliminating under utilized capacity and redundant capabilities. Grid computing also enables the use of smaller individual hardware components, thus reducing the cost of each individual component and providing more flexibility to devote resources in accordance with changing needs.
Overview of Application Architecture
There are two common ways to architect a database: client/server or multitier. As internet computing becomes more prevalent in computing environments, many database management systems are moving to a multitier environment.
Client/Server Architecture.Multiprocessing uses more than one processor for a set of related jobs. Distributed processing reduces the load on a single processor by allowing different processors to concentrate on a subset of related tasks, thus improving the performance and capabilities of the system as a whole.
An SQL SERVER database system can easily take advantage of distributed processing by using its client/server architecture. In this architecture, the database system is divided into two parts: a front-end or a client, and a back-end or a server.
The Client.The client is a database application that initiates a request for an operation to be performed on the database server. It requests, processes, and presents data managed by the server. The client workstation can be optimized for its job. For example, it might not need large disk capacity or it might benefit from graphic capabilities. Often, the client runs on a different computer than the database server, generally on a PC. Many clients can simultaneously run against one server.
The Server.The server runs SQL SERVER software and handles the functions required for concurrent, shared data access. The server receives and processes the SQL and PL/SQL statements that originate from client applications. The computer that manages the server can be optimized for its duties. For example, it can have large disk capacity and fast processors
Overview of Physical Database Structures
The following sections explain the physical database structures of an SQL SERVER database, including datafiles, redo log files, and control files
Datafiles.Every SQL SERVER database has one or more physical datafiles. The datafiles contain all the database data. The data of logical database structures, such as tables and indexes, is physically stored in the datafiles allocated for a database. The characteristics of datafiles are:
1.A datafile can be associated with only one database.
2.Datafiles can have certain characteristics set to let them automatically extend when the database runs out of space.
3.One or more datafiles form a logical unit of database storage called a tablespace.
Data in a datafile is read, as needed, during normal database operation and stored in the memory cache of SQL SERVER. For example, assume that a user wants to access some data in a table of a database. If the requested information is not already in the memory cache for the database, then it is read from the appropriate datafiles and stored in memory.
Control Files.Every SQL SERVER database has a control file. A control file contains entries that specify the physical structure of the database. For example, it contains the following information:
1. Database name
2. Names and locations of datafiles and redo log files
SQL SERVER can multiplex the control file, that is, simultaneously maintain a number of identical control file copies, to protect against a failure involving the control file
Every time an instance of an SQL SERVER database is started, its control file identifies the database and redoes log files that must be opened for database operation to proceed. If the physical makeup of the database is altered then the control file is automatically modified by SQL SERVER to reflect the change. A control file is also used in database recovery.
Redo Log Files.Every SQL SERVER database has a set of two or more redo log files. The set of redo log files is collectively known as the redo log for the database. A redo log is made up of redo entries . The primary function of the redo log is to record all changes made to data. If a failure prevents modified data from being permanently written to the datafiles, then the changes can be obtained from the redo log, so work is never lost. To protect against a failure involving the redo log itself, SQL SERVER allows a multiplexed redo log so that two or more copies of the redo log can be maintained on different disks. The information in a redo log file is used only to recover the database from a system or media failure that prevents database data from being written to the datafiles. For example, if an unexpected power outage terminates database operation, then data in memory cannot be written to the datafiles, and the data is lost. However, lost data can be recovered when the database is opened, after power is restored. By applying the information in the most recent redo log files to the database datafiles, SQL SERVER restores the database to the time at which the power failure occurred.
Archive Log Files. You can enable automatic archiving of the redo log. SQL SERVER automatically archives log files when the database is in ARCHIVELOG mode.
Parameter Files. Parameter files contain a list of configuration parameters for that instance and database. SQL SERVER recommends that you create a server parameter file as a dynamic means of maintaining initialization parameters. A server parameter file lets you store and manage your initialization parameters persistently in a server-side disk file.
Alert and Trace Log Files. Each server and background process can write to an associated trace file. When an internal error is detected by a process, it dumps information about the error to its trace file. Some of the information written to a trace file is intended for the database administrator, while other information is for SQL SERVER Support Services. Trace file information is also used to tune applications and instances. The alert file, or alert log, is a special trace file. The alert log of a database is a chronological log of messages and errors.
Backup Files. To restore a file is to replace it with a backup file. Typically, you restore a file when a media failure or user error has damaged or deleted the original file. User-managed backup and recovery requires you to actually restore backup files before you can perform a trial recovery of the backups. Server-managed backup and recovery manages the backup process, such as scheduling of backups, as well as the recovery process, such as applying the correct backup file when recovery is needed.
Overview of Logical Database Structures
The logical storage structures, including data blocks, extents, and segments, enable SQL SERVER to have fine-grained control of disk space use.
Tablespaces.A database is divided into logical storage units called tablespaces, which group related logical structures together. For example, tablespaces commonly group together all application objects to simplify some administrative operations. Each database is logically divided into one or more tablespaces. One or more datafiles are explicitly created for each tablespace to physically store the data of all logical structures in a tablespace. The combined size of the datafiles in a tablespace is the total storage capacity of the tablespace. Every SQL SERVER database contains a SYSTEM tablespace and a SYSAUX tablespace. SQL SERVER creates them automatically when the database is created. The system default is to create a smallfile tablespace, which is the traditional type of SQL SERVER tablespace. The SYSTEM and SYSAUX tablespaces are created as smallfile tablespaces. SQL SERVER also lets you create bigfile tablespaces. This allows SQL SERVER Database to contain tablespaces made up of single large files rather than numerous smaller ones. This lets SQL SERVER Database utilize the ability of 64-bit systems to create and manage ultralarge files. The consequence of this is that SQL SERVER Database can now scale up to 8 exabytes in size. With SQL SERVER-managed files, bigfile tablespaces make datafiles completely transparent for users. In other words, you can perform operations on tablespaces, rather than the underlying datafiles.
SQL SERVER Data Blocks.At the finest level of granularity, SQL SERVER database data is stored in data blocks. One data block corresponds to a specific number of bytes of physical database space on disk. The standard block size is specified by the DB_BLOCK_SIZE initialization parameter. In addition, you can specify up to five other block sizes. A database uses and allocates free database space in SQL SERVER data blocks.
SQL SERVER Data Blocks.At the finest level of granularity, SQL SERVER database data is stored in data blocks. One data block corresponds to a specific number of bytes of physical database space on disk. The standard block size is specified by the DB_BLOCK_SIZE initialization parameter. In addition, you can specify up to five other block sizes. A database uses and allocates free database space in SQL SERVER data blocks.
Extents. The next level of logical database space is an extent. An extent is a specific number of contiguous data blocks, obtained in a single allocation, and used to store a specific type of information.
Segments. Above extents, the level of logical database storage is a segment. A segment is a set of extents allocated for a certain logical structure. The following table describes the different types of segments.

- 12 -

SQL SERVER数据库体系结构

SQL SERVER数据库是一个将收集处理作为一个单位数据的数据库，是建立存储和检索相关数据的数据库。数据库服务器是解决信息管理问题的核心组件。大体上说，数据库服务器的作用是可靠地管理多用户环境下的大规模数据，使多用户可以并发地访问相同的数据，同时实现系统的高性能。数据库服务器还要阻止未授权的操作，并提供高效的故障恢复解决方案。SQL SERVER数据库是第一个为企业网格计算而设计的数据库，它为管理信息和应用提供了灵活