《课选的统筹与线性规划毕业设计(本科论文).doc》由会员分享，可在线阅读，更多相关《课选的统筹与线性规划毕业设计(本科论文).doc（70页珍藏版）》请在金锄头文库上搜索。
1、大连交通大学信息工程学院2012届本科生毕业设计（论文）外文翻译大连交通大学信息工程学院毕业设计(论文)任务书题 目 Useful课选的统筹与线性规划任务及要求：1.设计（研究）内容和要求任务：1、 调查基于Useful课选的统筹与线性规划系统，完成实习报告，字数不少于3000，第三周交给指导老师。2、 结合自己实习情况安排进度，填写进度计划表，第二周完成后交给指导老师签字，并严格执行。3、 按照软件工程思想，独立完成系统的设计和程序开发，完成代码估计2000行左右。4、 用JSP实现Useful课选的统筹与线性规划系统。5、 程序简洁，算法可行，运行情况良好。要求：1、 每周和指导老师至少见
2、面沟通一次，回报课题进展情况，接受老师询问。2、 接到任务书后，查阅与题目及专业相关的外文资料进行翻译，要求不少于10000个外文字符，译出汉字不得少于3000，于第四周交给指导老师审阅。3、 毕业设计第13周完成毕业论文的装订，并由指导老师评阅。论文要求12000字以上，包括综述、系统总体设计、系统实现、性能分析、结论等。4、 教学第13周通过中软及教研室组织进行软件验收，验收时要提供软件使用说明书。5、 于第13周提出毕业答辩申请并签字。6、 第14 周答辩，要求制作PPT2.原始依据通过大学几年的学习，已经学习了诸如软件工程、数据库原理及应用、数据结构、C+、Visual Basic、J
3、AVA等多门程序设计语言和网络等基础知识和专业知识，学生有能力而且可以独立完成小中型项目的设计与开发。学校现有设备和环境可以提供给学生实习和上机，而且具有专业老师可以指导学生。3.参考文献1 张跃平.JSP实用教程M.北京清华大学出版社.2003 2 SunMicrosystems.Database Programming With Java TechnologyM.20013 Java Servlet & JSP CookbookM.OReilly Press.20044 万峰科技编著.JSP 网站开发四酷全书M.电子工业出版社.20055 武卫华.计算机专业英语M.科学出版社.20046
4、王国辉.李文立.杨亮.JSP数据库系统开发完全手册M.北京人民邮电出版社.2006.37 吴斌.赵有珍等.SQL Server应用与提高M.科学出版社.2002.78 Bruce Eckel 著.Java编程思想.北京机械工业出版社.2004.019 Kevin duffey.Vikram goyal.Ted husted著.JSP站点设计编程指南M.电子工业出版社.2002.610 汪孝宜.刘中兵.徐佳晶等著.JSP数据库开发实例精粹M.电子工业出版社.2005.111 Elliote Rusty Harold,DavidFlanagan 著. Java Network Programmin
5、g. OReilly.1997.0612 Harvey M.Deitel.Paul J.Deitel 著.Java How to Program.北京机械工业出版社.2002.01指导教师签字：教研室主任签字： 2012年3月26日大连交通大学信息工程学院毕业设计(论文)进度计划与考核表学生姓名滕晓汝专业班级计算机科学与技术08-2班指导教师袁振海 宋丽芳本课题其他人员无题目Useful课选的统筹与线性规划日期计划完成内容完成情况指导老师检查签字第1周拟订毕业论文进度计划与考核表第2周完成实习或调研报告第3周提交外文文献翻译资料第4周系统概要设计阶段第5周系统详细设计阶段第6周系统编码实施、完
6、成论文初稿第7周完成系统编码实施第8周系统编码调试、提交论文初稿第9周完成系统编码调试、完善毕业论文第10周完成撰写毕业设计论文编写及代码测试第11周完成论文终稿、准备毕业论文打印、装订第12周提交毕业论文终稿及代码第13周完成毕业论文 第14周毕业论文答辩指导教师签字： 2012年3月30日大连交通大学信息工程学院毕业设计(论文)外文翻译学生姓名 滕晓汝 专业班级 计算机08-2班 指导教师 袁振海 宋丽芳 职 称 高工副教授 所在单位 信息科学系计算机教研室 教研室主任 宋丽芳 完成日期 2012 年 4 月 13 日Infrastructure for Automatic Dynamic
7、 DeploymentOf J2EE Application in Distributed EnvironmentsAnatoly Akkerman, Alexander Totok, and Vijay KaramchetiAbstract: in order to achieve such dynamic adaptation, we need an infrastructure for automating J2EE application deployment in such an environment. This need is quite evident to anyone wh
8、o has ever tried deploying a J2EE application even on a single application server, which is a task that involves a great deal of configuration of both the system services and application components.Key words: j2ee; component; Distributed; Dynamic Deployment; 1 IntroductionIn recent years, we have se
9、en a significant growth in component-based enterprise application development. These applications are typically deployed on company Intranets or on the Internet and are characterized by high transaction volume, large numbers of users and wide area access. Traditionally they are deployed in a central
10、 location, using server clustering with load balancing (horizontal partitioning) to sustain user load. However, horizontal partitioning has been shown very efficient only in reducing application-related overheads of user-perceived response times, without having much effect on network-induced latenci
11、es. Vertical partitioning (e.g., running web tier and business tier in separate VMs) has been used for fault isolation and load balancing but it is sometimes impractical due to significant run-time overheads (even if one would keep the tiers on a fast local-area network) related to heavy use of remo
12、te invocations. Recent work 14 in the context of J2EE component based applications has shown viability of vertical partitioning in wide-area networks without incurring the aforementioned overheads. The key conclusions from that study can be summarized as follows: Using properly designed applications
13、, vertical distribution across wide-area networks improves user-perceived latencies. Wide-area vertical layering requires replication of application components and maintaining consistency between replicas. Additional replicas may be deployed dynamically to handle new requests. Different replicas may
14、, in fact, be different implementations of the same component based on usage (read-only, read-write). New request paths may reuse components from previously deployed paths.Applying intelligent monitoring 6 and AI planning 2, 12 techniques in conjunction with the conclusions of that study, we see a potential for dynamic adaptation in industry-standard J2EE component-based applications in wide area networksThrough deployment of additional application components dynamically based on active monitoring. However, in order
