📄 档案资料管理.md~
字号:
fill_color 13434879
nlines 1
max_width 312
justify 0
label "<Thread Name>")
stereotype (object ItemLabel
Parent_View @49
location (740, 389)
fill_color 13434879
anchor 10
nlines 1
max_width 312
justify 0
label "<<thread>>")
icon_style "Icon"
line_color 3342489
fill_color 13434879
quidu "35DB3CB002BC"
width 330
height 172
annotation 8
autoResize TRUE)
(object AssociationViewNew "$UNNAMED$18" @50
location (596, 464)
stereotype TRUE
line_color 3342489
quidu "35DB3E72017C"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$19" @51
Parent_View @50
location (-300, 0)
stereotype TRUE
line_color 3342489
quidu "35DB3E73005A"
client @50
supplier @48
line_style 0)
(object RoleView "$UNNAMED$20" @52
Parent_View @50
location (-300, 0)
stereotype TRUE
line_color 3342489
quidu "35DB3E730096"
client @50
supplier @49
line_style 0))))))))
logical_presentations (list unit_reference_list
(object ClassDiagram "Architecturally Significant Model Elements"
quid "34E36BDE02C6"
title "Architecturally Significant Model Elements"
documentation "Elements of the Design Model which are considered architecturally significant should be presented in this diagram. This diagram will be presented in the document generated using the SoDA Software Architecture Document."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @53
location (672, 304)
label (object ItemLabel
Parent_View @53
location (28, 19)
fill_color 13434879
nlines 13
max_width 1253
label
|
|This diagram is just produced for architectural significant packages.
|
|This diagram shows the Architectural Significant Classes and Packages in this package. Only significant operations and attributes are shown on the classes in this diagram.
|
|See Rational Unified Process:
|Activity: Architectural Design
|Step: Include Architecturally Significant Model Elements in the Logical View
|
|This will be a part of the "Software Architecture Document" :
|- "Logical View"
|- "Architecturally Significant Model Elements"
)
line_color 3342489
fill_color 13434879
width 1313
height 582)
(object NoteView @54
location (1696, 160)
label (object ItemLabel
Parent_View @54
location (1358, 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 ClassDiagram "Architecture Overview - Package and Subsystem Layering"
quid "354A9751015E"
title "Architecture Overview - Package and Subsystem Layering"
documentation
|This diagram depicts the organization of the design model into layers. This diagram will be presented in the document generated using the SoDA Software Architecture Document.
|
|See Rational Unified Process:
|Activity: Architectural Analysis
|Step: Define the High-Level Organization of Subsystems
|
|Activity: Incorporate Existing Design Elements
|Step: Update the Organization of the Design Model
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @55
location (576, 256)
label (object ItemLabel
Parent_View @55
location (44, 31)
fill_color 13434879
nlines 9
max_width 1028
label
|This diagram shows the design model layers.
|
|See Rational Unified Process:
|Activity: Architectural Analysis
|Step: Define the High-Level Organization of Subsystems
|
|Activity: Architectural Design
|Step: Define the Low-level Organization of Subsystems
)
line_color 3342489
fill_color 13434879
width 1088
height 463)
(object NoteView @56
location (1520, 176)
label (object ItemLabel
Parent_View @56
location (1182, 45)
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))))))
logical_presentations (list unit_reference_list
(object ClassDiagram "Welcome"
quid "3512226B0028"
title "Welcome"
documentation
|Welcome to the Rational Unified Process Frame Work
|
|Purpose of the FrameWork:
|a) provide a good structure for a Rose model
|b) provide a style guide with naming conventions/suggestions
|c) identify a minimal set of diagrams to produce
|d) relate activities in RUP to Rose diagrams
|e) provide a basis for sophisticated SoDA reports. For instance based on this structure most of the Rose parts of the "Software Architecture Document" are generated from SoDA.
|
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @57
location (768, 384)
label (object ItemLabel
Parent_View @57
location (121, 96)
fill_color 13434879
nlines 14
max_width 1259
label
|Welcome to the Rational Unified Process Rose Model Framework
|
|Purpose of the Framework:
|a) provide a good structure for a Rose model
|b) provide a style guide with naming conventions/suggestions
|c) identify a minimal set of diagrams to produce
|d) relate activities in RUP to Rose diagrams
|e) provide a basis for sophisticated SoDA reports. For instance based on this structure most of the Rose parts of the "Software Architecture Document" are generated from SoDA.
)
line_color 3342489
fill_color 13434879
width 1319
height 588)))))
root_subsystem (object SubSystem "Component View"
quid "34DBB4830143"
documentation
|In Rational Unified Process the "Component View in Rose" is used to organize the implemetation model.
|
|The Implementaition View in Rational Unified Process
|
|
physical_models (list unit_reference_list
(object SubSystem "Implementation Model"
quid "35B67C9A0348"
documentation
|The Implementation Model in Rational Unified Process is a collection of components, and the implementation subsystems that contain them.
|
|An architectural view that describes one or several system configurations; the mapping of software components (tasks, modules) to the computing nodes in these configurations.
|
|Defines, executables, dll's, files, subsystems, compilation order etc.
|
|Rational Unified Process:
|Activity: Define the Organization of Subsystems
|
|These diagram will be presented in the Implementation View section in the document generated using the SoDA Software Architecture Document.
|
|It is recommended that, in most cases, the mapping should be
|1:1 between design and implementation, that is, for each package in design there is one subsystem in the implementation model.
|
physical_models (list unit_reference_list)
physical_presentations (list unit_reference_list
(object Module_Diagram "Implementation Model Structure"
quid "34DBB487006E"
title "Implementation Model Structure"
documentation "This diagram presents the organization of the Implementation Model."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @58
location (624, 160)
label (object ItemLabel
Parent_View @58
location (21, 26)
fill_color 13434879
nlines 5
max_width 1170
label
|
|RationalUnified Process:
|Activity: Structure the implementation model
|Step: Create the Initial Implementation Model Structure
)
line_color 3342489
fill_color 13434879
width 1230
height 281))))))
physical_presentations (list unit_reference_list
(object Module_Diagram "Main"
quid "35C6339B029E"
title "Main"
documentation "This diagram, required by Rose, simply provides a way of navigating to the Implementation Model."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object SubSysView "Component View::Implementation Model" @59
location (736, 800)
label (object ItemLabel
Parent_View @59
location (552, 713)
fill_color 13434879
nlines 2
max_width 368
justify 0
label "Implementation Model")
icon_style "Icon"
line_color 3342489
fill_color 13434879
quidu "35B67C9A0348"
width 381
height 187)))))
process_structure (object Processes
quid "34DBB4830144"
ProcsNDevs (list
(object Processor "<processor name>"
quid "34DBBD4300B4"
documentation "This node provides <enter a short description here of the functionality and capability of the node>."
connections (list connection_list
(object Connection_Relationship
quid "34DBBD4B008C"
supplier "<device name>"
quidu "34DBBD47019A"
supplier_is_device TRUE))
characteristics ""
scheduling "Preemptive"
processes (list processes
(object Process "<process name>"
quid "35DB411001D6"
documentation "This process corresponds to the process with the same name in the Logical View::Process Model."
stereotype "process"
priority "")
(object Process "<thread name>"
quid "35DB41720348"
documentation "This process corresponds to the thread with the same name in the Logical View::Process Model."
stereotype "thread"
priority "")))
(object Device "<device name>"
quid "34DBBD47019A"
documentation "This device provides <enter a short description of the capability the device provides> for the system."
characteristics "")
(object Process_Diagram "Deployment View"
quid "34DBB4830146"
title "Deployment View"
documentation
|The Deployment View in Rational Unified Process
|
|Defines the typical physical network configurations, including those typically used by end users, as well as special configurations used for development and test.
|
|See Rational Unified Process:
|Activity: Describe Distribution
|
|This diagram will be a part of the SoDA template-generated Software Architecture Document under the "Deployment View" .
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object ProcessorView "<processor name>" @60
location (512, 1056)
label (object ItemLabel
Parent_View @60
location (276, 900)
nlines 2
max_width 400
justify 0
label "<processor name>")
icon_style "Label"
quidu "34DBBD4300B4"
width 475
height 381
annotation 3)
(object DeviceView "<device name>" @61
location (1040, 1056)
label (object ItemLabel
Parent_View @61
location (867, 950)
nlines 2
max_width 275
justify 0
label "<device name>")
icon_style "Icon"
quidu "34DBBD47019A"
width 350
height 282
annotation 0)
(object ConnectionView "" @62
stereotype TRUE
quidu "34DBBD4B008C"
client @60
supplier @61
line_style 0)
(object NoteView @63
location (816, 304)
label (object ItemLabel
Parent_View @63
location (38, 29)
fill_color 13434879
nlines 11
max_width 1521
label
|This Diagram defines the typical physical network configurations, including those typically used by end users, as well as special configurations used for development and test.
|
|
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -