基于JAVAEE技术的电信计费数据优化系统毕业设计外文翻译

1、毕业设计说明书英文文献及中文翻译学生姓名：学院：学号：专业：指导教师：NET-BASED TASK MANAGEMENT SYSTEMABSTRACTIn n et-based collaborative desig n en viro nment, desig n resources become more and more varied and complex. Besides com mon in formatio n man ageme nt systems, desig n resources can be orga ni zed in connection with desig n

2、 activities.A set of activities and resources linked by logic relations can form a task. A task has at least one objective and can be broken down into smaller ones. So a design project can be separated into many subtasks forming a hierarchical structure.Task Man ageme nt System (TMS) is desig ned to

3、 break dow n these tasks and assig n certa in resources to its task no des. As a result of decompositi on. al1 desig n resources and activities could be man aged via this system.KEY WORDS : Collaborative Design. Task Management System (TMS), Task Decomposition, Information Man ageme nt System1 Intro

4、ductionAlong with the rapid upgrade of request for advaneed design methods, more and more design tool appeared to support new design methods and forms. Design in a web environment with multi-partners being in volved requires a more powerful and efficie nt man ageme nt system .Desig n part ners can b

5、e located everywhere over the net with their own organizations. They could be mutually independent experts or teams of tens of employees. This article discusses a task man ageme nt system (TMS) which man ages desig n activities and resources by breaking down design objectives and re-organizing desig

6、n resources in connection with the activities. Compari ng with com mon in formatio n man ageme nt systems (IMS) like product data man ageme nt system and docume nt man ageme nt system, TMS can man age the whole desig n process. It has two tiers which make it much more flexible in structure.The lower

7、 tier con sists of traditi onal com mon IMSS and the upper one fulfills logic activity management through controlling a tree-like structure, allocating design resources and making decisions about how to carry out a desig n project. Its functioning paradigm varies in differe nt projects depe nding on

8、the project ' s scale and purpose. As a result of this structure, TMS can separate its data model frctm i logic mode1.lt could bring about structure optimizati on and efficie ncy improveme nt, especially in a large scale project.2 Task Management in Net-Based Collaborative Design Environment2.1

9、Evolution of the Design EnvironmentDuring a n et-based collaborative desig n process, desig ners tran sform their work ing environment from a single PC desktop to LAN, and even extend to W AN. Each design partner can be a single expert or a comb in ati on of many teams of several subjects, eve n if

10、they are far away from each other geographically. In the net-based collaborative design environment, people from every terminal of the net can exchange their information interactively with each other and send data to authorized roles via their design tools. The Co Design Space is such an environment

11、 which provides a set of these tools to help design partners communicate and obtain design information. Code sign Space aims at improving the efficiency of collaborative work, mak ing en terprises in crease its sen sitivity to markets and optimize the con figurati on of resource.2.2 Management of Re

12、sources and Activities in Net-Based Collaborative EnvironmentThe expa nsion of desig n environment also caused a new problem of how to orga nize the resources and desig n activities in that en vir onment. As the nu mber of desig n partners in creases, resources also in crease in direct proporti on.

13、But relatio ns betwee n resources in crease in square ratio. To orga nize these resources and their relati ons n eeds an in tegrated man ageme nt system which can recog nize them and provide to desig ners in case of they are n eeded.One solutio n is to use special in formatio n man ageme nt system (

14、IMS).A n IMS can provide database, file systems and in/o ut i nterfaces to man age a give n resource. For example there are several IMS tools in Co Desig n Space such as Product Data Man ageme nt System, Docume nt Man ageme nt System and so on. These systems can provide its special in formati on whi

15、ch desig n users want.But the structure of desig n activities is much more complicated tha n these IM S could man age, because even a simple desig n project may in volve differe nt desig n resources such as docume nts, drafts andequipments. Not only product data or documents, design activities also

16、need the support of organizations in design processes. This article puts forward a new design system which attempts to in tegrate differe nt resources into the related desig n activities. That is task man ageme nt system (TMS).3 Task Breakdown Model3.1 Basis of Task BreakdownWhen people set out to a

17、ccomplish a project, they usually separate it into a sequenee of tasks and finish them one by one. Each desig n project can be regarded as an aggregate of activities, roles and data. Here we defi ne a task as a set of activities and resources and also havi ng at least one objective. Because large ta

