企业工资福利社会保障系统论文(论文)大学-大学毕业设计.doc

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

题 目 企业工资福利社会保障系统

任务及要求：　
1.设计（研究）内容和要求　
任务：
1、 调查企业工资、福利、社会保障系统方面当前技术的发展近况，完成实习报告，字数不少于3000，第三周交给指导老师。
2、 结合自己实习情况安排进度，填写进度计划表，第二周完成后交给指导老师签字，并严格执行。
3、 按照软件工程思想，独立完成系统的设计和程序开发，完成代码估计2500行左右。
4、 用JAVA技术实现企业工资、福利、社会保障系统功能。
5、 程序简洁算法可行，运行情况良好。

要求：
1、 每周和指导老师至少见面沟通一次，回报课题进展情况，接受老师询问。
2、 接到任务书后，查阅与题目及专业相关的外文资料进行翻译，要求不少于10000个外文字符，译出汉字不得少于3000，于第四周交给指导老师审阅。
3、 毕业设计第13周完成毕业论文的装订，并由指导老师评阅。论文要求12000字以上，包括综述、系统总体设计、系统实现、性能分析、结论等。
4、 教学第13周通过中软及教研室组织进行软件验收，验收时要提供软件使用说明书。
5、 于第13周提出毕业答辩申请并签字。
6、 第14 周答辩，要求制作PPT
2.原始依据
通过大学几年的学习，已经学习了诸如软件工程、数据库原理及应用、数据结构、C++、Visual Basic、JAVA等多门程序设计语言和网络等基础知识和专业知识，学生有能力而且可以独立完成小中型项目的设计与开发。学校现有设备和环境可以提供给学生实习和上机，而且具有专业老师可以指导学生。

3.参考文献
[1] 张桂珠.刘丽.陈爱国.Java面向对象程序设计[M].北京邮电大学出版社.2007
[2] Brian Goetz.Tim Peierls.Joshua Bloch.Joseph Bowbeer.David Holmes.Doug Lea. Java programming and training.北京邮电大学出版社.2012
[3] BrueeEekel.Java编程思想(第3版).机械工业出版社.2005
[4] 印旻.王行言.Java语言与面向对象程序设计(第2版).清华大学出版社.2007
[5] 成富.深入理解Java7：核心技术与最佳实践.机械工业出版社.2012
[6] 王立新.石艳捷.霍泉宇.维权百事通6：工资、工龄与社保、福利待遇.中国法制出版社.2006
[7] 仇雨临.员工福利概论/21世纪劳动与社会保障系列教材.中国人民大学出版社.2007
[8] 福塔.MYSQL必知必会.人民邮电出版社.2009

[9] 贝尔.欣达尔.达勒马纳.高可用性MySQL.东南大学出版社.2011
[10] 龚永罡.Java程序设计基础教程.清华大学出版社.2009
[11] 昊斯特曼.Java核心技术：卷Ⅰ基础知识.机械工业出版社.2008

指导教师签字：
教研室主任签字：
　　　　　　　　　　　　　　　　　　　　　　 年 月 日
大连交通大学信息工程学院
毕业设计(论文)进度计划与考核表
学生姓名
罗旭
专业班级
计算机科学与技术08-2班
指导教师
王影
魏琦
本课题其他人员

题　目
企业工资福利社会保障系统
日　期
计划完成内容
完成情况
指导老师检查签字
第1周
实习调研，查阅课题相关外文资料

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

第3周
完成10000字符或3000汉字以上的外文翻译，准备资料，学习java相关技术

第4周
进行需求分析和概要设计

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

第6周
详细设计各部分功能

第7周
编码

第8周
编码

第9周
系统联调

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

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

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

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

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

指导教师签字：　　　　　　　　　　　 　　年　　月　　日

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

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

学生姓名 罗旭 专业班级 计算机08-2班
指导教师 王影　魏琦 职 称 高工　讲师
所在单位 信息科学系计算机教研室
教研室主任 宋丽芳

完成日期 2012 年 4 月 13 日
MySQL

