SYSTEMS DEVELOPMENT LIFE CYCLE

SYSTEMS DEVELOPMENT LIFE CYCLE

Chantel MckeeDyan StrausheimAudrey Reitsma

Plan Analyze Design Develop Test Implement Maintain

PLANSystem Requirements

•The system that we are developing is a website for our company, Bikes for Tykes, that will allow customers access and purchase the large variety of merchandise that we offer. •We will need to smoothly manage the website by providing accurate information at all times and clearly and quickly communicate with our customers about new products or special offers that we might have (meaning that we will constantly need to keep the website updated and be available to answer any questions or concerns that customers may have, as well).•We want our website to be easily accessible and usable.

Critical Success Factor•Our website needs to be data-driven.•Must be easily accessible and understandable too customers. •Simple navigation throughout•On-line ordering with on-line payments accepted•Customers can easily contact Bikes for Tykes via phone, fax, e-mail, etc.

Feasibility Studies• For the feasibility studies, the two studies we chose to use are the

following:• Economic Feasibility (cost-benefit analysis): It allows us to

compare the benefits and costs (development and operating) of a system to evaluate its effectiveness.

• Schedule Feasibility: It allows us to ensure that we can constantly keep track of projects, events, etc. and that we meet the requirements for each by the deadline.


Project Timeline/Milestones• December 1, 2012- Project plan and business requirements

completed• December 4, 2012- Database models completed and sent to

programming company• December 10, 2012- Initial prototype completed and ready for beta

testing• December 13, 2012- Database received from programming

company• December 14, 2012- Website completed and ready for system

testing• December 16, 2012- Final product approved• December 19, 2012- User documentation due• December 20, 2012- Launch website and databases to the public


Project Analysis: Business Requirements

1) System must be easy to navigate2) System must have a simple log-in process3) Have an online ordering system and an online payment system4) System should allow us to manage all accounts to analyze business performance5) System should allow us to generate reports based on customer activity6) Allows customers to easily contact the business with any questions, concerns, or comments

Plan Analyze Design Develop Test MaintainImplement

Analyze: Customer Login ProcessThis process allows customers to login if they are already in our database. If they do not enter the correct user ID and password, then they will an error will be read and they will have to retry. If the customer is a new user, then they will be asked to enter in information about themselves, create a login. and become a member in our database. After login is successful, customers will have full access to our website.

Plan Analyze Design Develop Test MaintainImplement


ANALYZE: Customer Order Process This process allows customers to login if they are already members in our database. If they enter the incorrect user ID or password, then they will be asked to retry. If they are not in our database, then they will be directed to the new user page where they may enter information about themselves, become members, and login.Once they have successfully logged in, customers will be directed to our production selection where they can view all of our products and order any product that they would like. Upon ordering our products, they must enter in payment information, and confirm the purchase.

Buy vs. Build• Our company has chosen to buy a commercial-off-the-shelf website rather

than build a website from scratch for the following reasons:– Meets the majority of our needs– Often more reliable. – Takes far less time to implement– Cheaper



Business NameLogo

Login

Create an Account

Schedule a Visit

Catalogue

Fan Page

Contact Us

Locate Us

About Us

Home

Privacy Policy Customer Service

Body

System Model-Website


BIKES FOR TYKES ER DIAGRAMCustomer Reservation

PaymentOrder

Product

Distributor


Login

Create an Account

Home

Catalogue

Schedule a Visit

Product

Add to Cart?

YesNo

Shopping Cart

Continue Shopping

Check Out

Abandon Cart

Fan Page

Contact Us

Locate Us

About Us

Privacy Policy

Customer Service

Recent Purchases

Check Out

WEBSITE NAVIGATION


HOME PAGE PROTOTYPE


PROTOTYPEWhy we chose it

• We chose this prototype because it is user friendly for customers and it allows customers to navigate to their chosen destination with ease. The simple layout helps customers to quickly find the information they are searching for about our company, products, and events.


TESTScreen / Form Tested

