教学管理系统毕业设计论文任务书

大连交通大学信息工程学院毕业设计(论文)任务书题 目 蒙奇奇教学管理系统任务及要求：1.设计（研究）内容和要求任务：1、 调查蒙奇奇教学管理系统的近况，完成实习报告，字数不少于3000，第三周交给指导老师。2、 结合自己实习情况安排进度，填写进度计划表，第二周完成后交给指导老师签字，并严格执行。3、 按照软件工程思想，独立完成系统的设计和程序开发，完成代码估计2000行左右。4、 用JSP技术实现基于教学中排课、选课等基本功能。5、 程序简洁，算法可行，运行情况良好。要求：1、 每周和指导老师至少见面沟通一次，回报课题进展情况，接受老师询问。2、 接到任务书后，查阅与题目及专业相关的外文资料进行翻译，要求不少于10000个外文字符，译出汉字不得少于3000，于第四周交给指导老师审阅。3、 毕业设计第13周完成毕业论文的装订，并由指导老师评阅。论文要求12000字以上，包括综述、系统总体设计、系统实现、性能分析、结论等。4、 教学第13周通过中软及教研室组织进行软件验收，验收时要提供软件使用说明书。5、 于第13周提出毕业答辩申请并签字。6、 第14 周答辩，要求制作PPT2.原始依据通过大学几年的学习，已经学习了诸如软件工程、数据库原理及应用、数据结构、C+、Visual Basic、JAVA等多门程序设计语言和网络等基础知识和专业知识，学生有能力而且可以独立完成小中型项目的设计与开发。学校现有设备和环境可以提供给学生实习和上机，而且具有专业老师可以指导学生。3.参考文献1 李发致.项目管理教程.电子工业出版社.2005.22 张怀庆.java案例精粹150例.北京冶金工业出版社.2005.23 张孝祥.JSP项目管理培训教程.清华大学出版社.2008.64 王建 张金波.java程序设计实训教程.北京海洋出版社.2006.015 Bernd Bruegge.面向对象软件工程.清华大学出版社.2003.76 Campbell R.Mconnell Stanley L.BrueMicro-EconomicsJset in century oldstyle by York Graphic Services20007 仝春灵,沈祥玖.数据库原理与应用MySQL.中国水利水电出版社.20038 耿祥义，张跃平.JAVA2实用教程M.清华大学出版社.20069 楼兴华.MySQL数据库系统开发实例导航M.人民邮电出版社.200410 钱雪忠.数据库原理及应用M.北京邮电大学出版社.2008指导教师签字：教研室主任签字： 2012年3月26日大连交通大学信息工程学院毕业设计(论文)进度计划与考核表学生姓名冯程程专业班级软件工程08-1班指导教师杨 迪李孝贵本课题其他人员无题目蒙奇奇教学管理系统日期计划完成内容完成情况指导老师检查签字第1周拟订毕业论文进度计划与考核表第2周完成实习或调研报告第3周提交外文文献翻译资料第4周系统概要设计阶段第5周系统详细设计阶段第6周系统编码实施、完成论文初稿第7周完成系统编码实施第8周系统编码调试、提交论文初稿第9周完成系统编码调试、完善毕业论文第10周完成撰写毕业设计论文编写及代码测试第11周完成论文终稿、准备毕业论文打印、装订第12周提交毕业论文终稿及代码第13周完成毕业论文第14周毕业论文答辩指导教师签字： 年月日注：“计划完成内容”由学生本人认真填写，其它由指导教师考核时填写。大连交通大学信息工程学院毕业设计(论文)外文翻译学生姓名 冯程程 专业班级 软件工程08-1班 指导教师 杨迪李孝贵 职 称 高工助教 所在单位 信息科学系软件工程教研室 教研室主任 刘瑞杰 完成日期 2012 年 4 月 13 日The Web application and the developmentIn this paper we present and discuss a template/meta-data based partial code generation system supporting web application development. Seamlessly incorporating the recent top-notch technologies, the framework maximally exploits the capabilities of the underlying implementation technologies. Our approach primarily benefits the framework and code developers. In addition, the complete separation of data model, navigation model, and presentation model reflects on a more general conceptual process that would decouple the technique and methodology from its underlying technology choices. The decoupling between the generated code and the code that is necessarily added later on through other development pathways than the generator deals with the incremental changes and adaptations of the models in the face of an operational system, therefore further enhances the extensibility, maintainability, and reusability of the generated applications.Categories and Subject DescriptorsInvolving with multiple disciplines relating to the computing and networking technologies, the development of web applications can be quite complex, costly and time-consuming, if not supported by a practical methodology 9. In order to increase the productivity of web application development, a wealth of languages and standards and techniques have been created. On the basis of our consulting experience in industry, we believe that the following technologies dominate in the present web application realm. The Java 2 platform, Enterprise Edition (J2EE) defines de facto standard software architecture for multi-tier interactive web applications 16. Meanwhile, application servers, which most commercial products available today are based on the J2EE platform, provide system-level environmental support for web application development that prevent developers from tedious coding of system level utilities 13. According to the J2EE paradigm, the architecture of a typical web application reflects the traditional three-tier architectural model 15: front-end, middle tier, and back-end. The Hyper-Text Markup Language (HTML),JSP, and JavaScript provide powerful means to describe dynamic web interfaces for applications; and Java Servlet provides underlying support to construct web page information on the fly. The concepts of session bean and entity bean in EJB techniqueclearly decouple the code serving for business logic processing from the code of data, thus provide a commanding infrastructure to construct the middle-tier of applications. Furthermore, the EJB engine provides a higher-level abstraction over the underlyingdata model storage devices the traditional relational database, which is considered to be the back-end of a web application. In addition, some other techniques further assist to firm the J2EEbased development methodology, such as Struts 23, Ant 1, and XML 21. Struts provides an open source unified front-end Model-View-Controller (MVC) framework 10 for web applications. Ant is a Java based prompt build tool that allows developers to utilize XML technique to configure the relationships between different building blocks and generate the compiled version. As a universal description language, XML provides a de facto standard language to define and describe web applications.J2EE-based techniques have enabled the explosion in the number of web applications that we have witnessed to date. More importantly, these techniques formalize the architecture of a typical web application; therefore make it feasible to expedite the development of web applications by exploiting automatic program generation techniques. In this paper we present and discuss a template/meta-data based partial code generation system supporting web application development. Seamlessly incorporating the XML and J2EE family of technologies, the framework maximally exploits the capabilities of the underlying implementation technologies. The rest of this paper is organized as follows. In Section 2, we discuss related work in web development techniques. In Section 3, we discuss our template/meta data based web code generator. In Section 4, we discuss an example. Conclusions and future workdirections are discussed in Section 5.Permission to make digital or hard copies of all or part of this work forpersonal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and thatcopies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.2. RELATED WORKA variety of research work has been conducted to expedite and automate the development of web applications. Among the various efforts, a lot of work focuses on assisting conceptual modeling of web applications. HDM 12 defines a popular model dedicated for hypermedia application design, which divides the conceptual schema into two categories: structural and navigational. Its variant recent descendent formats include HDM2000 2, OOHDM 22, WebML 5, and HDM-lite 9. Web Modeling Language (WebML) 5 is a notation of designing a complicated web site at the conceptual level, which defines a web site along five dimensions: data content, page composition, navigation links, page presentation, and customization features. HDM2000 and WebML intend to integrate a number of considerations typical of large-scale Web applications, such as requirements elicitation, customization aspects, operational aspects, and transactional aspects. HDM-lite 9 adds a presentation schema to the conceptual design of web applications. Its development environment Autoweb stores the conceptual schemas together with the data content in the development database. Jweb 3 provides a design and prototyping environment that integrates XML technology with HDM in order to help design the conceptual schema. There are also other conceptual design techniques. Conallen extends the Unified Modeling Language (UML) 4 notation to model web specific elements, thus making it feasible to model whole web applications with the UML. Gaedke uses WebComposition and the WebComposition Markup Language (WCML) to present a systematic approach for code reuse in component-based webapplications 11. IIPS models navigational structure, compositional structure, and user interface through ontology 20. The formalized interfaces of J2EE techniques make it extremely suitable for code generation. There are several code generation products and tools aiming at accelerating the development process of web applications. Torrisoft is an on-going environment aiming at helping web site development utilizing Web Modeling Language. IIPS provides a set of visual tools supporting web site generation from the conceptual design model. Some generation tools aim to help generate specific parts of a web application. CodeCharge helps to generate front-end codes in selected languages such as ASP, JSP, and ColdFusion; KoolFrog 19 helps to generate PL/SQL routines from Oracle database; EJBGen helps generating EJB 2.0 code. Tekadence 25 offers a point-and-click programming interface and visual design tool to help build up Java applications. GslGen is a generic-purpose code generator from XML file and schema file using generalpurposeschema language (GSL). Tekadence and GslGen generators are bound to specific script languages. JeeWiz is a product that provides an environment to help generate code forJ2EE-based web applications, such as EJB beans and deploymentdescriptor.3. TEMPLATE / META-DATA BASEDPARTIAL CODE GENERATIONIn this paper we present and discuss a template/meta-data based partial code generation system supporting web application development. Seamlessly incorporating the XML and J2EE family of technologies, the framework maximally exploits the capabilities of the underlying implementation technologies. We make an assumption here that a web application is represented by a set of web pages linked together by different operations. The web pages shown in a web application are dynamically generated based on the previous pages and the actions operated by users through the web browsers. Based on these basic assumptions, we identify three components in the conceptual design of a web application: data model, navigation model, and presentation model. Data model contains the information content to be shown on every web presentation page in an application. For example, a page displays a students address information, thus the data model of the page is the students address object. Navigation model manages the navigation links among different pages, therefore handles the control flow of a web application. For example, from a students address display page, a student can navigate to a page that displays his financial account information. Presentation model stores the display features of every web page to be exhibited, e.g. the layout of each data item of a students address information. Following the Object-Oriented paradigm, data models can be represented by data objects; and navigation models can be represented by the relationships among data models. These two types of models are naturally designed and developed by developers. Meanwhile, the presentation model focuses on the look and feel of every web page to be generated, therefore it is more natural for visual designers to handle parallel to the code developers. The information of the presentation model can be stored separately, and applied to the corresponding web page at run time. As a result, here we will concentrate on the automatic code generation of the first two types of models. The complete separation of data model, navigation model, and presentation model reflects on a more general conceptual process that would decouple the technique and methodology from its underlying technology choices. We will discuss in more detail how our approach facilitates the code generation of a web application from the first two models.3.1 Data Model GenerationWe designed and implemented an XML-based web code generator called WebGen. Similar to existing code generators, WebGen defines a set of templates to generate the code. Based on our investigation of J2EE family of technologies and utilizing state-of-the-art XML technology, which detailed information can be found from our previous work 26, WebGen provides a complete set of fourteen templates that can help automatically generate the code of a fully functioning running web application system. This template system provides code templates from the front-end to the back-end of a web system. JSP and form bean contain templates for JSP pages and their associated data models. Pre-action and Post-action templates define actions to format a web page and to collect information interactively supplied by page users. The Java bean template defines the business data object. We use the entity-bean home interface template, remote interface template, and implementation template to generate EJB entity beans. Likewise, the session-bean home interface template, remote interface template, and implementation template generate EJB session beans .The deployment descriptor template generates deployment descriptor segments for the corresponding entity beans and session beans. The service layer template generates service method signatures. The database schema template generates SQL statements for creating and deleting tables in the database. Given the large amount of code that we generateFigure 2. A Java class template file =DATA=NAME=Bean.javaautomatically, a developer merely needs to define the data modeland to implement the business logic in order for the webapplication to be complete. We use a concept of data file to store the data model of each web page. A data file is an XML file that describes the content of a data model to be merged into template files. Every data file is applied to template files to generate corresponding code. Figure 1 is an example of a data file that defines a data model of StudentGrade. As shown in Figure 1, for every item of the corresponding data model, one can define its name and data type. StudentGrade contains four data items: student id, year, term, and grade information. All four items have the same data type as “String”. The attribute Key is utilized to store the primary key internally. In addition, any aspect can be specified as a attribute of an item. For instance, as illustrated in Figure 1, the attribute Unique is utilized to specify whether the particular item can be treated uniquely or not. A template file itself is a code file, which contains tags that must be replaced at generation time by the corresponding values from the data files. Figure 2 is a simplified template file for a Java bean class. It can be used to generate a fully functional Java class file, which comprises a constructor and a set of getters and setters. WebGen defines three categories of tags: simple tag, repeating pattern, and conditional. A simple tag is a single tag, which will be replaced by the corresponding value defined in the data file. For example, tag in Figure 2 can be replaced by “String” defined in data file in Figure 1. A repeating pattern is an area that will repeat the pattern once per element of a list of data, such as the method body of constructor in Figure 2. The syntax of a repeating pattern is: pattern . Simple tags can be contained in the pattern. A conditional provides different patterns as options to choose from. The syntax of conditional is: pattern . The semantics is that, if VAL1 equals to VAL2, then the pattern contained in the tag will appear in the generated file, otherwise it will not. A data file can be applied to multiple template files, and a template file can also be applied to different data files.A configuration file provides knowledge to the WebGen, such as the style and criteria of the generation, in XML format. It bridges between data files and template files. Separated from data files, configuration files enhance the reusability of data files over different template files. There are two basic types of information that a configuration file needs to pass to WebGen. First, the output location of the generated files needs to be specified. The generated files can be configured in a way that they are stored in hierarchical directories. Second, a configuration file informs the generator about the relationships between template files and data files. This relationship is generally a many-to-many relationship.Figure 3 is an example of a configuration file for the corresponding data model StudentAddress. As shown in Figure 3,Figure 3. Example of a configuration filethe Java bean file will be stored in directory univ/businessObject; the data file StudentAddress will be used to generate the business object file, database table schema, and entity bean files, among others. In real world situations the code-generation approach imperatively runs into the problems of its closed world assumption of control. Data models may change overtime, and business logic may change during the life cycle of the development. Normal code generation tools cannot handle updated generated files; thus their powers eliminate. Facing the incremental changes and adaptations of the models in the full life cycle of web application development, it is important to separate between the generated code and the code that is necessary. In order to address this issue most code-generation supporting systems are facing, WebGen utilizes a simple configurable solution. Developers are able to decide whether the target file will be completely regenerated, or partly replaced, by specifying the value of attribute Change to be All or Part respectively, as shown in Figure 3. If it is specified as All, the target file will be completely regenerated every time the generator is invoked. Otherwise the generator will first search for the target file. If this file is not found, the generator will create a new code file. Otherwise, if a target file is found, the generator will search for the corresponding portion in the target file and replace it if the portion exists, or will add a new part if this portion does not exist.The rest of the portions of the file will be kept untouched. The separation of a generated portion and an immutable portion in one file enables regenerating a file without removing the embedded business logic. Since changes to data models are inevitable during design and implementation, this feature can improve the flexibility of the code generated.3.2 Navigation Model GenerationAs we discussed in the previous section, a navigation model stores the relationship among different web pages, and decide what a page can navigate to in the next step. In a business web application, the navigational information normally exhibits as a set of visible menu items on web pages. Therefore in our approach, we utilize the concept of menu system in order to manage the navigation model. The navigation model is stored in a menu system data structure; and the corresponding menu system generator (MSG), which is part of WebGen, assists to generate the code to display the menu system, including navigational information associated with each menu item. We follow the menu tree specified in Java Swing 24 as the data structure of our menu system. Since the description of a menu system is configured in an XML file, “visual designers” can assert their ideas by modifying the menu system independent of the coding of the system. Further, programmers do not need to do any coding of the menu system. MSG accepts configurations of a menu sys