Professional Documents
Culture Documents
Executive Summary
Introduction
Vision
Mission
Case Background
Organizational Background
Organizational Chart
Corporate Culture
Stakeholder Analysis
Team Reflection:
Summary:
Milestones
Milestone 1: Overview
References
Appendices
Introduction
The primary objective of this project is to explore and examine how Lamborghini uses AWS to
have a competitive advantage from others. The group members will be able to understand the
business requirements, functionality and steps to implement an enterprise system. The group will
start from the strategic planning phase to execution to gasp a holistic approach for
implementation.
Case Background
Lamborghini wanted to upgrade their technology infrastructure and evaluated multiple solutions
to design, implement, and integrate. They decided to use AWS because it met all the
requirements they were looking for. Utilizing AWS will help Lamborghini to maintain
competitive advantage.
Milestones
Milestone #1 – September 22, 2019
Milestone #2 – October 6, 2019
Milestone #3 – October 20, 2019
Milestone #4 – November 3, 2019
Milestone #5 – November 24, 2019
Organization background/summary/vision/mission
Lamborghini is an automotive company that is known for producing high-end performance cars.
They were founded in 1963 by Ferruccio Lamborghini, and are headquartered in Sant’Agata
Bolognese, Italy. They are known for hitting several milestones in the car industry such as when
Diablo held the title of the world’s fastest car at one point. Also, when Lamborghini released a
limited-edition Aventador J which earned the title of “Best of Show” at the 2012 Geneva Motor
Show. This title made the Aventador J so desirable to customers, that Lamborghini had reached a
new record for traffic on their website.
This new record, however, would reveal to Lamborghini that their website was hosted on
outdated infrastructure that was also at the end of its lifecycle. Between the infrastructure being
poorly optimized, high cost of maintenance, and not scalable, the companies’ new initiatives had
suddenly become much more difficult. Lamborghini then considered 3 ways to solve this which
were implementing a data center that costs a lot, uses a local provider that doesn’t offer
scalability, and cloud computing. They ended up going with cloud computing and used AWS as
their architecture. This proved to work very well for them as the website was able to support the
new traffic numbers.
Organizational Chart
Culture Summary
Lamborghini seeks to maintain a fair and transparent environment in their workplace. They have
an official ethic code that each employee is required to follow in the company as they continue to
produce high cost products. Their shared values are intended to guide the decisions they make as
a company and how they work with collaborators. The ethics code also has a massive emphasis
on ethnicity as Lamborghini strictly states that they want equal treatment of all ethnic groups. In
addition to all of this, Lamborghini has a dedicated whistleblower system in the event that a
higher up in the company should be reported for wrongdoing. There are several available
channels for employees to report and this system is intended to maintain the image of the
company.
It is expected that the team will work together in all parts of the project to some extent. Our core
values for this project are respect, patience, time, and integrity. All perspectives from all team
members will be considered before a final decision is made. Any breach of values will result in
proper disciplinary action.
Stakeholder Analysis: A stakeholder analysis includes using both internal and external
perspectives in considering the actions, roles, and outlook of customers, partners, sponsors, IT
systems, and etc.
External Stakeholders:
Internal Stakeholders:
Employees - Employees are people who work for the company such as website
designers, IT, marketing professionals, salespeople, and etc. All these people should be analyzed
when considering the company. Communication with employees are extremely necessary for a
good work-flow and mission alignment. Employees take on day to day roles in the business such
as selling cars or updating inventory. Although all employees are not involved in the project they
can often influence it.
Team Reflection:
Diana Chowdhury:
Overall the goal of this project was a great success. I have learned a great deal about
project management and how to apply what we learned in real life. I find it very valuable to have
learned UML and feel confident in making diagrams now. In general this taught me real world
application, time management, and lastly how to lead a team to success.
Robert Sonnelitter:
These milestones for the most part have gone quite well. The team was usually willing to
communicate what we needed to do and how we would get it done. Each time we started a new
milestone, the work would be divided up evenly amongst each of the group members based
primarily on preference. Outside of how we handled the work, I found that what we worked on
gave me more insight into talking about systems integrations, and how companies handle these
kinds of topics.
Alair Moody Daniels: The project was extremely successful because we divided the work
equally and everyone was responsible for their work and diagrams. This group project taught me
a lot about use case and activity diagrams. I learned how businesses use these diagrams to depict
how the user will interact with the systems. Also, I learned how to create these diagrams that can
help me in the real world.
Grant Hart:
I felt as if this project went well. Everyone did a good job of following the deliverable
and putting their best foot forward. The content was consistent with the class materials. I have a
new understanding of how data and technological aspects can be represented with specific
language and diagrams. This project taught me the importance of communication across the
board and I am thankful for that.
Summary:
Milestone 1: Overview
In the first milestone our tasks included setting up meeting locations, scheduling remote
meetings, a decision on which collaborative document to use and lastly means of
communication. We decided to use Google Drive as our collaborative document and group me as
our primary means of communication.As a group we decided Lamborghini due to an
appreciation for cars and lastly we developed our project plan to be efficient and split up the
work.
In the second milestone, we created an use-case diagram that shows the actors and relationships
for Lamborghini. In each attribute we included how each use case how the user interact with the
system. In this milestone, we gave a holistic overview of how the system will work. We created
use case diagrams that will have different functionalities that users can do on the system. For
example, we have use cases for ordering a car and placing a maintenance request.
In the third milestone, we created activity diagrams that were based off the use-case diagrams.
The activity diagrams created a more indepth user interaction with the system. The activity
diagram helps depicts the workflow from start to finish.
In Milestone 4, we created descriptions for each of the use cases that we created in
Milestone 2. These descriptions provided a more in depth look at what we included in our
diagrams. They provided information such as the flow of events, the relationships of the
elements, triggers, and the case name. This would allow us to show how these use cases would
come into play and what would occur during them.
Milestone 5 primarily involved the creation of our sequence diagrams. We based these
off of our activity diagrams for what to describe, but obviously the sequence diagrams depicted
different information. The activity diagrams showed a more simple step by step process, while
the sequence diagrams show a more code oriented approach. They showed who the actor was,
what objects were involved, and what messages would be sent and received. This allowed us to
create a visual for if we were to give a developer a more technical look at what is expected.
● More clear feedback on results including need of connecting milestones to each other
● Have a few more relevant examples and how they are connected to the content
References:
Use Case Name: Order Car Parts ID: 1 Importance Level: Low
Primary Actor: Mechanic/Supplier
Stakeholders and Interests:
Car Manufacturer, Car Dealer, Lamborghini, Parts mechanic supplier
Brief Description: The functionality of this use case is to depict the flow process of ordering car parts
when placed.
Trigger:
When a maintenance order comes in the Lamborghini has to order the parts for the order.
Relationships:
Include: Maintenance Details, Authentication
Extend: (N/A)
SubFlows:
S-1:
1. Contact parts manufacturer
S-2:
1. Supply Chain of parts for the car
Alternate/Exceptional Flows:
N/a
Brief Description:
This use case is to depict the flow process of scheduling a maintenance appointment.
Trigger: Lamborghini owner needs an oil change, tire rotation, etc.
Relationships:
Include: manage account, load website, host a website, enter maintenance details, authenticate user,
maintenance details
Extend: Schedule maintenance appointment
Normal Flow of Events:
1. Customer accesses website
2. AWS displays website
3. Customer schedules appointment which involves entering details
4. Mechanic logs in
5. Mechanic views appointment
6. Mechanic orders necessary parts
SubFlows:
S-1: Customer has account
1. Customer is able to submit request under their account
S-2: Customer does not have an account
1. Customer continues a guest
Alternate/Exceptional Flows:
N/A
Use Case Description 3
Alternate/Exceptional Flows:
A-1: Lamborghini decides to use new website
1. Lamborghini Developer deletes site
2. Lamborghini Developer creates site
3. Lamborghini Developer uploads site
4. Lamborghini Developer modifies site
Team Members:
Meeting Schedule:
Meeting Attendees Meeting Schedule Meeting Alternate
Channel Communication
Platform
Commitments Section:
Participation: Group members will be expected to attend class meetings, remote meetings, and
if there are valid reasons for missing a meeting they are expected to reach out to the team to get
the information. A meeting log will be created with attendance numbers also being submitted.
Communication: Communication for Team 12 will be through email, phone calls, and
GroupMe. Communication is expected to be reciprocated within 24 hours. Failure to promptly
communicate will result in deliverables taking longer than they should and it should be
minimized. Also, a lack of communication will result in the Project Head being notified and
proper disciplinary action being taken.
Decision Making: Main decision making on deliverables will be made by the team during the
weekly meetings. Any final decisions will be made by the Project Manager Diana. All
viewpoints will be heard and responded to in a respectful and timely manner.
Meeting Log:
This is our potential project plan, we may make changes depending on the circumstance.