MySQL's original developer intent is to use the mSQL and their rapid low-level routines ( ISAM ) to connect to form. After some tests, the developers concluded: mSQL and there is no need for them so fast and flexible. This led to a use almost like mSQL API interface for their database of the new SQL interface, so, the API is designed to allow for use on the mSQL to write the third party code easier to transfer to MySQL.
The name MySQL is how come is not clear. Basic guide and a large number of libraries and tools with the prefix "my" has had more than 10 years, and no matter what, co-founder of MySQL AB Monty Widenius The daughter also named My. The two which one it was given the name MySQL remains a mystery, including developers, also do not know.
MySQL Dolphins Logo name is" sakila", which is composed of a MySQL AB founder from the users in the" dolphin named" contest suggested a name table as select. The winning name is made from Africa and Swaziland's open source software developer Ambrose Twebaze. According to Ambrose, Sakila from a SiSwati Swaziland dialect, but also in the Ambrose 's home town of Uganda, near Tanzania's Arusha is one of the town's name.
And other large databases such as Oracle, DB2, SQL Server compared to MySQL, has its own disadvantages, such as small size, limited functionality ( MySQL Cluster function and efficiency are relatively poor ), but it did not reduce its popularity. For the average individual users and small and medium enterprises, the functionality provided by MySQL is more than sufficient, and because MySQL is open source software, thus can greatly reduce the total cost of ownership.
LAMP:
The current Internet popular website architecture is LAMP ( Linux + Apache + MySQL + PHP / Perl / Python ) and LNMP ( Linux + Nginx + MySQL + php / Perl / Python ), which uses the Linux as the operating system, Apache and Nginx as the Web server, MySQL as the database, PHP / Perl / Python as a server-side script interpreter. As a result of the four software are free or open source software ( FLOSS ), so use this way without spending a dime ( except artificial cost ) to establish a stable, free website system.
MyISAMMysql default database, the most commonly used. Have a high insertion, search speed, but does not support transactions InnoDB transactional database preferred engine, support for ACID affairs, support row-level locking BDB from Berkeley DB, transactional database for another option, support for COMMIT and ROLLBACK and other transaction characteristics of Memory all of the data in memory storage engine, with a high insertion, update and query efficiency. But it will take and data is proportional to the amount of memory space. And its content in the Mysql restart lost when Merge will be a certain amount of MyISAM combined into a whole, in the large scale data storage is useful when Archive is very suitable for storing a large number of independent, as history data. Because they don't often been read. Archive has efficient insertion speed, but its effect on query support relatively poor Federated different Mysql server logic together, form a complete database. Very suitable for distributed application of Cluster / NDB high redundancy storage engine, using multiple data machine combined to provide services to improve overall performance and safety. Suitable for large amount of data, safety and performance requirements of high CSV application logic comma separated data storage engine Cluster / NDB.
BlackHole black engine, written in any data will disappear, generally used for recording binlog replication of the relay EXAMPLE storage engine is a don't do anything stub engine. It is designed as MySQL one example in the source code, used to demonstrate how to start writing a new storage engine. Similarly, it is of major interest to developers. EXAMPLE storage engine does not support indexing. In addition, Mysql storage engine interface definition of good. Interested developers can by reading the document prepared its own storage engine.
The index is a special file ( InnoDB data index is a table space is an integral part of ), they contain the data inside and outside all recorded reference pointer. The index is not a panacea, the index can speed up data retrieval operation, but can make the data modification operation slow. Each modified data recording, index must refresh time. In order to in certain procedures to remedy this one flaw, many SQL command has a DELAY_KEY_WRITE. This option is the role of temporary suppression of MySQL in the order of each insert a new record and each modified an existing immediately after the index on the index to refresh, refresh will wait until all record insert / modified after. The need to bring many new record is inserted into a data table of the occasion, the DELAY_KEY_WRITE option effects will be very obvious. In addition, the index will be in hard disk takes up considerable space. Therefore should only for the most frequent queries and most often sorted data column is indexed. Note that, if a data column contains many duplicate content, as it establishes index is not much actual effect.
From theoretic tell, can provide data and each of the fields were built an index, but MySQL the same data and index number is limited to 16.
1.InnoDB data table index
With InnoDB data table, in the InnoDB table, index on the InnoDB table importance is much greater. In InnoDB data table, the index will not only play a role in the search data records, or data row level locking mechanism, acenaphthene based. " The data row level locking" mean in transaction operation during the execution of the locking is being dealt with an individual record, do not allow other users to access. The lock will be affected ( but not limited to ) SELECT, LOCKINSHAREMODE, SELECT, INSERT, UPDATE and FORUPDATE commands and DELETE command. For efficiency reasons, InnoDB data row level locking actually occur in their index, rather than the data itself. Obviously, the data row level locking mechanism only in relation to the data table having a suitable index for locking time to work.
2 limit
If the WHERE clause in the query terms are not equal ( WHERE coloum!= )MySQL , will not be able to use the index. Similarly, if the WHERE clause in the query terms used in function ( WHEREDAY ( column ) = MySQL ), will be unable to use the index. In the JOIN operation ( from multiple data extraction data ), MySQL only in the primary and foreign keys to the same data type to use index.
If the WHERE clause in the query conditions using comparison operators LIKE and REGEXP, MySQL only in search of template first character is not a wildcard conditions can use the index. For example, if the query is ' LIKE 'abc%, MySQL will use the index; if the query is ' LIKE %abc, ' MySQL will not use index.
In the operation of ORDERBY, MySQL only in the sorting condition is not a query condition expression condition that use index. ( even so, in a plurality of data query, even if the index is available, the index in accelerating ORDERBY has no effect). If a data column contains many duplicate values, even if it establishes index will not have a good effect. For example, if a data column contains the net is something such as" 0 / 1" or" Y / N" equivalent, there is no need for it to create an index.
Only when the database has enough test data, its performance test results have practical reference value. If the test database only hundreds of data recording, they are often in executing the first query command after being loaded into memory, it will make the subsequent inquiry command to perform very fast -- with or without using an index. Only when the records in a database of more than 1000, the amount of data is more than the amount of memory on the MySQL server, database performance testing results are meaningful. On the uncertainty in which data should create index on a column of the time, people from the EXPLAINSELECT command there can often get some help. This is simply to give a common SELECT command plus a EXPLAIN keyword as a prefix. With this key, MySQL will not to follow the SELECT command, but to analyze it. MySQL will be in the form of the query execution process and uses the index information list. In the output of the EXPLAIN command results, the first column is the data read from the database table name, they are to be read in the order. The type column specifies the data table and other table relationships ( JOIN ). In various types of relationships, efficiency is highest in system, followed by const, eq_ref, ref, range, index and All ( All means: a data table corresponding to each record, this table all records must be read again -- this can often be used to an index to avoid ). Possible_keys data column gives the MySQL in search of the data record can be chosen each index. Key data column is MySQL practical selection index, this index in bytes of the key_len length in the columns of the data given in the. For example, for a INTEGER data column index, the byte length will be 4. If used in the composite index, the key_len data column can also see MySQL specific use of it which part. As a general rule, key_len data column value in the smaller is better. Ref data column gives the relationship of another data data select column name. Row data column is MySQL in executing this query is expected from this data and the read data line number. Row data column in all digital product can generally understand the need to deal with the number of combination query. Finally, the extra data column is provided with JOIN operation for more information about, for example, if the MySQL in executing this query must create a temporary table, will be listed in the extra see usingtemporary.
In the CHAR and VARCHAR data type column definition index, the index can be the length limit for a given number of characters ( this number must be less than the field the maximum allowed number of characters ). The benefit of this is can be generated in a relatively small size, the retrieval speed is fast compared to the index file. In most applications, the database string data mostly a variety of names, the index length is set to 10 ~ 15 characters were enough to narrow your search to a few data records. In the BLOB and TEXT data types to create index, to index length limits allowed by the MySQL; the maximum index full text index text field on the general index can only accelerate to appear in the field contents first string (i.e. field content retrieval operation initial characters ). If a field store is composed of several, or even more words constituting the larger text, general index of little use. This retrieval tends to form, the MySQL is very complex, if need to handle large volumes of data, response time will be very long.
Most of today's application in the heart is the underlying database. In this case, brook no delay in the design and implementation of the key business application data structure is very important.
All had good modeling tools, such as MySQL workbench support forward engineering, means that all use SQL code to create the database, and also can automatically write related objects and correct operation. This eliminates the developer or DBA error-prone and time-consuming process.
Data design and its response database version control and management of life cycle, such as the application, therefore, the most important is the data architect, database administrators, developers.
To understand their database and metadata design implementation of the appropriate change management needs. Link to certain information model driven method is optimal, but access to data modeling and metadata object manual method can be run.
In the change management, may face data management professionals are facing the most serious challenge is one of the existing physical database design in the successful implementation of these complex changes.
Fortunately, most good modeling tools, such as MySQL workbench can alleviate this problem, because they contain the synchronization efficiency, to allow the database administrator or developer to change physical data modeling, and then use the existing physical database to synchronize these changes. The tool is all about execution effect analysis or generation of the appropriate database code all the work, in the target database prior to implementation, easy to preview all changes.
In most of the tools, reverse engineering is also can be made very good - can modify a data modeling, to reflect on the existing physical database changes. This aspect is very important, because it is often required to perform an emergenc