SE 430: Object Oriented Modeling
Assignments

There are seven (7) assignments, a critique and a term project.

All assignments must be submitted electronically through Desire2Learn (D2L) and are due at 11:59 pm. CT. The documents may be in Microsoft Word (.doc) format, HTML, or Adobe PDF. Any included figures must be embedded directly within the document, not bundled separately. Your submission must be a single file.

Written solutions to homework assignments and exams will be posted the following day on D2L.

Please note well: all assignments and related material are copyrighted material and may not be used for purposes other than solving these assignments. They may NOT by copied or provided to other students.

Assignments and due dates:

September 2016 Su Mo Tu We Th Fr Sa              1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

October 2016 Su Mo Tu We Th Fr Sa                    1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

November 2016 Su Mo Tu We Th Fr Sa        1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

1. Assignment 1 (Due September 22) Visitor Information Subsystem (Mobile Tour Guide) Requirements
2. Assignment 2 (Due September 29) Visitor Information Subsystem (Mobile Tour Guide): Subsystem Use Cases and Use Case Supplemental Diagrams
3. Assignment 3 (Due October 6) Visitor Information Subsystem (Mobile Tour Guide): Domain Model
4. Assignment 4 (Due October 20) Mixed Information Display – CRC Cards, Objects and Operations, and Viewer State chart
5. Assignment 5 (Due October 27 Museum Automation Subsystem Design Scenario and CRC Cards
6. Assignment 6 (Due November 3) Museum Automation Subsystem – Revised Design Scenario and CRC Cards, and Sequence
7. Assignment 7 (Due November 10) Museum Automation Visitor Information Subsystem Visitor Audit Tracking – Design Class Diagram
8. Critique (Due November 17)

Team project assignments: 

1. Team Project – Preliminary Description (Due October 20) Team Project – Preliminary Description
2. Team Project (Due November 17 COB)

Midterm Examination (October 8-12)  Midterm Examination will be using Desire2Learn (https://courses.depaul.edu/).  See important information about Taking Quizzes on-line
Final Exam: (November 12-18) Final Examination will be using Desire2Learn (https://courses.depaul.edu/).  See important information about Taking Quizzes on-line

Assignments (and deliverables):

Problem Statement: The assignments will be based on a common domain problem (The Museum Automation Problem). The information needed to assist in working on the assignments, Museum Automation Problem Description, will be posted on the class pages. Be sure you have read  this and the associated Mobile Guide paper and understand them.

The details of each assignment will be found in the links below, together with information about the deliverables. The material provided below is just a summary of the assignment.

1. Assignment 1 (Due  September 22) Visitor Information Subsystem (Mobile Tour Guide) Requirements
   Produce a brief document, approximately five (5) pages in length, not including the cover page, that describes the Visitor Information Subsystem in greater detail than it is described in the overall project statement.
   You may use the Assignment 1 skeleton MS Word template for your document
   • Deliverables:
   • Cover page. Include assignment name, your name, and submission date for the document.
   • Project Overview Statement.
   • List of users for the subsystem.
   • Subsystem features list.
   • Subsystem Context Description.
   • Supplementary Requirements.
   • Glossary.
   • Additional references (optional).
2. Assignment 2 (Due September 29) Visitor Information Subsystem (Mobile Tour Guide): Subsystem Use Cases and Use Case Supplemental Diagrams
   Part I: Produce the use case model for the Visitor Information subsystem [List of all actors, their goals and objectives, High level descriptions of all use cases, expanded Use Case Description of major use case, Use Case Diagram (all use cases - together), Rank order of the use cases, Basis of the rank order ] Part II: Use case supplemental diagram. Produce a system sequence diagram for the Visitor Information subsystem use case included at the end of this assignment.
• Deliverables:
• Cover page.
• Identification of use cases.
• Use case diagram.
• Detailed use case.
• System Sequence Diagram
• Glossary
3. Assignment 3 (Due October 6) Visitor Information Subsystem (Mobile Tour Guide): Domain Model
   Domain model. Produce a domain model diagram for the Visitor Information Subsystem.
• Deliverables
• Cover page.
• Domain model diagram.
• Glossary.
4. Assignment 4 (Due October 20) Mixed Information Display – CRC Cards, Objects and Operations, and Viewer State chart
   • Create a CRC card for each object in the Mixed Information Display design 
   • Create an operation contract for each operation shown in the sequence diagram
   • Create a state chart for the behavior of the Viewer object 
   • Deliverables
   • Cover page. Include assignment name, your name, and submission date for the document.
   • Mixed Information Display Objects and Operations. Use the templates provided  to document the CRC cards for each object and the operation contracts for each operation. The start of the CRC card for the Browser object is provided for you as an example, as is the complete operation contract for the whereIs() method of the Directory object.
   • Viewer State chart.  The state chart should include all the state information described in the Description section, above, and should follow the UML state chart conventions.
     
5. Assignment 5 (Due October 27) Museum Automation Visitor Information Subsystem Visitor Audit Tracking – Design Scenario and CRC Cards
   Create some design artifacts for the Visitor Information System Visitor Audit Tracking feature. 
   • Design the Visitor Audit Tracking feature. 
   • Develop a design scenario for this functionality.
   • Create CRC cards for this design scenario.
   • Deliverables
   • Cover page. Include assignment name, your name, and submission date for the document.
   • Design scenario process description. In a bulleted narrative list, describe the process used in working through the problem. The intent of this task is to help you capture and examine the process you use to uncover abstractions, work out collaborations, and assign responsibilities. Be sure to mention any use of patterns or application of design principles such as coupling and cohesion, or any other trick or method you use.
   • Documentation of CRC cards. Using the format provided in the lecture notes from Class 4 or from Assignment 6, document the CRC cards you create as part of the design scenario process for the detailed use case.
   • Glossary. Produce a glossary consisting only of those objects that are documented in your CRC cards. Do not include the complete glossary of the whole subsystem!
     
6. Assignment 6 (Due November 3) Museum Automation Visitor Information Subsystem Visitor Audit Tracking – Revised Design Scenario and CRC Cards, and Sequence Diagrams
   Revisit the Visitor Audit Tracking (VAT) feature design that you created in the last assignment and apply new insights you've gotten from our discussions of the problem at the beginning of class [lecture 8] and from the detailed walk through of a design scenario during lecture. Revise your design scenario and CRC cards, then create two sequence diagrams detailing the interactions among the objects in the realization.
   • Deliverables
   • Cover page. Include assignment name, your name, and submission date for the document.
   • Design scenario process description with annotated revisions. 
   • Documentation of CRC cards with annotated revisions. 
   • Use case realization diagrams. Provide two different diagrams to illustrate the VGD and CAM components of the scenario.
   • Glossary with annotated revisions.
7. Assignment 7 (Due November 10) Museum Automation Visitor Information Subsystem Visitor Audit Tracking – Design Class Diagram
   Flesh out the conceptual model and make it into a full fledged class diagram.
   • Deliverables
   • Cover page. Include assignment name, your name, and submission date for the document.
   • Design class diagram. You should produce as complete a design class diagram for the Visitor Audit Tracking feature as possible. Include essential attributes and methods for each class. You need not identify every attribute and method! Identify associations, navigation, and dependencies, as well as any additional class relationships you might find useful: generalization, aggregation, implements, and composition. You should consider this document as the starting point for an actual implementation effort. Therefore, carefully examine your earlier work—interaction diagrams and CRC cards—to ensure that you have as complete a design class diagram as possible.
   • Glossary. Include a glossary entry for every class on your design class diagram. The glossary must contain brief definitions or descriptions of each class. You do not need to provide detailed class specifications as we discussed in class.
8. Critique (Due November 17)
   Students must write and submit a brief critique of their own work on the assignments after reviewing the sample solution(s). The critique is due at the end of the term. The assignment critiques (taken together) will count as one homework assignment.

Term Project (Due November 17 COB)

Every member of the class will submit a term project. This will be in collaboration with other class members. See the Team Project document for discussion on the subject matter of the project. See below for details for the first submission. See the Team Project Report for discussion of Contents and Requirements. You will also need to rate your team – follow the attached instructions and submit the ratings by email by November 17.

1. Team Project – Preliminary Description (Due October 20) Team Project – Preliminary Description
   Provide a brief description of the product you'll be using in your final project and the use case(s) you'll be examining in detail. Provide a short description of the product, along with a short description of the use case(s) you have identified for the final project.
   • Deliverables
   • Cover page. Include assignment name, student name, and submission date for the document.
   • Brief product description.
   • Brief description of use case(s).

Policies:

• NEVER send assignments to me in email. Always use the D2L submission procedure.
• If an assignment is submitted to D2L after the server stops accepting assignments, it is late, regardless of the real, wall, time. You should assume that the server will not be accurate about time, and should submit earlier versions of work, and also submit your last version significantly in advance of the closing time.
• If an assignment is not in an acceptable, readable, format it will not be graded. Check your carriage returns. Check your file extensions. Check your protections.
• In general, I do not accept late assignments except for serious extenuating circumstances. Here is the procedure for late assignments:
  • Notify me immediately when you plan to submit work late, with explanation. Get my approval.
  • It is in your interest to submit partially completed work to D2L on time. Just make it clear, at the top of your text, that you want partial credit and that you are not finished.
  • If you complete an assignment late, send me a brief email note that you have completed a late assignment. Send the assignment in email. Do NOT change your assignment in D2L after this time. I will use your email as a timestamp for when you completed the assignment, and will feel free to grade it at some time after that point. 
  • The sooner you complete the assignment, the more credit you might get, in general.