Systems development life cycle
This presentation is the property of its rightful owner.
Sponsored Links
1 / 19

Systems Development Life Cycle PowerPoint PPT Presentation


  • 76 Views
  • Uploaded on
  • Presentation posted in: General

Plan. Analyze. Design. Systems Development Life Cycle. Develop. Test. Dirt Sport Custom. Implement. Maintain. Plan. Project Plan. Analyze.

Download Presentation

Systems Development Life Cycle

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Systems development life cycle

Plan

Analyze

Design

Systems Development Life Cycle

Develop

Test

Dirt Sport Custom

Implement

Maintain


Systems development life cycle

Plan

Project Plan

Analyze

System Requirements – We are developing a company website. We need a place for customers to go to view and order our products and services. We also need somewhere for customers to visually manipulate their desired customizations. We set up a website that allows for customer log in and member functions. This site includes access to company videos, information, product viewing and ordering, and manipulation of customer’s own designs and ability to view former customers customizations.

Our critical success factors are a fully functional data-driven website, quality service, quality products to meet the needs of our customers and optimize revenue.

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Project Plan cont.

Plan

Project Feasibility – We used economical and technical feasibility studies to assess our project feasibility. We chose these two studies because we wanted to assure first off that we could afford the website in accordance with its costs and we wanted to be sure the website would integrate well with our current organizational structure.

~Cost-Benefit Analysis: We would gather all the relative data to the estimated cost of the website and estimated revenue the addition of the website would add to our company. We then would compare these two figures on the whole and in specific parts to identify if the website benefits would outweigh the costs.

~Technical Feasibility Study: We would look at the requirements of building and implementing this new website and the effects it would have on the company. We would then compare this to our company’s current ability and resources and ensure that we could actually accomplish the website as desired.

Analyze

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Project Plan cont.

Plan

Analyze

Milestones

Dec. 1 – All analysis and feasibility tests completed

Dec. 4 – All necessary resources gathered and prepared

Dec. 12 – Have website ready for beta testing

Dec. 20 – Have all beta testing finished

Dec. 25 – Have final programming ready to implement

Dec. 31 – Website Operational

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Plan

Analysis – Business Requirements

Analyze

The website allows customers to easily view and purchase custom parts.

The customer can easily understand and navigate the process of making or choosing and saving their own custom bike designs.

Customer information can be effectively tracked and stored starting from login and going to logout.

The website efficiently allows customers to set up appointments with our staff and allows us to track our appointments.

The website provides all necessary and desired information about our company, bike part installation, and bike customization to our customers.

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Process Diagram: Website Login

Plan

Analyze

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Process Diagram: Website Login

Plan

When the customer enters our site the will immediately have the option to login with an already existing account or a create a new one. A returning customer will just have to provide their valid user ID and password to login and their email and all former information will then be accessible to them. A new customer will have the option to create an account by providing a new user ID, email, and custom password. All customer information from this specific part will be stored in the Customer and Product database. After a customer has logged into our website they will have the two main options of looking through our custom parts or looking at our custom designs. If a customer chooses to browse products any information they save to the website will be logged in the Customer and Product database. If a customer chooses to look at custom designs any information they save here will be stored in the Design database. A customer may then chose to log our or just exit our website.

Analyze

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Process Diagram: Product purchase and design.

Plan

Analyze

Design

Develop

Test

Implement

Design database

Maintain


Systems development life cycle

Process Diagram: Product purchase and design.

Plan

Analyze

After logging in, a customer can chose to design customizations. Once they enter this section of the website they will have three initial options: pick a bike component, pick a general design, or pick design specifics.

If they chose ‘pick a bike component’ they will be shown a diagram of their desired dirt bike model and they will be able to chose which component they would like to build their custom design for.

If they chose ‘pick a general design’ they will be allowed to look through general possible designs that our staff have suggested or that former customers have made.

If they chose ‘pick design specifics’ they can start their own designs from scratch. This option also allows them to modify general designs that they picked earlier.

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Process Diagram: Product purchase and design cont.

Plan

Analyze

All three of these options can be gone back and forth in between to allow for changes at any point along the process. At any point along the process the customer may chose to save or cancel their design. If they cancel they will automatically be taken back the start of the design products page. If they save they will be asked if they want an email notification or if they want to set up an appointment to have the design done and applied. After they select they can either return to the design products page or home page.

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Plan

Analysis – Build vs. Buy

Analyze

We have decided to go with a build approach rather than buy. We chose to do this so we could customize our website as desired. We have a lot of odd parts like custom part ordering and bike design customization which require a unique combination of website elements. We wanted to be sure that the elements we wanted to have were included and connected as desired. We also use our website to work with several other independent companies and we wanted to be assured the we could modify our dynamics to best fit with our partner companies.

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Plan

System Model - Website

Analyze

Logo

Design

Business Name

Home Login Order Products Design Products Videos

Develop

Body

Test

Implement

Contact Us

Directions and Hours

Privacy Policy

Maintain

History

About Us


Systems development life cycle

Plan

ER Diagram – Customer and Product

Analyze

ORDER

CUSTOMER

Design

Develop

CUSTOM PARTS

PAYMENT

Test

Implement

DISTRIBUTOR

Maintain


Systems development life cycle

Plan

System Model - Navigation

Directions and Hours

Analyze

Privacy Policy

About Us

Company History

Contact Us

Design

HOME

Login

Videos

Order Product

Design Product

Develop

Chose product

Chose Design

Test

No?

Yes?

Yes?

No?

Implement

Place Order

Save Design

Maintain

Continue Browsing?

Return Home?

Continue Browsing?

Return Home?


Systems development life cycle

Develop – Homepage

Plan

Analyze

Design

Develop

Test

Implement

We chose this design because it was very simple and yet neat. It is very clear and flows well, which makes it easier for our customers to navigate and use. This design also effectively houses all of our desired elements in a well set and easy to read and understand pattern.

Maintain


Systems development life cycle

Testing

Plan

Analyze

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Implementing

Plan

  • We will use the Plunge Conversion because we have a small number of employees that adapt quickly to changes and diving right into using the new system will reduce our costs.

  • We will use the Train the Trainer method. Our small number of workers will become the trainers. As our company grows and expands, our number of workers will also increase. The current employees will become a reliable source for teaching new personnel that start at our company.

  • Our form of user documentation would be a Word document, that serves as a user manual, will be saved on all employees computer. With this document always on your computer, it makes it quickly accessible. With Word’s ability to search for key phrases or words, time looking for certain information can be cut down and problems can be solved at a much faster rate.

Analyze

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Maintaining

Plan

  • Adaptive and corrective maintenance: To insure that our website is always up to date and at it’s best performance, we will perform scheduled maintenance every Tuesday at 9 p.m. PST. This will include testing links and updates. Also, we will have a F.A.Q. section where customers can view common problems and submit questions, of which will be reviewed during maintenance.

  • Preventive maintenance will include annual updates to software that strengthens our system and reduces the chances for system failures.

  • Perfective maintenance: Monthly online inventory scans to figure out what the top selling products is in order to promote them more.

Analyze

Design

Develop

Test

Implement

Maintain


Systems development life cycle

Maintenance schedule

Plan

  • December 1st – December 31st

  • Weekly scans on software

  • Bi-weekly scans for bugs that identify and fix bugs that are harming the system

  • Once a week “Training the trainer” sessions

  • Starting January 1st

  • Quarterly full system scans

  • Weekly scans on software is continued

  • Answer customer questions every Tuesday with scans

  • Monthly inventory scans

  • Annual updates to software

Analyze

Design

Develop

Test

Implement

Maintain


  • Login