Newest Viewed Downloaded

CD Solution for createNewAssignment:Assignment 1: create(title, description, dueDate, authors) 1.1: set (t=title,  desc=description, due=dueDate) :Assignment Handler creatNewAssignment (title, description, dueDate, authors) :Instructors [i] List<instructor> 2: create (authors)  2.1*: name = author  by Creator & Expert by Creator by Controller

CD Solution for createNewAssignment

:Assignment 1: create(title, description, dueDate, authors) 1.1: set (t=title,  desc=description, due=dueDate) :Assignment Handler creatNewAssignment (title, description, dueDate, authors) :Instructors [i] List 2: create (authors)  2.1*: name = author  by Creator & Expert by Creator by Controller Not a façade … too complex UC controller is what works for the role of Assignment Handler ‹#›

Design Class Diagram

* Assignment title… description... dueDate… getInstructor() … Instructor name... assigns() edits() … Assignment Handler … createAssignment() createInstructor() … thisAssignment author * ‹#›

CD Solution for createNewRubric

:Rubric 1: create(assignment, pointsAvailable, initialReqts, authors) 1.1: reqts=initialReqts  1.2: pts=pointsAvailable :Assignment Handler creatNewRubric (assignment, pointsAvailable, initialReqts, authors) :Instructors [i] List 2: create (authors)  2.1*: name = author  by Creator & Expert by Creator by Controller ‹#›

Design Class Diagram

Instructor name... … Rubric requirements… pointsAvailable... addNewReqt() … Assignment Handler … createRubric() createInstructor() … thisRubric author * * ‹#›

CD Solution for addRequirement

:Rubric 1: append(reqt) :Assignment Handler addRequirement (rubric, reqt) :Rubric 1: append(reqt)  By Expert & Cohesion by Expert & Cohesion by Controller addRequirement (rubric, reqt) Two viable and largely equal options. First is to use a controller to handle the add. Advantage is could aggregate adding of requirements with other :Rubric elements. Disadvantage is increased coupling. Second is to go direct to :rubric that contains the requirements, but the utility of a controller handling the interface is lost. ‹#›

Design Class Diagram

Rubric requirements… pointsAvailable... addNewReqt() … Assignment Handler … addRequirement() … addedReqt * ‹#›

ungraded

* currentSubmission Assignment title… description... dueDate… getInstructor() getRubric() … Instructor name... assigns() edits() … Grader name... grades() edits() addReqt() … Rubric requirements… pointsAvailable... addNewReqt() collectsFdBack() evaluates() … Assignment Handler … createAssignment() ? createRubric() createInstructor() importSubmissions() getSubmission() … Submission submissionDate… studentAnswers… grade… getInstructor() getassignment() … created Assignment thisRubric current Assignment * thisRubric author * * 1..* 0..* 1 1 grader thisRubric 0..* evaluatedAssignment 1 1 FeedbackItem title… points… comment… thisItem {map} collection * 1 1 1 1 * * ‹#›

Showing 1 - 7 of 7 items Details

Name: 
possibleSession18solut...
Author: 
Alex Lo
Company: 
N/A
Description: 
CD Solution for createNewAssignment:Assignment 1: create(title, description, dueDate, authors) 1.1: set (t=title,  desc=description, due=dueDate) :Assignment Handler creatNewAssignment (title, description, dueDate, authors) :Instructors [i] List<instructor> 2: create (authors)  2.1*: name = author  by Creator & Expert by Creator by Controller
Tags: 
assign | author | rubric | instructor | handler | name | pointsavail | titl
Created: 
1/10/2012 2:30:53 AM
Slides: 
7
Views: 
0
Downloads: 
0
Rating: 
0


> Comment



Share this presentation
|

Comments

Share this presentation:

|
Sitemap