?? 數字校園類圖.md~
字號:
(object Petal
version 47
_written "Rose 8.0.0303.1400"
charSet 134)
(object Design "Logical View"
is_unit TRUE
is_loaded TRUE
attributes (list Attribute_Set
(object Attribute
tool "Java"
name "IDE"
value "Internal Editor")
(object Attribute
tool "Java"
name "UserDefineTagName1"
value "")
(object Attribute
tool "Java"
name "UserDefineTagText1"
value "")
(object Attribute
tool "Java"
name "UserDefineTagApply1"
value "")
(object Attribute
tool "Java"
name "UserDefineTagName2"
value "")
(object Attribute
tool "Java"
name "UserDefineTagText2"
value "")
(object Attribute
tool "Java"
name "UserDefineTagApply2"
value "")
(object Attribute
tool "Java"
name "UserDefineTagName3"
value "")
(object Attribute
tool "Java"
name "UserDefineTagText3"
value "")
(object Attribute
tool "Java"
name "UserDefineTagApply3"
value ""))
quid "36D487460258"
defaults (object defaults
rightMargin 0.250000
leftMargin 0.250000
topMargin 0.250000
bottomMargin 0.500000
pageOverlap 0.250000
clipIconLabels TRUE
autoResize TRUE
snapToGrid TRUE
gridX 16
gridY 16
defaultFont (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
showMessageNum 1
showClassOfObject TRUE
notation "Unified")
root_usecase_package (object Class_Category "Use Case View"
quid "34DBB4830142"
documentation
|The Use Case View organizes the Use-Case Model and the optional Business Use-Case Model.
|
exportControl "Public"
global TRUE
logical_models (list unit_reference_list
(object Class_Category "Business Use-Case Model"
quid "35B677D701B8"
documentation
|Optional Model:
|The business modeling workflow in Rational Unified Process produces two models: the business use-case model, and the business object model. Both show the business
|processes, but different aspects of them. In the business use-case model each business use case represents a business process, described (text and/or activity diagrams) from an "external" view point without worrying about who does what to whom inside of the organization.
|In the business object model, you include realizations of each business use case to show how workers and entities collaborate to perform the process. You do that using class diagrams, activity diagrams with swimlanes, collaboration diagrams, and/or interaction diagrams.
|
|<Any additional description of the Business Use Case Model, such as modeling conventions that the reader/reviewer may need to understand the model, should be described here.>
exportControl "Public"
logical_models (list unit_reference_list)
logical_presentations (list unit_reference_list
(object UseCaseDiagram "Global View of Business Actors and Business Use Cases"
quid "35C0DFF50172"
title "Global View of Business Actors and Business Use Cases"
documentation "This is a global view of the system showing all Busines Use Cases and Business Actors. It is intended to be an overview diagram, so if the diagram becomes too complex for easy comprehension, use several diagrams, each of which should focus on a different aspect of the system. Usually, organizing use case diagrams around actors is a good approach."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @1
location (464, 352)
font (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
label (object ItemLabel
Parent_View @1
location (42, 11)
fill_color 13434879
nlines 14
max_width 809
label
|Global View of Business Actors and BusinessUse Cases
|
|This diagram presents all Business Actors and all concrete Business Use Cases (those that are directly instantiable).
|
|Related Rational Unified Process Activities:
|- Activity: Find Business Actors and Use Cases
|- Activity: Structure the Business Use Case Model
|
|*Note: this note may be deleted once the diagram is created.
)
line_color 3342489
fill_color 13434879
width 869
height 694)
(object NoteView @2
location (1280, 160)
font (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
label (object ItemLabel
Parent_View @2
location (942, 29)
fill_color 13434879
nlines 5
max_width 640
label
|Created/modified by: <name>
|Date: <creation/modification date>
|
|Approved by: <name>
|Date: <approval date>
)
line_color 3342489
fill_color 13434879
width 700
height 275)))))
(object Class_Category "Use-Case Model"
documentation
|The Use-Case Model in Rational Unified Process contains a model of the behavior of a system which supports the business processes.
|
|<The description entered here should capture the Survey Description of the Use Case Model>.
|
|
|
visible_categories (list visibility_relationship_list
(object Visibility_Relationship
quid "35C633DA030C"
documentation "The Use-Case Model describes a system which realizes some of the required functionality described in the business use-case model, therefore the Use-Case Model is dependent on the Business Use-Case Model."
supplier "Use Case View::Business Use-Case Model"
quidu "35B677D701B8"))
exportControl "Public"
logical_models (list unit_reference_list
(object Class_Category "Actors"
quid "3518CBC9026C"
documentation
|All Actors in the system are contained in this package. This is both as a way to organize the model, making it easier to understand, and to provide a way to manage the actors in a single configuration item.
|
|If different individuals are responsible for different actors and their related artifacts, the actors should be organized into their own packages and placed under separate configuration control.
exportControl "Public"
logical_models (list unit_reference_list
(object Class "<Actor Name>"
quid "353D5816026C"
documentation
|<<The brief description of the actor is entered here. For guidance on what should go in this description, see the following Rational Unified Process references:
|
|- Activity: Find Actors and Use Cases
|- Guidelines: Actor>>
stereotype "Actor"))
logical_presentations (list unit_reference_list))
(object Class_Category "Use Cases"
quid "34E37E430280"
documentation
|All Use Cases in the system are contained in this package. This is done strictly as a way to organize the model and make it easier to understand.
|
|See Rational UnifiedProcess:
|Activity " Describe the Use Case Model".
|
|In order to version control use cases it is recommended to specify use case packages within this package.
|
|Use Cases are often documented in a separate text file, use the Rational Unified Process template or use the use case template in Rational Requsite Pro.
|
|The "Use Case Realizations" that correspond to these use cases are created in the Design Model..
exportControl "Public"
logical_models (list unit_reference_list
(object Class_Category "<Use Case Name>"
quid "35C0EC150366"
documentation " A separate package is recommended for each Use Case to facilitate access and version control of related use case artifacts."
exportControl "Public"
logical_models (list unit_reference_list
(object UseCase "<Use Case Name>"
quid "34E37FB203D4"
documentation
|<<The brief description of the use case is entered here. For guidance on what should go in this description, see the following Rational Unified Process references:
|
|- Activity: Find Actors and Use Cases
|- Guidelines: Use Case>>
logical_presentations (list unit_reference_list
(object UseCaseDiagram "Local View - <Use Case Name>"
quid "34E3E970019A"
title "Local View - <Use Case Name>"
documentation "This diagram presents the Local View of Use Case <Use Case Name>. The diagram depicts all actors which interact with <Use Case Name>, and any Use Cases which are associated with <Use Case Name>."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @3
location (480, 400)
font (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
label (object ItemLabel
Parent_View @3
location (33, 35)
fill_color 13434879
nlines 15
max_width 859
label
|Local View - Use Case <Use Case Name>
|
|This diagram presents the Local View of Use Case <Use Case Name>. The diagram depicts all actors which interact with <Use Case Name>, and any Use Cases which are associated with <Use Case Name>.
|
|Related Rational Unified Process Activities:
|Activity: Detail a Use-Case
|Step: Illustrate Relationships with Actors and Other Use-Cases
|
|*Note: this note may be deleted once the diagram is created.
)
line_color 3342489
fill_color 13434879
width 919
height 743)
(object NoteView @4
location (1344, 160)
font (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
label (object ItemLabel
Parent_View @4
location (1006, 29)
fill_color 13434879
nlines 5
max_width 640
label
|Created/modified by: <name>
|Date: <creation/modification date>
|
|Approved by: <name>
|Date: <approval date>
)
line_color 3342489
fill_color 13434879
width 700
height 275)
(object UseCaseView "Use Case View::Use-Case Model::Use Cases::<Use Case Name>::<Use Case Name>" @5
location (1088, 1024)
font (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
label (object ItemLabel
Parent_View @5
location (1088, 1162)
anchor_loc 1
nlines 2
max_width 631
justify 0
label "<Use Case Name>")
icon_style "Icon"
line_color 3342489
fill_color 13434879
quidu "34E37FB203D4"
autoResize TRUE)
(object ClassView "Class" "Use Case View::Use-Case Model::Actors::<Actor Name>" @6
ShowCompartmentStereotypes TRUE
IncludeAttribute TRUE
IncludeOperation TRUE
location (448, 1024)
font (object Font
size 9
face "Arial"
bold FALSE
italics FALSE
underline FALSE
strike FALSE
color 0
default_color TRUE)
label (object ItemLabel
Parent_View @6
location (448, 1184)
anchor_loc 1
nlines 2
max_width 325
justify 0
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -