1 / 25

Team Members

Team Members. Fan Yang Email: Yangf1566@uhcl.edu Role: Team Leader and Programmer Ashok Kumar Bodepudi Email: bodepudia2644@uhcl.edu Role: Research and Development & Programmer. Sridhar Karthik Sethupat Email: sethupats4357@uhcl.edu Role: Webmaster and Programmer

guinevere-murphy
Download Presentation

Team Members

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. Team#2 Bugflow Enhancements

  2. Team#2 Bugflow Enhancements Team Members • Fan Yang Email: Yangf1566@uhcl.eduRole: Team Leader and Programmer • Ashok Kumar Bodepudi Email: bodepudia2644@uhcl.edu Role: Research and Development & Programmer • Sridhar Karthik Sethupat Email: sethupats4357@uhcl.edu Role: Webmaster and Programmer • Raja Praveen Bhavanam Email: BhavanamR6349@uhcl.edu Role: Testing and Programmer

  3. Team#2 Bugflow Enhancements Mentor & Instructor Mentor Scott HetheringtonTietronix Software, Inc.scott.hetherington@tietronix.comwww.tietronix.com Instructor Dr. Kwok-Bun Yue Professor, Computer Science and Computer Information Systems Chair, Division of Computing and Mathematics

  4. Team#2 Bugflow Enhancements Contents • Introduction • Existing Application • Flow Diagram • Requirements • Technologies used • Demo of the application • Detailed requirements with Prototypes • Timeline • References

  5. Team#2 Bugflow Enhancements Introduction- What is Bug flow ? • Bugflow is a web-based tool. • It is a process-centric bug tracking tool. • It is developed and used internally by Tietronix.

  6. Team#2 Bugflow Enhancements Existing Application • BugFlow is a Java-J2EE application that runs on the TieFlow Process Automation engine. • It controls routing and status of the bugs. • Each user has a “worklist” that has a list of bugs currently assigned to him.

  7. Team#2 Bugflow Enhancements Flow Diagram Saved Defect Start Accept-Reject Defect Review/Assign Defect Work on Defect Review the rejection Validate the Defect Solution End

  8. Team#2 Bugflow Enhancements Requirements • Add the ability to reopen closed bugs. • Allow users to configure their work lists. • Distinguish between read and unread bugs in the work list. • Save reports. • Segregate some of the global data.

  9. Team#2 Bugflow Enhancements Technologies Used The Existing application uses • JSP • SQL Server 2000 • Javascript • XHTML • J2EE • Display Tag

  10. Team#2 Bugflow Enhancements Demo of the application

  11. Team#2 Bugflow Enhancements Team Progress • Initial hosting of the existing system in the local machines. • Add Realistic data • Study the existing application –code and database • Requirement analysis is completed.

  12. Team#2 Bugflow Enhancements Detailed Requirements-1 • In this an interface is created to allow the administrators to view closed bugs. • An email notification is sent to the supervisor. • Change in the status of the bug.

  13. Team#2 Bugflow Enhancements Detailed Requirements-2 • In this User’s are allowed to select his choice of columns on the worklist. • The user’s choice of worklist configuration is saved in the database. • If no choice is selected by the user the default settings are displayed.

  14. Team#2 Bugflow Enhancements

  15. Team#2 Bugflow Enhancements Detailed Requirements-3 • Work list is like the main page for the user, wherein he can view bugs reported to him. • Many bugs ,user cannot distinguish between read and unread bugs. • Work list -analogous to the email inbox. • Emails-analogous to bugs reported. In inbox we can distinguish between read and unread emails.

  16. Team#2 Bugflow Enhancements Detailed Requirements-3 • Similarly, this requires us to come up with a method to determine bugs –read or new. • Upon discussing -usage of checkboxes and buttons were thought to be a good option. • Maintain sessions!! • This can be achieved by using cookies and databases.

  17. Team#2 Bugflow Enhancements

  18. Team#2 Bugflow Enhancements Detailed Requirements-4 • Enter into the “Reports” tab -- we see a set of twelve parameters that can be selected . • User can save the current selection as public or private. • He should be able to pull his selection from a list and be able to run it.

  19. Team#2 Bugflow Enhancements Detailed Requirements-4 • Solution to this would be to give a pulldown list of existing reports and providing buttons with the option of saving a new report. • Further when these reports are saved they should be able to run each time they are selected.

  20. Team#2 Bugflow Enhancements

  21. Team#2 Bugflow Enhancements Detailed Requirement-5: • Project has –Global and project specific values • Admin has the power to manage project • Interfaces which need modification to segregate global data to project specific data are : • Priority • Severity • Operating system • Software version

  22. Team#2 Bugflow Enhancements

  23. Team#2 Bugflow Enhancements Timeline

  24. Team#2 Bugflow Enhancements References: • http://dcm.uhcl.edu/yue/courses/csci6838/Fall2007/OralPresentation.html • http://www.tietronixproducts.com/tieflow.htm • https://wiki.kubuntu.org/Bugs/WorkFlow • http://www.tietronix.com/

  25. Team#2 Bugflow Enhancements Thank You.

More Related