ICTSAD609 Assessment 1 Word Version 20-05-2023 10 35 47 021aedfc48

ASSESSMENT BOOKLET – ICTSAD609
Assessment 1 – Coversheet
Student and Submission Details
Student
Studen
ID
t Name
Unit ICTSAD609 - Plan and monitor Date of
Code and business analysis activities in an ICT submission 00/00/0000
Name environment
STUDENT DECLARATION
I declare
that
a. This assessment is my own work.
b. None of this work has been completed by any other person.
c. I have not cheated or plagiarized the work or colluded with any other student/s.
d. I have correctly referenced all resources and reference texts throughout these assessment
tasks.
e. I understand that if I am found to be in breach of policy, disciplinary action may be taken
against me.
Student Signature :
Assessor To Complete
Assessment 1 Assessment Result Date Type Of Submission
Short Answer □ C (Competent) ☐ First submission
Questions □ NYC (Not ☐ First re-submission
Yet 00/00/0000 ☐ Second re-submission
Competent)
Assessor □ NA (Not
feedback Assessed)
Assessor Name
Assessor
Signature:
Unsatisfactory
Not Present
Satisfactory
This assessment meets the following Knowledge Evidence
• business analysis process, procedures and techniques

• project management process, procedures and techniques
• risk management strategies
• technology solution patterns
• stakeholder management techniques and processes
ANIT Australia Pty Ltd T/A Albright Institute of Business and Language RTO#:45041 CRICOS#:03553J www.albrightinstitute.edu.au
HeadOfficeAddress:Level2,4&8,341- 345 Queen Street, Melbourne VIC Tel:1300189154 Campuses at: Sydney, Brisbane, Adelaide
3000
TRG-DOC-09Assessment Booklet –ICTSAD609| Version: 1.1| Last Reviewed: July 2022 | Next review Date: As required |Page 1 of 33
• communication constraints that may impact on stakeholders

• requirements management processes, procedures and
techniques
• metrics used in measuring business analysis performance
• organisational and legislative requirements and procedures
applicable to business analysis activities.
3000
Assessment 1 – Knowledge Questions
Assessment summary You are required to answer all the written questions in this
assessment.
Resources and • Access to textbooks and other learning materials.
equipment required • Access to a computer, printer, Internet and
to complete this email software (if required).
assessment
When and where • This assessment may be done in your own time as
should the homework or you may be given time to do this
assessment be task in class (where applicable).
completed • Your assessor will provide you with the due date for this
assessment.
What needs to Your answers to each question in this assessment along with
be submitted references.
Instructions • This is an open book test – you can use your
text book/learning materials as reference.
• You must answer all questions in this
assessment correctly.
• You must answer the questions by typing your
answers in Microsoft Word and converting it into a
pdf.
• Please include the following details in the header
section of each page of your assessment document:
o Student Name and ID
o Course Code and title
o Unit Code and title
o Trainer and assessor name
o Page numbers
• You are required to submit your assessment on the LMS
(Moodle). No submissions will be accepted via emails.
3000
ANIT Australia Pty Ltd T/A Albright Institute RTO#:45 CRICOS#:0 www.albrightinstitute.
of Business and Language 041 3553J edu.au
Campuses at: Sydney, Brisbane,
Adelaide
HeadOfficeAddress:Level2,4&8,341- 345 Tel:13001
Queen Street, Melbourne VIC 3000 89154
TRG-DOC-09Assessment Booklet –ICTSAD609| Version: 1.1| Last Reviewed: July 2022 | Next review Date: As
required |Page 10 of 33
Assessment Task 1– Knowledge Questions

Please answer the following questions.
Questions
Provide answers to all of the questions below:
1. Describe a general business analysis process. In your answer include:

 a definition of business analysis in an ICT environment
 steps that outline the business analysis process
 examples of business analysis deliverables.
Business Analysis Process in an ICT Environment:

Business analysis in an Information and Communication Technology (ICT) environment involves the systematic
examination of an organization's business needs and goals, along with the identification and recommendation of
solutions that leverage technology to achieve those objectives. It plays a critical role in aligning technology solutions
with business strategies.
Here's a general business analysis process in an ICT environment:
1. Define the Problem or Opportunity:
 Identify the specific business problem, opportunity, or need that requires analysis and potential
