※ 引述《SongYiYi (有ADSL真是爽歪歪)》之銘言：
: 1.Constructor:Grady Booch,Jim Rumbaugh,Ivar Jacobson
UML的主要開發者......重要
: 2.Team: Object Management Group(OMG)
UML開發的團體OMG.......重要
: 3.Rational Unified Process(RUP): By Booch, Rumbaugh,Jacobson
: 4.Notation: Notation is the graphic stuff you see in the syntax of the
: modeling language.
Notation:是指在UML裡的圖型
例如Use Case裡的小人是指actor、Class Diagram裡的Class是指Class
: 5.Meta-model:A diagram,usually is the class diagram,that defines the notation.
Meta-model:是指整個diagram，也就是notation所組合的圖形。
: 6.Formal method: In such technique,design and specifications are represented
: using some derivative predicate caculus.
: Formal method often leads to getting bogged down in details.
Formal method:是指正式的表示法，用數學的公式來表示method
: 7.Why do analysis and design?
: a)Communication:Using UML to highlight important details.
: Using patterns to describe important ideas in the systems.
: b)Leaning OO:Using these diagrams to learn OO well.
: c)Communicating with Domain experts:
--
※ 發信站: 批踢踢實業坊(ptt.csie.ntu.edu.tw)
◆ From: 61-217-130-24.HINET-IP.hinet.ne
> -------------------------------------------------------------------------- <
作者: SongYiYi (有ADSL真是爽歪歪) 看板: b89902xxx
標題: Re: UML的重點二
時間: Tue Jun 12 19:16:02 2001
※ 引述《SongYiYi (有ADSL真是爽歪歪)》之銘言：
: 8.The phase of the developement process Process的四個階段
: a)Inception 構思
: b)Elaboration 準備
: c)Constrution 建造
: d)Transtion 發行
: 9.Inception:
: a)Decide the scope of the project.
確定Project的範圍及大小
: b)Tell the sponsor how much it will cost and how much it will bring in.
說明此Project的收益和成本
: c)Get the commitments from the project sponsors to go futher.
獲得支助者的支持開始進一步的[分析
: 10.Elaboration:
: a)Collect more detailed requirements,do high-level analysis and design.
考慮更一步的需求作分析
: b)Get a better understanding of the problem
: b-1)What is it you are actually going to build?
: b-2)What are you going to build?
: c)Four Risks:
: c-1)Requirement Risks
: The biggest danger problem is that you build the wrong system.
最大的問題是做沒人要的系統
: c-2)Technological Risks
: The biggest technological risks is how all componets fit together
最大的挑戰是如何讓所有的元件合在一起work well
: c-3)Skill Risks
程式designer的速質
: c-4)Political Risks
大環境的因素像：經濟不景氣
--
※ 發信站: 批踢踢實業坊(ptt.csie.ntu.edu.tw)
◆ From: 61-217-130-24.HINET-IP.hinet.ne
> -------------------------------------------------------------------------- <
作者: SongYiYi (有ADSL真是爽歪歪) 看板: b89902xxx
標題: Re: UML重點三
時間: Wed Jun 13 09:02:37 2001
※ 引述《SongYiYi (有ADSL真是爽歪歪)》之銘言：
: 11.When Elaboration is finished?
什麼時候Elaboration可以結束
: a)The developers can feel comfortable providing estimate,
: to the nearst person-week effort,
: of how long it will take to build each use case.
當程式的開發者可以精確的估算計畫所須的時間和人力
: b)All the significant risks have been identified,
: and the major ones are understood to extent thatyou know
: how you intend to deal with time.
大部分的風險都能考慮到以及有辦法能解決
: 12.Construction:
: a)Set up a series of iteration.
在此階段要在細分成許多的小階段(interation)
: b)Define functionalities to deliver in each iteration.
並規劃在每一個小階段推出新的功能
: 13.Contingency factor:
: Add a contingency factor :10 percent to 20 percent of the construction time
保留一些緩衝的時間可做為修正
: 14.Refactoring:
就是程式碼的重新整理組合
: a)The full suite of the unit tests should be run at each intergration,
: to ensure full intergration tests.
: b)Redesign causes short-term pain for long-term gain.
: c)Refactoring is made easier by the following principles.
: 1)Don't refactor a program and add functionality to it at the same time.
在做程式的重組簡化的時候不要加新的功能
: 2)Make sure you have good tests in place before you begin refactoring.
在重組前要先要有測試的程式
: 3)Take short,deliberate steps.
: Ex:Fuse two similar methods into a super class.
重組後的程式讓他們簡短，易理解
: 15.Self Tests:
: a)unit test:Unit test should be written by the developers.
每一個元件的測試要交付程式開發者
: b)Function test:
: Function tests should be developed by a seperate team.
整個程式的test交付專門測試的部門
重點一和重點二在前面喔。........
To Be Continue.........
--
※ 發信站: 批踢踢實業坊(ptt.csie.ntu.edu.tw)
◆ From: 61-217-125-5.HINET-IP.hinet.net
> -------------------------------------------------------------------------- <
作者: SongYiYi (有ADSL真是爽歪歪) 看板: b89902xxx
標題: Re: UML重點四
時間: Wed Jun 13 09:27:02 2001
※ 引述《SongYiYi (有ADSL真是爽歪歪)》之銘言：
: 16.Transition:
: a) A prime example is to optimize and fix bugs.
目的是為了讓程式最佳化和除錯
: b)There is no develonment to add functionality, unless it is small and
: essential.
在此階段不在加新的功能除非必要
: 17.Scenario:
敘述
: A scenario is a sequence of steps describing an interaction a user and
: a system.
Scenario 就是記錄事件的敘述包括使用者和系統的互動
: 18.Use Case:
: A use case is a set of scenarios tied together by common user goal.
Use Case是指Scenario的集合，並且把他圖形化
: 19.Actor:
是指在Use Case的小人
: a) An actor is a role that is a user with the respect to the system.
Actor是指在系統中伴演的角色
: b)When dealing the actors , it is important to think about roles
: rather than people or job titles.
對於Actor的解釋與其說是人或是工作到不如看作是角色
: c)You should always question use cases with system actors,
: find out what real user goal.
: 20.Use Case Relationship
: a)<include> -------->用虛線加上箭頭表示並附注<<include>>
使用include時代表兩種或是兩種以上的圈圈用到此功能
: Use include when you are repeating yourself in two or more seperate
: use cases.
: You want to avoid repetition.
: b)<generalization>用實線和箭頭表示並附注<<generalization>>
: Use generaliation when you are describing a variantion on normal
: behavior and you wish to describe it casually.
: c)<extend> --------->用虛線加上箭頭表示並附注<<extend>>
: Use extend when you are describing a variation on noraml behavior
: and you wish to use the more controlled form.
其實generalization和extend的意義差不多，只是extend的用法較強調
--
※ 發信站: 批踢踢實業坊(ptt.csie.ntu.edu.tw)
◆ From: 61-217-125-5.HINET-IP.hinet.net