Date Tested Home Page November 26, 2012

Tester Tech Specialist

Test Condition Expected Results Actual Results (Circle one)Log into the system Pass Fail

Schedule a visit Pass Fail

Catalogue Pass Fail

Fan Page Pass Fail

Customers can successfully log into the system using a current username/password or are given the option to create one.

The condition is functioning for both accepting current login/password combinations and offering the option to create them.

The system will offer a calendar with appropriate times available for scheduling and process a visit request successfully

The system offers a calendar with appropriate time slots, but does not save the visit currently being scheduled into the system

The system will offer all available issues of our catalogue for online viewing, as well as the opportunity to purchase a subscription

All catalogue issues downloaded quickly and successfully, the process for purchasing a subscription was functioning

Functioning links to social media accounts, a fan wall that allows for comments, and a fan photo slideshow that allows for uploads

All attributes were functioning. The links work, the testing comment posted, and the testing photo downloaded


IMPLEMENTTraining

User documentation will be provided in both hard copy and digital.• Employees will be provided with a hard copy packet that includes images of each page on the website in order to

familiarize themselves with the look of the site. This packet will also contain information as to what each button the website re-directs to. Their will be a troubleshooting section that gives fast questions and answers for employees to utilize during the conversion.

• Employees will be given a power point document that also gives images of the website and quick tips. • Employees will be given a URL to the website with working links in order to familiarize themselves with the website.

This will be available for a week before launching the address to the public.The chosen method for training users is train-the-trainer

• Our website will not be difficult to navigate, so it would be a waste of money and time to hire a trainer to give all employees a workshop, also we are all in the same area geographically so online training is not necessary.

• Managers in each area of the business will be trained on the in’s and out’s of the website. Each manager will then be available to trouble shoot with individual employees.

• We will hold a meeting with managers after 1-2 weeks of running the website to gather feedback

Implementation MethodOur implementation method is the plunge conversion

• We do not currently have an alternate system so the most logical conversion is the plunge conversion.• By using plunge instead of conversion, employees are motivated to learn the system quickly as all phases will be

functioning, thus all departments need to be informed on the site at the same time.• We will have plans in place for responding to a system fail should it occur. Currently our customer base is small, so our

risk is lower than a company with high traffic.


MAINTAINMaintenance Team

There will be an established team in charge of system maintenance• The team will be comprised of one founder, and IT employee, an employee feedback supervisor, and a

customer feedback supervisor• The team will be in charge of creating a help desk for users, this means helping hire employees that will

comprise the help desk and offering those employees support as their supervisors.• The team will be in charge of performing system maintenance when they deem it is necessary• The team will facilitate a healthy environment supportive of feedback from employees and customers.

This means being available for questions, assisting the help desk in outlets for support for users, and continually releasing updates/changes so everyone is on the same page.

• The team will either remain in place as is or replace members as necessary in the future


MAINTAINMaintenance Schedule

We have both a short term and a long term schedule plan• January 1st- April 1st

Daily: A help desk employee will scan the website for errors. All attributes will be tested. Daily: Imaginary purchase orders will be placed to test functionality and payment process Daily: Customer/Employee complaints will be addressed Daily: Updates will be performed Weekly: Check that databases are correct and new customers have been entered

• Effective April 1st

Daily: Customer/Employee complaints will be addressed Weekly: A help desk employee will scan the website for errors. All attributes will be tested. Weekly: Imaginary purchase orders will be placed to test functionality and payment process Weekly: Updates will be performed Monthly: Check that databases are correct and new customers have been entered Quarterly: Data cleansing Quarterly: Generate reports on website

ReferencesLeishman, R. (Artist). Vector of a Cartoon Boy Riding a Dirt Bike [Clip art].

Retrieved November 26, 2012, from: http://vecto.rs/design/vector-of-a-cartoon-boy-riding-a-dirt-bike-outlined-coloring-page-by-ron-leishman-19939

Documents

SYSTEMS DEVELOPMENT LIFE CYCLE