The University of Newcastle

School of Design, Communication and Information Technology

INFO6030 Systems Analysis and Design
Trimester 3, 2014

Assignment 2
Due: Electronic copy submitted to the course Assessment link on Blackboard and a hard copy (printout) of selected
items are to be submitted at the start of the presentation in week 12.
Worth: 20% of the course total. Note that the submission is a combination of electronic (via the course
Assessment link) and paper copy with an attached cover sheet signed by all team members. Academic staff will
not mark assignments that do not have a signed cover sheet. Cover sheets will be available from the course
Blackboard site.
This is Part 2 of your Two-Part assignment. As in Part 1, it is to be undertaken in teams. Each team is to include
the Peer Review document as the first page of the assignment submission (following the cover page for the
assignment). The Peer Review document will indicate the relative contribution by each member of the team to
the final work, which should be done using a percentage. If there is a dispute in allocation the course
coordinator will contact individual team members for feedback.
Each team should continue to upload their progressive project schedule and weekly minutes to the groups file
exchange area on Blackboard. These minutes will form an ongoing part of the assessment for the assignment.
The team minutes may also be used to assist determination of member contribution and quality in case of a
dispute between team members.

Weeks 9-12
You should proceed with the detailed design of an agreed part of the system. For this:
You will provide a feasibility report for the selected solution.
You will develop a design (detailed) class diagram and some state diagrams for each relevant class.
You will develop detailed use case descriptions of selected use cases. For each of these selected use cases you
will develop design (detailed) sequence diagrams.
You will develop design screens that will simulate the functionality of your selected use cases.
Note: the class structure (attributes and methods) of your class diagram should be consistent with the sequence
and state diagram messages, and the functionality and data used in your screens should be consistent with all of
your models.
You will also be required to provide an implementation strategy, training, testing and maintenance procedures
for your developed system. A test plan and test data bank will be created that will adequately test your selected
use cases and some example business rules. These will be judged from a practical (rather than theoretical)
viewpoint.
Presentation week 12 during tutorial, all members are to be present.
As usual, you should provide appropriate evidence of the management of your team (e.g., an ongoing project
schedule such as a Gantt chart and brief weekly minutes (task allocation and task reporting) to be uploaded to
your group area).

Assignment Submission:
Note that both an electronic and a hard-copy submission are required.
Electronic Submission:
An electronic submission must be submitted as a single zipped folder called
INFO6030Assignment2_TeamCode (your group number is the team code) through the course Blackboard
site by the required time. Marks will be deducted if this is not strictly adhered to. The single zipped folder
is to contain:
A folder called System Artifacts. This will include the Gantt chart project file, Interface (design
screens) files and PDF files of your diagrams/models.
A Word file is required to be put through TurnItIn before submission to the Assessment link.
This is to be one word document with any appendices as required. It will have an Executive
Summary, Table of Contents, Introduction and headings as required (signposting) and images of
all models, interfaces, etc as described in the detailed submission requirements below. The
models and interfaces will require some form of description.
The submitted zipped file (named according to the specifications above) has to contain all relevant files
for the submission.
Hard-Copy Printout:
A hard copy of selected items is to be submitted at the lecture by the required time.
It must have on the front a copy of the Assignment cover sheet available from the course Blackboard site,
signed by ALL members of the team.
It should contain a printout (the Word document) for each of the diagrams, interfaces and models (with
descriptions as required), system implementation and management except for the Gantt chart as an electronic
copy only.
For Both Submissions:
Be aware of the University policies for plagiarism and copying another persons assignment. If you are
caught the penalties are very harsh and may jeopardize your University degree in addition to possible
expulsion from this course.
Reference all work where required - if is not your own words or work then references from where you
got the material are required.
The Word document required for the final assignment submission must be checked by Turnitin and the
result is to be put with your hard copy.

Detailed Submission Description:

Assignment Cover Sheet signed (scanned signatures) by all team members. Please note that this is a
mandatory component.
Peer Review
o A one-page document from the team using a template supplied in the Blackboard Group
Administration Files folder. The team allocates a % contribution for each team member,
covering the contribution from each team member through the trimester and towards the final
assignment submission (the combined total of all members contribution should be
approximately 100%).
System Implementation and Risk Management
o Detailed Implementation Plan (how the system is to be implemented and integrated into the
organisation), covering aspects shown below:
How the business rules will be implemented (at a design level). This is an updated
version of your first submission. You must show how this has changed and why as the
project has developed.

Testing
Training
Data migration (if required)
Installation plan (hardware and software installation)
Maintenance
o A list and ranking of major risks for the project (if there are any). To help with this you might
like to consider the following questions:
What use cases involve risk? Is there any risk that requires Professional Liability
insurance? Are there any ethical considerations that will need to be considered if so,
what are they? Are there any special privacy or security conditions expected by the
client? Are there any special commercial considerations, for example, how will
Intellectual Property be addressed?
This is an updated version of your first submission. It will have new risks such as data
migration or implementation issues or team skills in developing system interfaces etc.
You must show how this has changed and why as the project has developed. So the risks
will include the project and your team.
System Design
o A revised Use Case diagram showing the proposed expansion/improvement, plus detailed use
case descriptions for two selected use cases.
o A Detailed Class diagram for the proposed system (View and Data Access classes should not be
included). Only major, important methods should be included in classes please note that
create() and delete() are default methods that are assumed for all classes and need not be shown
in the class diagram for your proposed system. Please note also that classes and associations need
to be labelled, multiplicity (cardinality) indicated and important attributes identified.
o Detailed Sequence diagrams for the two selected use cases.
o Statechart diagrams for three selected classes.
o Screen designs for the two selected use cases. The screens do not have to connect to any database
but they should have some realistic data in listboxes, combo boxes, etc, that will display their
functionality. No error checking etc no code required.
Presentation and Project Management
o Your team will present the submission in your tutorial in week 12. This should be done as a
formal presentation to the management of your clients organisation (and to the other teams in
the tutorial). The presentation will run for 20 minutes plus time for questions.
o Your project management documentation will form part of the assessment of how your team
managed themselves. This will include any change management, weekly meeting and task
allocation.