Visual Paradigm: First-Cut Design Class Diagram Creation

Task 1: Draw the First-Cut Design Class Diagrams

Page 2 of 6 In Visual Paradigm: Make a copy of your existing A4_ VPRU_TeamID.vpp (First-cut Design Class Diagram) to A5_ VPRU_TeamID.vpp. A5 Tips: a) In Visual Paradigm (VP), you can reuse methods in multiple UML diagrams using the method type “Call”; you need to explicitly create operations. b) Each class in the Design Class Diagram (DCD) should each have 3 parts: • a stereotype designation (in VP, use either <> or <>) and all class names must be in Pascal notation; • fully-defined attributes (camel notation) with visibility and data types; • VP Tip: Under Window | Project Options, set Data Type to C# (Language in use); add DateTime and other C# data types, as needed. • fully-defined method signatures (camel notation) with parameters and visibility • to reduce clutter, do not specify method parameter data types (e.g., int), especially if they match the attribute data types. • you can use data transfer object (DTO) pattern to simplify multiple method parameters (Hint: use a UML note to define the DTO). Note: Do not include default constructors, getter/setter methods, select-insert- update-delete operations, as they are implied c) In the DSD diagram, display all the different types of classes (except <> class), as robustness analysis icons. _____________________________________________________________________ Task 1: Draw the First-cut Design Class Diagrams In the new A5_VPRU_TeamID.vpp file, create a new VPRU Domain Layer class diagram • This is where you will add new <> and <> classes drag and drop these domain classes to your new VPRU Domain Layer class diagram • Resort, RoomType, VacationPackage (from RRS) • Student, VPBooking, VPBookingGuest (from VBS) Result: The associations and multiplicities will automatically appear. Page 3 of 6 • You must have a minimum of six (6) domain classes as enumerated above. To avoid clutter, do not show the other classes (e.g., CustomerAccount) that are not used in the use cases mentioned in Task 2 below. rename domain classes and verify associations/ multiplicities, as needed set the stereotype of these domain classes to <> type Add and/or update class attributes (visibility, data type), and any other modeling elements, as needed. create a new VPRU View Layer class diagram • This is where you will add new <> classes create a new VPRU Data Access Layer class diagram • add a new VPBookingContext <> clas Page 2 of 6 In Visual Paradigm: Make a copy of your existing A4_ VPRU_TeamID.vpp (First-cut Design Class Diagram) to A5_ VPRU_TeamID.vpp. A5 Tips: a) In Visual Paradigm (VP), you can reuse methods in multiple UML diagrams using the method type “Call”; you need to explicitly create operations. b) Each class in the Design Class Diagram (DCD) should each have 3 parts: • a stereotype designation (in VP, use either <> or <>) and all class names must be in Pascal notation; • fully-defined attributes (camel notation) with visibility and data types; • VP Tip: Under Window | Project Options, set Data Type to C# (Language in use); add DateTime and other C# data types, as needed. • fully-defined method signatures (camel notation) with parameters and visibility • to reduce clutter, do not specify method parameter data types (e.g., int), especially if they match the attribute data types. • you can use data transfer object (DTO) pattern to simplify multiple method parameters (Hint: use a UML note to define the DTO). Note: Do not include default constructors, getter/setter methods, select-insert- update-delete operations, as they are implied c) In the DSD diagram, display all the different types of classes (except <> class), as robustness analysis icons. _____________________________________________________________________ Task 1: Draw the First-cut Design Class Diagrams In the new A5_VPRU_TeamID.vpp file, create a new VPRU Domain Layer class diagram • This is where you will add new <> and <> classes drag and drop these domain classes to your new VPRU Domain Layer class diagram • Resort, RoomType, VacationPackage (from RRS) • Student, VPBooking, VPBookingGuest (from VBS) Result: The associations and multiplicities will automatically appear. Page 3 of 6 • You must have a minimum of six (6) domain classes as enumerated above. To avoid clutter, do not show the other classes (e.g., CustomerAccount) that are not used in the use cases mentioned in Task 2 below. rename domain classes and verify associations/ multiplicities, as needed set the stereotype of these domain classes to <> type Add and/or update class attributes (visibility, data type), and any other modeling elements, as needed. create a new VPRU View Layer class diagram • This is where you will add new <> classes create a new VPRU Data Access Layer class diagram • add a new VPBookingContext <> clas