1 / 53

Coleman Stewardship Services Website

Coleman Stewardship Services Website. Ashley Cooper Stephanie Locher Matt Schultz Justin Turney. Content of Presentation. Project Plan System Design Implementation Plan Deployment Plan . Project Plan. Project Plan: Environment. Organization:

chione
Download Presentation

Coleman Stewardship Services Website

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Coleman Stewardship Services Website Ashley Cooper Stephanie Locher Matt Schultz Justin Turney

  2. Content of Presentation • Project Plan • System Design • Implementation Plan • Deployment Plan

  3. Project Plan

  4. Project Plan: Environment • Organization: • Coleman Stewardship Services, Inc. manages projects • It is located in Raleigh-Durham, North Carolina • Ted Huskins is the president and CEO

  5. Project Plan: Environment • Business context: • The website will connects to clients and supporters • It will promote the business value of the company. • It will allow easier access to information about Coleman Stewardship Services, Inc.

  6. Project Plan: Boundary • Scope: • A well-designed, professional website to spread their presence • training for the end users

  7. Project Plan: Boundary • What’s In: • The website includes the following pages: • About us • Testimonials • Contact us • Search • Donate • Follow us

  8. Project Plan: Boundary • What’s Out: • The client’s website expectations had to be simplified. • His idea was too complex • PayPal

  9. Project Plan: Objectives • Fulfill the client’s specifications and needs. • Simple • Conservatively professional • Functional • Visually appealing • Readable

  10. Project Plan: Objectives • Business benefits: • Maintain a good reputation • Discover new clients • Improve searchability

  11. Project Plan: Objectives

  12. Project Plan: Stakeholders • Matt Schultz is the team leader • Ashley Cooper is the client liaison • Stephanie Locher is the time/record keeper • Justin Turney was the webmaster • Ted Huskins is the client

  13. Project Plan: Tools & Resources • Labor • We will be building the website • Ted might hire an employee to maintain the website • Facilities • The website is hosted by godaddy.com

  14. Project Plan: Schedule Work Breakdown Schedule

  15. Project Plan: Schedule • Milestones • Project approval = Completed • Project charter = Completed • Design walkthrough presentation = In Process • Project committal report • Project outcome evaluation • Project completion report • Client handover and training

  16. Project Plan: Economic Feasibility • The project is economically feasibly • Breakeven Analysis

  17. Project Plan: Economic Feasibility • Tangible Benefits: • Increase in clients • Intangible Benefits: • Improved reputation • Improved awareness • Tangible costs: • Website host • Maintenance employees • Intangible costs: • Ted Huskins’ time • Team’s time

  18. System Design

  19. Requirements Analysis • USER REQUIREMENTS: • Convey information about the business practices of Coleman Stewardship Services to the WWW. • Provide enough SEO’s for the website • Provide concepts for a logo • Easy to maintain • Easy for navigation – only a few pages needed for now with possibility of expanding the site later • Enable user input to the system

  20. Requirements Analysis • PROJECT REQUIREMENTS (for us): • Half way through our development • Keep on schedule! • Avoidance of scope creep • Keep client happy

  21. Requirements Analysis Requirements Model:

  22. Requirement Analysis Use Case

  23. Process Design DFD – level 1

  24. Process Design Sequence and Communication Diagram

  25. Process Design State Chart –> submitting the form

  26. Logic Design Primitive DFD

  27. Logic Design IF submission is from testimonials page THEN check the box for past client ELSE don’t check box for past client ENDIF Pseudocode Examples: IF form is blank THEN discard form AND show error message ELSE input into database ENDIF IF first name, last name is blank THEN discard form AND show error message ELSE input into database ENDIF

  28. Data Design ERD

  29. Data Design

  30. Class Structure

  31. Software Architecture

  32. Interface Design

  33. Interface Design

  34. HOME PAGE

  35. ABOUT US PAGE

  36. RESOURCES PAGE

  37. TESTIMONIALS PAGE

  38. CONTACT US PAGE

  39. Implementation Plan

  40. Coding Plan • Godaddy.com – HTML (hyper text markup language) • CSS style sheets • This is a style sheet language used to describe the look and formatting of a document that is written in a markup language. • We will use these style sheets to change things like the layout, colors and fonts.

  41. Testing Plan • Alpha: Initial testing by our team, Ted and any other close users/customers. • Beta: Make a beta copy to send to a larger audience to have them test for any issues. • Test cases: performance, load, stability, usability, security, internalization, and localization. • Unit: Test different areas; database, links etc. • System: Test the system as a whole to verify that it has met its requirements.

  42. Installation Plan • Phased Installation Plan: We will be installing this software in phases. • 1st– The first phase we will give it to Ted, our team and any other close users Ted wants. • 2nd – We will give it to many people, half of the clients/users. • 3rd – It will be installed on 75% of the users computers and ready to be used • 4th – It will be installed for 100% of users.

  43. Training Plan • System/user documentation • Very important • Ted not too tech savvy • Maintain site • Online Help • Helpful tool • Links to sites they may need • Charities • Client sites

  44. Training Plan • Training Sessions • Hold a couple training sessions • Train on: • How to use website • Updating website • Maintaining website • Workshops • If we have a workshop it will be in the beginning, we want him to maintain without us after were done.

  45. Maintenance/Support Plan • Time, personnel, helpdesk • Ted can learn • Time consuming • Doesn’t have to pay someone • Pay someone to do it • Cost money • Doesn’t have to learn There will be no need for a helpdesk since these are Teds two options

  46. Maintenance/Support Plan • Business Continuity • Backup/recovery • Go Daddy • Second backup • Mozy

  47. Post Implementation Review • Performed after a period of live running after the project is completed. This review Includes: • Feedback • Evaluation • Change Management

  48. Deployment plan

  49. Deployment • All hosting done through GoDaddy.com • Pages • Database • Backups • Domain name

  50. Client-Server Interaction • Computer with internet • Only requirement • No special software • Only a web browser is needed

More Related