systems proposal

17
Systems Proposal INFO 361 Section 002 Kweku B. Ocran

Upload: kweku-ocran

Post on 13-Apr-2017

351 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: Systems Proposal

Systems Proposal INFO 361

Section 002

Kweku B. Ocran

Page 2: Systems Proposal

TABLE OF CONTENTS

ORIGINAL SYSTEMS REQUEST .......................................................................................................................... 4

TEAM CHARTER ............................................................................................................................................... 5

BUSINESS CASE ................................................................................................................................................ 8

FEASIBILITY ANALYSES .............................................................................................................................................. 8 COST/BENEFIT ANALYSIS .......................................................................................................................................... 9

USE-CASE DIAGRAM ...................................................................................................................................... 11

CLASS DIAGRAM ............................................................................................................................................ 12

SEQUENCE DIAGRAM .................................................................................................................................... 13

STATE MACHINE DIAGRAM ............................................................................................................................ 14

USER INTERFACE PROTOTYPE SCREENS & TEST REPORT ................................................................................ 14

GANTT CHART…………………………………………………………………………………………………………………………………………….17

Page 3: Systems Proposal

SUMMARY

Pete’s Pawn Shop was a tedious project. His employees and he require a working knowledge of the internet

to conduct business. Pete also needs a complete upgrade of his database and spreadsheet framework to handle

inventory. Pete needs to buff up his security with better cameras and alarms; and a better system to track and report

questionable goods. Finally, the main requirement that this pawn shop needs is definitely its own website. Without

this website, there is no way Pete’s Pawn shop can progress. He has not specified a budget, but it is very limited. The

appraisal cost must be reduced to cut cost, or just find a different appraiser. When a pawn takes place, an employee

must have the knowledge to use this new software. Employees are in charge of recording the pawned item in the

database with the customer’s information. Pete will be in charge of capturing pictures of the item/customer with

additional special functions (i.e. refunding, checking transactions, overriding, and etc.).

Thus far, Pete now has become very technologically savvy with his new system. Security has buffered up

and the ease of the spreadsheets/databases are appreciated. Even Pete’s website access for customers is going well.

The only concern that needs to be watched is his economic feasibility. That will be determined good or bad over

time. An enhancement that can be added later on is, advertisement. At some point Pete’s Pawn Shop will gain more

attention. Manual promo reaches its peak at some point, and needs assistance to push further. Pete can strike a deal

with low-level companies and negotiate placing his pawn shop on their sites. The cost may be worse some at first,

but it will increase his clientele. Increasing his clientele will ultimately increase revenue in the long run.

Page 4: Systems Proposal

System Request

Project Name: Pete's Pawn Shop

Project Sponsor: Peter "Pete" Forthright, owner and chief operating officer

Business Need: Pete's Pawn Shop has been in the pawning business for 30+ years. The business

specializes in jewelry, electronics, furniture and antiques, but other items may be

accepted on occasion. Though Pete has been using a computer for simple tasks such as

word processing, and managing inventory in simple spreadsheets, he has a difficult

time keeping up with the record keeping and the legal requirements, and many

accounting errors have resulted in substantial losses. Pete believes that his business

operations could be made more efficient and effective with the proper information

systems support.

Functionality: The expected functionality includes transaction support for sales, purchases, and

pawning, as well as managing inventory and repeat-customers, provide financial and

legal reporting [stolen property, etc.], and marketing.

Expected Value: Reduce losses due to book keeping errors, reduce cost for clerical support, better

decision-making in offering loans and appraising items, and improve relationships

with customers (new and repeat).

Special Issues or

Constraints: Limited funds for equipment upgrades and software development; limited information

systems expertise; many one-time customers; reporting requirements to identify stolen

goods; need for outside appraisers for some items; two workstations with Internet

access; one external mass storage device; no website, FaceBook or other social media

identity.

Page 5: Systems Proposal

Blah:

The Team Charter

I. Team Members

Kweku Ocran - team leader ~ e-mail: [email protected]

Fernando Nero ~ e-mail: [email protected]

Derrick Freeman ~ e-mail: [email protected]

Corbrina Robinson ~ e-mail: [email protected]

*team jobs fluctuate between every assignment*

II. Team Strengths and Weaknesses

Kweku Ocran - organized, team player/work schedule

Fernando Nero - organized, team player/work schedule

Derrick Freeman - organized, punctual/work schedule, leadership

Corbrina Robinson - very collaborative, willing to be in a leadership role/work

schedule

III. Roles and Responsibilities

