brokenpeg
DESCRIPTION
TRANSCRIPT
Presented by:
Broken ‘Peg
Who Are We
Develop software solutions in close collaboration with clients in an effort to increase company productivity
Aim to ensure our products integrate seamlessly with existing systems
Expand our clients’ customer base through increased web exposure and
We produce software with the highest level of quality, ensuring minimal software downtime and providing exceptional product support.
What we do
What is Broken ‘Peg?Project GoalsBenefits to the ClientPhasesRisk AnalysisPrototypesQuestions
Overview
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
The system will use a graphical map to aid in the process of identifying and locating municipal issues such as: PotholesSewer Back-UpWater Main BreakRoadkill
What is Broken ‘Peg?
Reduce the volume of calls received by the Winnipeg 311 Call Centre
Allow citizens to enter Request for Service tickets via the internetIncreasing access to Winnipeg 311 services
Allows the public to track government productivity
The integration of our system will improve the overall effectiveness of the Winnipeg 311 Service
Benefits To The Client
Phases
Network / Database implementationWeb Front-End
Consistent with current Winnipeg 311 websiteBasic Google Maps integrationCreate ticket with Captcha verification
Desktop administration toolCreate, update, modify, delete and close ticketsSearch by outstanding or closed tickets
Estimated Time: 6 weeksEstimated Cost: $11,520
Phase 1
Enhancements to Web Front-EndStatistics showing number of open and resolved
ticketsAccount creationAccount login and authentication
Enhancements to Desktop administration toolReports by zone or ticket type
Email ticket notification / updatingMobile website
Estimated time: 4 weeksEstimated cost: $8,640
Phase 2
Enhancements to Web Front-EndStatistics showing average wait timePicture uploadingAbility to sort problem flags by type, or ability to
focus on a specific city zone Enhancements to Administrative Desktop Tool
Search by Full Name or Username of person who reported the ticket
Web Administrative LoginHelp documentation for internal users
Estimated Time: 5 weeksEstimated Cost: $9,600
Phase 3
Enhancements to Web Front-EndAbility to view submitted pictures
Enhancements to Administrative Desktop ToolAbility to apply ticket prioritization
Desktop WidgetMobile Application
Estimated Time: To Be DeterminedEstimated Cost: To Be Determined
Phase 4
Web Front-End
Administrative Back-End
Risk Analysis
Risk AnalysisRisk Probability Consequen
ce Type Mitigation Plan
Team Conflicts Low Medium Mitigation Resolved conflicts and issues internally through open discussions and reasoning
Increased Workflow for city support employees
Medium High Mitigation Develop our product to have a streamlined approach to minimize impact on user workload
Product Integration Issues
Low High Mitigation Analyze current city systems infrastructure and develop our product to interoperate with the existing systems.
Risk Probability
Consequence
Type Mitigation Plan
Loss of system service due to downtime
Low High Transferring
Ensure the client’s existing infrastructure includes redundancy countermeasures to minimize possible risk of downtime
Milestone Delays
High Medium Mitigation Project development broken into multiple phases to provide more concise timeframes and associated deliverables
Change in client requirements
High Low to High Mitigation Establish a system to manage changes in user requirements and negotiate with the client concerning cost and viability of implementing new changes
Risk Analysis cont.
Risk Probability
Consequence
Type Mitigation Plan
Risk to outside users from inappropriate content
Medium High Mitigation / Transferring
Service tickets are not made public till the ticket has been verified by an internal user
Risk to internal user from inappropriate content
Medium Medium Mitigation / Transferring
Client will advise internal users on measures for dealing with inappropriate content in tickets
Possible effects of H1N1 pandemic on development process
Low Medium Mitigation Cross-discipline team to minimize the effect of any absence – regular milestone meetings would advise client of any potential delays
Risk Analysis cont.
Network & Database
Network Deployment
Operating SystemsCentOS For ServersSmoothWall for Firewall
Web ServicesApache
DBMSMySQL
Software
Use Case Diagrams
Website User Functionality
Administrator Functionality
Email Recipient Functionality
Questions?
Team Members Role
John Bain Project Leader / Network Management
David Bartel Network Management
Amy La Page Application Development Leader
Kyle Kotowich Application Development
Ryan Giesbrecht Application Development
Jason Wood Application Development
Jesse Favelle Web Development
Christopher Purdy Database Administrator