The University of Newcastle School of Design, Communication and Information Technology INFO6030 Systems Analysis and Design Trimester 3, 2016 Assignment 1 Due: Electronic copy submitted to the course Assessment link on Blackboard by 5pm Wednesday Oct 19, 2016. Worth: 15% of the course total. Cover sheets are available from the course Blackboard site. This is Part 1 of a Two-Part assignment presented in the course. It is to be undertaken in teams (of 4 or 5 members). Your individual contribution to the team and your assignment mark will be peer-reviewed. Each team is to include the Peer Review document (a template will be available on the course Blackboard site) 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. This should be done using a percentage, in a similar manner to being payed $100 for the work and having to divide it between the contributing members. If there is a dispute in allocation the course coordinator will contact individual team members for feedback (make sure you keep all your working documentation if it indicates your individual effort as this will be used in the evaluation of member’s contribution by the course coordinator). Please read the relevant sections of the course outline regarding responsibility for your work. From Week 3 onwards each team is to keep a project schedule indicating their tasks and resources (people) allocated to each task. In each task, one nominated person is to be the quality assurance (QA) person for that task (they are to be identified in the QA role for specific tasks and they cannot be a person involved in carrying out the task that they are QA’ing). Teams should also supplement the project schedule with (brief) minutes of their weekly team review and planning meetings (indicating briefly the assigned tasks and review comments of ongoing and also completed tasks from the task QA person). Both the progressive project schedule and weekly minutes should be uploaded weekly to the group’s file exchange 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. Assignment Research and Readings Satzinger, J.W., Jackson, R.B., Burd, S.D. (2005) Object-Oriented Analysis and Design with the Unified Process Thomson Publishing Co Satzinger, J.W., Jackson, R.B., Burd, S.D. (2016) Systems Analysis and Design in a Changing World Cengage Learning Schwalbe, K. (2014) Information Technology Project Management (7th Ed) Cengage Learning - Note: Earlier editions of Schwalbe are equally good A rough timeline of the assignment requirements follows: Note: you might decide to perform activities in different sequences and in different stage ...

1. The University of Newcastle
School of Design, Communication and Information Technology
INFO6030 Systems Analysis and Design
Trimester 3, 2016
Assignment 1
Due: Electronic copy submitted to the course Assessment link
on Blackboard by 5pm Wednesday Oct 19, 2016.
Worth: 15% of the course total. Cover sheets are available from
the course Blackboard site.
This is Part 1 of a Two-Part assignment presented in the course.
It is to be undertaken in teams (of 4 or 5
members). Your individual contribution to the team and your
assignment mark will be peer-reviewed. Each
team is to include the Peer Review document (a template will be
available on the course Blackboard site) 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. This should be
done using a percentage, in a similar manner to being payed
$100 for the work and having to divide it between
the contributing members. If there is a dispute in allocation the
course coordinator will contact individual team
members for feedback (make sure you keep all your working
documentation if it indicates your individual effort

2. as this will be used in the evaluation of member’s contribution
by the course coordinator). Please read the
relevant sections of the course outline regarding responsibility
for your work.
From Week 3 onwards each team is to keep a project schedule
indicating their tasks and resources (people)
allocated to each task. In each task, one nominated person is to
be the quality assurance (QA) person for that
task (they are to be identified in the QA role for specific tasks
and they cannot be a person involved in carrying
out the task that they are QA’ing). Teams should also
supplement the project schedule with (brief) minutes of
their weekly team review and planning meetings (indicating
briefly the assigned tasks and review comments of
ongoing and also completed tasks from the task QA person).
Both the progressive project schedule and weekly
minutes should be uploaded weekly to the group’s file exchange
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.
Assignment Research and Readings
Satzinger, J.W., Jackson, R.B., Burd, S.D. (2005) Object-
Oriented Analysis and Design with the
Unified Process Thomson Publishing Co
Satzinger, J.W., Jackson, R.B., Burd, S.D. (2016) Systems
Analysis and Design in a Changing World
Cengage Learning

3. Schwalbe, K. (2014) Information Technology Project
Management (7th Ed) Cengage Learning
- Note: Earlier editions of Schwalbe are equally good
A rough timeline of the assignment requirements follows:
Note: you might decide to perform activities in different
sequences and in different stages – but please discuss
this with your tutor and ensure that you keep the tutor informed
of your progress and problems.
Weeks 3-7
You should start getting requirements and constructing initial
models.
These would be use case diagrams (start building medium
descriptions), activity diagrams and domain class
diagrams (with initial state diagrams for each domain class
where they may be relevant). You might decide to
create event tables if you think it would help in your system
development. Please note that not all of these
diagrams may be needed for Assignment 1 but they will be
essential for a complete understanding of the system
and the detailed development work that will be required in
Assignment 2.
You should look to identify business processes and user
requirements and suggest ways of enhancing the
business through IT. You should also try to identify business
rules of the organisation and the required system.
You should use the UP disciplines to guide you in the inception
and elaboration phases (e.g., the environment,
requirements and business modelling disciplines looking at the
organisation; and the project management and

4. change control disciplines looking at your team management
and consistency).
You should develop suggestions to enhance business processes
with IT and provide solutions to identified
business problems – there may be several alternative solutions
you could provide to an identified problem (these
solutions may only be partial solutions to the problem or full
solutions). These will be in the form of a written
report with initial feasibility discussion for each alternative (so
that they can be compared by the client and one
or more particular direction selected).
As aforementioned, you should provide appropriate evidence of
the management of your team. For example, an
ongoing project schedule such as a Gantt chart and brief weekly
minutes (task allocation and task reporting).
Assignment Submission:
You are to use the Unified Process for this assignment. You are
free to choose any drawing tool to produce any
models and these will be submitted as PDF documents. Your
submissions will be electronic and these will be
outlined in the formal assignment specifications.
Electronic Submission:
An electronic submission must be submitted as a single zipped
folder called
INFO6030Assignment_TeamCode (you will be assigned a group
number, which is your 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 Models containing the diagrams and

5. models described below in the
detailed submission description.
A folder called Assignment Documents containing the
documents required by the system. These
items are required to be also put through TurnItIn before
submission. The documents are
described in the detailed submission requirements below.
The submitted zipped file (named according to the
specifications above) has to contain all relevant files
for the submission.
For your submissions:
• Be aware of the University policies for plagiarism and copying
another person’s 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 documents required for the final assignment
submission must be checked by Turnitin.
Detailed Submission Description:
• Assignment Cover Sheet signed (scanned signatures) by all
team members. Please note that is a
mandatory component.

6. • Peer Review - a single Word document
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 Proposal - a single Word document with section
headings shown below
o Executive summary – with your suggested preferred
solution(s) to the main problem areas.
o Organisation Background and Current System (indicating
problems, areas for improvement and
potential advantages).
o Business Rules (covering as broad a range of the
organisation’s activities as possible).
o Proposed
Solution
s – these should have a full discussion of the feasibility for each
solution
(cost/benefit statements may be given in terms of
advantages/disadvantages of each solution

7. instead of financial cost/benefit reports). You should indicate
any preferences in your proposed
solutions.
• Project Charter and Scope document on the Agreed