Project title: cloud based customer relationship management
Minimum 30 references
Chapter-3 Related academic and commercial research
3.1.1 case study 1 (case study should be industrial based like sap, google, amazon case study of customer relationship management) (www.featuredcustomers.com) consult this site for case study.
3.1.2 conclusion
3.1.3 Finding
3.1.4 summary
3.2.1 case study 2
3.2.2 conclusion
3.2.3 finding
3.2.4 summary
3.3.1 case study 3
3.3.2 conclusion
3.3.3 finding
3.3.4 summary
3.4 Theories
3.4.1 justification
3.5 framework
3.5.1 justification
Chapter-4 Research methodology 17
4.1 Project Methodology 17
(for this project we have used agile and scrum methodologies)
4.1.1 Comparison with other methodologies 18
4.2 Research design 18
4.2.2 Data collection method 18
4.2.3 research approach 19
Chapter-5 Discussion of Project 20
5.1 Discussion of project 20
5.3 Testing and strategies 23
5.3.1 testing strategies 23
5.3.2 Testing types 23
Chapter-6 Findings. Limitation and Recommendation 24
6.1 findings 24
6.2 Limitations 24
6.3 Recommendations 24
7.Conclusion 26
ES Project Brief for Belfield Service Centre
Role
Name & Title
Signature
Date
Sponso
Super Use
Project Manage
Version Control
Ref#
Date
Key Updates
Version 0.1
4/2/20
Initial draft
Project Definition
Client:
Belfield Service Centre
4 Carter St, Belfield NSW 2191, Australia
https:
www.belfieldservicecentre.com.au
Background
Belfield Service Centre (BSC), can take that classic old car and have it looking as good as it did the day it rolled off the lot. From the exterior to the engine, transmission and chassis, from major servicing to replacing a simple part, it does it all. The company policy is to provide outstanding service to customers. However, due to its growing customer base the company would like to build a Client/Service Management System.
Project Objective
This Project aims to capture BSC’s business requirements in order to build a cloud based Client/Service Management System. The solution must serve as a single source of truth for effectively managing the Client Information & service schedules with reporting capabilities.
Desired Outcomes
· Understand the BSC’s business requirement and document the processes to implement proposed Client Management Solution in Cloud.
· The new system must be scalable and easily adaptable to changing requirements.
· The Client/Service Management system developed is easy to use in maintaining & managing Client details, Service Management, Service Schedules, Bookings & Loyalty details based on the repeat profile of the customers.
· There should be integration from the Client Management system to capture details about the customer from social media channels with consent for marketing campaigns.
· Customers must be able to book servicing through the online portal.
· The booking information captured through the online channels must sync with the calendar scheduling.
· Fast easy to use cloud powered business analytic services or alternative reporting.
Project Scope
Inclusions:
1. Design of the system should be Secure, durable & scalable with an object storage platform
2. Project documentation for the system process requirements
3. The information system should be able to perform the below functions:
· Client Management
· Service Management
· Integration through custom APIs for social channels
· Track Service booking schedules
· Campaigns
· Analytics & Reporting
4. Information management & reporting for managing the below functions
Client Management
· Client Profile, Manage Contact Details, Service Profile
Service Management
· Service Job records, Fleet Management
Booking/Scheduling
· Manage Bookings, Service Scheduling
· Create Integration with the online channels for Customers to make service bookings online
Reporting
· Multidimensional Reporting capability on all data entities
· Reporting and dashboards analytics
Constraints and Assumptions
· Alternative workable solution needs to be provided if any deviation from any of the points of the desired outcomes
· Performance tuning of the system needs to be performed in the wa
anty period
· Penetration and or security recommendations will be provided at the end of the project
Project Tolerances
· TBD
Key Users
· Admin/Management Use
· Service Manage
· Service Users
Interfaces
· Integrate with Social Media channels through public APIs to source client details (Subject to consent from the client) for marketing campaigns.
Project Structure
· Project team should determine the structure and internal roles according to Methodology chosen.
Project Write-Up
ITECH7415-Masters Project
(Percentage: 45%, Due Date: Week 13/14)
The Project Write-Up is the conclusion of the project’s work. The objective of this document is to provide comprehensive and detailed information regarding the work undertaken by the project team, and should include a description of the product(s) created as solution(s) to the project problem. Students should determine the structure of the Write-up, whilst incorporating the recommended content.
The recommended length of the report is 10,000 words.
The most important criteria is that the project has been well documented in the Write-Up. Particularly, academic aspects such as an elaborate literature review and description of adopted methodologies/approach must be emphasised. Products developed can be included as Appendices.
The report should include ALL aspects of the project and ALL students in a group are expected to take an active role in writing-up.
Submission and Marking Guidelines
· The Project Write-Up should be written following the university guidelines for writing. (A link to this is included in the Footer)
· The Project Write-Up should be submitted via Turnitin by one member of the team.
· The Project Write-Up should be included in each student’s Mahara ePortfolio page
· Alongside the Project Write-Up, each student should include in the portfolio page, a 10-15 minute video reflection documenting his/her participation project.
· Please note that this is an important part of this assessment task. It is the student’s responsibility to convince assessors of his/her contribution to the project. Reflections should include:
· Justification of contributions as per skillsets and time allocated to projects.
· Description of the largest 3 contributions. Evidence should be included in the video.
· Unique things you did/learned. Story of your contributions..
· Ideas to improve the course – what you liked the most and least
· If your reflection does not reveal much understanding, clarity, and contribution to the Project’s products and process, you will be awarded less than 100% of the team’s mark as below:
Student demonstrates a high level of understanding, clarity, engagement, and contribution - 100%
Student demonstrates high level of understanding, but insufficient engagement and contribution – 75%
Student demonstrates low understanding and low engagement/contribution – 50%
Student demonstrates no understanding and little or no contribution – 0%
Group Name:
Student 1 Name/ID: XXXXXXXXXXStudent 2 Name/ID:
Student 3 Name ID: XXXXXXXXXXStudent 4 Name/ID:
Content
Allocated Marks
Awarded Marks
Overall Presentation and Quality of the Document
Is the report well written, with good grammar, sentence, and paragraph construction?
FedUni presentation guidelines (link in Footnote) must be adhered.
3
Problem Statement
Is the project problem clearly explained? Are the relevant stakeholders co
ectly identified?
Are user stories specified with acceptance criteria included?
2
2
Project Objectives
Is the aim of the project clearly stated to align with a solution to the project problem?
2
Related Academic and Commercial Research
Is a structured review of relevant literature presented?
What conclusions are drawn from the review of relevant literature?
How does the literature inform the proposed product as solution to the project problem?
What relevant theories, perspectives, or frameworks has been adopted to address the project problem? Is justification provided for the selected theory/framework?
3
2
3
3
Project Approach
Explanation of project approach, its application in the project, and specific tasks undertaken in development of the product.
5
Discussion of Product(s)
Comprehensive description/demonstration of the product developed
Results and findings from product testing/evaluation as per acceptance criteria
5
5
Summary, Limitations, and Recommendation
What are the applications of the product?
What are the limitations of the product?
How might the product be improved?
2
2
2
References
Are references relevant?
Are they co
ectly cited and listed?
2
2
Total
45
Comments & Feedback :
https:
federation.edu.au/__data/assets/pdf_file/0017/190043/General-Guide-to-Layout-and-Appearance.pdf
CRICOS Provider No. 00103D
School of Science, Engineering
and Information Technology
School of Science, Engineering
and Information Technology
School of Science, Engineering
and Information Technology
School of Science, Engineering
and Information Technology