.Open Assigned field work . Pairing Ideally each assignment will be done by a pair of students working together and handing in a single piece of work with both names on it. I will accept work form one person. I will not accept work from three! I expect pairs to change as we move through the project. . Plan The work is assigned on a Wednesday so you have more 4 days to do it. This is timeboxed: hand in what you have when it is due. I will ask one member of each pair to give a short verbal report as they hand in the work. I will review and comment on the work. I will redistribute copies of the marked up work to form the basis of the next assignment. However, the grades will be posted to the web site rather than written on the work. . Schedule of Assigneed Field Work .Table Id# Date due Topic Chapters .Row $W3 M Jan 12 Introduction 1 .Row - M Jan 19 MLK HOLIDAY - .Row $W6 M Jan 26 Inception 4, 5, 6, 7 .Row $W8 M Feb 2 Elaboration 1 Requirements 8, 9, 10, 11, 12 .Row $W10 M Feb 9 Elaboration 1 Design 14,15, 16, 17, 18,19, 20 .Row $W12 M Feb 16 Elaboration 2 Use-cases 21, 22, 23 .Row $W14 M Feb 23 Elaboration 3 Generalization & States 24, 25, 26, 27, 28,29 .Row $W16 M Mar 1 Elaboration 3 Architecture 30, 31 .Row $W18 M Mar 8 Elaboration 3 Persistence? 32, 33, 34 .Row $W20 M Mar 15 Elaboration 3 Deployment 38 .Close.Table . Details (may change) (W3): Introduction. Given: documents analyzing the Free Interface to School (FIS) and the example on page 8 of the text. Goals: A brief use case found in FIS + a simple partial domain model for that use case. Hint: pick a simple example of how a Student gets something that they want from FIS. Grading: 4 points for use case, 4 points for domain model, 2 points if they fit together. Total 10 points. Due: Jan 12. (W6): Inception. .Set Given: .List Vision (should have been done in class) .See http://www/dick/cs375/vision.html List of Use Cases .See http://www/dick/cs375/FIS1.html Initial Domain Model .See http://www/dick/cs375/FISDom1.gif .Close.List Goals: .List Use Cases: Brief descriptions of all but one use cases and a fully dressed description of one use case (Chapter 6). -- 4 points Use Case Diagram (Section 6.13) -- 2 point Supplementary Requirements (section 7.2 .. 7.3) -- 3 points Glossary/Data Dictionary (section 7.6 .. 7.7) -- 1 point .Closed.List Hints: Chapter 6 and 7. Process: Suggest three meetings in pairs. (1) review previous work and revise/correct/consolidate (2) draft documents. (3) review and improve documents. Total 10 points. Due: Jan 26. .Close.Set (W8): Elaboration 1 Requirements. .Set Given: collection the requirements from previous work. Goals: revised requirements, an SSD of one use case, and a domain model. Process: .List Review previous work, revise, and keep. Select one fully dressed use case and draw an SSD of the main success scenario. Draw a domain model capturing the classes, associations, attributes to support `all` your revised requirements. Check the model vs the use cases and SSD. Hand in: 1. use case diagram(1 pt), 2. SSD(4 points), one domain model(4 points). .Close.List Hints: Make sure that the models fit together. (1 point) Also -- you can pick a use case with a small SSD without losing points. Grading: Total 10 points. Mainly for technical correctness of diagrams. Due: Feb 2. .Close.Set (W10): Elaboration 1 Design. .Set Given: collection of SSDs, domain model, and use case diagram from previous work. Goals: A collaboration diagram of a given use case + a design model for that use case. Suggested Process: In pairs, if possible. .List Review previous work. Revise and keep. Select one SSD. Draw a collaboration diagram showing a set of objects and messages, following the GRASP guidelines. Add comments naming the GRASP you used. Draw a design model to support your collaboration. Hand in: 1. collaboration(3 pt), 2. Design model(3 points), 3. GRASP (2 points). Fit (2 points) .Close.List Hints: You can pick a use case with a small SSD without losing points. Grading: Total 10 points. For technical correctness of diagrams and using GRASP. Due: Feb 9. Optional: Some code+tests for a simple but vital use case. .Close.Set (W12): Elaboration 2 Use Cases. .Set Given: Work done so far. Process: Review work, and examine use-cases. Goal: Show how to use include and extend in a use case diagram at least once each. Grading: Total 10 points, split into 5 for include and 5 for extend, further divided into 3 points for correct notation, and 2 points for the result making sense. Due: during class Feb 16. .Close.Set (W14): Elaboration 3 Generalization & States. .Set Given: Work done so far. Goals: Refine and improve the use case and domain model using techniques in chapter 25 through to 29 inclusive. Optional: update and test code. Hints: .List Can generalization improve the domain model? Can you refine the domain model further using other techniques? Any new use cases or SSDs to add? Draw a state chart of something! .Close.List Deliverables: .List A domain model with at least one new relationship and a comment either rejecting it or proposing it and giving a reason. (5 points) A state chart of something in the FIS project. (5 points) .Close.List Grading: Total 10 points. In each change, 3 points for correct notation and 2 points for giving a good reasone for keeping or rejecting the changes. Due: Feb 23. .Close.Set (W16): Elaboration 3 Logical Architecture for FIS. .Set Given: Work done so far. Goals: Define an architecture(Ch 30) and packages(Ch 31). Optional: does your code need refactoring? Hints: Use the book and think. Deliverables: .Net (1) Package diagram with dependencies. (2) Packages should contain a sample class or two. (3) A short note expressing one doubt that you have about your logical architecture. .Close.Net Grading: Total 10 points = notation 7 + ideas 3. Due: Mar 1. .Close.Set (W18): Elaboration 3 Persistence. To be done by either one or more people working together and handing in one piece of work with all names. .Set Given: Work done so far. Goals: Complete architectural analysis and look for useful patterns. Is there any persistent data? If so how might you handle it (no more than one paragraph)? (Ch 32, 33, 34). Hints: .See http://www/dick/cs375/w18.txt Deliverables: (1)A set of packages each with a design class diagram. (2) a list of persistent data types. (3) A paragraph suggesting a simple way to handle this data. Grading: Design 6 points, persistent data 2 points, suggestion 2 points. Total 10 points. Due: Mar 8. .Close.Set (W20): Elaboration 3 Deployment. To be done by a group of people working together and handing in one piece of work with names of all contributors. .Set Given: Work done so far. Goal: Improve grasp of software components and their deployment onto hardware nodes. Deliverables: One diagram showing a set of components (software/code/data) deployed onto nodes (hardware) and showing communication and dependencies. For each component a brief description of its content, eg classes, data, programs. Hints: Ch 38 and hand outs. Grading: Total 10 points = 6 points for correct use of UML + 4 points for choice of components, nodes, etc, ...(subjective and holistic). Due: Mar 15 .Close.Set .Close Assigned field work