(object Petal

    version    	43

    _written   	"Rose 6.5.9232.10"

    charSet    	0)

(object Design "Logical View"

    is_unit    	TRUE

    is_loaded  	TRUE

    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)

				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)

				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"

		is_unit    	TRUE

		is_loaded  	FALSE

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

		quid       	"35B677F4010E"))

	logical_presentations 	(list unit_reference_list

	    (object UseCaseDiagram "Main"

		quid       	"35C6339B029F"

		title      	"Main"

		documentation 	

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

		zoom       	90

		max_height 	28350

		max_width  	21600

		origin_x   	0

		origin_y   	0

		items      	(list diagram_item_list

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

			location   	(400, 864)

			font       	(object Font

			    size       	10)

			label      	(object ItemLabel

			    Parent_View 	@3

			    location   	(256, 780)

			    fill_color 	13434879

			    nlines     	2

			    max_width  	288

			    justify    	0

			    label      	"Use-Case Model")

			icon_style 	"Icon"

			line_color 	3342489

			fill_color 	13434879

			quidu      	"35B677F4010E"

			width      	300

			height     	180)

		    (object NoteView @4

			location   	(1168, 592)

			font       	(object Font

			    size       	10)

			label      	(object ItemLabel

			    Parent_View 	@4

			    location   	(941, 390)

			    fill_color 	13434879

			    nlines     	9

			    max_width  	419

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

			line_color 	3342489

			fill_color 	13434879

			width      	479

			height     	416)

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

			location   	(384, 320)

			label      	(object ItemLabel

			    Parent_View 	@5

			    location   	(189, 229)

			    fill_color 	13434879

			    nlines     	2

			    max_width  	390

			    justify    	0

			    label      	"Business Use-Case Model")

			icon_style 	"Icon"

			line_color 	3342489

			fill_color 	13434879

			quidu      	"35B677D701B8"

			width      	403

			height     	194)

		    (object ImportView "" @6

			stereotype 	TRUE

			line_color 	3342489

			quidu      	"35C633DA030C"

			client     	@3

			supplier   	@5

			line_style 	0)

		    (object AttachView "" @7

			stereotype 	TRUE

			line_color 	3342489

			client     	@6

			supplier   	@4

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

		    (object Class_Category "Business Object Model"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"35B678080064")

		    (object Class_Category "TZ Compiler"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40E569BC024F")

		    (object Class_Category "LTClasses"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40A89DC203B0")

		    (object Class_Category "Time Zone Database Management"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40B1E4A6003A")

		    (object Class_Category "Local Time Conversion"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40B1D43200B7")

		    (object Class_Category "System Time Management"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40B1D49203C5")

		    (object Class_Category "TZClasses"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40F3CEAF0324")

		    (object Class_Category "BClasses"

			is_unit    	TRUE

			is_loaded  	FALSE

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

			quid       	"40F3CFB10172"))

		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$0"

				quid       	"35409E9D02A8"

				stereotype 	"realize"

				roles      	(list role_list

				    (object Role "$UNNAMED$1"

					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$2"

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

					attributes 	(list Attribute_Set

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProProjectPath"

						value      	"")

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProProjectGuid"

						value      	"")

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProDocumentName"

						value      	"")

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProDocumentGuid"

						value      	"")

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProDocType"

						value      	"")

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProReqType"

						value      	"")

					    (object Attribute

						tool       	"RequisitePro"

						name       	"ReqProRequirementId"

						value      	""))

					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 @8

						logical_models 	(list unit_reference_list))

					    (object Mechanism @9

						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 	@8

						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 	@9

						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 @10

						location   	(704, 144)

						label      	(object ItemLabel

						    Parent_View 	@10

						    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>" @11

						location   	(1152, 528)

						label      	(object ItemLabel

						    Parent_View 	@11

						    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>" @12

						location   	(608, 960)

						label      	(object ItemLabel

						    Parent_View 	@12

						    location   	(608, 1148)

						    anchor_loc 	1

						    nlines     	2

						    max_width  	651

						    justify    	0

						    label      	"<Use-Case Name>")

						stereotype 	(object ItemLabel

						    Parent_View 	@12

						    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$0" @13

						location   	(876, 741)