CS 2212 -- Introduction to
Software Engineering
Group Assignment 1
Due Date: Friday, February 10, at 11:59pm
Percentage of
total mark: 7%
This is a group assignment. READ THIS ENTIRE
ASSIGNMENT OVER CAREFULLY BEFORE MEETING WITH YOUR GROUP!.
Each group in the class is to hand in one separate
assignment. You can delegate the individual parts of the assignment to a subset
of the group members, but it is a good idea for all group members to read over
the entire completed assignment before one of the members hands it in to
webct.
Overview
In this assignment, your group will do the first stages of
the high level design of your software for the group project. Your project report must be of high quality and
typed. The entire
assignment, i.e. the report, must be submitted as one pdf file. If you do not
have pdf writer software, there is a good free one called CutePDF at: http://www.cutepdf.com/. Join the pdf files
for the title page, personnel snapshots, class diagram, use case diagram, and
gantt chart together into one large, neatly organized pdf that the teaching
assistant can print off in order to grade your report.
Your hand-in/report should consist of the following things
(see below for more details):
- A title page.
- Section 1: A Personnel Snapshot
- Section 2: A UML Use Case Diagram resulting from your
analysis of the group project requirements.
- Section 3: A UML Class Diagram resulting from your
analysis of the group project requirements.
- Section 4: A Project Plan for managing your group's
time.
Title Page
The title page should contain:
- The course number
- The section number.
- The assignment number.
- The due date of the assignment.
- The number of your group.
- The names of all your group members in alphabetical
order
Sample Title Page:
CS 2212a, Section 001 Group
Assignment 1 Due Date: June 1, 2011
Group 999
Group Members: Justine Bateman Courtney
Cox Geena Davis Michael J. Fox Tom Hanks
|
Personnel Snapshot
Include a list of all the group members and a brief summary
of the skills or background knowledge that they contribute to the project. Limit
your description to a maximum of five sentences per person.
UML Use Case Diagram
This section should consist of:
- an UML Use Case diagram resulting from your analysis of
the group project requirements. Please use only the features of UML Use Case
diagrams that are discussed in the course slides on Use Case diagrams.
Evaluate your UML Use Case diagram based on the advice given in the
slides.
- give the details (use case name, description, narrative,
main course scenario, preconditions, post conditions, one alternate scenario
with pre and post conditions, other design considerations (if any)) for the
use case: An administrative user adding a new contestant.
UML Class Diagram
Draw a UML class diagram resulting from your analysis of the
project requirement specifications. Use only the features of UML discussed in
class. Your diagram must have sensible classes, attributes, methods,
associations, hierarchies, etc., that capture the requirements in as complete a
manner as possible. As this stage however, we do not expect details such as
attribute type, method return type or whether the methods are public or private.
Only model the domain, you do not need to model the interface (i.e. you do not
need to include any classes for the user interface for this assignment).
NOTE: You MUST use MS Visio in order to draw the
UML Class Diagrams and Use Case Diagram. MS Visio is available free to Western
Students. Go to the bottom of the page http://www.csd.uwo.ca/, and
click on the link . Then, using a pdf writer,
convert the class diagram and use case diagram to pdf files.
Project Plan --> Gantt Chart
For CS2212, we will have the following milestones:
- Milestone 1 --> Group Assignment 1
- Milestone 2 --> Group Assignment 2
- Milestone 3 --> Group Assignment 3
- Milestone 4 --> Code Submitted for Acceptance
Testing
- Milestone 5 --> Group Assignment 4
There are several tasks that must be completed before
achieving each milestone. For example, in order to reach milestone 1, your group
must do at least the following tasks:
- complete the UML Class Diagram
- complete the UML Use Case Diagram
- complete the Personnel Profiles Document
- learn MS Project
- complete the Project Plan
In order to reach Milestone 5, your group might have to
complete tasks such as:
- code the User Interface
- code the Regular User Class
- unit test the Regular User Class.
You must draw a Gantt chart to indicate the required tasks,
who was assigned the tasks (could be more than one person), how long each task
will likely take, which tasks must be completed before another task can start,
etc. You MUST use MS Project in order to draw the Gantt chart. MS Project is
available free to Western Students. Go to http://www.csd.uwo.ca/, and click on the link
. Note: to indicate
a milestone in MS Project, set the duration to 0. You might want to change the
duration units to hours rather than days, but this is up to you. Duration unit
is set under Tools>Options>Schedule
On your Gantt chart indicate:
- the 5 milestones listed above and when each milestone
must be completed by
- the tasks your group decided were required to reach
Milestone 1 and indicate who performed each task (NOTE: this is called
a resource in MS Project) and how long each task took and when you worked on
them (the start and finish times). Include a column for % complete.
Indicate 100 % complete, since you handed in your assignment, so for milestone
1, you must have completely finished all these tasks.
- the tasks your group has decide are required to reach
Milestone 2. Indicate who will perform each task and how long you
estimate each task will take. You are making your best guess here, don't worry
if you end up being a bit off, you will get better at estimating time
durations by the end of the course. If you have already started any of these
tasks, indicate what percentage of the task you have completed.
- if you want, you can start listing the other tasks that
your group has decided will be required in order to reach the other
milestones. Don't worry if this list of tasks is not yet complete at this
point, it is just to get your group thinking about planning.
Send your Gantt chart to a pdf file. Don't worry if you
Gantt chart doesn't fit on one page, you can span it across on to other
pages.
Tips
- Save a copy of what you hand in. Make a copy of what you
write available to your other group members on the GAUL system; you may want
to make a hardcopy also.
- Evaluate your UML use case diagram according to the
guidelines in the course notes. DO NOT make the diagram overly busy, as this
will result in a loss of marks, just as a sparse use case diagram would also
result in a loss of marks. Try to make it fairly clean and simple.
- Evaluate your UML Class diagram according to the
evaluation guidelines in the course notes. The overall form of the diagram
must be correct and it must avoid common errors. It must have sensible
classes, attributes, operations, hierarchies, multiplicities and associations
that capture the requirements in as complete a manner as possible.
- Make sure that it is clear, to the reader of your
detailed use case, what the user has typed and what the system has responded
with.
Marking
The marks will be tentatively assigned as
follows:
- Title page and general formatting of hand-in: 2 marks.
- Section 1: Personnel Snapshot: 2 marks
- Section 2: UML Use Case Diagram: 5 marks.
- Section 3: UML Class Diagram: 8 marks.
- Section 4: Project Plan: 5 marks.
Submitting the Assignment
- Create one large pdf file that
contains the title page, personnel snapshots, the UML use case diagram, the
UML class diagram, and the Gantt chart. Remember that part of your mark is
based on the clarity and organization of your report so make sure it is neat
and well organized.
- The pdf file should be called
Group?Assignment1.pdf where ? is your group
number
- Have one of the members in your
group:
- Log onto webct.
- Go to assignments, Group
Assignment 1
- Attach your
Group?Assignment1.pdf file using the Attach button
in Webct.
- Hit the Submit button
- Hit the OK button
Peer Evaluation (to be done individually)
Within four days immediately after this
assignment's due date, complete the following peer evaluations for each
individual (including yourself) in your group. For each peer evaluations that
you fail to submit within four days of the due date, you will individually lose
0.5% off of your final course mark (up to a total of 2% for the 4 peer
evaluations you must submit).
Click here to
submit a peer evaluation (remember to also evaluate your own
performance as well as ALL your other group members)
Note: Peer evaluations can affect the final
mark given to an individual so please complete these peer evaluations
CONSTRUCTIVELY.