Defect Tracking System using MVC Architecture

1
Defect Tracking System
using MVC Architecture

• Advisor Dr. Wang, Chung-E
• Department of Computer ScienceCalifornia State
  Univ., Sacramento
• Presenter Rama K Sudireddi
• Date Nov. 08, 2004

2
Agenda

• Motivation
• Model View Controller (MVC) Architecture
• Defect Tracking System
• Legacy Defect Tracking System
• Defect Tracking System - MVC
• Advantages
• Difficulties
• Conclusion

3
Motivation

• Enterprises has to provide consistent/accurate
  data
• to different types of users (web, wireless,
  B2B agents, administrators)
• Legacy applications may embed business logic in
  presentation layer leading to inflexibility.
• Bugzilla (web interface)

4
MVC defined

• Multi tier Paradigm
• Presentation logic (View)
• Control logic (Controller)
• Business logic (Model)
• Each layer can be replaced with out affecting
  other layers
• Analogous to OSI model

5
MVC Architecture
Controller
Client
Request


Forward
Response
Model
View
6
MVC Enterprise System
Web
Admin
Web customer
Wireless customer
B2B Agent
Admini-strator
HTML view
WML view
Swing view
XML SOAP
Enterprise Information System
7
Defect Tracking System

• Provides individuals to request services related
  to software and hardware products.
• Ability to track the progress of their requests
  for bug fixes, enhancements, metric reports or
  new projects.
• Management insight into the work load and
  progress of their projects as ability to assign
  priority.

8
Legacy Defect Tracking System

• Single tier Architecture
• Inflexible
• Hard to maintain
• Suffer Scalability

9
Defect Tracking System - MVC
View
Controller
Servlet
HTML
DB
Request
Submit

Model
Response
Forward
Beans
JSP
10
Advantages

• More Scalable
• Enhances Reliability
• Enable Reusability
• Greater Flexibility
• Easy to Extend
• Clarity of design
• Ease of Maintenance
• Best use of different skill sets

11
Difficulties

• More files to manage
• Significant planning
• Over kill for small applications

12
Conclusion

• MVC architecture provides a best approach for
• the development of enterprise applications
• Taking the time to lay down the MVC architecture
  is worth the payoff

13
Questions

• ?