IT 216 GMU What Are Potential Risks Involved in The Fairfax Town Project

This is a group project I need just part 3 donePart 3 Preliminary Analysis of your solution [10 points]

1)

Critically analyze the solution proposed:

a. What Are potential risks involved in the implementation of your project?UseaFishbonediagram to provide

examples of potential risks. Include at least three different factors (eg.: quality, time, costs, etc.) and two examples for each factor (eg: the performance is too slow, the time for completion of each activity is underestimated, the budget for programmers is insufficient). 1.
This is a group exercise that would normally be done in class. You will use your project groups to
complete this assignment, creating 1 submission for the group.
Using the Perfect Pizza Scenario – prepare and submit a document with the following information:
List the students who participated in the Class Exercise (I recognize that some students
might not respond, but please give everyone time to respond to proposed meeting times)
Respond to each of the items presented within the document which includes:
○
○
○
2.
A list of the entities and logical / business processes your group believe apply (5
points)
A Context Level Data Flow Diagram (DFD) based on your response to the list of
entities and processes (5 points)
A Level 0 DFD based on your Context level diagram (10 points)
Perfect Pizza Scenario
Perfect Pizza wants to install a system to record orders for pizza. When regular
customers call Perfect Pizza on the phone, they are asked their phone number. When the
number is typed into a computer, the name, address, and last order date is automatically
brought up on the screen.
Once the order is taken, the total, including tax and delivery, is calculated. Then the order
is given to the cook. A receipt is printed. Occasionally, special offers (coupons) are
printed so the customer can get a discount.
Drivers who make
deliveries give customers
a copy of the receipt and
a coupon (if any). Weekly
totals are kept for
comparison with last
year’s performance.
—————————————————————————————————————————–
Entities-
●
●
●
●
Phone Number (customer)
Perfect Pizza (Team)
Cook
Driver
Process names:
(1) Find and display customer record
(2) Take customer order
(3) Send order to cook
(4) Print customer receipt
(5) Deliver customer order
Data stores:
(1) Customer master
(2) Product file
(3) Coupons
(4) Sale history
a) Find and display customer record.
• Input is the customer number and the customer record.
• Output is customer information.
b) Take customer order.
• Input is the order information (including the customer number).
• Output is the total amount due for the order.
c) Send order to cook.
• Input is the customer order.
• Output is the cook’s order.
d) Print customer receipt.
• Input is the customer order and the customer master record.
• Output is the customer receipt.
e) Deliver customer order.
• Input is the customer receipt and coupons.
• Output is the delivered receipt to the customer.
Customer
Perfect
Pizza
Cook
Driver
PART 1: DEFINING THE PROBLEM
1. We’ve designed an activity and class registration system for the Fairfax Town Community Center
to assist people with the enrollment process.
a. Domain: Community Center Manager
b. Scope: Mobile and Computer Application
2. In relation to our goals and motivations, four problems that we’ve encountered during our
research are: Complicated class and event registration menu, many factors to track for each
individual, too much information displayed on one page, and lack of online assistance.
a. An observed issue was that the registration system can be difficult to navigate and
explore due to the variety of classes and events offered in different locations to
members of all ages. While the extensive courses offered can be seen as an advantage,
the main issue derived when a member attempted to enroll but registered in the wrong
location as a result of the system’s complicated registration menu. Another
encountered issue is the unorganized system needed to track each individual’s records.
This had led to private information being mixed up between different members within
the community.
b. Motivations: Improve customer satisfaction, increase website usability, improve
assistance for all users, encouraging more community members to join
c. Goals: One of our main goals is to create a quick and easy process for class, event, and
member registration. Another goal is to increase the overall user experience for current
and new members who are navigating the system and website for the first time.
d. Specific aims: In regards to creating a quick and easy process, users will be able to freely
navigate the system by accessing it through the community center’s website. The
website will be easier to operate with properly organized subsections with their
respective functions. For example, when specifying nearby locations during the
registration process, the system will automate an option with a “Find My Location,” to
search for community centers within the vicinity. For better practice, a confirmation
page will be implemented to overview the registration information, prior to submitting
the official enrollment to avoid any mistakes. In addition, we aim to increase online
assistance with a 24/7 online chat, or over the phone with a representative to aid with
enrollment.
3. Formalized definition of problems
Statement
Issues
Objectives
Requirements
Many factors to track
for each individual
member.
Each member of the
community center
needs to be classified
under many descriptors
such as age, rates,
titles, etc.
Creating a record
system to properly
track the members of
the community center,
their membership
status, and yearly rate.
The record system
established must
ensure clarity and
minimal redundancy
when tracking each
members’ information.
This could lead to
confusion and mix-ups
when needing to
address a certain
member. Information
has the possibility of
being lost or repeated.
Complicated class,
event, and
membership
registration menu
The registration menu
could lead to
unintended setbacks
such as wrong
selections in locations
and events. Having a
complicated user
experience would
decrease customer
satisfaction, which
could discourage users
from continuing their
enrollment and
membership.
Keep the registration
menu short, simple,
and organized to
increase usability.
A simple menu that
allows users to
navigate through
various class and event
offerings.
Too much information
displayed on one page
The website lacks
organization, which
leads to an overload of
information being
randomly condensed in
one page. This
decreases the website’s
usability and the user’s
experience.
Reorganize the
community center’s
website to make each
web page more
accessible and user
friendly.
A straightforward,
clean website design
with accessible links
that lead users to the
intended tab.
Lack of online
assistance
The lack of assistance
could deter possible
members who intend
to enroll.
Users who require
additional assistance in
enrollment will have
the ability to
communicate with a
community staff
member through a
24/7 online chat, or
over the phone with a
representative
Additional staff
members to work the
online 24/7 chat, along
with the customer
service line through
specified hours.
A “Find My Location”
widget will be included
when selecting the
community center
location for higher
assistance.
A confirmation page
will be added prior to
submitting official
enrollment to prevent
mistakes.
A new chat system will
need to be
implemented.
PART 2: DEFINING YOUR SOLUTION
1. Solution:
a. Stakeholders (Mihret’s part)
i.
Board of Directors:- Guide and direct high level strategies for the overall
operation of the community center.
ii.
Community members:- People that reside in the town of Fairfax and are
registered members of the community center.
iii.
Staff members:- People that work inside the center or outside either paid or
voluntarily that oversee the operations at a lower level
iv.
Employees:- Hired by the community center for daily operations to maintain the
Center’s functions like custodial employees, and hired teachers.
b. Components involved in system: (Mihret’s part)
i.
Community member:- focus of the system; will go on to website to register for a
class
ii.
Website (process):- Displays the options of classes available for selection.
iii.
Database system (storage) :- where the record file of the user information is
stored when they sign up.
iv.
Customer service:- a person that answers requested questions to members.
v.
Register (process):- registers the user to a selected class and sends a
confirmation email.
vi.
Confirmation email:- an email that will be sent to the registered user’s account
to confirm their sign up for a class.
vii.
Creating an account (process): the user will create an account to be able to sign
up for classes.
c. 10 use-case scenarios:
Use Case Scenario
Feature and Functionalities of the Proposed
Project
Check Community Center User Profile
The user will be able to click on a “User
Profile” button that will send them to either
a “Login In” page or a “Account Information”
if they are already logged in.
Register for Community Center Classes
The user will be able to click on a “Register”
button that will send them to the
appropriate webpage that will allow the user
to browse and select the classes or programs
they will want to take throughout a given
time period.
Contacting the Staff
The user will be able to select a “Contact”
button that will send them to the “contact
list” page which will display all of the
appropriate information involving the
community center. Phone numbers, emails,
staff name, and staff titles.
Becoming a member
The user will click on a bottom that will send
the user to a webpage that will allow the
user to “upgrade” their account in order to
provide exclusive benefits based of their
criteria.
Community Center store
The user will click on a “Store” button that
will send them to the appropriate web page.
This page will consist of an online store and
catalogs of items the user can buy from the
community center.
Checking locations
The user will click on a “location” button and
similar to the “Contact”, will send the user
to a web page containing all the information
related to the facility and the related
buildings to it. Information such as maps,
addresses, and nearby landmarks will be
included on this page.
Checking for events
The user will click on the “events” button
which will bring them the “Scheduled
Events” page. This page will project a visual
calendar that will highlight specific events
being held by the community center during
those times. Events such as classes, special
holiday events, and community center fairs
will be displayed.
Checking general information about the
community center
The user will have all the general
information displayed to them on the
website’s home page. This information will
contain the operating hours and current
events going on that day. This page will also
have a general “about us” statement
explaining the brief history of the center.
Browsing the gallery
The user will click on the “gallery” button
that will navigate them to the “gallery” page.
This page will contain a variety of pictures
posted by the community center staff. Each
picture will have a short title or description
to give the user context.
Checking the current news
Users will click on a “news” button directing
them to a webpage containing all of the
current news relating to the community
center and the general area around it.
d. Workload table:
Existing System
Proposed System
Task
Display information about
the community center for
the users.
Cater information for each
specific user based on their
member status while
continuing the simple
streamline information the
previous system provided.
Method
No system in place to help
track user’s and their
member status.
All users will be asked to log
in or create an account to
properly track and manage
their information and
membership status.
Personal
Users and staff members
Users and staff members
When and how
No system to implement a
proper timeline in which
information would be
updated.
Daily: News for current and
upcoming events will be
posted on the front page of
the website.
Monthly: the event calendar
for the entirety of the
month will be updated
accordingly so users can
plan out in advance to
attend certain future events.
Human Time Requirements
The amount of time
required of a physical
human’s interaction was
estimated to be none or
unknown due to the lack of
an established community
center tracker
Daily: 10 minutes
Monthly: 20 minutes
Computer time
requirements
Daily: est. 10 minutes
Monthly: est. 20 minutes
Daily: 10 minutes
Monthly: 20 minutes
e. Requirements:
Hardware
● Operating System – one that can support the website on either MacOS or Windows 10.
○ This OS would also allow the website to run on an Android or IOS.
● Connectivity – The Community Center Tracker will need access to the internet access for
both the user’s convenience and easily accessible data for the staff.
● Physical Computer – A computer or smart devices is needed to access this community
center website and therefore will need the previous stated internet access and OS
requirements as well as needed memory and download speed in accordance.
Software
● Applications within the website pages such as videos or animations might require the
user to download the appropriate media player.
● Latest drivers and updates must be met so ensure that everything on the website is able
to run properly.
● If the website is being displayed on a mobile device all updates must be met for that
device as well.
● Third party applications might hinder some of the website’s applications and may be in
detriment when using them in tandem with the website.
Personal
● Time for the user to use the physical website and time for the staff to keep the website
up to date.
● Cost for the website upkeep and domain.
● User’s and staff must be able to user the appropriate browsers to access the website
● Color’s, images, and videos’ handled by the staff must comply with regulations in order
to provide a family friendly and enjoyable experience.
PART 3: PRELIMINARY ANALYSIS OF YOUR SOLUTION (Bobby’s part)
1. Analyze the solution proposed:
a. Potential Risks: