專案/系統/UI開發相關知識
Thursday, July 12th, 2007專案開發:
Sap.com Design Guid
介面(UI)設計:
Concept: Persona (Cooper.com)
專案開發:
Sap.com Design Guid
介面(UI)設計:
Concept: Persona (Cooper.com)
Types of UML Diagrams:
A use case diagram is a simple diagram that shows who is using your system and what processes they will perform in the system.
Best use: The use case diagram is an extremely important diagram for the Requirements Gathering and Analysis workflows. Throughout the entire development, all work should be traceable back to the Use Case diagram.
find actors(depend on system boundary):
![]()
Use case diagrams and use case relationships are secondary in use case work. Use cases are text documents. Doing use case work means to write text.
A Class diagram show a set of classes in the system and the associations and inheritance relationships between the classes. Class nodes might also contain a listing of attributes and operations.
Best Use: The Class Diagram is essential for showing the structure of the system and what needs to be programmed. Most UML case tools can generate code based on the class diagram.
把大部分的Flash/Flex/ActionScript/Web Design/等參考連結,都放到delicious.com了。
我的 del.icio.us
也可以在旁邊的sidebar裡頭找到我的delicious ![]()
Ivar Jacobson, use case之父
推薦閱讀:(雖然有點舊了)
Use Cases—Yesterday, Today, and Tomorrow
他的官方網站資源
OOA:
Emphasizes an investigation of the problem and requirements, rather than a solution. For example, if a new online trading system is desired, how will it be used? What are its functions?
OOD:
Emphasizes a conceptual solution (in software and hardware) that fulfills the requirements, rather than its implementation. For example, a description of a database schema and software objects. Design ideas often exclude low-level or “obvious” detailsobvious to the intended consumers. Ultimately, designs can be implemented, and the implementation (such as code) expresses the true and complete realized design.
Useful analysis and design have been summarized in the phrase do the right thing (analysis), and do the thing right (design).