Archive for the ‘系統分析設計(OOA/D)’ Category

一次展開Tree元件的所有節點(Expand All Children of Tree)

Sunday, March 22nd, 2009

展開一個Tree元件的所有節點的方法,有兩個階段:
1. 走訪所有節點
2. 如果是枝幹(branch)結點,就打開它( 有預設的方法可以使用, expandChildrenOf( node, open) )

要提醒的地方是,所有ListBase類型的元件,裡頭都有一個collectionChangeHandler的涵式,我們可以複寫他,讓每次資料重讀之後,就打開全部節點。
請見下方原始碼 :)

===
All ListBase-components handle collection with a collectionChangeHandler(event). All we have to do is override it by adding a expandAll() function. How will we do with this expandAll()? See following sample:

override protected function collectionChangeHandler(event:Event):void
{
    super.collectionChangeHandler( event );
   
    if( expandChildrenAfterReset )
    {
        if( CollectionEvent( event ).kind == CollectionEventKind.RESET )
        {
            expandAll();
        }
    }
}


public function expandAll():void
{
    if( collection )
    {
        var c:IViewCursor = collection.createCursor();
        var o:Object;
        while( !c.afterLast )
        {  
            o = c.current;
           
            if( dataDescriptor.isBranch( o ) )
                expandChildrenOf( o ,true );

            c.moveNext();
        }
    }
}

As you see, we just iterate all tree node, determining if it is a branch and then call the built-in expandChildreOf(node,open) method.

專案/系統/UI開發相關知識

Thursday, July 12th, 2007

專案開發:
Sap.com Design Guid

介面(UI)設計:
Concept: Persona (Cooper.com)

UML Basics

Wednesday, May 30th, 2007

Types of UML Diagrams:

  • Use Case:

    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.

  • use case scenario template

    find actors(depend on system boundary):
    To find actors depending 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.

  • Class:

    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.

  • (more…)

開始用del.icio.us

Wednesday, May 30th, 2007

把大部分的Flash/Flex/ActionScript/Web Design/等參考連結,都放到delicious.com了。
我的 del.icio.us
也可以在旁邊的sidebar裡頭找到我的delicious :)

Requirements Analysis Process Map

Thursday, May 10th, 2007

同事給了一份很棒的文件, 我把它的主要分析設計流程重繪出來:

精簡的流程:
Process Map

詳細的流程:
Process Map detail

about:USE CASE

Tuesday, May 8th, 2007

Ivar Jacobson, use case之父
推薦閱讀:(雖然有點舊了)
Use Cases—Yesterday, Today, and Tomorrow
他的官方網站資源

OOA, OOD

Monday, May 7th, 2007
  • OOA (Object Oriented Analysis)
  • OOD (Object Oriented Design)

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).