technology solutions.
 Create a clear and concise problem statement or business case.
2. Planning and Scoping:
 Develop a project plan outlining the objectives, scope, and stakeholders.
 Define the boundaries of the analysis effort, including what is in and out of scope.
 Identify key stakeholders and their roles.
3. Gather Information and Data:
 Collect and analyze relevant data, which may include interviews, surveys, market research, and
existing documentation.
 Understand current business processes and technologies in use.
4. Identify Business Requirements:
 Translate the gathered information into specific business requirements.
 Distinguish between functional requirements (what the system should do) and non-functional
3000
TRG-DOC-09Assessment Booklet –ICTSAD609| Version: 1.1| Last Reviewed: July 2022 | Next review Date: As required |Page 1 1 of 33
requirements (performance, security, etc.).

5. Analyze and Prioritize Requirements:
 Evaluate and prioritize requirements based on their importance and alignment with business goals.
 Consider the impact and feasibility of implementing each requirement.
6. Develop Solutions:
 Explore potential technology solutions to meet the identified requirements.
 Create system designs, specifications, and architecture proposals.
7. Evaluate and Select Solutions:
 Assess the proposed solutions against the requirements.
 Compare cost, risks, and benefits of each solution.
 Select the most suitable option.
8. Create Business Analysis Deliverables:
 Develop various deliverables that aid in the analysis process, including:
 Business Requirements Document (BRD)
 Functional Requirements Specification (FRS)
 Use Cases
 Data Flow Diagrams
 System Design Documents
 Risk Assessment Reports
9. Implement and Test:
 Collaborate with development teams to build and implement the chosen solution.
 Perform testing, quality assurance, and user acceptance testing to ensure the solution meets the
requirements.
10. Manage Change and Stakeholder Communication:
 Plan for changes and manage stakeholder expectations throughout the project.
 Communicate progress and issues to stakeholders.
11. Document and Close the Project:
 Create documentation for the implemented solution.
 Conduct a post-implementation review to ensure the solution meets the business goals.
12. Continuous Improvement:
 Monitor the implemented solution's performance and gather feedback from users.
 Identify opportunities for improvement and future enhancements.
3000
Examples of Business Analysis Deliverables:

 Business Requirements Document (BRD): A detailed document outlining the high-level business needs and
objectives.
 Functional Requirements Specification (FRS): A document specifying the system's functional capabilities,
including use cases and feature descriptions.
 Use Cases: Descriptions of system interactions and scenarios to help understand how the system will be
used.
 Data Flow Diagrams: Visual representations of data flow and processes within the system.
 System Design Documents: Detailed technical specifications, including architecture and design choices.
 Risk Assessment Reports: Identifying potential risks and their impacts on the project.
2. Complete the table outlining legislation, standards and organisational policies and
procedures related to business analysis.
Description Example (provide one)

Data protection legislation, such as Data Protection Act (e.g., Health
Legislation
HIPAA, mandates strict controls and Insurance Portability and
safeguards for the handling of Accountability Act - HIPAA in
personal health information. the USA)
Business analysts working in
healthcare must adhere to these
regulations when gathering,
processing, or storing healthcare data
to protect patient privacy and
security.
ISO/IEC 27001 is a widely ISO/IEC 27001 (Information
Standards
recognized standard for information Security Standard)
security management systems.
Business analysts may follow this
standard to ensure that the
information security aspects of the
projects they are involved in are
well-defined, implemented, and
maintained.
An organization's Change Change Management Policy and
Policies
Management Policy and Procedure Procedure
and provide guidelines on how changes
procedures to processes, systems, and
technologies are assessed, approved,
implemented, and monitored.
Business analysts often adhere to
these policies to ensure that changes
to business processes and systems are
3000
well-managed and align with the

organization's goals and objectives.
3. List four tools often used in business analysis to identify and understand
problems, needs or opportunities in a workplace.
Business analysts use a variety of tools to identify and understand problems, needs, or opportunities in a workplace.
Here are four commonly used tools for this purpose:
1. SWOT Analysis: SWOT stands for Strengths, Weaknesses, Opportunities, and Threats. It is a structured
framework for assessing the internal strengths and weaknesses of an organization, as well as the external
opportunities and threats it faces. SWOT analysis helps in understanding the current state of the organization
and identifying areas for improvement or potential advantages.
2. Fishbone Diagram (Ishikawa or Cause-and-Effect Diagram): This tool is used to analyze the root causes
of a problem or issue. It visually represents the various potential causes of a problem, categorizing them into
different branches on the "fishbone." By identifying the underlying causes, business analysts can develop
strategies to address the problem at its source.
3. Gap Analysis: Gap analysis compares the current state of an organization with its desired future state. It
helps in identifying the gaps or differences between the two, whether related to processes, performance, or
outcomes. By understanding these gaps, business analysts can recommend solutions to bridge them
effectively.
4. Interviews and Surveys: While not strictly tools, interviews and surveys are essential methods for gathering
qualitative and quantitative data directly from stakeholders and employees. Business analysts often use these
methods to understand the needs, concerns, and preferences of individuals within the organization. This
primary research helps in identifying problems, needs, and opportunities.
These tools, in combination with other techniques and methodologies, enable business analysts to gain a
comprehensive understanding of the workplace and its challenges, facilitating the development of appropriate
solutions and strategies.
4. Describe a general project management process. In your answer include:

 a definition of project management in an ICT environment
 steps that outline the project management process
Project Management Process in an ICT Environment:
Definition of Project Management in an ICT Environment:

Project management in an Information and Communication Technology (ICT) environment involves planning,
executing, and controlling projects related to technology infrastructure, software development, or IT services to
achieve specific objectives within constraints such as time, cost, and scope. It encompasses the application of
knowledge, skills, tools, and techniques to effectively manage ICT projects throughout their lifecycle.
Steps in the Project Management Process:
Initiation:
Define the project's purpose, goals, and objectives.

Identify key stakeholders and their roles.
Develop a project charter that formally authorizes the project.
Planning:
3000
Create a detailed project plan outlining the scope, schedule, budget, and resources.
Develop a Work Breakdown Structure (WBS) to break the project into manageable tasks.
Identify risks and develop a risk management plan.
Define project deliverables and quality standards.
Establish communication and reporting processes.
Execution:
Assemble the project team and allocate resources.

Implement the project plan according to the defined scope, schedule, and budget.
Manage stakeholder expectations and communication.
Monitor and control project performance.
Monitoring and Controlling:
Continuously track project performance against the plan.

Identify and manage changes, issues, and risks.
Ensure that the project stays within scope, schedule, and budget.
Conduct regular status meetings and reporting to stakeholders.
Closing:
Complete all project deliverables and ensure they meet quality standards.
Obtain formal acceptance of the project's results from stakeholders.
Conduct a lessons learned session to document successes and areas for improvement.
Close out contracts, release project resources, and archive project documentation.
Post-Implementation Review:
After project closure, evaluate the project's overall success in achieving its objectives.
Analyze what worked well and what could be improved for future projects.
Capture best practices and lessons learned to inform future ICT projects.
Throughout the project management process, project managers and their teams work collaboratively to ensure that
ICT projects are delivered successfully and meet the intended business goals. Effective project management is
crucial in the ICT sector to handle the complexities of technology projects and to adapt to the rapidly evolving nature
of the industry.
3000
5. Summarise two project management techniques that are often associated with an ICT
environment. Use the table below for your answer. An example has been provided for
you in the first row.
Technique Description
Waterfall This method builds on the classic method and is suitable for
more complex projects. It focuses on the sequential
performance of tasks. Gantt charts are often used.
Agile Agile project management is an iterative and flexible approach,
well-suited to ICT projects with evolving requirements. It
emphasizes collaboration, adaptability, and delivering working
increments of the product in short cycles, called sprints. Agile
methodologies include Scrum, Kanban, and Extreme
Programming (XP). It contrasts with the Waterfall approach by
embracing change and customer feedback throughout the project.
Agile is highly effective for software development, allowing
teams to respond quickly to changing technology and business
needs.
DevOps DevOps is not a traditional project management technique but a
cultural and technical movement within ICT. It bridges the gap
between development (Dev) and operations (Ops) teams to
enable continuous integration, continuous delivery, and
automation in software development and system administration.
DevOps emphasizes faster and more reliable software releases,
reduced deployment failures, and improved collaboration among
IT teams. It helps organizations manage the complexities of
delivering ICT services and software efficiently.
6. Complete the table explaining the types of risk that may be associated with a
business analysis initiative and its stakeholders. For each type of risk, you are
required to provide an ICT relevant example. The first row has been completed as an
example for you to follow.
Type of risk Description Example
Strategic risk These risks can occur at Initiate process automation

any time and are related throughout the organisation at
to the business or the expense of personal client
organisation’s strategy. relationships and interaction.
Compliance risks relate to the Failing to comply with data privacy
Compliance risk
potential failure to adhere to regulations (e.g., GDPR) during the
relevant laws, regulations, or collection and processing of user
industry standards. data, leading to legal penalties and
reputational damage.
3000
Financial risks are associated Exceeding the allocated budget for

Financial risk
with budget overruns, cost an ICT project due to unforeseen
uncertainties, or resource software licensing fees, requiring
allocation issues. financial adjustments or project
cutbacks.
3000
Type of risk Description Example

Operational risks pertain to A critical server malfunction during
Operational risk
disruptions in project a software deployment, causing
execution, such as technology downtime and operational
failures, process errors, or disruptions, potentially leading to
vendor issues. customer dissatisfaction and
financial losses.
7. Explain three strategies that may be used to mitigate and manage risks
associated with a business analysis initiative. You answer should include:
 an explanation of the mitigation strategy
 appropriate example to illustrate the strategy.
Mitigating and managing risks in a business analysis initiative is crucial for its success. Here are three strategies to
mitigate and manage risks:
1. Risk Avoidance:
 Mitigation Strategy: Risk avoidance involves taking actions to eliminate or avoid the risk
altogether by making decisions or changes that prevent the risk from occurring.
 Example: In a business analysis initiative, if there is a high risk associated with using a particular
third-party software vendor due to a history of security vulnerabilities, the project team might decide
to avoid this risk by choosing a different vendor with a more secure track record.
2. Risk Transfer:
 Mitigation Strategy: Risk transfer involves shifting the responsibility for managing the risk to a
third party, often through contracts, insurance, or outsourcing.
 Example: When an organization engages a software development company to create a custom
application, they can transfer the risk of software defects and project delays to the vendor by
including specific clauses in the contract that outline penalties for non-compliance or delays. The
vendor then becomes responsible for managing these risks.
3. Risk Mitigation through Contingency Planning:
 Mitigation Strategy: Contingency planning involves developing a backup plan or strategy to
respond to the risk if it materializes, reducing its potential impact.
 Example: In an ICT project with a tight deadline, the risk of unexpected resource unavailability
(e.g., a key team member falling ill) can be mitigated through contingency planning. The project
manager may identify backup resources or cross-train team members to step in if necessary,
ensuring that the project can continue without significant delays in case the risk becomes a reality.
These strategies help business analysts and project managers proactively identify, assess, and address potential risks,
minimizing their negative impact on the success of the business analysis initiative.
8. Complete the table below, outlining a general stakeholder management process.
Step Description of what the step involves Tools/techniques

(provide two per step)
Involves identifying all individuals, groups, 1. Stakeholder Registers:
Identify
or entities that can affect or be affected by Create a stakeholder register
stakeholder
3000
the business analysis initiative. This includes to record the names, roles,
s
internal and external stakeholders. interests, and potential
influence of identified
stakeholders. 2.
Brainstorming and
Interviews: Use
brainstorming sessions and
interviews with relevant
team members to identify
stakeholders and their
concerns.
Involves categorizing stakeholders based on 1. Power-Interest Grid: Use
Classify
their level of influence, interest, and a power-interest grid to
stakeholder relevance to the project. Common classify stakeholders into
s classifications include high/medium/low categories based on their
priority or primary/secondary/tertiary power and interest in the
stakeholders. project. 2. Salience Model:
Apply the Salience Model
to classify stakeholders
based on their power,
legitimacy, and urgency in
relation to the project.
Create a strategy that outlines how each 1. Influence-Interest Grid:
Develop
stakeholder will be managed and engaged Use an Influence-Interest
stakeholder throughout the project. This strategy Grid to define tailored
managemen considers the specific needs, expectations, approaches for different
t strategy and concerns of each stakeholder group. stakeholder groups based on
their level of influence and
interest. 2. Stakeholder
Engagement Plan: Develop
a Stakeholder Engagement
Plan that details the
communication and
engagement activities for
each stakeholder, including
frequency, channels, and
content.
Involves designing a communication plan 1. Communication Matrix:
Plan
that outlines how information will be shared Create a communication
communicati with stakeholders. This includes defining matrix that specifies what
on what information to communicate, when, information needs to be
and through which channels. communicated to each
stakeholder, when, and
through which
communication channels. 2.
Stakeholder Mapping: Use
stakeholder mapping
techniques to visually
represent the flow of
information and feedback
between stakeholders and
3000
the project team.
3000
Step Description of what the step involves Tools/techniques

(provide two per step)
This step involves putting the stakeholder 1. Communication Tools:
Execute
engagement and communication plan into Utilize various
communicati action. It includes actively communicating communication tools such
on with stakeholders, providing updates, as email, project
addressing concerns, and fostering management software,
collaboration throughout the business video conferencing, and
analysis initiative. collaboration platforms to
reach stakeholders and
disseminate project
information. 2. Status
Meetings: Conduct regular
status meetings, such as
weekly or bi-weekly
updates, to provide
stakeholders with project
progress, discuss
challenges, and gather
feedback in real-time.
Adelaide
9. List three communication constraints that may impact stakeholders.
1. Language and Cultural Barriers:

 Description: Language differences or cultural barriers can hinder effective communication. When
stakeholders have diverse cultural backgrounds or speak different languages, it may lead to
misunderstandings, misinterpretations, and difficulty in conveying and comprehending information.
 Impact on Stakeholders: Stakeholders from various cultural backgrounds or regions may struggle to
grasp the nuances of the project, making it challenging to convey requirements, expectations, or
project updates accurately.
2. Geographical Distance and Time Zones:
 Description: Geographical dispersion of stakeholders, particularly in global or distributed teams, can
result in time zone differences. This can lead to difficulties in scheduling meetings, sharing real-time
information, and responding to urgent communication.
 Impact on Stakeholders: Stakeholders in different time zones may face challenges in coordinating
their availability for meetings or obtaining timely responses to their inquiries, potentially causing
delays in decision-making and project progress.
3. Technological Constraints:
 Description: Technological limitations or disparities in the tools and platforms used for
communication can be a significant constraint. These limitations may include incompatible software,
insufficient bandwidth for video conferencing, or security restrictions on certain communication
channels.
 Impact on Stakeholders: Technological constraints can impede the use of modern collaboration and
communication tools, making it difficult for stakeholders to access project information, participate in
virtual meetings, or share critical project documents and updates effectively.
10. Summarise requirements management as it relates to business analysis. In your answer include:
 an explanation of what requirements analysis is
 outline of how requirements can be managed
 a description of four types of requirements
 tools or techniques relevant to requirements management.
Requirements Management in Business Analysis:

1. Explanation of Requirements Analysis: Requirements analysis is a crucial phase in business analysis that
involves the systematic gathering, documentation, and management of business and system requirements. It is the
process of identifying, defining, and analyzing the needs and objectives of a project or system to ensure they are
well-understood and can be effectively implemented. Requirements analysis helps bridge the gap between business
stakeholders' expectations and the development of a solution that meets those expectations.
2. Outline of How Requirements Can Be Managed: Requirements management is the process of systematically
controlling and tracking requirements throughout the project lifecycle. It involves:
 Elicitation: Gathering and collecting requirements from stakeholders.
 Documentation: Creating clear and detailed requirements documents.
 Analysis: Evaluating, prioritizing, and validating requirements.
 Communication: Ensuring that stakeholders and team members understand and agree on requirements.
 Change Control: Managing changes to requirements and assessing their impact.
 Traceability: Establishing traceability links to connect requirements to project objectives.
 Validation: Ensuring that the requirements meet business needs and can be implemented.
 Verification: Checking that the requirements are accurate, complete, and consistent.
 Prioritization: Ranking requirements based on their importance and impact.
 Acceptance Criteria: Defining criteria to confirm when a requirement is met.
3. Description of Four Types of Requirements:
a. Business Requirements: These describe the high-level goals, needs, and objectives of the organization. They are
not specific to the system but provide the context for the project.
b. Functional Requirements: These specify what the system or solution must do and include details about system
behavior, features, and interactions with users and other systems.
c. Non-Functional Requirements: These define the qualities or characteristics the system must possess, such as
performance, security, scalability, and usability. They set the criteria for how well the system functions.
d. Transition Requirements: These describe the conditions and tasks needed to transition from the current state to
the future state defined by the project. They may include data migration, training, and deployment plans.
4. Tools and Techniques Relevant to Requirements Management:
 Requirements Traceability Matrix (RTM): A matrix that links requirements to their sources and
associated test cases. It helps ensure that all requirements are addressed and tested.
 Requirements Management Software: Tools like IBM Rational DOORS, Jira, or Microsoft Azure DevOps
help in documenting, tracking changes, and managing requirements in a centralized and collaborative
environment.
 Use Cases: A technique to document functional requirements by describing interactions between users and a
system, helping to define user scenarios and system behavior.
 Prototyping: Creating a working model of the system to help stakeholders visualize and refine requirements
through an iterative and feedback-driven process.
11. Define “technology solution patterns”.
Technology solution patterns, also known as design patterns, are reusable templates for solving common software
design and development problems. They provide best-practice solutions and guidelines to improve software quality,
maintainability, and reusability. Examples include Singleton, MVC, Factory Method, Observer, and Strategy
patterns.
12. List four metrics that can be used when monitoring business analysis performance.
When monitoring business analysis performance, several metrics can be used to assess the effectiveness and progress
of the analysis work. Here are four such metrics:
1. Requirements Coverage: This metric measures the extent to which business requirements have been
documented and addressed. It assesses whether the analysis has considered and covered all necessary
requirements to meet the project's objectives.
2. Requirement Traceability: Requirement traceability is a metric that evaluates how well requirements are
linked to their source and tracked throughout the project. It ensures that changes and decisions related to
requirements are properly documented and communicated.
3. Stakeholder Satisfaction: Assessing stakeholder satisfaction involves obtaining feedback from project
stakeholders to gauge their level of contentment with the business analysis process. This can be done
through surveys, interviews, or feedback mechanisms.
4. Deliverable Timeliness: This metric evaluates the punctuality of business analysis deliverables, such as
requirement documents or analysis reports. It ensures that these documents are produced and delivered
within predefined timelines and deadlines.
ANIT Australia Pty Ltd T/A Albright Institute RTO#:45 CRICOS#:03553J

of Business and Language 041
HeadOfficeAddress:Level2,4&8,341- 345 Tel:13001 www.albrightinstitute.edu.au
Queen Street, Melbourne VIC 3000 89154 Campuses at: Sydney, Brisbane,
Adelaide
Knowledge Questions Answers
What to submit:
• Answers to all questions
• References
Adelaide

ICTSAD609 Assessment 1 Word Version 20-05-2023 10 35 47 021aedfc48

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ICTSAD609 Assessment 1 Word Version 20-05-2023 10 35 47 021aedfc48

Uploaded by

Copyright:

Available Formats

ASSESSMENT BOOKLET – ICTSAD609

This assessment meets the following Knowledge Evidence

• business analysis process, procedures and techniques

• communication constraints that may impact on stakeholders

Assessment 1 – Knowledge Questions

Assessment Task 1– Knowledge Questions

1. Describe a general business analysis process. In your answer include:

Business Analysis Process in an ICT Environment:

requirements (performance, security, etc.).

Examples of Business Analysis Deliverables:

Description Example (provide one)

well-managed and align with the

4. Describe a general project management process. In your answer include:

Project Management Process in an ICT Environment:

Definition of Project Management in an ICT Environment:

Steps in the Project Management Process:

Define the project's purpose, goals, and objectives.

Assemble the project team and allocate resources.

Continuously track project performance against the plan.

Type of risk Description Example

Strategic risk These risks can occur at Initiate process automation

Financial risks are associated Exceeding the allocated budget for

Type of risk Description Example

8. Complete the table below, outlining a general stakeholder management process.

Step Description of what the step involves Tools/techniques

the project team.

Step Description of what the step involves Tools/techniques

9. List three communication constraints that may impact stakeholders.

1. Language and Cultural Barriers:

Requirements Management in Business Analysis:

11. Define “technology solution patterns”.

within predefined timelines and deadlines.

ANIT Australia Pty Ltd T/A Albright Institute RTO#:45 CRICOS#:03553J

Knowledge Questions Answers

You might also like