PayBackTM

1
PayBackTM

• By Max Aller, Jason Salameh, Alex Odle, Chen
  Lee, Douglas Copas, Ian Struiksma

2
Overview

• System architecture
• Team Structure/Schedule
• Risk assessment
• Test and documentation plan

3
System Architecture

• Microsoft Server Architecture
• Four main components
• IIS Server
• ASP.NET Framework
• C Business Logic
• MS SQL Server

4
System ArchitectureAdd an expense
5
Team Structure

• PM
• Alex
• Business Layer
• Alex
• Ian
• Max
• Chen
• UI
• Jason
• Doug

6
Payback Schedule

• May 4th UI beta done
• May 7th Code beta done
• May 10th Beta 1 milestone
• May 15th Add Beta 2 features
• May 17th Beta 2 UI
• May 19th Code for Beta 2 implemented, feature
  set finalized
• May 22nd Beta 2 finalized
• May 30th Final version replaced

7
Risk Assessment
Risk Chance of occurring (High, Med, Low) Impact if it occurs (H,M,L) Steps taking to increase chance it wont occur Mitigation plan should it occur
Page load/data access is too slow Med High Use efficient SQL and Business Logic Run profilers to determine bottlenecks
Time constraints Low High Frequent team meetings, constantly review milestones Cut back features, reallocate resources
UI is too complicated Med High Talk with customers Allocate more resources towards improving design. Work with customers
8
Test and Documentation Plan

• Testing
• Unit testing
• System testing
• Usability
• Bugzilla
• Documentation
• Site walkthrough
• FAQ

9
Conclusion

• Robust system architecture
• Feasible schedule
• Aggressive risk prevention
• Comprehensive test plan and documentation