Your SlideShare is downloading. ×
0
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Brokenpeg
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Brokenpeg

128

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
128
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • JohnHello! My name is John Bain and we are The Armadillos. Our multi-faceted team comprises of expertise in Computer Programming, Web Development, Database and Network Management.On myright/left I would like to introduce you to: (Say Names)Christopher Purdy Database ManagementRyan Giesbrecht Computer Analyst/ProgrammerJesse Favelle Web DevelopmentAmy La Page Computer Analyst/ProgrammerJason Wood Computer Analyst/ProgrammerDavid Bartel Network ManagementAndKyle Kotowich Computer Analyst/Programmer
  • Some of you may be curious about what we Well:We Develop software solutions in close collaboration with our clients in an effort to increase company productivity (pause) this enables us to meet our customers needs. Our main focus is to ensure our products integrate seamlessly with existing systems to minimize the impact of any un foreseen circumstances.With the use of our software and web applications we hope to increase our clients customer base by applying the latest in idea’s and technology. We produce software with the highest level of quality, ensuring minimal downtime and providing exceptional product support and documentation.
  • In this presentation you will hear from each of the team members and a question period is available at the end. I would now like to call upon Chris to discuss our new project.
  • ChrisNEXT….SOME BENEFITS TO THE CLIEINT…
  • ChrisPASS TO RYAN - Phases
  • Broke project down into phases to provide more reliable estimates of time frame and cost.
  • Ryan
  • Ryan
  • RyanThe Deliverable December 10, 2009
  • RyanPASS TO JESSE – Web Front-End
  • JesseIntegrating into the current 311 / City of winnipeg layout The frontend will uses the Google maps api which uses javascript to give the user a map that can be scrolled and zoomed in or out. Users will login into their account and are then able to pick the area from the list at right or directly enter the address. The map will zoom to that location allowing you to pin on the map where the accident is located. You can then pick the type of problem or submit the photo if you have. This loads all the information into a database using php which will send out an email with this data. It will also send a screenshot of the google maps.PASS TO AMY – Administrative Back-End
  • Amy Once the user enters the Request for Service through the website, an email containing all the information is automatically generated and sent to Winnipeg 311.The Email will contain: Email Header – To, From, and Subject containing the Service Ticket #User Info – When the ticket was submitted, and the username it was submitted underService Info – Special comments added by the user, a picture (if uploaded) and the google map indicating the problem location.Modify Ticket – Links to close or report abuse
  • AmyInformation regarding tickets can also be viewed via the administrative desktop tool. Built entirely in PowerBuilderConnects into the Broken ‘Peg databaseAllows the user to do the following:Enter the Ticket Maintenance windowEnter the Search WindowGenerate ReportsAbout the programExit the programWhen the Ticket Maintenance window contains the following sectionsSection that allows input of ticket information to be maintainedStatus Open/ClosedThe user then has the following options:Add TicketDelete TicketUpdate TicketExit Currently Open WindowPASS TO JASON – Risk Analysis
  • JasonWe will develop our system so it is similar to Winnipeg 311’s current systemEmployees will not have to learn a new system, it is just a new method for external users
  • JasonManage timeline by breaking the system into phases (as discussed earlier by Ryan)We will be able to better estimate when each phase will be deliveredLess delays
  • Pictures/Inappropriate Content in TicketsTicket information (including pictures in later phases) will not be displayed until it is approved by an internal user.In terms of internal users interacting with inappropriate ticket content, the client will advise his employees on Winnipeg 311 protocol.PASS TO DAVE – Networking & Database
  • David – Talk about hardware & softwareDistributed services between two servers – allows for expandability and enhanced stabilityServers layered behind a firewall – forwards traffic only for services essential to operation
  • Benefits / Track Record of CentOSSmoothWall BenefitsApache – Proven track record / excellent PHP integrationMySQL – Scalable, enterprise-level DBMSAnd now Kyle will talk briefly about our Use Case Diagrams
  • Kyle-Identified the User’s ability to submit the ticket as the most critical use case. -Submitting ticket triggers the email alert,sets the system into motion.-This process must be quick, efficient, and easy to use.-Feedback will be provided to the User to aid in producing an error-free ticket quickly.
  • Kyle-backend desktop app for administrative use-add ticket, potholes reported via phone, then submit-modify existing tickets that are in the correct state(not in progress, complete, etc)-login, logout to keep track of users(auditing actions)-search and delete, for internal house keeping
  • Kyle-embedded coding in the email process actions performed by the administrator-clicking on a link will trigger an action, auto update status/state of the ticket-can change status to something else manually-view any photos uploaded in a larger view
  • John – Conclusion & Invite QuestionsThank you for giving us the opportunity to show you Broken Peg. The whole concept of making the data open and available is a quickly growing trend. By creating Web 2.0 applications we open doors to greater transparency, participation, and collaboration in an effort to improve services provided by our clients. If you have any further questions we would be glad to answer them (pause) or you can contact us though email at team@winnipeg311.infoNetwork ManagementComputer Analyst/ProgrammerWeb DevelopmentDatabase Management
  • Transcript

    • 1. Presented by:<br />Broken ‘Peg<br />
    • 2. Who Are We<br />
    • 3. Develop software solutions in close collaboration with clients in an effort to increase company productivity <br />Aim to ensure our products integrate seamlessly with existing systems <br />Expand our clients’ customer base through increased web exposure and<br />We produce software with the highest level of quality, ensuring minimal software downtime and providing exceptional product support.<br />What we do<br />
    • 4. What is Broken ‘Peg?<br />Project Goals<br />Benefits to the Client<br />Phases<br />Risk Analysis<br />Prototypes<br />Questions<br />Overview<br />
    • 5. Will be a Web 2.0 application for the Winnipeg 311 system that will allow a user to issue “service tickets” for non-emergency problems through the convenience of their web browser<br />The system will use a graphical map to aid in the process of identifying and locating municipal issues such as: <br />Potholes<br />Sewer Back-Up<br />Water Main Break<br />Roadkill<br />What is Broken ‘Peg?<br />
    • 6. Reduce the volume of calls received by the Winnipeg 311 Call Centre <br />Allow citizens to enter Request for Service tickets via the internet<br />Increasing access to Winnipeg 311 services<br />Allows the public to track government productivity<br />The integration of our system will improve the overall effectiveness of the Winnipeg 311 Service<br />Benefits To The Client<br />
    • 7. Phases<br />
    • 8. Network / Database implementation<br />Web Front-End<br />Consistent with current Winnipeg 311 website<br />Basic Google Maps integration<br />Create ticket with Captcha verification<br />Desktop administration tool<br />Create, update, modify, delete and close tickets<br />Search by outstanding or closed tickets<br />Estimated Time: 6 weeks<br />Estimated Cost: $11,520<br />Phase 1<br />
    • 9. Enhancements to Web Front-End<br />Statistics showing number of open and resolved tickets<br />Account creation<br />Account login and authentication<br />Enhancements to Desktop administration tool<br />Reports by zone or ticket type<br />Email ticket notification / updating<br />Mobile website<br />Estimated time: 4 weeks<br />Estimated cost: $8,640<br />Phase 2<br />
    • 10. Enhancements to Web Front-End<br />Statistics showing average wait time<br />Picture uploading<br />Ability to sort problem flags by type, or ability to focus on a specific city zone <br />Enhancements to Administrative Desktop Tool<br />Search by Full Name or Username of person who reported the ticket<br />Web Administrative Login<br />Help documentation for internal users<br />Estimated Time: 5 weeks<br />Estimated Cost: $9,600<br />Phase 3<br />
    • 11. Enhancements to Web Front-End<br />Ability to view submitted pictures<br />Enhancements to Administrative Desktop Tool<br />Ability to apply ticket prioritization<br />Desktop Widget<br />Mobile Application<br />Estimated Time: To Be Determined<br />Estimated Cost: To Be Determined<br />Phase 4<br />
    • 12. Web Front-End<br />
    • 13.
    • 14. Administrative Back-End<br />
    • 15.
    • 16.
    • 17. Risk Analysis<br />
    • 18. Risk Analysis<br />
    • 19. Risk Analysis cont.<br />
    • 20. Risk Analysis cont.<br />
    • 21. Network & Database<br />
    • 22. Network Deployment<br />
    • 23. Operating Systems<br />CentOS For Servers<br />SmoothWall for Firewall<br />Web Services<br />Apache<br />DBMS<br />MySQL<br />Software<br />
    • 24. Use Case Diagrams<br />
    • 25. Website User Functionality<br />
    • 26. Administrator Functionality<br />
    • 27. Email Recipient Functionality<br />
    • 28. Questions?<br />team@winnipeg311.info<br />

    ×