首页 > 代码库 > UML期末绘图及细节总结
UML期末绘图及细节总结
往届期末绘图的题目例如以下所看到的：
Read the providing materials carefully, and then do tasks.
2.1: Use Case Diagram
Develop a detailed use case model for the application “X单词”. The model should take auser’s(rather than system’s) perspective.Define use cases for handling user’s input and actions, butdonot be specific about system’s computationsor web page creation activities.
Show dependencies between use cases. Specify ?include?and ?extend?relationshipsand anyimportant constraints.
2.2: UML Activity Diagram.
Develop a UML activity model for the use case“背单词”of the application. The model visualizesthe interactions between a user and the application to fill a user’s goals. Pay attention on useractions,do notapply swim lane activity diagram.
2.3: UML State Diagram.
Develop a UML state model for the control process of the use case“背单词”. The modelvisualizes the relationship between external events and business scenes.
2.4: Domain Model.
Develop a domain model of the application(注意:仅须要从设置学习内容,背单词用例中获取领域对象). The model should take business perspectives.The conceptual model should showattributes in classes and relationships between classes. All associations should have multiplicitiescarefully defined. There is no need to specify attribute types and operations (methods).
2.5 System Sequence Diagram & Post-condition
According to the main scenario of the use case“背单词”, Develop a SSD model to identify somesystem operations for the system. And then give the post-condition of the operation“startLearning()”(即開始学习操作)
2.6 Package Diagram
For OO architecture design, we always use MVC pattern to build layer architecture. Develop apackage diagram illustrates these layers. Please show the dependencies between packages, andthen put software classes of the main scenario of the use case“背单词”into these packages.
2.7 UML Sequence Diagram
According to BCE pattern, develop a interaction model with sequence diagram for the mainscenario of the use case“背单词”.
2.8 UML Design Class Diagram (DCD)
Develop a DCD including C&E elements onlyaccording to results of 2.7 and 2.4
附加题(10 marks)
2.9 UML Deployment Diagram
The architect(架构师) studied the use case“打卡”, he want a DB server to hold user profiles(用户注冊信息)and achievements(成就), a Web server to provide some services for clients, Mobilephones with android operation system as client hold MVC component and Proxy servicescomponent. A client communicates with the web server using HTTP and JSON protocol.
Develop a deployment model to illustrate the architect’s design. Stereotype must be used toclassify physical nodes.
然后题目答案我也打包了，点击链接下载：http://download.csdn.net/detail/luoshengkim/8841305
最后，我来总结一下在老师上课讲课的时候提到过的。UML绘图中须要注意的一些细节事项吧：
1）用例图的圆圈里要用动词
2）活动图：提到用例的时候不用画多泳道，说业务的时候才会出现并行（业务可画多泳道）
3）需求时期最须要 领域模型（数据库的设计须要他）
4）设计时须要交互图
5）类图中须要注意的3个差别：a）泛化&继承 b）操作和方法 c）组合和聚合
6）在软件设计方法中。泛化＝继承
7）在非软件设计方式中，泛化 !＝继承
8）用例图：遵循boss准则。关注业务过程。单步操作。不出现名词。不要太多分层（include不要超过4层）
9）活动图：不要太仔细，画清楚分支选择（主要的操作。子用例）
10）状态图：［］表示条件，／表示系统，一定要有起点，不一定有终点，单词解释是复杂对象，没描写叙述类一定会扣分
11）部署图三要素：节点，部件，关联
12）系统顺序图。不要有ifelse。消息不超过五条
以上的细节知识点都是我上课记录下来的，当然还有非常多细节须要注意。总之。UML绘图还是要慢慢来，前后相应一定要一致。画的多了，自然就通了。最后，希望期末考试能给力一些～Fighting！
最后再来说一下对这整个学期甚至这整个半年的感想和总结吧，UML这门课还真是挺奇妙的。学期一開始的时候认为这门课非常枯燥，可是越到后面越喜欢这门课，也越发的意识到系统分析与设计的重要性。
我认为最基本的原因还是理论＋实践的结合吧，这一点潘老师做得非常好，我们在实践中学习，小组做project过程中同一时候在画UML图，在实战的过程中我们发现了非常多的不足，也因此做了非常多的改进，也学到了不少。UML在工程领域还真是挺重要的一个东西。
UML期末绘图及细节总结