18、sks can be separated into small ones, if we separate a project target into several lower level objectives, we defi ne that the project is broke n dow n into subtasks and each objective maps to a subtask. Obviously if each subtask is accomplished, the project is surely finished. So TMS integrates des

19、ign activities and resources through pla nning these tasks.Net-based collaborative desig n mostly aims at products developme nt. Project man agers (PM) assig n subtasks to desig ners or desig n teams who may locate in other cities. The desig ners and teams execute their own tasks under the constrain

20、ts which are defined by the PM and negotiated with each other via the collaborative desig n environment. So the desig ners and teams are in depe ndent collaborative part ners and have in compact coupli ng relati on ships. They are drive n together only by theft desig n tasks. After the PM have fini

21、shed decompos ing the project, each desig ner or team leader who has bee n assig ned with a subtask become a low-class PM of his own task. And he can do the same thing as his PM done to him, re-break ing dow n and re-assig ning tasks.So we put forward two rules for Task Breakdow n in a n et-based en

22、vironmen t, in compact coupli ng and object-drive n. In compact coupli ng means the less relati on ship betwee n two tasks. When two subtasks were coupled too tightly, the requireme nt for com muni cati on betwee n their desig ners will in crease a lot. Too much communication will not only waste tim

23、e and reduce efficiency, but also bring errors. It will become much more difficult to man age project process tha n usually in this situati on. On the other hand every task has its own objective. From the view point of PM of a superior task each subtask could be a black box and how to execute these

24、subtasks is unknown. The PM concerns only the results and constraints of these subtasks, and may n ever concern what will happe n in side it.3.2 Task Breakdown MethodAccording to the above basis, a project can be separated into several subtasks. And when thisseparati ng con ti nu es, it will fin all

25、y be decomposed into a task tree. Except the root of the tree is a project,all eaves and bran ches are subtasks. Since a desig n project can be separated into a task tree, all its resourcescan be added to it depe nding on their relati on ship. For example, a Small-Sized-Satellite.Desig n (3SD) proje

26、ct can be broke n dow n into two desig n objectives as Satellite Hardware. Desig n(SHD) and Satellite-Software-Exploit (SSE). And it also has two teams. Design team A and design team B which we regard as desig n resources. When A is assig ned to SSE and B to SHD. We break dow n the project as show n

27、 in Fig 1.It is alike to man age other resources in a project in this way. So whe n we defi ne a collaborative desig nproject task model, we should first claim the project targets. These targets include functional goals, performance goals, and quality goals and so on. Then we could confirm how to ex

28、ecute this project. Next we can go on to break down it. The project can be separated into two or more subtasks since there are at 1east two partners in a collaborative project. Either we could separate the project into stepwise tasks, which have time seque nce relati on ships in case of some more co

29、mplex projects and the n break dow n the stepwise tasks accord ing to their phase-to-phase goals.There is also another trouble in executing a task breakdown. When a task is broken into severa1subtasks; it is not merely“ a simple sum moti on” of other tasks. In most cases their subtasks could havemor

30、e complex relati ons.To solve this problem we use constraints. There are time sequence constraint (TSC) and logiccon stra in t (LC). The time seque nce con stra int defi nes the time relati on ships among subtasks. The TSC has four differe nt types, FF, FS, SF and SS. F means finish and S prese nts

31、start. If we say Tabb is FS and lag four days, it means Tb should start no later than four days after Ta is finished.The logic con stra int is much more complicated. It defi nes logic relati on ship among multiple tasks.Here is give n an example:“ Task TA is seprated into three subtasks, Ta, T b and

32、 Tc. But there are two more rules.Tb and Tc can not be executed until Ta is finished.Tb and Tc can not be executed both , that means if Tb was executed, Tc should not be executed, andSo we say Tb and Tc have a logic constraint. After finishing breaking down the tasks, we can get a task tree as Fig,

33、2 illustrates.4 TMS Realization4.1 TMS StructureAccord ing to our discussi on about task tree model and task breakdow n basis, we can develop a Task Man ageme nt System (TMS) based on Co Desig n Space using Java Ian guage, JSP tech no logy and Microsoft SQL 2000. The task management system' s st

34、ructure is shown in Fig. 3.TMS has four main modules n amely Task Breakdow n. Role Man ageme nt. Statistics and Query and Data In tegrati on. The Task Breakdow n module helps users to work out task tree. Role Man ageme nt module performs authe nticati on and authorizati on of access con trol. Statis

35、tics and Query module is an extra tool for users to find more in formatio n about their task. The last Data In tegrati on Module provides in/out in terface for TMS with its peripheral en viro nment.4.2 Key Points in System Realization4.2.1 Integration with Co Design SpaceCo Desig n Space is an in te

36、grated in formatio n man ageme nt system which stores, shares and processes design data and provides a series of tools to support users. These tools can share all information in the database because they have a universal Data Mode1. Which is defined in an XML (extensible Markup Language) file, and h

37、as a hierarchical structure. Based on this XML structure the TMS h data mode1 defi niti on is orga ni zed as follow ing.<?xml version= 1.0 encoding= UTF- 8' ?><!-comment :Com mon Resource Defin iti ons Above . The Followi ngare Task Desig n-><!ELEMENT ProductProcessResource (Prcse

38、s?, History? , AsBuiltProduct* , ItemsObj?, Changes?, Man ufacturerParts? , SupplierParts? , Attachme ntsObj?,Con tacts? , PartLibrary?,Additio nalAttributes*)><!ELEMENT Prcses (Prcs+) ><!ELEMENT Prcs (Prcses, PrcsNotes?, PrcsArc* , Con tacts? , Additio nalAttributes* ,Attachme nts?)>

39、<!ELEM ENT PrcsArc EMPTY<!ELEMENT PrcsNotes(PrcsNote*)><!ELEMENT PrcsNote EMPTY>Notes: Element“ Pros ” is a task node object, and“ Process ” is a task set object which containsobjects and is belo ngs to a higher class task object. One task object can have no more than oneobjects. Acco

40、rding to this definition,“ Prcs ” objects are orgfoniBedcin prtreess. The otherobjects are resources, such as task link object (“ Presage ” ), task notes (“ Pros Notes ” ),(“ Attachments ” ) .These resources are shared in Co Design database中北大学2014届毕业设计英文文献译文基于网络的任务管理系统摘要在网络与设计协同化的环境下，设计资源变得越来越多样化和复

41、杂化。随着信息管理系统的普 及，设计资源在各种设计活动的相互联系过程中被迅速组织起来。一整套在逻辑关系中联接的活动和资源可以组成一个任务。一个任务至少有一个对象，并且可被拆分为很多小的子任务。所以设计项目可分为许多子任务，并由它们形成一个严谨的层次结构。任务管理系统（TMS ）是被设计来打破这些任务，并指定某些资源去协调其相关工作。这样做 的结果就是所有的设计资源和活动都通过这个系统被管理起来。关键词：协同设计，任务管理系统（TMS ），任务分解，信息管理系统1简介随着对先进设计方法的要求的不断提高，支持新的设计方法和形式的设计工具不断涌现。在网 络环境下多伙伴参与的设计活动，需要一个更强大和

42、有效率的管理系统。设计伙伴可以在任何地点 锁定自己的组织，它们可以让专家或团队数千员工相互独立起来。本文论述了一种通过打破并重组 设计资源与活动来管理设计和活动资源的任务管理系统（TMS ）。与普通信息管理系统 （IMS）比较，例如产品数据管理系统和文件管理系统，任务管理系统能够管理整个设计过程。它的双层结构使之 结构更加灵活。底层由传统的普通信息管理系统结构（IMSS ）组成，而高层通过控制树形结构来实现逻辑活动 的管理，配置资源以及就如何开展设计项目展开设计和决策。其运作模式也会根据项目的规模和目 的产生变化。正是由于这种结构，任务管理系统可以把它的数据模型从其逻辑模型中分离出来，这 样将

43、会带来结构优化和效益改善，尤其对一个大型项目来说，作用更加明显。2基于网络的任务管理系统开发环境2.1设计环境的演进在网络化协同设计过程中，设计师不断变换着自己的工作环境，从个人电脑到局域网等，甚至延伸至广域网。每个设计伙伴，可以是一个单独专家或结合许多项目的几个科研小组，即使在地理位 置上相距遥远。在这样网络化协同设计环境中，来自不同网络终端的人们都可以通过协同的设计空 间互动的互相交流信息和发送数据。这种环境提供了一整套工具来帮助设计伙伴沟通和获取设计资料。协同空间旨在提高效率的协同工作，使企业增加敏感的市场，优化配置资源。2.2在互动的网络环境下对资源和活动的管理设计环境的扩展同样造成了

44、一系列新的问题，比如在这种环境下怎么样组织资源和活动。随着设计伙伴数量的不断增加。资源也在成比例的不断增加着。但是不同资源之间的联系也在不断的随 着它们的增加而不断提高。如何组织资源间的联系就需要一个综合的管理系统，一个可以组织它们 并在各种条件下将其提供给那些需要它的设计师的管理系统。一个解决方法是使用特殊的信息管理系统 （IMS）。这种信息管理系统能够提供数据库 ，文件系统 和输入/输出接口来管理已知的资源。 举个例子，在工作空间中有各种不同的 ISM工具，如产品数据 管理系统文件管理系统等。这些系统可以给他们的用户提供他们需要的各种特殊的信息。但是结构的设计活动是一项比IMS所能管理的极

45、限还要复杂的多的活动，因为即使一个简单的设计工作可能也需要处理不同的设计资源比如说文件、汇票和各种设备。不仅仅只有产品的数据或者文件，设计活动同样也需要设计过程所提供的各种组织过程。这篇文章提出了一种新的设计系统，它试图把不同的设计资源放进相关的设计活动中，这个就是任务管理系统（TMS ）。3任务分解模型3.1任务分解的依据当人们去完成一个项目时，他们通常会先把它分解成一个个的小任务，然后再去一个个的完成它。每个设计的项目都可以看作是一个整体的活动，各种对象和数据。我们定义的这个任务同样也需要一系列的活动和资源，并最少拥有一个活动。因为大的任务可以被分解成小的任务，如果我们将一个项目目标分解成

46、几个低级别的目标，我们定义了将这个项目分解成不同的子任务同时每个目 标也都映射到一个子任务。显然，如果每个子任务都完成，这个项目肯定已经被完成掉，所以TMS根据这些任务规划了资源和活动的分配。大多数的网络化协同设计都将他们的目标定在产品的发展上。项目的管理者将这些子任务交给设计师或者设计团队。这些设计师或者团队在项目主管指定的条件下进行他们各自任务的设计。所以这些设计师和设计团队是相互独立的伙伴并且组织松散。当项目主管完成对这些项目的分解时，每个设计师或者设计团队的领队都会被指派一个已经低级别的子任务，并且他们可以做和他们主管同样的事，将这些子任务打破并且重新分配给他的设计师或者团队。因此，在

47、网络环境下我们为任务分解提出了两项规则，松散的组合和有目的的项目。松散的组 合指得是两项任务之间的联系很少，当两个子任务被捆绑的很紧的话，它们的设计者之间的通信量 将会增加很多。大量的通信只会浪费时间和降低效率，与此同时也会带来错误。管理项目的过程也 会变得比平常更加的困难。另一方面，每个任务都有它自己的工作对象。从项目主管的角度来看， 每个子任务都是未知的。他们的注意力只会放在结果和这些子任务的内容上，并且可能永远都不会 关心这个小黑匣子里面会发生什么。3.2任务分解模式根据上面的基础，一个项目能被分解为一些子任务，并且当这些分解继续进行时，它最终会组成 一个任务树。除非树的结点是一个项目，

48、所有其他的树叶和树枝都是一个个子任务，正是由于一个 设计项目可以被分解成一个任务树，所有这些资源都能根据它们之间的关系被添加到适当的位置上，举个例子来说，一个小型的卫星。设计项目可以像卫星一样被分解成 2个设计项目。硬件，设计和软件。并且他也可以有2个团队，设计团队A和设计团队B，这些我们都可以把他们看作设计资源，当 A被映射到SSE, B映射 到SHD时，我们就像图1 一样将这个项目分解掉。管理一个项目中的其他资源用的也是这种方法，所以当我们确定了一个设计项目的任务模型时，我们应该首先搞清楚这个项目的目的。这些目标包括系统的目的，业绩的目标，质量的目标等等。然后我们应该确定如何执行这个项目，紧接着我们可以开始将它细化。因为有最少2个的设计伙伴，这些项目可以被分解成一个或者更多的子任务。或者当我们遇到一些更复杂的项目时，可以将这项 项目分解成有层次感的任务，并按它们相互间的目标来逐步的实现这些任务。当我们对一个任务进行细化时还将遇到一个难题。当我们将一个