diff -r 924385140d98 -r c2c61fdca848 tzservices/tzserver/analysis/DAYLIGHT SAVINGS ANALYSIS.md~ --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tzservices/tzserver/analysis/DAYLIGHT SAVINGS ANALYSIS.md~ Wed Sep 01 12:24:48 2010 +0100 @@ -0,0 +1,6210 @@ + +(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. +| +| + + 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: +|Date: +| +|Approved by: +|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" + 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 "" + quid "34E36BB7017C" + documentation +|