1 

     2 (object Petal

     3     version    	43

     4     _written   	"Rose 6.5.9232.10"

     5     charSet    	0)

     6 

     7 (object Design "Logical View"

     8     is_unit    	TRUE

     9     is_loaded  	TRUE

    10     quid       	"36D487460258"

    11     defaults   	(object defaults

    12 	rightMargin 	0.250000

    13 	leftMargin 	0.250000

    14 	topMargin  	0.250000

    15 	bottomMargin 	0.500000

    16 	pageOverlap 	0.250000

    17 	clipIconLabels 	TRUE

    18 	autoResize 	TRUE

    19 	snapToGrid 	TRUE

    20 	gridX      	16

    21 	gridY      	16

    22 	defaultFont 	(object Font

    23 	    size       	9

    24 	    face       	"Arial"

    25 	    bold       	FALSE

    26 	    italics    	FALSE

    27 	    underline  	FALSE

    28 	    strike     	FALSE

    29 	    color      	0

    30 	    default_color 	TRUE)

    31 	showMessageNum 	1

    32 	showClassOfObject 	TRUE

    33 	notation   	"Unified")

    34     root_usecase_package 	(object Class_Category "Use Case View"

    35 	quid       	"34DBB4830142"

    36 	documentation 	

    37 |The Use Case View organizes the Use-Case Model and the optional Business Use-Case Model.

    38 |

    39 	

    40 	exportControl 	"Public"

    41 	global     	TRUE

    42 	logical_models 	(list unit_reference_list

    43 	    (object Class_Category "Business Use-Case Model"

    44 		quid       	"35B677D701B8"

    45 		documentation 	

    46 |Optional Model:

    47 |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 

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

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

    50 |

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

    52 		

    53 		exportControl 	"Public"

    54 		logical_models 	(list unit_reference_list)

    55 		logical_presentations 	(list unit_reference_list

    56 		    (object UseCaseDiagram "Global View of Business Actors and Business Use Cases"

    57 			quid       	"35C0DFF50172"

    58 			title      	"Global View of Business Actors and Business Use Cases"

    59 			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."

    60 			zoom       	100

    61 			max_height 	28350

    62 			max_width  	21600

    63 			origin_x   	0

    64 			origin_y   	0

    65 			items      	(list diagram_item_list

    66 			    (object NoteView @1

    67 				location   	(464, 352)

    68 				label      	(object ItemLabel

    69 				    Parent_View 	@1

    70 				    location   	(42, 11)

    71 				    fill_color 	13434879

    72 				    nlines     	14

    73 				    max_width  	809

    74 				    label      	

    75 |Global View of Business Actors and BusinessUse Cases

    76 |

    77 |This diagram presents all Business Actors and all concrete Business Use Cases (those that are directly instantiable).

    78 |

    79 |Related Rational Unified Process Activities:

    80 |- Activity: Find Business Actors and Use Cases

    81 |- Activity: Structure the Business Use Case Model

    82 |

    83 |*Note: this note may be deleted once the diagram is created.

    84 				    )

    85 				line_color 	3342489

    86 				fill_color 	13434879

    87 				width      	869

    88 				height     	694)

    89 			    (object NoteView @2

    90 				location   	(1280, 160)

    91 				label      	(object ItemLabel

    92 				    Parent_View 	@2

    93 				    location   	(942, 29)

    94 				    fill_color 	13434879

    95 				    nlines     	5

    96 				    max_width  	640

    97 				    label      	

    98 |Created/modified by: <name>

    99 |Date: <creation/modification date>

   100 |

   101 |Approved by: <name>

   102 |Date: <approval date>

   103 				    )

   104 				line_color 	3342489

   105 				fill_color 	13434879

   106 				width      	700

   107 				height     	275)))))

   108 	    (object Class_Category "Use-Case Model"

   109 		is_unit    	TRUE

   110 		is_loaded  	FALSE

   111 		file_name  	"M:\\DST\\analysis\\UseCases.cat"

   112 		quid       	"35B677F4010E"))

   113 	logical_presentations 	(list unit_reference_list

   114 	    (object UseCaseDiagram "Main"

   115 		quid       	"35C6339B029F"

   116 		title      	"Main"

   117 		documentation 	

   118 |This diagram depicts the relationships between the packages (models) contained in the 'Use-Case View": the Use-Case Model (for the system) and the Business Use-Case Model (describing the business).

   119 		

   120 		zoom       	90

   121 		max_height 	28350

   122 		max_width  	21600

   123 		origin_x   	0

   124 		origin_y   	0

   125 		items      	(list diagram_item_list

   126 		    (object CategoryView "Use Case View::Use-Case Model" @3

   127 			location   	(400, 864)

   128 			font       	(object Font

   129 			    size       	10)

   130 			label      	(object ItemLabel

   131 			    Parent_View 	@3

   132 			    location   	(256, 780)

   133 			    fill_color 	13434879

   134 			    nlines     	2

   135 			    max_width  	288

   136 			    justify    	0

   137 			    label      	"Use-Case Model")

   138 			icon_style 	"Icon"

   139 			line_color 	3342489

   140 			fill_color 	13434879

   141 			quidu      	"35B677F4010E"

   142 			width      	300

   143 			height     	180)

   144 		    (object NoteView @4

   145 			location   	(1168, 592)

   146 			font       	(object Font

   147 			    size       	10)

   148 			label      	(object ItemLabel

   149 			    Parent_View 	@4

   150 			    location   	(941, 390)

   151 			    fill_color 	13434879

   152 			    nlines     	9

   153 			    max_width  	419

   154 			    label      	"The Use-Case Model is traceable to (and derives from) the Business Model.  The system (as described in the Use Case Model) provides behavior that supports the business.")

   155 			line_color 	3342489

   156 			fill_color 	13434879

   157 			width      	479

   158 			height     	416)

   159 		    (object CategoryView "Use Case View::Business Use-Case Model" @5

   160 			location   	(384, 320)

   161 			label      	(object ItemLabel

   162 			    Parent_View 	@5

   163 			    location   	(189, 229)

   164 			    fill_color 	13434879

   165 			    nlines     	2

   166 			    max_width  	390

   167 			    justify    	0

   168 			    label      	"Business Use-Case Model")

   169 			icon_style 	"Icon"

   170 			line_color 	3342489

   171 			fill_color 	13434879

   172 			quidu      	"35B677D701B8"

   173 			width      	403

   174 			height     	194)

   175 		    (object ImportView "" @6

   176 			stereotype 	TRUE

   177 			line_color 	3342489

   178 			quidu      	"35C633DA030C"

   179 			client     	@3

   180 			supplier   	@5

   181 			line_style 	0)

   182 		    (object AttachView "" @7

   183 			stereotype 	TRUE

   184 			line_color 	3342489

   185 			client     	@6

   186 			supplier   	@4

   187 			line_style 	0)))))

   188     root_category 	(object Class_Category "Logical View"

   189 	quid       	"34DBB4830141"

   190 	documentation 	

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

   192 	

   193 	exportControl 	"Public"

   194 	global     	TRUE

   195 	subsystem  	"Component View"

   196 	quidu      	"34DBB4830143"

   197 	logical_models 	(list unit_reference_list

   198 	    (object Class_Category "Analysis Model"

   199 		quid       	"35B678170028"

   200 		documentation 	

   201 |This model is optional.

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

   203 		

   204 		exportControl 	"Public"

   205 		logical_models 	(list unit_reference_list

   206 		    (object Class_Category "Business Object Model"

   207 			is_unit    	TRUE

   208 			is_loaded  	FALSE

   209 			file_name  	"M:\\DST\\analysis\\LogicalBusinessObjects.cat"

   210 			quid       	"35B678080064")

   211 		    (object Class_Category "TZ Compiler"

   212 			is_unit    	TRUE

   213 			is_loaded  	FALSE

   214 			file_name  	"M:\\DST\\analysis\\TZCOMPILER.CAT"

   215 			quid       	"40E569BC024F")

   216 		    (object Class_Category "LTClasses"

   217 			is_unit    	TRUE

   218 			is_loaded  	FALSE

   219 			file_name  	"M:\\DST\\analysis\\Classes.cat"

   220 			quid       	"40A89DC203B0")

   221 		    (object Class_Category "Time Zone Database Management"

   222 			is_unit    	TRUE

   223 			is_loaded  	FALSE

   224 			file_name  	"M:\\DST\\analysis\\LogicalTZDBM.cat"

   225 			quid       	"40B1E4A6003A")

   226 		    (object Class_Category "Local Time Conversion"

   227 			is_unit    	TRUE

   228 			is_loaded  	FALSE

   229 			file_name  	"M:\\DST\\analysis\\LogicalLocaltimeConv.cat"

   230 			quid       	"40B1D43200B7")

   231 		    (object Class_Category "System Time Management"

   232 			is_unit    	TRUE

   233 			is_loaded  	FALSE

   234 			file_name  	"M:\\DST\\analysis\\LogicalSysTimeMngmt.cat"

   235 			quid       	"40B1D49203C5")

   236 		    (object Class_Category "TZClasses"

   237 			is_unit    	TRUE

   238 			is_loaded  	FALSE

   239 			file_name  	"M:\\DST\\analysis\\TZClasses.cat"

   240 			quid       	"40F3CEAF0324")

   241 		    (object Class_Category "BClasses"

   242 			is_unit    	TRUE

   243 			is_loaded  	FALSE

   244 			file_name  	"M:\\DST\\analysis\\BClasses.cat"

   245 			quid       	"40F3CFB10172"))

   246 		logical_presentations 	(list unit_reference_list))

   247 	    (object Class_Category "Design Model"

   248 		quid       	"35B6782302DA"

   249 		documentation 	

   250 |The Design Model in Rational Unified Process.

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

   252 |

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

   254 |

   255 |The design model hierarchy consists of layers. 

   256 |

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

   258 		

   259 		exportControl 	"Public"

   260 		logical_models 	(list unit_reference_list

   261 		    (object Class_Category "<Layer Name> Layer"

   262 			quid       	"34E3686A00F0"

   263 			documentation 	

   264 |The design model is normally organized in layers. The number of layers is not fixed, but varies from situation to situation. 

   265 |

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

   267 |

   268 |Layers are identified using the naming conventions shown in the name of this package. 

   269 			

   270 			exportControl 	"Public"

   271 			logical_models 	(list unit_reference_list

   272 			    (object Class_Category "<package name>"

   273 				quid       	"34E36BB7017C"

   274 				documentation 	

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

   276 |

   277 |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>

   278 				

   279 				exportControl 	"Public"

   280 				logical_models 	(list unit_reference_list)

   281 				logical_presentations 	(list unit_reference_list

   282 				    (object ClassDiagram "<package name> - Dependencies"

   283 					quid       	"37BC2256004D"

   284 					title      	"<package name> - Dependencies"

   285 					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."

   286 					zoom       	100

   287 					max_height 	28350

   288 					max_width  	21600

   289 					origin_x   	0

   290 					origin_y   	0

   291 					items      	(list diagram_item_list))

   292 				    (object ClassDiagram "<package name> - Interfaces"

   293 					quid       	"37BC226D026D"

   294 					title      	"<package name> - Interfaces"

   295 					documentation 	"This diagram shows only the classes that are visible outside this package. The interfaces of the package."

   296 					zoom       	100

   297 					max_height 	28350

   298 					max_width  	21600

   299 					origin_x   	0

   300 					origin_y   	0

   301 					items      	(list diagram_item_list))))

   302 			    (object Class_Category "<Subsystem Name>"

   303 				quid       	"35C0F38200B4"

   304 				documentation 	

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

   306 |

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

   308 				

   309 				stereotype 	"subsystem"

   310 				exportControl 	"Public"

   311 				logical_models 	(list unit_reference_list)

   312 				logical_presentations 	(list unit_reference_list

   313 				    (object ClassDiagram "<subsystem name> - Dependencies"

   314 					quid       	"35C0F4220190"

   315 					title      	"<subsystem name> - Dependencies"

   316 					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."

   317 					zoom       	100

   318 					max_height 	28350

   319 					max_width  	21600

   320 					origin_x   	0

   321 					origin_y   	0

   322 					items      	(list diagram_item_list))

   323 				    (object ClassDiagram "<subsystem name> - Interfaces"

   324 					quid       	"37BC21080165"

   325 					title      	"<subsystem name> - Interfaces"

   326 					documentation 	

   327 |The Process View in Rational Unified Process

   328 |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"

   329 					

   330 					zoom       	100

   331 					max_height 	28350

   332 					max_width  	21600

   333 					origin_x   	0

   334 					origin_y   	0

   335 					items      	(list diagram_item_list)))))

   336 			logical_presentations 	(list unit_reference_list

   337 			    (object ClassDiagram "All Packages in <Layer Name> - Layer"

   338 				quid       	"34E36C2903C0"

   339 				title      	"All Packages in <Layer Name> - Layer"

   340 				documentation 	"This diagram shows all packages in this - Layer."

   341 				zoom       	100

   342 				max_height 	28350

   343 				max_width  	21600

   344 				origin_x   	0

   345 				origin_y   	0

   346 				items      	(list diagram_item_list))))

   347 		    (object Class_Category "Use-Case Realizations"

   348 			quid       	"34E36D3203CA"

   349 			documentation 	

   350 |In this Package we will describe "Use Case Realizations" as stereotyped use cases.

   351 |

   352 |A use-case realization describes how a particular use case is realized within  the design model, in terms of collaborating objects.

   353 |

   354 |A realize dependency is used between the "Use Case Realization" and the "Use Case" in the use-case  model that is realized. 

   355 |

   356 |

   357 			

   358 			exportControl 	"Public"

   359 			logical_models 	(list unit_reference_list

   360 			    (object Association "$UNNAMED$0"

   361 				quid       	"35409E9D02A8"

   362 				stereotype 	"realize"

   363 				roles      	(list role_list

   364 				    (object Role "$UNNAMED$1"

   365 					quid       	"35409E9E0294"

   366 					supplier   	"Use Case View::Use-Case Model::Use Cases::<Use Case Name>::<Use Case Name>"

   367 					quidu      	"34E37FB203D4"

   368 					is_navigable 	TRUE)

   369 				    (object Role "$UNNAMED$2"

   370 					quid       	"35409E9E0295"

   371 					supplier   	"Logical View::Design Model::Use-Case Realizations::<Use-Case Name>::<Use-Case Name>"

   372 					quidu      	"352F38180276")))

   373 			    (object Class_Category "<Use-Case Name>"

   374 				quid       	"35D083E100BE"

   375 				documentation 	" A separate package is recommended for each Use Case Realization to facilitate access and version control of related use case artifacts."

   376 				exportControl 	"Public"

   377 				logical_models 	(list unit_reference_list

   378 				    (object UseCase "<Use-Case Name>"

   379 					attributes 	(list Attribute_Set

   380 					    (object Attribute

   381 						tool       	"RequisitePro"

   382 						name       	"ReqProProjectPath"

   383 						value      	"")

   384 					    (object Attribute

   385 						tool       	"RequisitePro"

   386 						name       	"ReqProProjectGuid"

   387 						value      	"")

   388 					    (object Attribute

   389 						tool       	"RequisitePro"

   390 						name       	"ReqProDocumentName"

   391 						value      	"")

   392 					    (object Attribute

   393 						tool       	"RequisitePro"

   394 						name       	"ReqProDocumentGuid"

   395 						value      	"")

   396 					    (object Attribute

   397 						tool       	"RequisitePro"

   398 						name       	"ReqProDocType"

   399 						value      	"")

   400 					    (object Attribute

   401 						tool       	"RequisitePro"

   402 						name       	"ReqProReqType"

   403 						value      	"")

   404 					    (object Attribute

   405 						tool       	"RequisitePro"

   406 						name       	"ReqProRequirementId"

   407 						value      	""))

   408 					quid       	"352F38180276"

   409 					documentation 	

   410 |This will be a stereotype on a usecase. 

   411 |In UML it is a stereotype on a collaboration and that does not exist in Rose.

   412 					

   413 					stereotype 	"use-case realization"

   414 					logical_models 	(list unit_reference_list

   415 					    (object Mechanism @8

   416 						logical_models 	(list unit_reference_list))

   417 					    (object Mechanism @9

   418 						logical_models 	(list unit_reference_list)))

   419 					logical_presentations 	(list unit_reference_list

   420 					    (object ClassDiagram "<Use Case Name> -  Realize Dependencies"

   421 						quid       	"37BC23B801F1"

   422 						title      	"<Use Case Name> -  Realize Dependencies"

   423 						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."

   424 						zoom       	100

   425 						max_height 	28350

   426 						max_width  	21600

   427 						origin_x   	0

   428 						origin_y   	0

   429 						items      	(list diagram_item_list))

   430 					    (object ClassDiagram "<Use Case Name> -  Participating Classes"

   431 						quid       	"37BC23E0036B"

   432 						title      	"<Use Case Name> -  Participating Classes"

   433 						documentation 	"This Diagram shows all participating classes in this Use Case Realization"

   434 						zoom       	100

   435 						max_height 	28350

   436 						max_width  	21600

   437 						origin_x   	0

   438 						origin_y   	0

   439 						items      	(list diagram_item_list))

   440 					    (object InteractionDiagram "<Use Case Name> -  Basic Flow"

   441 						mechanism_ref 	@8

   442 						quid       	"35081E3603A2"

   443 						title      	"<Use Case Name> -  Basic Flow"

   444 						zoom       	100

   445 						max_height 	28350

   446 						max_width  	21600

   447 						origin_x   	0

   448 						origin_y   	0

   449 						items      	(list diagram_item_list))

   450 					    (object InteractionDiagram "<Use Case Name> -  <Flow Type>"

   451 						mechanism_ref 	@9

   452 						quid       	"3540A0B901AE"

   453 						title      	"<Use Case Name> -  <Flow Type>"

   454 						zoom       	100

   455 						max_height 	28350

   456 						max_width  	21600

   457 						origin_x   	0

   458 						origin_y   	0

   459 						items      	(list diagram_item_list)))))

   460 				logical_presentations 	(list unit_reference_list

   461 				    (object ClassDiagram "Realize Dependency"

   462 					quid       	"34E39DA90302"

   463 					title      	"Realize Dependency"

   464 					documentation 	"This diagram shows the Use Case and the Use Case Realization and the realizes dependency between them."

   465 					zoom       	100

   466 					max_height 	28350

   467 					max_width  	21600

   468 					origin_x   	0

   469 					origin_y   	0

   470 					items      	(list diagram_item_list

   471 					    (object NoteView @10

   472 						location   	(704, 144)

   473 						label      	(object ItemLabel

   474 						    Parent_View 	@10

   475 						    location   	(38, 25)

   476 						    fill_color 	13434879

   477 						    nlines     	5

   478 						    max_width  	1296

   479 						    label      	

   480 |

   481 |This diagram shows the Use Case and the Use Case Realization and the realize dependency between them.

   482 						    )

   483 						line_color 	3342489

   484 						fill_color 	13434879

   485 						width      	1356

   486 						height     	250)

   487 					    (object UseCaseView "Use Case View::Use-Case Model::Use Cases::<Use Case Name>::<Use Case Name>" @11

   488 						location   	(1152, 528)

   489 						label      	(object ItemLabel

   490 						    Parent_View 	@11

   491 						    location   	(1152, 666)

   492 						    anchor_loc 	1

   493 						    nlines     	2

   494 						    max_width  	631

   495 						    justify    	0

   496 						    label      	"<Use Case Name>")

   497 						icon_style 	"Icon"

   498 						line_color 	3342489

   499 						fill_color 	13434879

   500 						quidu      	"34E37FB203D4"

   501 						autoResize 	TRUE)

   502 					    (object UseCaseView "Logical View::Design Model::Use-Case Realizations::<Use-Case Name>::<Use-Case Name>" @12

   503 						location   	(608, 960)

   504 						label      	(object ItemLabel

   505 						    Parent_View 	@12

   506 						    location   	(608, 1148)

   507 						    anchor_loc 	1

   508 						    nlines     	2

   509 						    max_width  	651

   510 						    justify    	0

   511 						    label      	"<Use-Case Name>")

   512 						stereotype 	(object ItemLabel

   513 						    Parent_View 	@12

   514 						    location   	(608, 1078)

   515 						    anchor     	10

   516 						    anchor_loc 	1

   517 						    nlines     	1

   518 						    max_width  	434

   519 						    justify    	0

   520 						    label      	"<<use-case realization>>")

   521 						icon       	"use-case realization"

   522 						icon_style 	"Icon"

   523 						line_color 	3342489

   524 						fill_color 	13434879

   525 						quidu      	"352F38180276"

   526 						autoResize 	TRUE)

   527 					    (object AssociationViewNew "$UNNAMED$0" @13

   528 						location   	(876, 741)

   529 						stereotype 	(object SegLabel @14

   530 						    Parent_View 	@13

   531 						    location   	(874, 746)

   532 						    anchor     	10

   533 						    anchor_loc 	1

   534 						    nlines     	1

   535 						    max_width  	450

   536 						    justify    	0

   537 						    label      	"<<realize>>"

   538 						    pctDist    	0.483333

   539 						    height     	5

   540 						    orientation 	1)

   541 						line_color 	3342489

   542 						quidu      	"35409E9D02A8"

   543 						roleview_list 	(list RoleViews

   544 						    (object RoleView "$UNNAMED$1" @15

   545 							Parent_View 	@13

   546 							location   	(236, -539)

   547 							stereotype 	TRUE

   548 							line_color 	3342489

   549 							quidu      	"35409E9E0294"

   550 							client     	@13

   551 							supplier   	@11

   552 							line_style 	0)

   553 						    (object RoleView "$UNNAMED$2" @16

   554 							Parent_View 	@13

   555 							location   	(236, -539)

   556 							stereotype 	TRUE

   557 							line_color 	3342489

   558 							quidu      	"35409E9E0295"

   559 							client     	@13

   560 							supplier   	@12

   561 							line_style 	0))))))))

   562 			logical_presentations 	(list unit_reference_list))

   563 		    (object Class_Category "Process View"

   564 			quid       	"35D227B103C0"

   565 			documentation 	"An architectural view that describes the concurrent aspect of the system: tasks (processes) and their interactions."

   566 			exportControl 	"Public"

   567 			logical_models 	(list unit_reference_list

   568 			    (object Class "<Process Name>"

   569 				quid       	"35DB3C8302D0"

   570 				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>."

   571 				stereotype 	"process")

   572 			    (object Class "<Thread Name>"

   573 				quid       	"35DB3CB002BC"

   574 				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>."

   575 				stereotype 	"thread")

   576 			    (object Association "$UNNAMED$3"

   577 				quid       	"35DB3E72017C"

   578 				roles      	(list role_list

   579 				    (object Role "$UNNAMED$4"

   580 					quid       	"35DB3E73005A"

   581 					supplier   	"Logical View::Design Model::Process View::<Process Name>"

   582 					quidu      	"35DB3C8302D0"

   583 					is_navigable 	TRUE

   584 					is_aggregate 	TRUE)

   585 				    (object Role "$UNNAMED$5"

   586 					quid       	"35DB3E730096"

   587 					supplier   	"Logical View::Design Model::Process View::<Thread Name>"

   588 					quidu      	"35DB3CB002BC"

   589 					Containment 	"By Value"

   590 					is_navigable 	TRUE))))

   591 			logical_presentations 	(list unit_reference_list

   592 			    (object ClassDiagram "Process View"

   593 				quid       	"35DB3C2A02B2"

   594 				title      	"Process View"

   595 				documentation 	"This diagram illustrates the composition of processes and threads, and the mapping of classes onto those processes and threads."

   596 				zoom       	100

   597 				max_height 	28350

   598 				max_width  	21600

   599 				origin_x   	0

   600 				origin_y   	0

   601 				items      	(list diagram_item_list

   602 				    (object ClassView "Class" "Logical View::Design Model::Process View::<Process Name>" @17

   603 					ShowCompartmentStereotypes 	TRUE

   604 					IncludeAttribute 	TRUE

   605 					IncludeOperation 	TRUE

   606 					location   	(288, 464)

   607 					label      	(object ItemLabel

   608 					    Parent_View 	@17

   609 					    location   	(122, 436)

   610 					    fill_color 	13434879

   611 					    nlines     	1

   612 					    max_width  	332

   613 					    justify    	0

   614 					    label      	"<Process Name>")

   615 					stereotype 	(object ItemLabel

   616 					    Parent_View 	@17

   617 					    location   	(122, 389)

   618 					    fill_color 	13434879

   619 					    anchor     	10

   620 					    nlines     	1

   621 					    max_width  	332

   622 					    justify    	0

   623 					    label      	"<<process>>")

   624 					icon_style 	"Icon"

   625 					line_color 	3342489

   626 					fill_color 	13434879

   627 					quidu      	"35DB3C8302D0"

   628 					width      	350

   629 					height     	172

   630 					annotation 	8

   631 					autoResize 	TRUE)

   632 				    (object ClassView "Class" "Logical View::Design Model::Process View::<Thread Name>" @18

   633 					ShowCompartmentStereotypes 	TRUE

   634 					IncludeAttribute 	TRUE

   635 					IncludeOperation 	TRUE

   636 					location   	(896, 464)

   637 					label      	(object ItemLabel

   638 					    Parent_View 	@18

   639 					    location   	(740, 436)

   640 					    fill_color 	13434879

   641 					    nlines     	1

   642 					    max_width  	312

   643 					    justify    	0

   644 					    label      	"<Thread Name>")

   645 					stereotype 	(object ItemLabel

   646 					    Parent_View 	@18

   647 					    location   	(740, 389)

   648 					    fill_color 	13434879

   649 					    anchor     	10

   650 					    nlines     	1

   651 					    max_width  	312

   652 					    justify    	0

   653 					    label      	"<<thread>>")

   654 					icon_style 	"Icon"

   655 					line_color 	3342489

   656 					fill_color 	13434879

   657 					quidu      	"35DB3CB002BC"

   658 					width      	330

   659 					height     	172

   660 					annotation 	8

   661 					autoResize 	TRUE)

   662 				    (object AssociationViewNew "$UNNAMED$3" @19

   663 					location   	(596, 464)

   664 					stereotype 	TRUE

   665 					line_color 	3342489

   666 					quidu      	"35DB3E72017C"

   667 					roleview_list 	(list RoleViews

   668 					    (object RoleView "$UNNAMED$4" @20

   669 						Parent_View 	@19

   670 						location   	(-300, 0)

   671 						stereotype 	TRUE

   672 						line_color 	3342489

   673 						quidu      	"35DB3E73005A"

   674 						client     	@19

   675 						supplier   	@17

   676 						line_style 	0)

   677 					    (object RoleView "$UNNAMED$5" @21

   678 						Parent_View 	@19

   679 						location   	(-300, 0)

   680 						stereotype 	TRUE

   681 						line_color 	3342489

   682 						quidu      	"35DB3E730096"

   683 						client     	@19

   684 						supplier   	@18

   685 						line_style 	0))))))))

   686 		logical_presentations 	(list unit_reference_list

   687 		    (object ClassDiagram "Architecturally Significant Model Elements"

   688 			quid       	"34E36BDE02C6"

   689 			title      	"Architecturally Significant Model Elements"

   690 			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."

   691 			zoom       	100

   692 			max_height 	28350

   693 			max_width  	21600

   694 			origin_x   	0

   695 			origin_y   	0

   696 			items      	(list diagram_item_list

   697 			    (object NoteView @22

   698 				location   	(672, 304)

   699 				label      	(object ItemLabel

   700 				    Parent_View 	@22

   701 				    location   	(28, 19)

   702 				    fill_color 	13434879

   703 				    nlines     	13

   704 				    max_width  	1253

   705 				    label      	

   706 |

   707 |This diagram is just produced for architectural significant packages.

   708 |

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

   710 |

   711 |See Rational Unified Process:

   712 |Activity: Architectural Design

   713 |Step:  Include Architecturally Significant Model Elements in the Logical View 

   714 |

   715 |This will be a part of  the  "Software Architecture Document" :

   716 |- "Logical View" 

   717 |-     "Architecturally Significant Model Elements"

   718 				    )

   719 				line_color 	3342489

   720 				fill_color 	13434879

   721 				width      	1313

   722 				height     	582)

   723 			    (object NoteView @23

   724 				location   	(1696, 160)

   725 				label      	(object ItemLabel

   726 				    Parent_View 	@23

   727 				    location   	(1358, 29)

   728 				    fill_color 	13434879

   729 				    nlines     	5

   730 				    max_width  	640

   731 				    label      	

   732 |Created/modified by: <name>

   733 |Date: <creation/modification date>

   734 |

   735 |Approved by: <name>

   736 |Date: <approval date>

   737 				    )

   738 				line_color 	3342489

   739 				fill_color 	13434879

   740 				width      	700

   741 				height     	275)))

   742 		    (object ClassDiagram "Architecture Overview - Package and Subsystem Layering"

   743 			quid       	"354A9751015E"

   744 			title      	"Architecture Overview - Package and Subsystem Layering"

   745 			documentation 	

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

   747 |

   748 |See Rational Unified Process:

   749 |Activity: Architectural Analysis

   750 |Step: Define the High-Level Organization of Subsystems

   751 |

   752 |Activity: Incorporate Existing Design Elements

   753 |Step: Update the Organization of the Design Model

   754 			

   755 			zoom       	100

   756 			max_height 	28350

   757 			max_width  	21600

   758 			origin_x   	0

   759 			origin_y   	0

   760 			items      	(list diagram_item_list

   761 			    (object NoteView @24

   762 				location   	(576, 256)

   763 				label      	(object ItemLabel

   764 				    Parent_View 	@24

   765 				    location   	(44, 31)

   766 				    fill_color 	13434879

   767 				    nlines     	9

   768 				    max_width  	1028

   769 				    label      	

   770 |This diagram shows the design model layers.

   771 |

   772 |See Rational Unified Process:

   773 |Activity: Architectural Analysis

   774 |Step: Define the High-Level Organization of Subsystems

   775 |

   776 |Activity: Architectural Design

   777 |Step: Define the Low-level Organization of Subsystems

   778 				    )

   779 				line_color 	3342489

   780 				fill_color 	13434879

   781 				width      	1088

   782 				height     	463)

   783 			    (object NoteView @25

   784 				location   	(1520, 176)

   785 				label      	(object ItemLabel

   786 				    Parent_View 	@25

   787 				    location   	(1182, 45)

   788 				    fill_color 	13434879

   789 				    nlines     	5

   790 				    max_width  	640

   791 				    label      	

   792 |Created/modified by: <name>

   793 |Date: <creation/modification date>

   794 |

   795 |Approved by: <name>

   796 |Date: <approval date>

   797 				    )

   798 				line_color 	3342489

   799 				fill_color 	13434879

   800 				width      	700

   801 				height     	275))))))

   802 	logical_presentations 	(list unit_reference_list

   803 	    (object ClassDiagram "Welcome"

   804 		quid       	"3512226B0028"

   805 		title      	"Welcome"

   806 		documentation 	

   807 |Welcome to the Rational Unified Process Frame Work

   808 |

   809 |Purpose of the FrameWork:

   810 |a) provide a good structure for a Rose model

   811 |b) provide a style guide with naming conventions/suggestions

   812 |c) identify a minimal set of diagrams to produce

   813 |d) relate activities in RUP to Rose diagrams

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

   815 |

   816 		

   817 		zoom       	100

   818 		max_height 	28350

   819 		max_width  	21600

   820 		origin_x   	0

   821 		origin_y   	0

   822 		items      	(list diagram_item_list

   823 		    (object NoteView @26

   824 			location   	(768, 384)

   825 			label      	(object ItemLabel

   826 			    Parent_View 	@26

   827 			    location   	(121, 96)

   828 			    fill_color 	13434879

   829 			    nlines     	14

   830 			    max_width  	1259

   831 			    label      	

   832 |Welcome to the Rational Unified Process Rose Model Framework

   833 |

   834 |Purpose of the Framework:

   835 |a) provide a good structure for a Rose model

   836 |b) provide a style guide with naming conventions/suggestions

   837 |c) identify a minimal set of diagrams to produce

   838 |d) relate activities in RUP to Rose diagrams

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

   840 			    )

   841 			line_color 	3342489

   842 			fill_color 	13434879

   843 			width      	1319

   844 			height     	588)

   845 		    (object CategoryView "Logical View::Analysis Model::TZ Compiler" @27

   846 			location   	(1136, 1008)

   847 			label      	(object ItemLabel

   848 			    Parent_View 	@27

   849 			    location   	(951, 924)

   850 			    fill_color 	13434879

   851 			    nlines     	2

   852 			    max_width  	370

   853 			    justify    	0

   854 			    label      	"TZ Compiler")

   855 			icon_style 	"Icon"

   856 			line_color 	3342489

   857 			fill_color 	13434879

   858 			quidu      	"40E569BC024F"

   859 			width      	382

   860 			height     	180)

   861 		    (object CategoryView "Logical View::Analysis Model::LTClasses" @28

   862 			location   	(432, 1008)

   863 			label      	(object ItemLabel

   864 			    Parent_View 	@28

   865 			    location   	(247, 924)

   866 			    fill_color 	13434879

   867 			    nlines     	2

   868 			    max_width  	370

   869 			    justify    	0

   870 			    label      	"LTClasses")

   871 			icon_style 	"Icon"

   872 			line_color 	3342489

   873 			fill_color 	13434879

   874 			quidu      	"40A89DC203B0"

   875 			width      	382

   876 			height     	180)

   877 		    (object CategoryView "Logical View::Analysis Model::Time Zone Database Management" @29

   878 			location   	(1872, 1040)

   879 			label      	(object ItemLabel

   880 			    Parent_View 	@29

   881 			    location   	(1638, 956)

   882 			    fill_color 	13434879

   883 			    nlines     	2

   884 			    max_width  	468

   885 			    justify    	0

   886 			    label      	"Time Zone Database Management")

   887 			icon_style 	"Icon"

   888 			line_color 	3342489

   889 			fill_color 	13434879

   890 			quidu      	"40B1E4A6003A"

   891 			width      	480

   892 			height     	180)

   893 		    (object CategoryView "Logical View::Analysis Model::Business Object Model" @30

   894 			location   	(512, 1408)

   895 			label      	(object ItemLabel

   896 			    Parent_View 	@30

   897 			    location   	(327, 1324)

   898 			    fill_color 	13434879

   899 			    nlines     	2

   900 			    max_width  	370

   901 			    justify    	0

   902 			    label      	"Business Object Model")

   903 			icon_style 	"Icon"

   904 			line_color 	3342489

   905 			fill_color 	13434879

   906 			quidu      	"35B678080064"

   907 			width      	382

   908 			height     	180)

   909 		    (object CategoryView "Logical View::Analysis Model::Local Time Conversion" @31

   910 			location   	(1728, 1392)

   911 			label      	(object ItemLabel

   912 			    Parent_View 	@31

   913 			    location   	(1543, 1308)

   914 			    fill_color 	13434879

   915 			    nlines     	2

   916 			    max_width  	370

   917 			    justify    	0

   918 			    label      	"Local Time Conversion")

   919 			icon_style 	"Icon"

   920 			line_color 	3342489

   921 			fill_color 	13434879

   922 			quidu      	"40B1D43200B7"

   923 			width      	382

   924 			height     	180)

   925 		    (object CategoryView "Logical View::Analysis Model::System Time Management" @32

   926 			location   	(1040, 1392)

   927 			label      	(object ItemLabel

   928 			    Parent_View 	@32

   929 			    location   	(855, 1308)

   930 			    fill_color 	13434879

   931 			    nlines     	2

   932 			    max_width  	370

   933 			    justify    	0

   934 			    label      	"System Time Management")

   935 			icon_style 	"Icon"

   936 			line_color 	3342489

   937 			fill_color 	13434879

   938 			quidu      	"40B1D49203C5"

   939 			width      	382

   940 			height     	180)))))

   941     root_subsystem 	(object SubSystem "Component View"

   942 	quid       	"34DBB4830143"

   943 	documentation 	

   944 |In Rational Unified Process the  "Component View in Rose" is used to organize the implemetation model. 

   945 |

   946 |The Implementaition View in Rational Unified Process

   947 |

   948 |

   949 	

   950 	physical_models 	(list unit_reference_list

   951 	    (object SubSystem "Implementation Model"

   952 		quid       	"35B67C9A0348"

   953 		documentation 	

   954 |The Implementation Model in Rational Unified Process is a collection of components, and the implementation subsystems that contain them.

   955 |

   956 |An architectural view that describes one or several system configurations; the mapping of software components (tasks, modules) to the computing nodes in these configurations.

   957 |

   958 |Defines, executables, dll's, files, subsystems, compilation order etc.

   959 |

   960 |Rational Unified Process:

   961 |Activity: Define the Organization of Subsystems

   962 |

   963 |These diagram will be presented in the  Implementation  View section in the document generated using the SoDA Software Architecture Document.

   964 |

   965 |It is recommended that, in most cases, the mapping should be

   966 |1:1 between design and implementation, that is, for each package in design there is one subsystem in the implementation model.

   967 |

   968 		

   969 		physical_models 	(list unit_reference_list)

   970 		physical_presentations 	(list unit_reference_list

   971 		    (object Module_Diagram "Implementation Model Structure"

   972 			quid       	"34DBB487006E"

   973 			title      	"Implementation Model Structure"

   974 			documentation 	"This diagram presents the organization of the Implementation Model."

   975 			zoom       	100

   976 			max_height 	28350

   977 			max_width  	21600

   978 			origin_x   	0

   979 			origin_y   	0

   980 			items      	(list diagram_item_list

   981 			    (object NoteView @33

   982 				location   	(624, 160)

   983 				label      	(object ItemLabel

   984 				    Parent_View 	@33

   985 				    location   	(21, 26)

   986 				    fill_color 	13434879

   987 				    nlines     	5

   988 				    max_width  	1170

   989 				    label      	

   990 |

   991 |RationalUnified Process:

   992 |Activity: Structure the implementation model

   993 |Step: Create the Initial Implementation Model Structure

   994 				    )

   995 				line_color 	3342489

   996 				fill_color 	13434879

   997 				width      	1230

   998 				height     	281)))))

   999 	    (object SubSystem "Components Analysis"

  1000 		is_unit    	TRUE

  1001 		is_loaded  	FALSE

  1002 		file_name  	"M:\\DST\\analysis\\Components.sub"

  1003 		quid       	"40D969B300E0"))

  1004 	physical_presentations 	(list unit_reference_list

  1005 	    (object Module_Diagram "Main"

  1006 		quid       	"35C6339B029E"

  1007 		title      	"Main"

  1008 		documentation 	"This diagram, required by Rose, simply provides a way of navigating to the Implementation Model."

  1009 		zoom       	100

  1010 		max_height 	28350

  1011 		max_width  	21600

  1012 		origin_x   	0

  1013 		origin_y   	0

  1014 		items      	(list diagram_item_list

  1015 		    (object SubSysView "Component View::Implementation Model" @34

  1016 			location   	(736, 800)

  1017 			label      	(object ItemLabel

  1018 			    Parent_View 	@34

  1019 			    location   	(552, 713)

  1020 			    fill_color 	13434879

  1021 			    nlines     	2

  1022 			    max_width  	368

  1023 			    justify    	0

  1024 			    label      	"Implementation Model")

  1025 			icon_style 	"Icon"

  1026 			line_color 	3342489

  1027 			fill_color 	13434879

  1028 			quidu      	"35B67C9A0348"

  1029 			width      	381

  1030 			height     	187)

  1031 		    (object SubSysView "Component View::Components Analysis" @35

  1032 			location   	(1408, 1392)

  1033 			label      	(object ItemLabel

  1034 			    Parent_View 	@35

  1035 			    location   	(1264, 1323)

  1036 			    fill_color 	13434879

  1037 			    nlines     	2

  1038 			    max_width  	288

  1039 			    justify    	0

  1040 			    label      	"Components Analysis")

  1041 			icon_style 	"Icon"

  1042 			line_color 	3342489

  1043 			fill_color 	13434879

  1044 			quidu      	"40D969B300E0"

  1045 			width      	300

  1046 			height     	150)))))

  1047     process_structure 	(object Processes

  1048 	quid       	"34DBB4830144"

  1049 	ProcsNDevs 	(list

  1050 	    (object Processor "<processor name>"

  1051 		quid       	"34DBBD4300B4"

  1052 		documentation 	"This node provides <enter a short description here of the functionality and capability of the node>."

  1053 		connections 	(list connection_list

  1054 		    (object Connection_Relationship

  1055 			quid       	"34DBBD4B008C"

  1056 			supplier   	"<device name>"

  1057 			quidu      	"34DBBD47019A"

  1058 			supplier_is_device 	TRUE))

  1059 		characteristics 	""

  1060 		scheduling 	"Preemptive"

  1061 		processes  	(list processes

  1062 		    (object Process "<process name>"

  1063 			quid       	"35DB411001D6"

  1064 			documentation 	"This process corresponds to the process with the same name in the Logical View::Process Model."

  1065 			stereotype 	"process"

  1066 			priority   	"")

  1067 		    (object Process "<thread name>"

  1068 			quid       	"35DB41720348"

  1069 			documentation 	"This process corresponds to the thread with the same name in the Logical View::Process Model."

  1070 			stereotype 	"thread"

  1071 			priority   	"")))

  1072 	    (object Device "<device name>"

  1073 		quid       	"34DBBD47019A"

  1074 		documentation 	"This device provides <enter a short description of the capability the device provides> for the system."

  1075 		characteristics 	"")

  1076 	    (object Process_Diagram "Deployment View"

  1077 		quid       	"34DBB4830146"

  1078 		title      	"Deployment View"

  1079 		documentation 	

  1080 |The Deployment View in Rational Unified Process

  1081 |

  1082 |Defines the typical physical network configurations, including those typically used by end users, as well as special configurations used for development and test.

  1083 |

  1084 |See Rational Unified Process:

  1085 |Activity: Describe Distribution

  1086 |

  1087 |This diagram will be a part of  the SoDA template-generated Software Architecture Document under the "Deployment  View" .

  1088 		

  1089 		zoom       	100

  1090 		max_height 	28350

  1091 		max_width  	21600

  1092 		origin_x   	0

  1093 		origin_y   	0

  1094 		items      	(list diagram_item_list

  1095 		    (object ProcessorView "<processor name>" @36

  1096 			location   	(512, 1056)

  1097 			label      	(object ItemLabel

  1098 			    Parent_View 	@36

  1099 			    location   	(276, 900)

  1100 			    nlines     	2

  1101 			    max_width  	400

  1102 			    justify    	0

  1103 			    label      	"<processor name>")

  1104 			icon_style 	"Label"

  1105 			quidu      	"34DBBD4300B4"

  1106 			width      	475

  1107 			height     	381

  1108 			annotation 	3)

  1109 		    (object DeviceView "<device name>" @37

  1110 			location   	(1040, 1056)

  1111 			label      	(object ItemLabel

  1112 			    Parent_View 	@37

  1113 			    location   	(867, 950)

  1114 			    nlines     	2

  1115 			    max_width  	275

  1116 			    justify    	0

  1117 			    label      	"<device name>")

  1118 			icon_style 	"Icon"

  1119 			quidu      	"34DBBD47019A"

  1120 			width      	350

  1121 			height     	282

  1122 			annotation 	0)

  1123 		    (object ConnectionView "" @38

  1124 			stereotype 	TRUE

  1125 			quidu      	"34DBBD4B008C"

  1126 			client     	@36

  1127 			supplier   	@37

  1128 			line_style 	0)

  1129 		    (object NoteView @39

  1130 			location   	(816, 304)

  1131 			label      	(object ItemLabel

  1132 			    Parent_View 	@39

  1133 			    location   	(38, 29)

  1134 			    fill_color 	13434879