📄 库存管理信息系统.mdl
字号:
size 12)
label (object ItemLabel
Parent_View @25
location (1216, 1200)
anchor_loc 1
nlines 2
max_width 327
justify 0
label "仓库管理员")
icon "Actor"
icon_style "Icon"
fill_color 16777215
quidu "3F8C029A0005"
annotation 8
autoResize TRUE)
(object AssociationViewNew "$UNNAMED$0" @26
location (896, 970)
stereotype TRUE
quidu "3F8C03D501C1"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$1" @27
Parent_View @26
location (-320, -70)
stereotype TRUE
line_color 3342489
quidu "3F8C03D600DC"
client @26
supplier @22
line_style 0)
(object RoleView "$UNNAMED$2" @28
Parent_View @26
location (-320, -70)
stereotype TRUE
line_color 3342489
quidu "3F8C03D600DD"
client @26
supplier @25
line_style 0)))
(object AssociationViewNew "$UNNAMED$3" @29
location (1080, 740)
stereotype TRUE
quidu "3F8C03D80360"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$4" @30
Parent_View @29
location (-136, -300)
stereotype TRUE
line_color 3342489
quidu "3F8C03D902AD"
client @29
supplier @23
line_style 0)
(object RoleView "$UNNAMED$5" @31
Parent_View @29
location (-136, -300)
stereotype TRUE
line_color 3342489
quidu "3F8C03D902AE"
client @29
supplier @25
line_style 0)))
(object AssociationViewNew "$UNNAMED$6" @32
location (1388, 731)
stereotype TRUE
quidu "3F8C03DC030B"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$7" @33
Parent_View @32
location (172, -309)
stereotype TRUE
line_color 3342489
quidu "3F8C03DD02EF"
client @32
supplier @24
line_style 0)
(object RoleView "$UNNAMED$8" @34
Parent_View @32
location (172, -309)
stereotype TRUE
line_color 3342489
quidu "3F8C03DD02F9"
client @32
supplier @25
line_style 0)))
(object UseCaseView "Use Case View::退仓出库" @35
location (1920, 928)
font (object Font
size 12)
label (object ItemLabel
Parent_View @35
location (1920, 1066)
anchor_loc 1
nlines 2
max_width 630
justify 0
label "退仓出库")
icon_style "Icon"
fill_color 16777215
quidu "3F8C03690071"
height 118)
(object AssociationViewNew "$UNNAMED$9" @36
location (1541, 985)
stereotype TRUE
quidu "3F8C03E00158"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$10" @37
Parent_View @36
location (325, -55)
stereotype TRUE
line_color 3342489
quidu "3F8C03E100D8"
client @36
supplier @35
line_style 0)
(object RoleView "$UNNAMED$11" @38
Parent_View @36
location (325, -55)
stereotype TRUE
line_color 3342489
quidu "3F8C03E100E2"
client @36
supplier @25
line_style 0)))
(object UseCaseView "Use Case View::盘点管理" @39
location (592, 1664)
font (object Font
size 12)
label (object ItemLabel
Parent_View @39
location (592, 1802)
anchor_loc 1
nlines 2
max_width 630
justify 0
label "盘点管理")
icon_style "Icon"
fill_color 16777215
quidu "3F8C038101B6"
height 118)
(object UseCaseView "Use Case View::货位管理" @40
location (1216, 2016)
font (object Font
size 12)
label (object ItemLabel
Parent_View @40
location (1216, 2154)
anchor_loc 1
nlines 2
max_width 630
justify 0
label "货位管理")
icon_style "Icon"
fill_color 16777215
quidu "3F8C038A024F"
height 118)
(object ClassView "Class" "Use Case View::仓库经理" @41
ShowCompartmentStereotypes TRUE
IncludeAttribute TRUE
IncludeOperation TRUE
location (1216, 1440)
font (object Font
size 12)
label (object ItemLabel
Parent_View @41
location (1216, 1600)
anchor_loc 1
nlines 2
max_width 327
justify 0
label "仓库经理")
icon "Actor"
icon_style "Icon"
fill_color 16777215
quidu "3F8C039203B9"
annotation 8
autoResize TRUE)
(object AssociationViewNew "$UNNAMED$12" @42
location (928, 1540)
stereotype TRUE
quidu "3F8C03E300E4"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$13" @43
Parent_View @42
location (-288, 164)
stereotype TRUE
line_color 3342489
quidu "3F8C03E400E6"
client @42
supplier @39
line_style 0)
(object RoleView "$UNNAMED$14" @44
Parent_View @42
location (-288, 164)
stereotype TRUE
line_color 3342489
quidu "3F8C03E400E7"
client @42
supplier @41
line_style 0)))
(object AssociationViewNew "$UNNAMED$15" @45
location (1216, 1738)
stereotype TRUE
quidu "3F8C03E60265"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$16" @46
Parent_View @45
location (0, 362)
stereotype TRUE
line_color 3342489
quidu "3F8C03E70203"
client @45
supplier @40
line_style 0)
(object RoleView "$UNNAMED$17" @47
Parent_View @45
location (0, 362)
stereotype TRUE
line_color 3342489
quidu "3F8C03E70204"
client @45
supplier @41
line_style 0)))
(object UseCaseView "Use Case View::订单管理" @48
location (1856, 1664)
font (object Font
size 12)
label (object ItemLabel
Parent_View @48
location (1856, 1802)
anchor_loc 1
nlines 2
max_width 630
justify 0
label "订单管理")
icon_style "Icon"
fill_color 16777215
quidu "3F8C037A00BB"
height 118)
(object AssociationViewNew "$UNNAMED$18" @49
location (1509, 1540)
stereotype TRUE
quidu "3F8C03EA00D0"
roleview_list (list RoleViews
(object RoleView "$UNNAMED$19" @50
Parent_View @49
location (293, 164)
stereotype TRUE
line_color 3342489
quidu "3F8C03EB00D2"
client @49
supplier @48
line_style 0)
(object RoleView "$UNNAMED$20" @51
Parent_View @49
location (293, 164)
stereotype TRUE
line_color 3342489
quidu "3F8C03EB00D3"
client @49
supplier @41
line_style 0)))))))
root_category (object Class_Category "Logical View"
quid "34DBB4830141"
documentation
|Rational Unified Process uses the "Logical View in Rose" to organize the Design Model and the Process View and the optional Business Object Model and Analysis Model.
exportControl "Public"
global TRUE
subsystem "Component View"
quidu "34DBB4830143"
logical_models (list unit_reference_list
(object Class_Category "Business Object Model"
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"
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -