Reference no: EM133840919
Capstone Project
LO1: Enumerate, explain, and analyse stakeholder needs with team members within a multi-specialisation setting.
LO2: Work effectively and efficiently with a team to explain how a multi-stage project can be planned and managed to resolve an organisation's complex problem(s) with the help of a specific specialisation.
LO3: Apply the knowledge and skills acquired cumulatively throughout this award and this unit to establish milestones, plan, design and implement a component or a system in the capstone project working with team members within a multi-specialisation setting.
Assessment Description
Students are required to build a portfolio of assessments every session by working on the task given (at the end of lecture). This will be collated together at the end of the unit in a portfolio or report to assess students' learning experience throughout this unit. To complete this assessment, it is required to attend the class and develop an understanding of the concepts and techniques covered in lectures. Can you do my assignment for me? We sure can!
ULO01: Enumerate, explain, and analyse stakeholder needs with team members within a multi-specialisation setting.
ULO03: Work effectively and efficiently with a team to explain how a multi-stage project can be planned and managed to resolve an organisation's complex problem(s) with the help of a specific specialisation.
ULO04: Apply the knowledge and skills acquired cumulatively throughout this award and this unit to establish milestones, plan, design and implement a component or a system in the capstone project working with team members within a multi-specialisation setting.
Assessment Description
Viva voce (Latin for "by live voice") is an oral examination where a student presents and defends its work before an examiner or a panel of examiners.
Presentation
Interim Presentation and QA
LO01: Enumerate, explain, and analyse stakeholder needs with team members within a multi-specialisation setting.
LO02: Enumerate and explain the gaps between an existing system and a proposed system by working effectively with team members within a multi-specialisation setting.
LO03: Work effectively and efficiently with a team to explain how a multi-stage project can be planned and managed to resolve an organisation's complex problem(s) with the help of a specific specialisation.
LO05: Collaborate with stakeholders to achieve and present outcomes of a project to key audiences.
Assessment Description
All team members to demonstrate:
Project Overview
Project Management Organization, and
Knowledge and a partially advanced application (with developed backend connectivity) or functional discipline-based project, or research project.
Student groups are required to present contents based on their work in progress and respond to individual questions about the project. This assessment is a combination of project showcase, presentation, and QA session. To complete this assessment, it is compulsory for students to attend the presentation day in Session 8.
This is a group assessment. Students are expected to cite using appropriate referencing to support their work.
Detailed Submission Requirements
List of references: this should be formatted in APA.
It is also vital that your work is guided by the marking rubric. Research expectation:
The submission needs to be supported with information by credible sources.
Credible sources should be varied and include, but not limited to, the Journal articles, Conference articles, Textbook, Government reports, Industry reports, and Books.
Use the EBSCO Databases accessed through the Library and Learning Support page.
Use APA referencing including the reference list.
Part A - Presentation
ULO01: Enumerate, explain, and analyse stakeholder needs with team members within a multi-specialisation setting.
ULO02: Enumerate and explain the gaps between an existing system and a proposed system by working effectively with team members within a multi-specialisation setting.
ULO03: Work effectively and efficiently with a team to explain how a multi-stage project can be planned and managed to resolve an organisation's complex problem(s) with the help of a specific specialisation.
ULO05: Collaborate with stakeholders to achieve and present outcomes of a project to key audiences.
Assessment Description
All team members to demonstrate:
Project Overview
Project Management Organization, and
Knowledge and a partially advanced application (with developed backend connectivity) or functional discipline-based project, or research project.
Student groups are required to present contents based on their work in progress and respond to individual questions about the project. This assessment is a combination of project showcase, presentation, and QA session. To complete this assessment, it is compulsory for students to attend the presentation day in Session 8.
Detailed Submission Requirements
List of references: this should be formatted in APA.
It is also vital that your work is guided by the marking rubric. Research expectation:
The submission needs to be supported with information by credible sources.
Credible sources should be varied and include, but not limited to, the Journal articles, Conference articles, Textbook, Government reports, Industry reports, and Books.
Use the EBSCO Databases accessed through the Library and Learning Support page on Moodle to find journal articles, case studies and more to help you prepare your assessment.
Use APA referencing including the reference list.
Part B
Presentation, Showcase, & Report
ULO1: Enumerate, explain, and analyse stakeholder needs with team members within a multi-specialisation setting.
ULO2: Analyse the role of information technology in Business Process Mapping. ULO3: Demonstrate capability in the application of a process mapping tool.
ULO4: Create and communicate recommendations for business process improvement.
ULO5: Collaborate with stakeholders to achieve and present outcomes of a project to key audiences.
Assessment Description
Presentation, Showcase, and QA Session 15% in Session 16 (Moodle Turnitin) In-class.
One student in the team to submit to Moodle a zip file including:
A MS Word or pdf document of 4000-words maximum focusing on mixed specialisation depending on team formation (same or different specialisation). The document must follow the minimum requirements as per each specific type of project:
Industry-based problem/ Business-cased problem: Student groups will propose, design, and implement solutions to a specific industry-based real-world problem based on their client's/lecturer's requirement with a detailed report and user manual containing details such as:
Title page
Table of contents
Introduction
Background
User requirements and project description or as discussed with lecturer
System methodology and described contributions
i) Data pre-processing, modelling technique, building model, analysis, recommendation (if the project is based on data analytics),
Cybersecurity application strategies, testing plans, testing results, contingency plans, solutions, and recommendations (if the project is based on cybersecurity),
website application, UML diagrams, analysis, implementation, test methods.
For other project types, ask your lecturer for specific requirements.
System requirements for installation
Step by step installation process for users
User manual
Minutes of meetings proving the use of one or more project collaboration tool(s) uses, WBS, RACI Matrix, GANTT, Backlogs, Trello Kanban charts, etc.
Research-based problem: Student groups will propose, research and report on real-world problem based on their academic advisor requirements with a detailed technical report conference style report:
Title page
Abstract
Introduction
Literature review
Proposed research/framework/model
Methodology
Experiments
Analysis and recommendations
Conclusions
References
Minutes of meetings proving the use of one or more project collaboration tool(s) uses, WBS, RACI Matrix, GANTT, Trello Kanban charts.
A compressed (zip, tar, rar, etc) file with all project files, source code (if any), and all related files to make your project functional and assessable.
Process, structure, and content:
Guidance is available from your lecturer and from whom you must seek approval for the business problem that you have chosen.
The structure of the project is a 4000-word maximum report. This is as per each specific area of the project.
The report serves as the finalized piece of work for submission and will be assessed according to the rubric provided on the last page. Any ad hoc submissions in alternative formats will not be evaluated.
The word count does not include the table of contents, the list of references or any appendices. However, please note that appendices should be used for supplementary information.
The report content will comprise of the following sections:
Title page: this must contain the title of the report and your names, unit name, unit number and date of submission.
Table of contents (TOC): ideally, but not necessarily, constructed using the hyperlink functions in Word. Lists of figures and tables are not required.
Executive summary: an executive summary provides an overview of the ENTIRE report. It is NOT an introduction section. It is NOT a background section. The purpose of an executive summary is to provide an understanding of the document without having to read the complete report. Ideally, half to one page in length (but no longer), the executive summary will contain a summary sentence or two on each section of the report. Do not use headings or titles in the executive summary; it should be written in essay narrative format and read seamlessly.
Introduction: the introduction informs the reader of the aims and methods applied in the project. It also defines the scope of the project (what is included and what is not). Whilst it may mention the chosen organisation by name, the introduction DOES NOT talk in detail about the chosen organisation or its industry.
Background: a background informs that reader of the context to the project. Here the organisation and its industry are described. Information about the past performance is presented along with any notes about major milestones. It is easy to ‘go overboard' with this section and consume much word count; one page is all that's needed to set the scene for the project.
Moreover, in this and other sections, too many students often over-rely on company websites. Most times, these websites present an organisation's promotions (advertising) or opinions masquerading as facts. Because of the convenience and profusion of this type of information, it is too easy for students to ignore the authoritative sources of data that can be reached through AIH library databases: however, the use of AIH library databases is the way to higher marks!
Methodology: This section highlights the methodologies applied on the given dataset. You need to clearly state a reason as to why they used that technique and provide supporting references especially if the technique is relevant for that particular industry.
Recommendations: The recommendation highlights any key findings from the analyses that would help the business and organisation address areas that can be improved based on the findings. Recommendation sections are usually concise and provide practical advice to an organisation on areas that needs to be addressed.
Conclusions: Through logical reasoning, this section should summarise how the project objectives have been achieved using appropriate business analytics tools and techniques.
List of references: this should be formatted in APA style.
Research expectation:
The submission needs to be supported with information by credible sources.
Credible sources should be varied and include, but not limited to, the Textbook, Government reports, Industry reports, Newspaper articles, Books, and Journal articles.
Use the EBSCO Databases accessed through the Library and Learning Support page on Moodle to find journal articles, case studies and more to help you prepare your assessment. Speak with the library assistants or email.