Leader - in charge of scheduling meets, planning responsibilities between members,

overseeing what work is done, and making sure that the final work is thoroughly

complete.

Researchers - in charge of looking up relevant, reliable, and useful information to

provide to team members.

Editor - in charge of formatting the work, proof read for any errors to edit and submit

the final work.

Page 6: Systems Proposal

IV. Agreed Upon Meeting Times

One online group chat once a week *no specific day*

Thursdays - 12:30pm-1:30pm

V. A List of Team Rules & Expectations

Come to meets on time unless notice is given ahead of time.

Contribute something to every assignment.

Will receive warning if a member is not contributing/always late. A team decision will

be made if it continues to happen.

If there are any issues with a member, let that member know.

Accountability is key, a member is responsible for whatever assignment they were

given.

Keep all work organized.

Be willing to help and maintain a friendly attitude.

Always…always keep it professional.

VI. A Code of Ethics

Listen and consider everyone’s opinion.

Respect everyone’s ability to grow and improve.

Treat all members and clients with the same respect.

Be Business Oriented and Profitable.

Be Aggressive Risk-takers.

Make sure to balance work & life.

VII. Short Bios

Page 7: Systems Proposal

Kweku Ocran: Is a senior planning to graduate next spring. My major is Information

Systems and I wish to get a job in Application Development or Cloud Computing. I

enjoy music, sports, and traveling. I was raised in Richmond, but hail from Baltimore

as well.

Fernando Nero: is a junior at VCU that is majoring in Business. His expected

graduation date is spring 2016. Fernando currently holds an Associate's degree in

Business Administration. In 2006, Fernando received a full time position at Wyeth

Pharmaceuticals which later transitioned to Pfizer Inc. as a Bulk Manufacturing

Technician. Prior to his employment at Wyeth Fernando was a Customer Service

Representative at the Richmond Downtown Marriott. Currently Fernando works full

time at Fareva Richmond and operates his own management company part time.

Following graduation, Fernando plans to pursue his management company full time.

Derrick Freeman: Is a junior majoring in Information Systems with a minor in criminal

justice. I work residential security and play Ultimate Frisbee in my free time. I want a

career in Cyber Security.

Corbrina Robinson: Was born and raised in Richmond, VA. I transferred from J.

Sargent Reynolds but VCU has always been my dream school. I love dogs and

attending church at Faith Landmarks Ministries. I am quiet and shy at first but once

I’m comfortable I learn to take charge. I lead by example always. I love history and like

to travel. I’m pursuing a master’s degree in Business Administration and plan to

graduate next spring.

Kweku B. Ocran

Fernando Nero

Derrick Freeman

Corbrina Robinson

Page 8: Systems Proposal

Business Case Report

Scope:

Pete’s Pawn Shop is a long standing shop in the Richmond area. Lately Pete’s shop has fallen by the way-

side because of technical and economic changes in the past few years. He has not been able to compete

with other pawn shops and businesses. Peter Forthright must become more technologically savvy in

order to advertise his pawnshop for repeat and new customers. Peter is concerned about funds, but

we’ll keep that in mind while assisting him with his pawn shop. We should have this completed and

implemented within 30 days. Pete needs to have a better system in place for his store and all his

customers. He has not specified a budget but it is very limited. He needs a better system to track and

report questionable goods. The appraisal cost must be reduced to cut cost, or just possibly find a

different appraiser. Tangible costs are expensive, but the intangible benefits will be far more rewarding.

Technical Feasibility:

There are several risks associated with addressing Pete's system request. Pete carries a relatively high

risk level; mainly considering Pete and his employee’s familiarity with the technology. There will be

significant risks upgrading his current software taking into account Pete's budget constraints. He will

also run the risk of a negative return on investment. Addressing the risk can be fairly simple by allowing

users to pretest new software. Employees should collaborate with IT in the development of the new

systems. We’ll be using tools like: GoDaddy for the website, Ultipro for employee payroll, Vector

Security for alarms and cameras, CRM for customer tracking, Verizon for internet access, and social

media. This way everyone will be on the same page with the business plan. An assessment of Pete's

current software will help avoid costly additions towards the end of the project.

Economic Feasibility:

The first year of investment doesn’t seem plausible to go on. It is not until 1.14 years that benefits and

costs break even. The measure of impact is high for Pete’s sake; saving him from errors and better

decision making. Operational costs are the biggest link to the risk though; mostly from

repairs/maintenance, IS support staff, and Ultipro costs fluctuating. Pete can address these risks by

