📄 库存管理信息系统领域图.mdl
字号:
quid "35B678080064"
documentation
|This model is optional.
|The Business Object Model contains a set of interacting workers and business entity (domain) classes which collaborate to enact the business processes. In some cases, only the business entity classes are documented. The business entity classes as a whole are sometimes referred to as a 'domain 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.
|
exportControl "Public"
logical_models (list unit_reference_list)
logical_presentations (list unit_reference_list))
(object Class_Category "Analysis Model"
quid "35B678170028"
documentation
|This model is optional.
|The Analysis Model contains a set of Analysis Classes, which describe an abstract realization of the use cases of the system. The analysis classes evolve into associated design elements which are modeled in the Design Model.
exportControl "Public"
logical_models (list unit_reference_list)
logical_presentations (list unit_reference_list))
(object Class_Category "Design Model"
quid "35B6782302DA"
documentation
|The Design Model in Rational Unified Process.
|The design model is adapted to model the real implementation environment, and serves as an abstraction of the source code. It is a "blueprint" of how the source code is structured and written.
|
|The design model is a hierarchy of packages (design subsystems and design-service packages), with "leaves" that are classes. Subsystems are a design "view" of the components that are defined in the Implementation Model.
|
|The design model hierarchy consists of layers.
|
|Classes represent abstractions of classes in the system's implementation. They define the objects, which in turn are abstractions of the objects in the system's implementation. The use cases are realized by the objects, and this is represented by use-case realizations in the Design Model. Each use-case realization has a realize dependency to a use case in the Use-Case Model.
exportControl "Public"
logical_models (list unit_reference_list
(object Class_Category "<Layer Name> Layer"
quid "34E3686A00F0"
documentation
|The design model is normally organized in layers. The number of layers is not fixed, but varies from situation to situation.
|
|During architectural analysis, focus is normally on the two high-level layers, that is, the application and business-specific layers; this is what is meant by the "high-level organization of subsystems." The other lower-level layers are in focus during architectural design, refer to the activity Architectural Design for more information.
|
|Layers are identified using the naming conventions shown in the name of this package.
exportControl "Public"
logical_models (list unit_reference_list
(object Class_Category "<package name>"
quid "34E36BB7017C"
documentation
|<Enter a short description of the package here. A package should be used in cases where a set of classes and/or other packages need to be grouped together for model organization purposes. Though the contents of the package can have public visibility, which makes them visible to model elements outside the containing package, packages are primarily just grouping mechanisms.
|
|If a set of classes is to be encapsulated and can be hidden behind a well-defined interface, a subsystem is a more appropriate container>
exportControl "Public"
logical_models (list unit_reference_list)
logical_presentations (list unit_reference_list
(object ClassDiagram "<package name> - Dependencies"
quid "37BC2256004D"
title "<package name> - Dependencies"
documentation "This diagram shows the package itself and the packages that it is dependent of. That is useful to know for instance when the package is a separate unit that can be reused in other systems."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))
(object ClassDiagram "<package name> - Interfaces"
quid "37BC226D026D"
title "<package name> - Interfaces"
documentation "This diagram shows only the classes that are visible outside this package. The interfaces of the package."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))))
(object Class_Category "<Subsystem Name>"
quid "35C0F38200B4"
documentation
|<Enter a short description of the subsystem here. A subsystem should be used in cases where a set of classes and/or other packages need to be encapsulated within a container and hidden behind a set of well-defined interfaces. By convention, none of the contents of subsystem are visible except the interfaces of the subsystem. This allows subsystems to be easily replaced, and the implementations changed, provided the interfaces remain unchanged. It offers a degree of encapsulation greater than that of the package.
|
|If a set of classes is merely to be grouped together, but public visibility of classes is still desirable, a package is a more appropriate container.>
stereotype "subsystem"
exportControl "Public"
logical_models (list unit_reference_list)
logical_presentations (list unit_reference_list
(object ClassDiagram "<subsystem name> - Dependencies"
quid "35C0F4220190"
title "<subsystem name> - Dependencies"
documentation "This diagram shows the package itself and the packages that it is dependent of. That is useful to know for instance when the package is a separate unit that can be reused in other systems."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))
(object ClassDiagram "<subsystem name> - Interfaces"
quid "37BC21080165"
title "<subsystem name> - Interfaces"
documentation
|The Process View in Rational Unified Process
|This package is used to organize the active classes in the system and will be presented in the SoDA-generated Software Architecture Document, under the "Process View"
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list)))))
logical_presentations (list unit_reference_list
(object ClassDiagram "All Packages in <Layer Name> - Layer"
quid "34E36C2903C0"
title "All Packages in <Layer Name> - Layer"
documentation "This diagram shows all packages in this - Layer."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))))
(object Class_Category "Use-Case Realizations"
quid "34E36D3203CA"
documentation
|In this Package we will describe "Use Case Realizations" as stereotyped use cases.
|
|A use-case realization describes how a particular use case is realized within the design model, in terms of collaborating objects.
|
|A realize dependency is used between the "Use Case Realization" and the "Use Case" in the use-case model that is realized.
|
|
exportControl "Public"
logical_models (list unit_reference_list
(object Association "$UNNAMED$24"
quid "35409E9D02A8"
stereotype "realize"
roles (list role_list
(object Role "$UNNAMED$25"
quid "35409E9E0294"
supplier "Use Case View::Use-Case Model::Use Cases::<Use Case Name>::<Use Case Name>"
quidu "34E37FB203D4"
is_navigable TRUE)
(object Role "$UNNAMED$26"
quid "35409E9E0295"
supplier "Logical View::Design Model::Use-Case Realizations::<Use-Case Name>::<Use-Case Name>"
quidu "352F38180276")))
(object Class_Category "<Use-Case Name>"
quid "35D083E100BE"
documentation " A separate package is recommended for each Use Case Realization 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 "352F38180276"
documentation
|This will be a stereotype on a usecase.
|In UML it is a stereotype on a collaboration and that does not exist in Rose.
stereotype "use-case realization"
logical_models (list unit_reference_list
(object Mechanism @52
logical_models (list unit_reference_list))
(object Mechanism @53
logical_models (list unit_reference_list)))
logical_presentations (list unit_reference_list
(object ClassDiagram "<Use Case Name> - Realize Dependencies"
quid "37BC23B801F1"
title "<Use Case Name> - Realize Dependencies"
documentation "This diagram shows the Use Case and the Use Case Realization and the realize dependency between them. This information is used to connect the use case with the use case realization."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))
(object ClassDiagram "<Use Case Name> - Participating Classes"
quid "37BC23E0036B"
title "<Use Case Name> - Participating Classes"
documentation "This Diagram shows all participating classes in this Use Case Realization"
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))
(object InteractionDiagram "<Use Case Name> - Basic Flow"
mechanism_ref @52
quid "35081E3603A2"
title "<Use Case Name> - Basic Flow"
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list))
(object InteractionDiagram "<Use Case Name> - <Flow Type>"
mechanism_ref @53
quid "3540A0B901AE"
title "<Use Case Name> - <Flow Type>"
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list)))))
logical_presentations (list unit_reference_list
(object ClassDiagram "Realize Dependency"
quid "34E39DA90302"
title "Realize Dependency"
documentation "This diagram shows the Use Case and the Use Case Realization and the realizes dependency between them."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object NoteView @54
location (704, 144)
label (object ItemLabel
Parent_View @54
location (38, 25)
fill_color 13434879
nlines 5
max_width 1296
label
|
|This diagram shows the Use Case and the Use Case Realization and the realize dependency between them.
)
line_color 3342489
fill_color 13434879
width 1356
height 250)
(object UseCaseView "Use Case View::Use-Case Model::Use Cases::<Use Case Name>::<Use Case Name>" @55
location (1152, 528)
label (object ItemLabel
Parent_View @55
location (1152, 666)
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 UseCaseView "Logical View::Design Model::Use-Case Realizations::<Use-Case Name>::<Use-Case Name>" @56
location (608, 960)
label (object ItemLabel
Parent_View @56
location (608, 1148)
anchor_loc 1
nlines 2
max_width 651
justify 0
label "<Use-Case Name>")
stereotype (object ItemLabel
Parent_View @56
location (608, 1078)
anchor 10
anchor_loc 1
nlines 1
max_width 434
justify 0
label "<<use-case realization>>")
icon "use-case realization"
icon_style "Icon"
line_color 3342489
fill_color 13434879
quidu "352F38180276"
autoResize TRUE)
(object AssociationViewNew "$UNNAMED$24" @57
location (876, 741)
stereotype (object SegLabel @58
Parent_View @57
location (874, 746)
anchor 10
anchor_loc 1
nlines 1
max_width 450
justify 0
label "<<realize>>"
pctDist 0.483333
height 5
orientation 1)
line_color 3342489
quidu "35409E9D02A8"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$25" @59
Parent_View @57
location (236, -539)
stereotype TRUE
line_color 3342489
quidu "35409E9E0294"
client @57
supplier @55
line_style 0)
(object RoleView "$UNNAMED$26" @60
Parent_View @57
location (236, -539)
stereotype TRUE
line_color 3342489
quidu "35409E9E0295"
client @57
supplier @56
line_style 0))))))))
logical_presentations (list unit_reference_list))
(object Class_Category "Process View"
quid "35D227B103C0"
documentation "An architectural view that describes the concurrent aspect of the system: tasks (processes) and their interactions."
exportControl "Public"
logical_models (list unit_reference_list
(object Class "<Process Name>"
quid "35DB3C8302D0"
documentation "This process provides <enter a description here of what the role of the process in the system is>. A separate process was chosen for this to be able to <enter the rationale for needing a separate process>."
stereotype "process")
(object Class "<Thread Name>"
quid "35DB3CB002BC"
documentation "This is a sub-process or thread within the <name of process of which this thread is a sub-process> process which handles <enter a description of what this thread does>. A separate thread was chosen for this to be able to <enter the rationale for creating a separate thread>."
stereotype "thread")
(object Association "$UNNAMED$27"
quid "35DB3E72017C"
roles (list role_list
(object Role "$UNNAMED$28"
quid "35DB3E73005A"
supplier "Logical View::Design Model::Process View::<Process Name>"
quidu "35DB3C8302D0"
is_navigable TRUE
is_aggregate TRUE)
(object Role "$UNNAMED$29"
quid "35DB3E730096"
supplier "Logical View::Design Model::Process View::<Thread Name>"
quidu "35DB3CB002BC"
Containment "By Value"
is_navigable TRUE))))
logical_presentations (list unit_reference_list
(object ClassDiagram "Process View"
quid "35DB3C2A02B2"
title "Process View"
documentation "This diagram illustrates the composition of processes and threads, and the mapping of classes onto those processes and threads."
zoom 100
max_height 28350
max_width 21600
origin_x 0
origin_y 0
items (list diagram_item_list
(object ClassView "Class" "Logical View::Design Model::Process View::<Process Name>" @61
ShowCompartmentStereotypes TRUE
IncludeAttribute TRUE
IncludeOperation TRUE
location (288, 464)
label (object ItemLabel
Parent_View @61
location (122, ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -