School of Computer, Data and Mathematical Sciences
300578 Professional Development Sydney City Session 1 2021
Unit Details
Unit Code:
300578
Unit Name:
Professional Development
Credit Points:
10
Unit Level:
3
Assumed Knowledge:
Understanding of systems analysis and design
Note: Students with any problems, concerns or doubts should discuss those with the Unit Coordinator as early as they can.
Unit Convenor (SCC)
Name: Dr. Rhys Tague
Email: r.tague@city.westernsydney.edu.au
Consultation Arrangement:
Please liaise directly with the academic teaching this unit regarding appropriate consultation times. It is usually best to make contact with these staff via email.
Program Convenor (SCC)
Name: Antoinette Cevenini
Email: a.cevenini@city.westernsydney.edu.au
Consultation Arrangement:
Please liaise directly with the academic teaching this unit regarding appropriate consultation times. It is usually best to make contact with these staff via email.
Edition: Sydney City Session 1 2021
Copyright ©2021 University Western Sydney trading as Western Sydney University ABN 53 014 069 881 CRICOS Provider No: 00917K No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without the prior written permission from the Dean of the School. Copyright for acknowledged materials reproduced herein is retained by the copyright holder. All readings in this publication are copied under licence in accordance with Part VB of the Copyright Act 1968.
Contents
1 About Professional Development 2
1.1 AnIntroductiontothisUnit ………………………………… 2 1.2 WhatisExpectedofYou ………………………………….. 2 1.3 ChangestoUnitasaResultofPastStudentFeedback ……………………. 3
2 Assessment Information 4
2.1 UnitLearningOutcomes ………………………………….. 4
2.2 ApproachtoLearning ……………………………………. 4
2.3 ContributiontoCourseLearningOutcomes …………………………. 5
2.4 AssessmentSummary ……………………………………. 6
2.5 AssessmentDetails …………………………………….. 7
2.5.1 TutorialSubmissions-Module1and2………………………… 7 2.5.2 GroupProject……………………………………. 10 2.5.3 FinalExam …………………………………….. 17
2.6 GeneralSubmissionRequirements………………………………. 18
3 Teaching and Learning Activities 20
4 Learning Resources 22
4.1 RecommendedReadings…………………………………… 22
Note: The relevant Learning Guide Companion supplements this document 1
1 About Professional Development 1.1 An Introduction to this Unit
This is a final year unit that builds on foundation and intermediate computing units to prepare students for professional experience. The unit covers the content in three modules as 1) Ethics and Professional Code of Conduct, 2) Project Management, and 3) Legal, Social, Environmental issues, Quality Assurance and IT Compliance. The content covered in these three modules are carefully designed to fill in the gaps in knowledge that is not so far covered in previous units in preparing students for the challenging projects units and professional working life ahead. This unit is a pre-requisite to the capstone project, covered in Professional Experience Project unit.
1.2 What is Expected of You
Study Load
A student is expected to study an hour per credit point a week. For example a 10 credit point Unit would require 10 hours of study per week. This time includes the time spent within classes during lectures, tutorials or practicals.
Attendance
It is strongly recommended that students attend all scheduled learning activities to support their learning.
Online Learning Requirements
Unit materials will be made available on the Unit’s vUWS (E-Learning) site (https://vuws.westernsydney.edu.au/). You are expected to consult vUWS at least twice a week, as all Unit announcements will be made via vUWS. Teaching and learning materials will be regularly updated and posted online by the teaching team.
Special Requirements
Essential Equipment:
Not Applicable
Legislative Pre-Requisites:
Not Applicable
Policies Related to Teaching and Learning
The University has a number of policies that relate to teaching and learning. Important policies affecting students include:
– Assessment Policy
– Bullying Prevention Policy and
– Guidelines
– Enrolment Policy
– Examinations Policy
– Review of Grade Policy
– Sexual Harassment Prevention Policy
– Special Consideration Policy
– Student Misconduct Rule
– Teaching and Learning – Fundamental Code – Student Code of Conduct
2
Academic Integrity and Student Misconduct Rule
In submitting assessments, it is essential that you are familiar with the policies listed above and that you understand the principles of academic integrity. You are expected to act honestly and ethically in the production of all academic work and assessment tasks, submit work that is your own and acknowledge any contribution to your work made by others.
Important information about academic integrity, including advice to students is available at https://www.westernsydney. edu.au/studysmart/home/academic_integrity_and_plagiarism. It is your responsibility to familiarise yourself with these principles and apply them to all work submitted to the University as your own.
When you submit an assignment or product, you will declare that no part has been: copied from any other stu- dent’s work or from any other source except where due acknowledgement is made in the assignment; submitted by you in another (previous or current) assessment, except where appropriately referenced, and with prior permission from the Unit Coordinator; written/produced for you by any other person except where collaboration has been au- thorised by the Unit Coordinator.
The Student Misconduct Rule applies to all students of Western Sydney University and makes it an offence for any student to engage in academic, research or general misconduct as defined in the Rule.
The University considers plagiarism, cheating and collusion as instances of academic misconduct. The University also considers submitting falsified documentation in support of applications for special consideration, including sitting of deferred examinations, as instances of general misconduct. You should be aware that changes were made to the Student Misconduct Rule commencing 1 January 2020 that provide for minimum sanctions that apply to certain conduct, including the provision of falsified documentation to the University.
You are strongly advised to read the Student Misconduct Rule and the Inappropriate Behaviour Guidelines at the commencement of each session to familiarise yourself with this process and the expectations of the University in relation to work submitted for assessment.
1.3 Changes to Unit as a Result of Past Student Feedback
The University values student feedback in order to improve the quality of its educational programs. The feedback provided helps us improve teaching methods and Units of study. The survey results inform Unit content and design, learning guides, teaching methods, assessment processes and teaching materials.
You are welcome to provide feedback that is related to the teaching of this Unit. At the end of the semester you will be given the opportunity to complete a Student Feedback on Unit (SFU) questionnaire to assess the Unit. You may also have the opportunity to complete a Student Feedback on Teaching (SFT) questionnaire to provide feedback for individual teaching staff.
As a result of student feedback, the following changes and improvements to this subject have recently been made:
– The number of assessment items has been reduced
– Face to face (zoom) lectures are now provided weekly
– Final quiz changed to final exam quiz in the formal examination period
– Scheduling of assessment submissions has been changed according to student feedback
– The group project is divided into two parts instead of one large submission, and a recorded presentation is
included with submission of the last part.
– There are two peer reviews submitted for the group project, a progress peer review and a final peer review
3
2 2.1
Assessment Information Unit Learning Outcomes
Outcome
1
Describe ethics and professional code of conduct associated with the professions related to computing and Information & communications technologies (ICT)
2
Communicate in a professional manner for IT projects among team members and with outside parties
3
Plan, schedule and manage ongoing project activities as a group and an individual
4
Carry out cost benefit analysis of software related projects
5
Manage team dynamics that involves working with people of varying skill levels, from different work/life experiences and diverse cultural backgrounds
6
Articulate the concepts related to security, privacy and freedom of information as it relates to electronic data
7
Explain legal, social and environmental issues in relation to computing and ICT
8
Describe the importance of quality assurance and techniques used in verifying quality of software development projects
9
Articulate the core concepts of IT compliance in order to develop a plan that addresses IT control elements
10
Recognise indigenous culture and safety issues in proposed system designs
2.2
Approach to Learning
Lecture:
Attendance in lectures is expected. For online students this will involve using the lecture recordings available on vUWS. This is the only face-to-face component of this unit. During the lectures the learning material is presented and discussed, along with announcements regarding assessment and administrative issues. If you miss a lecture it is advised you go through the lecture notes in your own time, and ensure you listen to the recording. If there is a lack of understanding the consultation hours provided by the teaching team should be utilised. It is the responsibility of the student to facilitate a way to catch up on material they have missed because of lack of attendance. The lectures and readings will examine the theoretical aspects related to the three content modules in this unit: (1) Ethics and Professional Code of Conduct, (2) Project Management, and (3) Legal, Social, Environmental issues, Quality Assurance and IT Compliance. The group project and independent learning activities in this unit are designed for you to further research and explore the topics and issues introduced in the weekly lectures, as well as consolidate knowledge from earlier units.
vUWS:
You are expected to consult vUWS at least twice a week: – Access learning and assessment material
– Submit assessments and receive assessment feedback
– Collaborate on the group project
– Check for messages from the teaching team
4
5
2.3 Contribution to Course Learning Outcomes
Key: (I)ntroduced (D)eveloped (A)ssured
3639: Bachelor of Information and Communications Technology
Program Learning Outcomes 1
2 3
4
5
6 I
7
8 9 10
1. Explain the complex networks involved when dealing with people, business and government in the context of ICT D development, support and service provision.
2. Evaluate the technological and software core of ICT theory and practice analysing and designing applications 3. Apply the knowledge and skills required for the development of new applications and new application areas
D
I
I
4. Innovate by keeping up to date with the rapid development in technology and practice across the ICT domain, as an extension of their current understandings and the ability to find innovative ICT solutions and move the ICT field forward.
D
5. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change relating to privacy of information and professional practice.
D I
I
I
2.4 Assessment Summary
The assessment items in this Unit are designed to enable you to demonstrate that you have achieved the Unit learning outcomes. Completion and submission of all assessment items which have been designated as mandatory or compulsory is essential to receive a passing grade.
To pass this Unit you must:
1. Make a full attempt of all the mandatory assessment components (see below), and submit these when they are due
2. Contribute equally to the group project (including the presentation)
3. Submit a progress and final peer review form based on your fellow group members
4. Achieve at least 50% in the final exam
5. Achieve a total mark for the unit of at least 50/100
The mandatory assessment components of this unit are:
a. Module 1 and 2 Tutorial Submissions
b. Group project part A and part B (including the presentation and the peer assessment forms) c. Final exam
Failure to submit ONE or more assessment component may result in a Fail Non Submit (FNS) grade.
Item
Weight
Due Date
ULOs Assessed
Threshold
Tutorial Submissions – Module 1 and 2
30%
Module 1: Ethics and Professional Code of Conduct – due 11:59pm, Friday of week 6. Module 2: Project Management – due 11:59pm, Friday of week 10.
1-6
No
Group Project
30%
Part A: Case Study Email with Questions and a Requirements Specification Document – due 11:59pm, Friday of week 8. Part B: Final Project Proposal including recorded presentation – due 11:59pm, Friday of week 13.
1 – 10
No
Final Exam
40%
In the formal exam period
1 – 10
Yes
Feedback on Assessment
Feedback is an important part of the learning process that can improve your progress towards achieving the learning outcomes. Feedback is any written or spoken response made in relation to academic work such as an assessment task, a performance or product. It can be given to you by a teacher, an external assessor or student peer, and may be given individually or to a group of students. As a Western Sydney University student, it is your responsibility to seek out and act on feedback that is provided to you as a resource to further your learning.
In this unit you can expect feedback 2 weeks after assessment due dates. Informal feedback will also be provided in lectures.
6
2.5 Assessment Details
2.5.1 Tutorial Submissions – Module 1 and 2
Weight:
30%
Type of Collaboration:
Individual
Due:
Module 1: Ethics and Professional Code of Conduct – due 11:59pm, Friday of week 6. Module 2: Project Management – due 11:59pm, Friday of week 10.
Submission:
Online (vUWS – Turnitin). The submission receipt must be kept as proof of submission. A self-plagiarising and maximum similarity index agreement must be reviewed and agreed to before a submission can be made on vUWS.
Format:
Written answers to assessment questions on topics covered in Module 1: Ethics and Professional Code of Conduct, and Module 2: Project Management. Your assessments will be submitted through Turnitin and must be in Word or PDF Format with text being represented as text for Turnitin to process – image based files are not acceptable and will not be marked. For each question, only the question number together with the answer is to be submitted, do not submit the question text. Failure to clearly identify the question numbers and relating answers may result in zero marks for that question, or all questions.
Length:
8-10 pages each module
Curriculum Mode:
Short Answer
Two (2) 8-10 page short answer reports will be submitted for this assessment. Each report is worth 15% and due on different dates over the semester. There will be a set of questions to be answered for each report and from these questions only three (3) answers will be chosen for marking. The three (3) questions will not be known to the students until marks are released.
The answers submitted must be in the students own words, based on the knowledge learned from the required readings and further research. Any answers containing copied material will receive zero marks for that answer and it may result in misconduct investigation being initiated.
Proper academic referencing is an assessable component of these two reports. Failure to correctly paraphrase and reference will lead to a deduction of marks for the assessment. For more information on referencing please visit vUWS and https://library.westernsydney.edu.au/main/guides/referencing-citation. The APA style is to be used.
The two reports are:
Module 1: Ethics and Professional Code of Conduct
This assessment is made up of a series of questions relating to ethics and professional codes of conduct in the ICT industry, professional communication, types of ICT applications and their impact on society and indigenous cultures and ethical decision making in ICT. When answering these questions a focus towards the Australian Computer Society’s professional code should be present.
The questions will be available on vUWS and students must use the lecture notes and recommended readings as a starting point for researching answers to these questions. All questions should be attempted. Answers to be assessed will be selected randomly by the teaching team. Completed answers must be submitted by 11:59pm, Friday of week 6.
The total available mark for this submission is 15%. All work is to be completed on an individual basis.
Note: Hurdle task – Referencing Quiz: Before you can submit your answers to the Module 1 assessment task,
7
you must complete the referencing quiz available on vUWS and gain a minimum score of 15 out of 18. Once you have satisfactorily completed this hurdle task, you will need to agree to the Self-plagiarising and maximum similarity index agreement before you get access to the submission facility. Do NOT leave the hurdle task to the last minute. Failure to complete this in time to meet the submission deadline for module 1 will not be accepted as a valid reason for a late submission.
Module 2: Project Management
This assessment is made up of a series of questions relating to the role of a project manager and the skills required to manage a project, create project proposals, business cases, management of stakeholders, work breakdown structures, estimating and preparing schedules, project monitoring, team work and leadership, and personal project management.
The questions will be available on vUWS and students must use the lecture notes and recommended readings as a starting point for researching answers to these questions. All questions should be attempted. Answers to be assessed will be selected randomly by the teaching team. Completed answers must be submitted by 11:59pm, Friday of week 10.
The total available mark for this submission is 15%. All work is to be completed on an individual basis. Failure to submit any one of these assessments may result in a Fail Non Submit (FNS) for your final grade. Self-plagiarising, plagiarising and maximum similarity index confirmation
Turnitin is an important tool to assist students with their academic writing by promoting awareness of plagiarism. Therefore, before submission of each of these reports a review and confirmation must be conducted by the student on vUWS in relation to self-plagiarising, plagiarising and a maximum Turnitin similarity index. This will ensure the student understands and confirms the following criteria of submission:
– they cannot submit any work previously submitted for any assessment within this unit or another prior to the submission, and if it is found they have, an academic misconduct investigation will be initiated
– an academic misconduct investigation will automatically be initiated if their work has a Turnitin similarity index equal to or greater than 20%
– although their work may have less than 20% similarity index, it will still be assessed individually by the marker for portions of text suspected to be plagiarised and could still lead to a misconduct investigation being initiated
To help meet this criteria and to develop a student’s understanding and awareness of plagiarism a Turnitin Similarity Test Link will be made available on vUWS. The student may submit to this submission link as needed – it is not the submission link for this assessment and no assessments will be marked from this link.
Resources:
Module 1: Ethics and Professional Code of Conduct – Lecture notes and recommended readings from week 1-5 Module 2: Project Management – Lecture notes and recommended readings from Week 1 – 10
For both modules: Referencing quiz for self assessment and guided learning about referencing, available on vUWS
8
Marking Criteria:
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Research, comprehension and relevance to question
The answer to
the question is outstanding and covers all aspects of the
question. It shows extensive research and a very good comprehension of the topic as well as application and relevance of the topic to industry real world scenarios.
The answer to the question is good, covers all aspects of the question and shows comprehension of the topic. Research is shown and the answer is relevant to industry.
The answer to
the question is acceptable,
covers all aspects of the
question and
shows basic comprehension. Some research
has been shown, however the
answer could be improved with more research.
The answer
shows some engagement
with the prescribed readings but
does not cover all aspects of the question or has
parts that are not relevant to the question OR the answer
does not show comprehension of the topic OR there is a
lack of research shown.
The answer is poor from a content point of view and show a lack of engagement with the prescribed readings or
a lack of
research OR the answer shows a lack of comprehension of the topic
area OR
the answer fails to address the
topic in the question adequately or is
inaccurate
Readability and presentation
The answer reads well and has correct spelling and grammar AND the format of the answer document is of a formal standard (incl. answers clearly
presented and numbered, appropriate use of headers, correct font/font size/line spacing as required in the assessment specification).
The answer has spelling or grammatical errors OR the answer text is not structured well (does not read well) OR the format of the answer document is not of a formal standard as required in the assessment specification.
The answer contains an unacceptable level of spelling or grammatical errors OR the answer shows a lack of organisation or clarity in the written expression OR the format of the answer is of an unacceptable and unprofessional standard.
Referencing
Correct referencing (incl. paraphrasing, in-text references and reference list).
(Marks will be deducted) The answer contains some referencing mistakes in the in-text references and/or the reference list.
(Marks will be deducted) The answer is poorly referenced or not referenced at all.
9
2.5.2 Group Project
Weight:
30%
Type of Collaboration:
Group
Due:
Part A: Case Study Email with Questions and a Requirements Specification Document – due 11:59pm, Friday of week 8. Part B: Final Project Proposal including recorded presentation – due 11:59pm, Friday of week 13.
Submission:
Online (vUWS – Turnitin). The submission receipt must be kept as proof of submission. A self-plagiarism, maximum similarity index, and group submission agreement must be reviewed and agreed to before a submission can be made on vUWS.
Format:
The group project assessment will be submitted through Turnitin and must be in PDF Format with text being represented as text for Turnitin to process – image based PDFs are not acceptable and will not be marked.
Each section of the report must be clearly presented within the submitted document. Failure to clearly present section(s) and related content may result in zero (0) marks for that section or all sections.
The final project proposal must also include submission of a recording of the group presenting their proposal.
Length:
Report 25-30 pages
Curriculum Mode:
Report
2.5.2 Group Project
This assessment is a 2 part group based project, resulting in a professional Project Proposal report for a software development project. This type of proposal is similar to what students will do in the capstone unit 300579 Professional Experience.
This assessment is a report style assessment with two deliverables. The final report to be submitted will have a minimum page count of 25-30 pages. To complete this assessment the student must demonstrate their skills and comprehension of business cases, management of stakeholders, work breakdown structures, estimating and preparing schedules, project monitoring, communication, team work and leadership, personal project management, identification of functional and non-functional requirements, legal considerations, and professionalism in the creation and presentation of a professional report.
The assignment specification will give a clear outline of what is required for each part to be submitted, as well as the sections required within the final report. All required sections must be present in each of the submissions.
There are two (2) submissions for this assessment:
1. Part A: Case Study ’Email’ with Questions and Requirements Specification Document (this must be combined and submitted as ONE document – worth 10%): The case study given to a group will be incomplete. To successfully complete the project proposal students are required to formulate and submit up to three (3) questions about their project case study via a professionally formulated ’email’ to the client. The text and formatting of this ’email’ is to be pasted into the requirements document in a separate section of the document. These questions will be answered by the marker in the assignment feedback. When doing this, the marker will be acting as the client. Poorly formulated ’email’ text, and/or poorly formulated and/or irrelevant questions could lead to an unfeasible final project proposal for the client, which will lead to significant loss of marks. The requirements document is a professional document that will outline the objectives for the client’s project from the perspective of the fictional company that the student ’works’ for, and will provide detailed functional and non-functional requirements derived from the assigned case-study. Feedback received from this submission must be acted upon and any changes incorporated into the final project proposal submission (part B). This part is due 11:59pm, Friday week 8.
2. Part 2: Final Project Proposal (worth 20%): Incorporating the information from the answers to the submitted questions, as well as any feedback on the specification document submitted in part A, the group is to submit a professional project proposal report (minimum 25-30 pages in length). The final project proposal report is due on 11:59pm, Friday week 14. Recorded presentation: As part of the final submission for the group
10
assignment, the group must create a presentation of their proposal. This presentation must be recorded and submitted together with part B. All group members must present. The format of the presentation must be professional, as if it was presented to the board. The presentation should be between 5 and 7 minutes long and can be completed using zoom. This task requires communication between the group members which is a learning outcome in the unit. The presentation will be marked based on clarity of communication, alternative solution overview, recommendation and justification for the recommendations.
Notes:
– For both submissions, only 1 group member is to submit the report. See section on ”Self-plagiarising, maximum similarity index, and group submission confirmation” below.
– The title page of the submissions must include the name and student id of all group members.
– All group members must submit individual and confidential peer review forms. This will be done through a submission link on vUWS. Each student will get their individual marks through this submission link. Failure to
submit the peer review forms may result in a Fail Non Submit (FNS) grade as your final grade for this unit.
– The peer review will be used to calculate your individual mark from your group’s overall mark for this assessment.
Your mark may or may not be the same as other members in the group.
The group formation will be done randomly and published on vUWS soon after Census date.
Self-plagiarising, maximum similarity index, and group submission confirmation
Turnitin is an important tool to assist students with their academic writing by promoting awareness of plagiarism. Therefore, before submission of each of these reports (Specification Document and final Project Proposal) a review and confirmation must be conducted by the student on vUWS in relation to self-plagiarising, plagiarising, a maximum Turnitin similarity index and group submission. This will ensure the student understands and confirms the following criteria of submission:
– they cannot submit any work previously submitted for any assessment within this unit or another prior to the submission, and if it is found they have, an academic misconduct investigation will be initiated
– an academic misconduct investigation will automatically be initiated if their work has a Turnitin similarity index equal to or greater than 20%
– although their work may have less than 20% similarity index, it will still be assessed individually by the marker for portions of text suspected to be plagiarised and could still lead to a misconduct investigation being initiated
– The group must agree on which student in the group will be the student that submits on behalf of the group. This student will be the delegate to submit both part A and part B of the assessment. Further instructions on this will be available on vUWS during semester.
To help meet this criteria and to develop a student’s understanding and awareness of plagiarism a Turnitin Similarity Test Link will be made available on vUWS. Students may submit to this submission link as needed – it is not the submission link for this assessment and no assessments will be marked from this link.
Resources:
Lectures and recommended readings from week 1-13.
11
Marking Criteria:
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Part A: Company and Client project objectives
A clear, focused and relevant outline and discussion of the goals and objectives of the case study given. Along with a clear position of the fictional company towards the case study, demonstrating an excellent understanding of the case study, the student’s role, and objectives of the client.
A relevant outline and discussion of the goals and objectives of the case study given, while also outlining briefly the position the fictional company has towards these, demonstrating a very good understanding of the case study and student’s role.
A discussion of the goals and objectives of the case study, and an introduction of the fictional company without an understanding of its position towards the case study.
A summary of the case study is given without further expansion of possible goals and objectives, or the goals and objectives are vague and not aligned with the case study and the fictional company. A lack of understanding of the fictional company’s role is present, or too much focus is on the fictional company instead of the client and the case study demonstrating a lack of understanding of the case study requirements.
A basic summary of the case study is given or goals and objectives are irrelevant or incorrect.
Part A: Email Questions
Questions are professional, demonstrate comprehension of the project case study, and show identification of crucial information not present in the case study to complete a feasible project proposal.
Questions are sensible and have identified basic information not present in the case study to complete a feasible project proposal.
Questions are simple or closed questions, and demonstrate a lack of understanding of the project case study.
Part A: Email Professionalism
Email is professional, with email signature, no use of jargon, and demonstrates empathy and professionalism towards the
client.
Email is informal, does not show empathy toward the client and is essentially just asking questions.
Email does not have a signature, uses jargon, does not introduce themselves or is not an email.
Part A & B: Functional Requirements
A comprehensive set of functional requirements with each consisting of a functional statement, a summary of the function, and excellent justification for the requirement towards the goals and objectives of the project. All requirements relevant to project case study.
A set of functional requirements with each consisting of a functional statement, a summary of the function, and justification for the requirement towards the goals and objectives of the project. All requirements relevant to project case study.
An outline of functional requirements with each consisting of a functional statement, a summary of the function, and okay justification for the requirement towards the goals and objectives of the project.
An outline of functional requirements with each consisting of a functional statement, a summary of the function, and vague or irrelevant justification for the requirement towards the goals and objectives of the project. Some functional requirements identified are not relevant to the project.
Functional requirements given without all of the following for each: a functional statement, a summary of the function, and justification. Many functional requirements are incorrect, incomplete or irrelevant.
12
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Part A & B: Non-Functional Requirements
A comprehensive set of non-functional requirements are present. Each requirement discussed and justified in relation to project case study. Success factors for each requirement is also discussed and given in a quantitative measure in addition to how they will be achieved.
A comprehensive set of non-functional requirements are present. Each requirement discussed and justified in relation to project case study. Discussion on how they will be achieved and given in a quantitative measure is present.
A set of non-functional requirements are present. Each requirement discussed and justified in relation to project case study and given in a quantitative measure.
A set of non-functional requirements are present. Each requirement discussed and justified in relation to project case study.
Only a list of non-functional requirements are present, or list is limited – less than five, or only areas of functional requirements are present, and actual requirements are not defined.
Part A & B: Professionalism in Written Communication
All required
sections are present and clearly outlined. The writing is in a professional tone and not an academic tone, not written like an assignment. Spelling and grammar is excellent. Overall look of the document is at a professional standard. All relevant sections of a basic professional document are present
(executive summary, introduction, conclusion, references as footnotes and/or appendices [if needed]). The executive summary provides a detailed summary of the content within the report. The conclusion summarises the proposal and the recommended solution while presenting next steps.
All required
sections are present and clearly outlined. The writing is in a professional tone and not an academic tone, not written like an assignment. Spelling and grammar is good. Overall look of the document is at a professional standard. All relevant sections of a basic professional document are present
(executive summary, introduction, conclusion, references as footnotes and/or appendices [if needed]). The executive summary provides a detailed summary of the content within the report. The conclusion summarises the proposal and the recommended solution.
All required
sections are present and clearly outlined. The writing is in a professional tone and not an academic tone, not written like an assignment. There are minor spelling and grammatical mistakes. Overall look of the document is at a professional standard. Most of the
relevant sections of a basic professional document are present (at a minimum includes executive
summary, introduction and conclusion). The executive summary provides a basic summary of the content within the report. The conclusion summarises the proposal and the recommended solution.
All required
sections are present and clearly outlined. There are numerous spelling and grammatical mistakes.
Overall look of the document is at a professional standard. All relevant sections of a basic professional document are present
(executive summary, introduction, conclusion) The executive summary provides a basic summary of the content within the report. The conclusion summarises the proposal and the recommended solution.
Not all required sections are present or clearly
outlined. There are considerable spelling and grammatical mistakes.
Overall look of the document is not at a professional standard. The document is missing many relevant
sections of a basic professional document (executive summary, introduction, conclusion). The executive summary is more an introduction to the project than a summary of the content within the document.
13
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Part B: Project Overview
An excellent demonstration of comprehension
of the project problem in relation to the project case study, and an outline of why
and what type
of solution is needed. An outline of
possible
benefits to the core business processes of the project case
study is also present.
A good demonstration of comprehension
of the project problem in relation to the project case study, and an outline of why
and what type
of solution is needed.
A fair demonstration of comprehension
of the project problem in relation to the project case study, and an outline of what type
of solution is needed.
A basic outline
of the project case study with
limited identification of the problem present in the project case study.
Failure to understand the problem within the project case study or reciting the sections of the project case study.
Part B: Key Personnel and Stakeholders
Identification of all possible internal and external personnel and stakeholders. An excellent understanding through justification shown for each personnel or stakeholders role within the project.
Identification of possible internal and external personnel and stakeholders. A basic understanding through justification shown for each personnel or stakeholders role within the project.
Identification of possible personnel and stakeholders. An outline of each personnel or stakeholder role within the project.
Identification of possible internal and external personnel and stakeholders.
Failure to identify major relevant key personnel or stakeholders within the project.
Part B: Alternative Solutions
Three (3) different and feasible alternative solutions are present. Each
one is discussed and outlined at length with the following sections: solution
overview, Resources (Human and Technologies), constraints and assumptions,
an in depth cost benefit analysis, benefits of solution and justification in relation to
project case
study.
Three (3) different and feasible alternative solutions are present. Each one is discussed and outlined with the
following sections: solution
overview, Resources (Human and Technologies), constraints and assumptions,
an in depth cost benefit analysis, benefits of solution and justification in relation to project case study.
Three (3) different and feasible alternative solutions are present. Each
one is discussed and outlined
with the following sections:
solution
overview, technologies to be used, constraints and assumptions, cost benefit
analysis.
Three (3)
different alternative solutions are present. Each
one is outlined
with the following sections:
solution
overview, technologies to
be used, constraints and assumptions,
cost benefit analysis.
Less than three (3) different alternative solutions are present. Each is briefly outlined with missing sections
outlined for a
pass mark or higher or one or more solutions are irrelevant or incorrect for the company or client.
Part B: Recommended Solution
An excellent justification and reasoning for recommended solution, providing a clear comparison of solutions with metrics, showing comprehension and solution application to the project case study.
A reasonable justification
and reasoning
for recommended solution is outlined, showing comprehension and solution application to the project case study.
A discussion of the recommended solution including reasoning for why the solution was recommended.
An outline of the recommended solution without reasoning.
A brief statement or identification of recommendation or no recommendation.
14
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Part B: Project Approach
A release
schedule outlining releases containing each functional requirement completed for each release. A realistic time frame is given and justified,
and a development approach is presented and reason is given
for approach.
A release
schedule outlining releases
containing each functional requirement completed for
each release. A realistic time frame is given, and a
development approach is presented.
A release schedule outlining releases containing each functional requirement completed for each release. A realistic time frame is given.
A release schedule outlining releases containing each functional requirement completed for each release.
A release schedule outlining releases is given without functional requirements for each release present or no release schedule is present.
Part B: Legal Considerations
A detailed comprehension of the legal considerations
that need to be taken into
account when undertaking the recommended solution with reference to various acts
and/or
government policies that
need to be
taken into
account is
present in relation to the
project case
study. An excellent understanding
of the consequences of violating these legal considerations
is also present.
A good comprehension of the legal considerations that need to be taken into account when undertaking the recommended solution with reference to various acts and/or government policies that
need to be
taken into account is
present in relation to the
project case study.
A
comprehension of the legal considerations that need to be taken into account when undertaking the recommended solution with reference to various acts and/or government policies that
need to be
taken into account is present.
An outline of the legal considerations that need to be taken into account when undertaking the recommended solution is present.
Failure to present legal considerations or failure to understand the relevance of the legal considerations for the project case study.
Part B: Quality Assurance
A comprehensive strategy is given discussing valid quality assurance tools and techniques along with relevant standards and procedures with an excellent explanation how these will improve the overall quality of the project.
A detailed strategy is given outlining valid quality assurance tools and techniques along with relevant standards and procedures with a good explanation of how these will improve the overall quality of the project.
A detailed strategy is given listing valid quality assurance tools and techniques along with relevant standards and procedures with a reasonable explanation of how these will improve the overall quality of the project.
A brief strategy is given listing some quality assurance tools and techniques along with some relevant procedures with a partial explanation of how these will improve the overall quality of the project.
A poor or incomplete strategy is given or no standards and procedures given.
15
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Part B: Recorded presentation
The presentation shows excellent communication with the audience, including eye contact and clear speech. Excellent communication and cooperation between group members is evident, and the alternative solution overview, recommendation and justification for the recommendations are clearly
presented showing a well-rehearsed presentation.
The presentation shows good communication with the audience, including eye contact and clear speech. Good communication and cooperation between group members is evident, and the alternative solution overview, recommendation and justification for the recommendations are clearly
presented showing a well-rehearsed presentation.
The presentation shows mostly good communication with the audience, including eye contact and clear speech. Good communication and cooperation between group members is evident, and the alternative solution overview, recommendation and justification for the recommendations are clearly
presented showing a well-rehearsed presentation.
The presentation shows reasonable communication with the audience, including some eye contact and mostly clear speech. Communication and cooperation between group members is evident, and the alternative solution overview, recommendation and justification for the recommendations are clearly
presented showing a reasonably rehearsed presentation.
The presentation gives the impression of poorcommunication with the audience, poor eye contact or muffled or hard to hear speech OR communication between group members seem poor, OR the alternative solution overview, recommendation and justification for the recommendations are poorly
presented OR the presentation is showing a lack of rehearsal or preparation.
16
2.5.3 Final Exam
Weight:
40%
Type of Collaboration:
Individual
Due:
In the formal exam period
Submission:
Via vUWS
Format:
Due to covid, the exam is changed from a 2 hour on campus closed book exam to a 60 minutes quiz via vUWS during the formal exam period.
Length:
60 minutes
Curriculum Mode:
Final Exam
Threshold Detail:
Students are required to achieve a minimum of 50% in this exam to be eligible to pass this unit.
This is an end of session exam that will be completed in the scheduled formal exam period.
The exam will be delivered as a quiz via vUWS. The exam will be 60 minutes long, and is worth 40%, with a threshold of 50%. This assessment is to be completed on an individual basis. Students will receive a mix of minor questions (multiple choice, True/False etc), short and long answer questions from the three modules covered in this unit.
See vUWS for more information.
Marking Criteria:
Criteria / Mark
0%
100%
Minor questions
Student selects inappropriate/incorrect answers
Student selects most appropriate choice
Criteria
High Distinction
Distinction
Credit
Pass
Fail
Short and Long answer questions
Answer demonstrates advanced comprehension of the topic and identifies industry relevance where appropriate
Answer demonstrates thorough comprehension of the topic
Answer demonstrates good comprehension of the topic
Answer demonstrates basic understanding of the topic
Answer demonstrates poor understanding of the topic or is wrong
Resources:
Lectures, assessments and recommended readings from weeks 1-13
17
2.6 General Submission Requirements Submission
– All assignments must be submitted by the specified due date and time.
– Complete your assignment and follow the individual assessment item instructions on how to submit. You must
keep a copy of all assignments submitted for marking.
Turnitin
– The Turnitin plagiarism prevention system may be used within this Unit. Turnitin is accessed via logging into vUWS for the Unit. If Turnitin is being used with this Unit, this means that your assignments have to be submitted through the Turnitin system. Turnitin from iParadigms is a web-based text-matching software that identifies and reports on similarities between documents. It is also widely utilised as a tool to improve academic writing skills. Turnitin compares electronically submitted papers against the following:
– Current and archived web: Turnitin currently contains over 24 billion web pages including archived pages
– Student papers: including Western Sydney University student submissions since 2007
– Scholarly literature: Turnitin has partnered with leading content publishers, including library databases, text-book publishers, digital reference collections and subscription-based publications (e.g. Gale, Pro- quest, Emerald and Sage)
– Turnitin is used by over 30 universities in Australia and is increasingly seen as an industry standard. It is an important tool to assist students with their academic writing by promoting awareness of plagiarism.By submitting your assignment to Turnitin you will be certifying that:
– I hold a copy of this assignment if the original is lost or damaged
– No part of this assignment has been copied from any other student’s work or from any other source except
where due acknowledgement is made in the assignment
– No part of the assignment has been written for me by any other person/s
– I have complied with the specified word length for this assignment
– I am aware that this work may be reproduced and submitted to plagiarism detection software programs for the purpose of detecting possible plagiarism (which may retain a copy on its database for future plagiarism checking).
Self-Plagiarising
– You are to ensure that no part of any submitted assignment for this Unit or product has been submitted by yourself in another (previous or current) assessment from any Unit, except where appropriately referenced, and with prior permission from the Lecturer/Tutor/Unit Coordinator of this Unit.
Late Submission
– If you submit a late assessment, without receiving approval for an extension of time, (see next item), you will be penalised by 10% per day for up to 10 days. In other words, marks equal to 10% of the assignment’s weight will be deducted from the mark awarded.
– For example, if the highest mark possible is 50, 5 marks will be deducted from your awarded mark for each late day.
– Saturday and Sunday are counted as one calendar day each.
– Assessments will not be accepted after the marked assessment task has been returned to students.
– This is consistent with Western Sydney University’s Assessment Policy
18
Extension of Due Date for Submission
Extensions are only granted in exceptional circumstances. To apply for an extension of time, locate an application form via the Western Sydney University homepage or copy the following link: https://www.westernsydney.edu.au/currentstudents/current_students/forms
Application forms must be submitted to the Unit Coordinator/Convenor. Requests for extension should be made as early as possible and submitted within policy deadlines. Appropriate, supporting documentation must be submitted with the application. An application for an extension does not automatically mean that an extension will be granted. Assessments will not be accepted after the marked assessment task has been returned to students.
Resubmission
Resubmission of assessment items will not normally be granted if requested.
Application for Special Consideration
It is strongly recommended that you attend all scheduled learning activities to support your learning. If you have suffered misadventure, illness, or you have experienced exceptional circumstances that have prevented your attendance at class or your completion and submission of assessment tasks, you may need to apply for Special Consideration via the Western Sydney University website. http://www.westernsydney.edu.au/currentstudents/current_students/services_ and_facilities/special_consideration2 or the Student Centre/Sydney City Campus Reception. Special Consideration is not automatically granted. It is your responsibility to ensure that any missed content has been covered. Your lecturer will give you more information on how this must be done.
19
20
3
Teaching and Learning Activities
Weeks
Lecture
Independent
Instructions
Assessments Due
Week 1 08-03-2021
1: Introduction
Module 1 tutorial questions
Week 2 15-03-2021
2: How to succeed in this unit
Module 1 tutorial questions
Release of M1: Module 1
Week 3 22-03-2021
M1 – 3: Professional Communications at work
Module 1 tutorial questions Complete referencing quiz
Week 4 29-03-2021
M1 – 4: Ethics and Professional code of Conduct
Module 1 tutorial questions
Week 5 05-04-2021
M1 – 5: Secruity & Privacy of information
Module 1 and 2 tutorial questions
Release of M2 = Module 2
Week 6 12-04-2021
M2 – 6: Project Management
Module 1 Tutorial Assessment due Friday
– Tutorial Submissions – Module 1 and 2
Week 7 19-04-2021
Q&A session for Group Project
Module 2 tutorial questions Group project
Note: Public Holidays may affect classes this week. More information will be provided on vUWS.
Note: Public Holidays may affect classes this week. More information will be provided on vUWS.
Finalise module 1 tutorial questions
Module 2 tutorial questions
Group project
21
Weeks
Lecture
Independent
Instructions
Assessments Due
Week 8 26-04-2021
M2 – 7: Business Plans and Business Cases
Module 2 tutorial questions. Collaborate on group project. Meet and finalise part A ready for submission.
Group project part A due 11:59pm Friday
Week 9 03-05-2021
M2 – 8: Software Teams
Module 2 tutorial questions. Group project
Week 10 10-05-2021
M3 – 9: Social Issues and Considerations
Finalise module 2 tutorial questions. Group project
Module 2 Tutorial Assessment due 11:59pm Friday
Week 11 17-05-2021
M3 – 10: Usability and Quality Assurance of IT Applications
Group project
Week 12 24-05-2021
M3 – 11: Legal Issues and IT Regulatory Compliance
Group project
Week 13 31-05-2021
Review & Exam discussion
Finalise group project.
Group project part B due 11:59pm Friday
– Group Project
Week 14 07-06-2021
Final Examination Period
– Final Exam
The above timetable should be used as a guide only, as it is subject to change. Students will be advised of any changes as they become known on the Unit’s vUWS site.
4 Learning Resources
4.1 Recommended Readings Prescribed Textbook
Cadle, J. & Yeates, D. (2008). Project management for information systems (5th ed.). Harlow, England: Pear- son/Prentice Hall.
McDermid, D. (Ed.). (2008). Ethics in ICT: An Australian perspective. Frenchs Forest, NSW: Pearson Education Australia.
Additional Reading
Bergland, E. (2016). Get it Done On Time! A Critical Chain Project Management/Theory of Constraints Novel. Berkeley, CA: Apress.
Bolton, R., & Bolton, D. G. (2009). People styles at work– and beyond making bad relationships good and good relationships better (2nd ed.). New York: American Management Association.
Brown, C. (2015). App accomplished : strategies for app development success. Upper Saddle River, NJ: Addison- Wesley.
Cornford, T., & Smithson, S. (2006). Project research in information systems : a student’s guide (2nd ed.). Basingstoke: Palgrave Macmillan.
Gantz, S. D. (2013). The Basics of IT Audit Purposes, Processes, and Practical Information. Burlington: Elsevier Science.
Highsmith, J. A. (2010). Agile project management : creating innovative products (2nd ed.). Upper Saddle River, NJ: Addison Wesley Professional.
Humphrey, W. S. (1997). Managing technical people : innovation, teamwork, and the software process. Reading, Mass.: Addison-Wesley.
Humphrey, W. S. (2005). PSP : a self-improvement process for software engineers. Boston: Addison-Wesley. Humphrey, W. S. (2006). TSP–leading a development team. Upper Saddle River, NJ: Addison-Wesley.
Humphrey, W. S., & Thomas, W. R. (2010). Reflections on management : how to manage your software projects, your teams, your boss, and yourself. Upper Saddle River, NJ: Addison-Wesley.
Jones, C. (2010). Software engineering best practices : lessons from successful projects in the top companies. New York: McGraw-Hill.
Kerzner, H. (2013). Project management : case studies (4th ed.). Hoboken, N.J.: John Wiley & Sons, Inc.
Landy, G. K., & Mastrobattista, A. J. (2008). The IT/digital legal companion a comprehensive business guide to software, Internet, and IP law : includes contracts and web forms. Boston: Elsevier.
Lock, D., & Scott, L. (Eds.). (2013). Gower handbook of people in project management. Farnham, Surrey: Gower Publishing.
Murray, A. P. (2016). The Complete Software Project Manager Mastering Technology from Planning to Launch and Beyond. Hoboken, New Jersey: John Wiley & Sons, Incorporated.
22
Project Management Institute (Ed.) (2013). A guide to the Project Management Body of Knowledge (PMBOK guide) (5th ed.). Newtown Square, Pa.: Project Management Institute.
Remenyi, D. (2012). How to Become a Successful IT Consultant. Hoboken: Taylor and Francis.
Rustad, M. (2016). Global Internet law in a nutshell (3rd ed.). St. Paul, MN: West Academic Publishing.
Solove, D. J., & Schwartz, P. M. (2011). Privacy, information, and technology (3rd ed.). New York: Wolters Kluwer Law & Business.
Straw, G. (2015). Understanding Project Management : Skills and Insights for Successful Project Delivery (1st ed.). London: Kogan Page.
Weckert, J., & Lucas, R. (2013). Professionalism in the Information and Communication Technology Industry. Canberra: ANU Press.
Wright, C., Freedman, B., & Liu, D. (2008). The IT regulatory and standards compliance handbook. Burlington, MA: Syngress Pub.
Zittrain, J. (2008). The future of the Internet and how to stop it. New Haven, CT: Yale University Press.
23