Posted: January 31st, 2023

ICT310 System Analysis and Design Task

ICT310
System Analysis and Design
Task 2
ATMC Semester 2, 2019
ATMC ICT310 System Analysis and Design Task 2
Page 2 of 12
Assessment and Submission Details
Marks: 35 % of the Total Assessment for the Course
Due Date: Midnight Monday, Week 12
The assignment MUST be submitted on time.
Assignments are to be submitted by SafeAssign.
DO NOT SUBMIT THE ASSIGNMENT TO THE
COURSE CO-ORDINATOR OR TUTOR.
The task is an individual assignment and will be marked out of a total of 100 marks and
forms 35% of the total assessment for the course. Once marked, ALL assignments will be
checked for plagiarism and/or collusion between individuals.
Refer to your Course Outline or the Course Web Site for a copy of the “Student
Misconduct, Plagiarism and Collusion” guidelines. Academic Integrity Information.
Note: Each student MUST make a second copy of the assignment and this copy MUST
be produced within 24 hours of it being requested by the Course Co-ordinator. Failure
to produce the second copy of the assignment when requested may result in loss of
marks or a fail grade for the assignment.
Assignment submission extensions will only be made using the official USC Guidelines.
Requests for an extension to an assignment MUST be made prior to the date of
submission and requests made on the day of submission or after the submission date
will only be considered in exceptional circumstances.
ATMC ICT310 System Analysis and Design Task 2
Page 3 of 12
Case Study: Your IT Support Crowd Pty Ltd.
Background:
Your IT Support Crowd Pty Ltd (YITSC) is an Adelaide based Information Systems Support
company. While also supporting various types of small to medium size businesses, YITSC
specialises in supporting resort management, real estate and legal businesses with their
specialist equipment and software requirements. These businesses have strict legal
requirements around network security and data privacy because of their Trust Account
management software and the sensitive client and guest data stored on the system
including credit card details, and other very personal information.
Roger Ben, a senior partner at YITSC, has been talking to clients about updating the security
of their systems and how they back up their data. A legal requirement for Trust Account
management is secure Offsite Backup of all trust account related data. Roger knows that
while some clients are happy to backup to a third party ‘Cloud’, most are unsure of the
security of cloud-based backups. Furthermore, some YITSC clients are part of corporate
businesses or franchises who would like to backup centrally to their own servers. Roger and
his partners discussed how they could cater for and all their client’s requirements and yet
retain oversight and control of the backup system.
They came up with the following concept (Figure 1):
• CLIENT – the client’s system where the data is stored that requires backup. The
‘CLIENT Backup’ application is installed on any computer or server with data that
needs to be transferred to a backup server
• SERVER – there is a range of different backup storage options such as third-party
cloud, YITSC servers, or an offsite corporate server. The ‘SERVER Backup’ application
stored on these systems receives and stores data from the ‘CLIENT Backup’
application
• CONTROLLER – YITSC central ‘CONTROLLER’ application system remotely sets up and
runs the ‘SERVER Backup’ application and then remotely sets up and runs the
‘CLIENT Backup’ application to send data to the ‘SERVER Backup’. The ‘CONTROLLER’
will log and monitor the backups and shut down the SERVER and CLIENT Backups
when the data has all been transferred to backup storage.
Roger and his team have designed and tested the CLIENT and SERVER backup applications.
For this they have adapted the rsync open source application which will take care of the
efficient transfer of data for backup. Currently they can manually set the rsync based
SERVER running and the rsync based CLIENT will successfully transfer data to the SERVER.
However, while Roger and his team have worked out the secure virtual private networking
(VPN) between CLIENT, SERVER and CONTROLLER, they are unsure as to how to design the
central CONTROLLER application and organise the CLIENT and SERVER setup information on
the CONTROLLER system. Roger has approached you and asked for your assistance. He has
some idea about the process the CONTROLLER would use, but he is unsure how to design or
model the new system. Roger has asked you to concentrate on designing and modelling the
CONTROLLER system only.
ATMC ICT310 System Analysis and Design Task 2
Page 4 of 12
Figure 1- YITSC Offsite Backup concept
Roger stated that the typical CONTROLLER process would start by YITSC IT Team setting up
and storing the business entity details. The business entity can be either the business client
needing data backed up, or the supplier of data storage for the backed-up data. The backup
task details for both the CLIENT and SERVER are entered and stored, and then the backup
tasks are scheduled to run at a particular time and interval. The backup would be run
according to the scheduled timing.
The CLIENT will send data to the SERVER to be backed up. The CONTROLLER would receive a
file transfer activity log and monitor that the backup was proceeding as normal. Roger
would like the log activity to be stored in a log file for reference purposes, however
whenever an error is logged he would like the CONTROLLER to notify him immediately by
email.
The final entry received in the log will notify the CONTROLLER when the backup is finished,
at which point the CONTROLLER will first stop the CLIENT, then stop the SERVER and email a
summary report to Roger.
When a business client no longer requires the backup service Roger will remove the
scheduled backup from the CONTROLLER and, after 6 months, will manually remove the
client’s backed up data from SERVERs not owned by the client.
At this stage Roger is only concerned with backing the data up. Although he would like to
create a ‘restore data’ option on the CONTROLLER, he realises that this could be prone to
error and decided not to include it in this project.
ATMC ICT310 System Analysis and Design Task 2
Page 5 of 12
Business Processes:
A JAD session with Roger revealed the following information. The business processes
described below are the system requirements for modelling this information system
solution:
• Although there are many possible system entities, the core CONTROLLER system
revolves around Business entities, computers that host SERVER and CLIENT backup
applications and data (Data Host Controller Computers), backup tasks, and a task
scheduler.
• Business entities includes businesses wanting data backed up and businesses able to
store the backed-up data. Roger would like Business Entity records to include contact
name, business name, contact address, start date and business ABN
• Data Host Controller Computers host the SERVER and CLIENT backup applications. They
also have direct access to the data to be backed up (CLIENT Host computer) or the
stored backed up data (SERVER Host computer). Your team has decided that data host
controller computers will record a computer name, IP address, data version date and
time, total data storage capacity, current storage size, data storage path, comments and
a Boolean isCurrent attribute.
• Each Business Entity must have one or more Data Host Controller Computers. Each Data
Host Controller Computer must have one or more Business Entity objects.
• Each Backup Task records a task name, task comment, and task type (‘server’ or ‘client’).
These tasks are categorized as one of the following:
o CLIENT Tasks – these tasks are the settings to send data to be backed up to a
SERVER Task. Records kept include rsync dash option, rsync dash dash option,
rsync module name, and Log file path.
o SERVER Tasks – these tasks are the settings to receive data to be backed from the
CLIENT Task. Records kept include server tcp port address, rsync module name,
and Log file path.
• Each SERVER Backup Task and each CLIENT Backup Task must have only one Business
Entity Data Host Controller. This connects the Backup Tasks to the Business Entity and
the Data Host Controller from which the Backup Task can access both the network
Addresses and Business name. Each Business Entity Data Host Controller may have many
SERVER Backup Tasks and CLIENT Backup Tasks.
• Task Schedule records include a schedule name, status (in progress, scheduled,
complete), start date and time and a latest finish date and time.
• Each Task Schedule must have only two Backup Tasks – a CLIENT Task and a SERVER
Task. Each Backup Task may have many Task Schedules.
• The Task Schedule will match a CLIENT task with a SERVER task and schedules the tasks
to run as a pair.
End of Case Study
ATMC ICT310 System Analysis and Design Task 2
Page 6 of 12
Part A – Essay
Question 1: Essay
Gabrielle is a business focused YITSC partner. Although Gabrielle understands project and
event management from a business perspective, she has a limited understanding of IT
projects. Gabrielle understands that competently managing the development of this backup
CONTROLLER project will help ensure that the CONTROLLER service will work well as per the
system requirement, will meet budget, and be developed and deployed in a timely fashion.
However, her research on information system project management has confused her a
little. She came across terms such as ‘Systems Development Life Cycle’ and ‘Agile’ and has
asked you to explain how these relate to the CONTROLLER Project.
The Systems Development Life Cycle (SDLC) defines six (6) core processes.
a) Describe each of the:
I. core processes (figure 10.5) in relation to the CONTROLLER project (15%
marks) and
II. core process activities (hints: Figures 11.5 and 11.12 as a start) the project
would require for each of these processes (15% marks).
b) Outline what ‘Agile’ means in relation to Information Systems projects and how it
would be applied in the CONTROLLER project (15% marks).
Roger, Gabrielle and their partners are your target audience for this essay. They are
executive business people and some of them have limited understanding of computer
terminology.
Your essay should be no less than one thousand five hundred (1500) words and it would be
best to be no longer than two thousand (2000) words long.
Appropriate referencing is required. The textbook Satzinger et. al is a valid resource,
however it is expected that at least five (5) other resources will also be used. Consult Rubric
in Appendix A for more details on how this question will be marked.
ATMC ICT310 System Analysis and Design Task 2
Page 7 of 12
Part B – Modelling and Diagramming
Review the YITSC case study and answer the following questions with reference to the
information in the case study.
Do NOT extend the scope for any of the following solutions beyond that specifically
described in the case study above.
You are permitted to make reasonable assumptions where necessary but these should be
noted.
It is recommended that you review all documentation for this case study before finalising
any single solution. Ensure that the required consistency has been included within and
between each question solution. Consult Rubric in Appendix A for more details on how
these questions will be marked.
Question 2: Use Case Modelling 30% marks
a) Event Table
Review the YITSC case study and prepare an event table for the information system to
support the business processes as described. Use at least the following headings for the
Event Table:
Event Event
Type Trigger Source Activity/Use
Case
System
Response/
Output
Destination
b) Use Case Diagram
Review the YITSC case study and your event table solution from question 3a above to
prepare a Use Case diagram for the supporting information system.
Solutions must follow the methodology as outlined within the Satzinger et al (2016)
textbook. Solutions are expected to align with the components as shown in figures 3-12
and 3-15. Consult Rubric in Appendix A for more details on how this question will be
marked.
c) Use Case Description
Prepare a fully developed Use Case description for the ‘Create Offsite Backup Task’ use
case, as documented in the event table solution and the use case diagram solution.
Solutions must follow the methodology as outlined within the Satzinger et al (2016)
textbook. Solutions are expected to align with the components as shown in figure 5-2.
Consult Rubric in Appendix A for more details on how this question will be marked.
ATMC ICT310 System Analysis and Design Task 2
Page 8 of 12
Question 3: Domain Modelling 25% marks
a) Domain Model Class Diagram
Review the YITSC case study to prepare a domain model class diagram for the supporting
information system.
Solutions must follow the methodology as outlined within the Satzinger et al (2016)
textbook. Solutions are expected to show:
• The class name and attributes list for each class and sub class as required
• All required associations
• All attributes as specifically mentioned in the case study must be reflected
• Other attributes as needed to support the described functionality.
It is not necessary to show methods, however you may include them if you wish. Solutions
are expected to align with the components as shown in figures 4-16 and 4-21. Consult
Rubric in Appendix A for more details on how this question will be marked.
b) Design Class Diagram
Prepare a Design class diagram for the Task Schedule and Backup Task classes ONLY. These
two classes should be part of the Domain model class diagram solution for the previous
question.
Each of these design class diagrams are expected to have a complete attributes list and a
comprehensive methods list which supports the specified functionality as described in the
case study.
Solutions must follow the methodology as outlined within the Satzinger et al (2016)
textbook. Solutions are expected to align with the components for the ‘Design class diagram
Student’ as shown on the right hand of figure 12.4. Consult Rubric in Appendix A for more
details on how this question will be marked.
End of Assignment 2
Appendix A – Marking Rubric
ICT310 Task 2 – Rubric
Criteria High Distinction (85-100%) Distinction (75-84%) Credit (65-74%) Pass (50-64%) Fail (0-49%)
(15%) Q1aI. SDLC
Core Processes –
Knowledge and
analysis of the
Systems
Development Life
Cycle (SDLC) 6 core
processes in the
case study.
Highly effective
application of
sophisticated knowledge
and advanced analysis of
SDLC processes in the
case study.
Effective application
of comprehensive
knowledge and
analysis of SDLC
processes in the case
study.
Applies adequate
knowledge and
adequate analysis
of SDLC processes
in the case study.
Applies adequate
knowledge and
limited analysis of
SDLC processes in
the case study.
Demonstrates
little or no
comprehension
of SDLC
processes in the
case study.
(15%) Q1aII. SDLC
Core Process
Activities – Use of
creativity to
develop innovative
and cost-effective
SDLC Activities
relevant to the
case study.
Grounded in a
comprehensive and
critical analysis of highly
relevant sources of
information evidences
high levels of creativity to
develop, evaluate and
fully justify highly
innovative and costeffective SDLC process
activities for the case
study.
Grounded in strong
analysis of relevant
sources of
information,
evidences strong
creativity to develop,
evaluate and justify
very innovative and
cost-effective SDLC
process activities for
the case study.
Demonstrates
creativity in
developing justified,
innovative and costeffective SDLC
process activities for
the case study.
Demonstrates
adequate levels of
creativity to develop
innovative and costeffective SDLC process
activities for the case
study.
Demonstrates
limited creativity
to develop SDLC
process activities
for the case study
which are
innovative and/or
cost-effective.
ATMC ICT310 System Analysis and Design Task 2
Page 10 of 12
Criteria High Distinction (85-
100%)
Distinction (75-84%) Credit (65-74%) Pass (50-64%) Fail (0-49%)
(15%) Q1b. Agile
Information
System Projects –
Identification and
critical analysis of
Agile in relation to
Information
System projects
and applied to the
case study.
Displays advanced ability
to identify, prioritise,
justify and critically
analyse Agile Information
System Projects with
insightful and clear
application to the case
study.
Demonstrates good
capacity to identify,
justify and critically
analyse Agile
Information System
Projects with clear
application to the
case study.
Demonstrates
reasonable
capacity to identify
and analyse
pertinent Agile
Information
System Projects
with good
application to the
case study.
Evidences some
capacity to identify
and analyse Agile
Information System
Projects with
adequate application
to the case study.
Demonstrates
inadequate
capacity to
identify and
critically analyse
Agile
Information
System Projects.
(10%) Q2a. Event
Table –
Demonstrate
critical thinking to
develop and
evaluate an Event
table and from the
case study.
Grounded in a strong
level of critical analysis of
relevant sources of
information, evidences
high levels of critical
thinking to develop,
evaluate and justify
highly appropriate Event
table to model case study
processes.
Grounded in
effective analysis of
relevant sources of
information,
evidences good
levels of critical
thinking to develop,
evaluate and justify
appropriate Event
table to model case
study processes.
Evidences sound
capacity for critical
thinking to develop
and evaluate
appropriate Event
table to model case
study processes.
Evidences adequate
capacity for critical
thinking but at times
this is not closely
reflected in the
Event table to model
case study
processes.
Demonstrates
limited or no
capacity to think
critically to
develop and
evaluate an
Event table for
the case study
processes.
ATMC ICT310 System Analysis and Design Task 2
Page 11 of 12
Criteria High Distinction (85-
100%)
Distinction (75-84%) Credit (65-74%) Pass (50-64%) Fail (0-49%)
(10%) Q2b. Use
Case Diagram –
Demonstrate the
application of a
Use Case Diagram
to model case
study processes
and its relationship
to the Event Table.
Evidences a correct and
clear application a Use
Case Diagram to case
study processes. All
relevant actors, syntax
and naming conventions
followed. clear
relationship between the
Use Case Diagram and
the Event Table use
cases.
Evidences a correct
application a Use
Case Diagram to
case study
processes. Relevant
Actors and naming
conventions used.
Good relationship
between the Use
Case Diagram and
the Event Table use
cases.
Evidences sound
capacity to
correctly apply a
Use Case Diagram
to case study
processes. Good
relationship
between the Use
Case Diagram and
the Event Table use
cases.
Evidences adequate
capacity to correctly
apply a Use Case
Diagram to case
study processes.
Some relationship
between the Use
Case Diagram and
the Event Table use
cases.
Demonstrates
limited or no
capacity to
correctly apply a
Use Case
Diagram to the
case study.
(10%) Q2c. Use
Case Description –
Evidence of critical
thinking to develop
and evaluate
appropriate Use
Case Description
for a Use Case in
the case study.
Grounded in a
comprehensive and
critical analysis of highly
relevant sources of
information, evidences
very high levels of critical
thinking to develop,
evaluate and fully justify
an insightful and clearly
formatted Use Case
Description for a Use
Case in the case study.
Grounded in strong
analysis of relevant
sources of
information,
evidences high levels
of critical thinking to
develop, evaluate and
strongly justify a clear
and well formatted
Use Case Description
for a Use Case in the
case study.
Evidences sound
levels of critical
thinking to develop,
evaluate and justify
correctly formatted
Use Case Description
for a Use Case in the
case study.
Adequately evidences
a capacity for critical
thinking to develop
and evaluate a
formatted Use Case
Description for a Use
Case in the case study.
Demonstrates
limited capacity to
think critically to
develop and
evaluate Use Case
Description for a
Use Case in the
case study.
ATMC ICT310 System Analysis and Design Task 2
Page 12 of 12
Criteria High Distinction (85-
100%)
Distinction (75-84%) Credit (65-74%) Pass (50-64%) Fail (0-49%)
(15%) Q3a. Domain
Model Class Diagram
– Identify and
organise case study
problem domain
‘things’ into
correctly formatted
Domain Model Class
Diagram classes with
class names,
attributes,
subclasses and
associations.
Identifies and clearly
organizes all case study
problem domain ‘things’
into classes with clear
and correctly formatted
class names, attributes,
subclasses and
associations.
Identifies and
correctly organizes
all case study
problem domain
‘things’ into classes
with clear class
names, attributes,
subclasses and
associations.
Identifies and
correctly organizes
most case study
problem domain
‘things’ into classes
with class names,
attributes,
subclasses and
associations.
Adequately
Identifies and
organizes essential
case study problem
domain ‘things’ into
classes with some
class names,
attributes,
subclasses and
associations.
Ambiguous,
illogical or
unsupported
classes. Limited
or inaccurate
understanding of
Domain Model
Class Diagrams
(10%) Q3b. Design
class diagram –
Construct a
correctly formatted
Design class
diagram which
includes a
complete
attributes list and a
comprehensive
methods list which
supports the
functionality
specified in the
case study.
Well formatted Design
class diagram with all
attributes and a
comprehensive list of
insightful methods which
support the functionality
specified in the case
study.
Well Formatted
Design class diagram
with all attributes
and clear methods
which support the
functionality
specified in the case
study.
Formatted Design
class diagram with
most attributes
and methods
which support the
functionality
specified in the
case study.
Formatted Design
class diagram with
some attributes and
methods which
support the
functionality
specified in the case
study.
Imprecise and
vague Design class
diagram

Check Price Discount

Study Notes & Homework Samples: BCJ100 (2) Define due process, as required by the Bill of Rights »A study of the role of human rights in the fight against terrorism