learning more about information and technology or his employees can work with IT staff. That way he

can ease back knowing costs are being managed while maintaining and conducting business at his

pawnshop. Increases in sales is of course a positive with the new improvements and upgrades.

Organizational Feasibility:

Page 9: Systems Proposal

The new system will have a high impact on Peter and his company since the system will save him time

and be more efficient than how he is doing things now which will ultimately save him money. It will have

a low impact on his customers by trying to get them to come back for repeat business. The system will

help the business goals and objectives by helping to manage inventory, accounting and legal

requirements that have been causing Peter errors since he is currently using simple spread sheets, this is

resulting him to lose a lot of money. This system will also help with everyday operation since it will save

time from only using simple spreadsheets by hand. Part of his goal is to also improve relationship with

customers and better decision-making in offering loans and appraising items. The system will have a

high impact on his operational cost and daily operation. It will reduce his operational cost by reducing

errors he made by using simple spread sheets for inventory management and accounting. Peter’s

computer skills will have a low impact because since companies will have support if he is having trouble

with the technology and some things will be automated so he does not have to worry about it. He also

has other employees that can help him even though Peter’s information systems expertise is limited.

Legal and contractual issues are taken care of for the most part by system which will have a high impact

on Pete’s Pawn Shop. It will keep track of all the paper work and send it out. The system will help

prevent him from getting into legal trouble and keeping his record keeping accurate and efficient.

Page 10: Systems Proposal
Page 11: Systems Proposal

Use-Case Diagram

Page 12: Systems Proposal

Class Diagram

Page 13: Systems Proposal

Sequence Diagram

Customer ManagerManager

RequestPawn(category, description)

Appraisal

AppraisePawn(category, description, estimated value)

Item Loan Contract

[AppraisePawn Complete] CalculateLoan(estimated value - interest)

LoanLength()

Pete's Database

ReceiptPrinted()

SignContract()

AcceptLoan?()

LoanTransaction()

UpdateInventory()

UpdateFinancialRecords()

SaveTransaction()

DatabaseUpdated()

TransactionConfirmed()

Pawn Use-Case

Page 14: Systems Proposal

State Machine Diagram

Entering

-ItemDescription+SeekPawn+SellItem+PurchaseItem+BrowseStore

Accepted

-ItemDescription-EstimatedValue+BargainPrice+ContractAgreed

Pawned

-DatePawned-InventoryNumber-ItemDescription+ContractSigned+PawnItem+RedeemItem+MovetoSaleItem

Redeemed

-ItemDescription-PaymentPrice+ReceiptReceived+ItemPurchased

Enters Pawn Shop

Offers

-ItemDescription-OfferedPrice+ManagerContactAppraiser

Offers the owner/manager an"inventory item" as a pawn

Customer

[Appraisal conducted and customer accepts loan]

Sale Item

-DatePurchased-DateSold-BuyingPrice-SalePrice+BuyItem+SellItem

[Contracted time expired]

[Returns within thecontracted time]

Satisfied

-TransactionDate-TransactionType+TransactionRecorded

Item returned after payment is made

[Contract updated to show that the pawn has been satisfied]

A record of the pawned item is created

Usability Interface Prototype Diagram & Test Report

The webpage created for Pete’s Pawn Shop is decent. The homepage advertise the longevity of the shop. Pete’s offer free appraisals. James, one of my fellow classmates said the page for the website was fine but no blank pages. I have critique it was too jumbled. The main menu screen is user friendly and novice users should be able to use with no issues. Singh suggested that add Pawn Inventory Items on the pawn screen but he thinks the website looks good. The testing involves the sales clerk choosing what action need to be done either buy, sell or pawn. The clerk will then enter the customer information into Pete’s Database. The pawn tab will be opened if it is pawn and lead to appraisal tab, then offer will be made to the customer based on the data, then screen will have a choice between accept or decline. If the pawn item is accepted; it will process the payment and will be entered as pawn and then calculates payments as well as

Page 15: Systems Proposal

loan amount. A customer that wants to sell an item the clerk will choose the SELL tab and then appraisal, an offer is made and ACCEPT OR DECLINE is chosen, and if item is accepted it will lead to an inventory screen and added to Pete’s inventory system; if declined it will return to the home screen. A customer that wants to buy an item, the clerk will hit the BUY tab, the items are scanned and clerk go to PAYMENT tab and amount and correct form of payment is chosen and a receipt is printed. The item is removed from Pete’s store inventory system.

Page 16: Systems Proposal
Page 17: Systems Proposal