I need an example UML diagram following the GRASP controller pattern with this i

Question

I need an example UML diagram following the GRASP controller pattern with this information. It needs to have these guidlines followed. It can be sketched by hand. Im just looking for an example with some of the information so I know where to go from there. Thank you

Correct representation of the business domain

Proper UML (also, do not use Aggregation in the DCD)

Appropriate use of the GRASP patterns (be sure to use the controller pattern)

Consistency between Sequence Diagrams and Class Diagrams

At the beginning of the semester instructors of EGR 405 will setup their section(s) in the system. After authenticating, the instructor will indicate the academic year and semester for their section, one section at a time if they have more than one section. The Instructor will need to indicate the day of the week that their section will meet and the date of the first meeting and last meeting. The system will then fill in each meeting date. The Instructor can than remove any meeting dates that are not necessary. The Instructor needs to indicate how many presentation slots will be available. The Instructor can set a default value for the number of slots per meeting date and then once the schedule is created the Instructor can then edit individual meeting dates to adjust the default number of presentation slots per night. The number of presentation slots must be between 1 and 5, no other number is acceptable. Finally, the Instructor will need to indicate whether the schedule is ready to be made available to students or not. This is called “publishing” the schedule. Publishing the schedule will make it available to students to sign up for presentation slots. By default, it will be in “draft” mode.

Explanation / Answer

The different patterns and principles used in GRASP are: controller, creator, indirection, information expert, high cohesion, low coupling, polymorphism, protected variations, and pure fabrication. All these patterns answer some software problem, and these problems are common to almost every software development project. These techniques have not been invented to create new ways of working, but to better document and standardize old, tried-and-tested programming principles in object-oriented design.

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.