6. 6
Business Case Analysis
Thomas’ House of Antiques & Treasures
Technical Feasibility (low-to-medium risk)
Familiarity with application (low)
• This is an entirely new system that THAT is unfamiliar with. They will need to be
trained on proper use of the labeling system, use of Wordpress for item updates,
the new registrar system and website; as well as QR codes and use of the
application in the maintenance phase.
• THAT can have their old registering system as a backup if problems occur on the
website or the application.
• The website will use Wordpress to allow for easy GUI-based management and
updates for THAT’s staff.
• The Business Squad consultants will familiarize themselves with use of the new
system and technology to properly train the employees at THAT.
• The Business Squad will have to learn new programming and design techniques
to properly implement the system.
Familiarity with Technology (moderate)
• THAT has moderate experience with technology. Thomas has some computer
experience, and his employees are familiar with using PCs to manually register
users and store financial data.
• The staff does not have the expertise to design a new system or perform
advanced troubleshooting on the system implemented. THAT will rely on the
ongoing and continuing support of The Business Squad to patch and make
modifications to the system.
• Consultants at The Business Squad have moderate-to-advanced experience with
website integration and fair experience with application development and
database management.
Project size (moderate)
• Business Squad estimates that the project will be initially moderate in size but
will expand as the application is adapted and perfected.
• Eventually, Business Squad hopes to expand the project to open consumer use
so that THAT’s customers and employees may access item information and data
through the combination of QR codes and an application, browse items and
track their own consignments.
• However, to begin with; the website will be used by employees to track items,
customers and purchases, and by customers to register for auction and browse
items before night of sale.
• Long term maintenance, upgrades, expansions and upkeep of the new system
will be provided by The Business Squad to THAT.
7. 7
Economical Feasibility (Medium Risk)
Please see attached spreadsheet for details.
The THAT project was designed to help Thomas track items before, during, and after
auctions, as well as keeping information about bidders.
Tangible costs and benefits
• 104% ROI over a five year period
• Total benefits after five years amounts to $749,991.92
• Decrease the number of miscounted and lost items
• Reduce printing expenses
• Reduce postage expenses
• Increase customer base
Intangible costs and benefits
• Improve customer service
• Improve THAT staff’s efficiency
• Improved how information is received by bidders
• Increased interaction with bidders
Organizational Feasibility (Excellent)
Project champion:
• Falon LaRose, Project Manager
Management:
• There is strong support from the THAT and project sponsor, Thomas.
Project Consultant:
• Jessica Morris, Information Systems Major at VCU
Users:
• The users will be the different types of bidders that the auction house interacts
with: new, preferred, absentee, telephone, and clients.
• The THAT staff that includes: four office staff members, one auctioneer, and the
list of temporary employees,
• It is expected that all bidders and THAT staff will enthusiastically use the
proposed system and benefit from it.
Other Stakeholders:
• The original owners of the items that are for sale
Additional Comments
• Rent a server when needed to reduce costs instead of investing in owning a new
one, begin using a small shared hosting plan
• The website will be hosted by an external host (WordPress)
11. 11
Use Case Scenario Narratives and Flow of Events
Use Case: Register to Bid
Actors: New and Old Bidders
Purpose: Collects the information needed from the Bidder and
registers them for the auctions.
Flow of Events: 1. Bidders go online to THAT’s website.
2. Bidders will then either create a new account or log into
their existing one.
3. Once the Bidders have logged on their accounts, they
will click the link to register to bid.
4. Bidders will then input their information and click
submit.
Use Case: Generate Bid Number
Actors: New and Old Bidders
Purpose: Generate bid numbers for the Bidders in an efficient
manner.
Flow of Events: 1. The website will receive the Bidders information.
2. It will then generate a bid number for the auction the
Bidder registered for based on the other bidders who have
already registered.
3. Once the bid number has been generated, it will notify
the Bidder of their bid number.
Use Case: Send Information
Actors: New and Old Bidders, New and Old Sellers
Purpose: To update Bidders on current and upcoming auctions, and
give them more information about THAT.
Flow of Events: 1. Bidders create/log on to their account.
2. Bidders will input an email/update their current email.
3. Once the website has their email on file, the bidders will
receive emails about current auctions they are registered
for, upcoming auctions, and important information about
THAT.
Use Case: Change/Add User
Actors: New and Older Bidders, New and Old Sellers
Purpose:
Flow of Events:
12. 12
Use Case: Register Items to Sell
Actors: New and Old Sellers
Purpose: Collects inventory item information and groups them
together for auctions.
Flow of Events: 1. Sellers go online to THAT’s website
2. Sellers either creates a new account or logs on to their
existing account.
3. Sellers input and submit the information about their
auction item.
4. Once the Sellers
Use Case: Track Items
Actors: QR Code System, New and Old Sellers, and Temporary
Staff
Purpose:
Flow of Events: 1. Auctions items arrive to THAT.
2. The Temporary will use the QR Code System to log the
item in.
3. Once the item has been scanned into the system, the
item will be stored away until the auction.
Use Case: Tag Auction Items
Actors: Temporary Workers and QR Codes System
Purpose:
Flow of Events:
Use Case: Authenticate User
Actors: Web Server
Purpose:
Flow of Events:
Use Case: Store User Data
Actors: Web Server
Purpose:
Flow of Events:
Use Case: Store Item Data
Actors: QR Code System and Web Server
Purpose:
13. 13
Flow of Events:
Use Case: Display Action Information
Actors: Web Server
Purpose:
Flow of Events:
Use Case: Place on Bidders List
Actors: Office Staff
Purpose: To keep an updated list of Bidders who will be attending
the auctions.
Flow of Events: 1. Once the Bidder has registered for an auction, the Office
staff will be notified.
14. 14
Non-Functional Requirements
Operational
Definition:
The technical and physical environments in which the system will operate
Behavioral Properties:
● The system will begin as browser-based allowing it to be flexible and
multi-platform
● Website will be hosted by a mid-tier webhost off site
Performance
Definition:
The reliability, speed, and capacity of the system
Behavioral Properties:
● The system tags will be uploaded in 10 seconds or less
● Update weekly
● Weekly backups
Security
Definition:
● Those who have access to the system under these circumstances
Behavioral Properties:
● Only employees can set tags
● Only the users of the website can create a login user ID and password
for the new website, which will allow them to access their
purchases/selling history
● Only individual users and THAT staff can access individual user data
● No category 1 data will be stored
Political/Cultural Needs
Definition:
● Cultural, legal requirements, and political factors that affect the
system
Behavioral Properties:
● No special cultural and political requirements are anticipated at this
time
49. 49
date. During in-person meetings, a group member should always create an online copy
that is a summary and outline of the meeting. Google documents are the official and
important records of our projects throughout the semester. Google Drive participation
is mandatory and acts as a direct form of attendance.
Code of Conduct
1. Keep a positive attitude toward the team, individual members, projects and
course.
2. Make criticisms constructive with suggestions for improvement and
nonjudgmental language
3. Do the work that has been assigned to you. Don’t push your work off to another
team member because you decided not to do your part. If you need help, please
ask.
4. All project team members confront issues directly and promptly.
5. Project team members have the responsibility to notify any potential difficulties
in meeting the schedule for any assigned tasks as soon as it is known by the team
member.
6. Each project team member is responsible for ensuring anticipated workload
conflicts with other assignments are brought to the attention of the project
team. Team members should ask for help if feeling “stuck” or falling behind the
schedule instead of waiting for a miracle.
7. All team members are responsible to own, followup and provide updates on the
assigned task (including but not limited to any identified risks, issues, changes,
approvals, clarification from professor). If any delay is observed, see vote policy.
If a noticeable or impacting amount of delay is observed, the team willnotify the
professor requesting an F for group member. The group member agrees to this F
as part of this team charter.
Decision Making Procedure:
Consensus is required on all major team decisions. Responsibilities are to be assigned in
the beginning of the project. Because most of the meetings occur virtually, an
acceptable way of assigning duties is through Groupme or email. Once the team
member has been notified through Groupme or email, they have 48 hours to either
accept or reject provided they have a better alternative and it equates to an equal
workload.
Team Communication
All team members maintain their contact info on the team contact list with contact
preference. The main forms of communication for this team are GroupMe, email,
Google Drive. Each project team member is responsible for ensuring anticipated
workload conflicts with other assignments are brought to the attention of the project
