Bugflow Enhancements 12/26/2015 7:40:43 AM Team#2 Bugflow Enhancements 1 Team # 2 12/02/200 8

 Fan Yang  Ashok Kumar Bodepudi  Sridhar Karthik Sethupat  Raja Praveen Bhavanam  Mentor Mr. Scott Hetherington  Instructor Dr. Kwok-Bun Yue 12/26/2015 7:40:43 AM 2 Team#2 Bugflow Enhancements Team Members

Mentor & Instructor Customer Information  Tietronix Software, Inc.  It is a full-service provider of custom software applications and advanced technology solutions.  Contact Persons  Mr. Scott Hetherington /26/2015 7:40:43 AM 3 Team#2 Bugflow Enhancements

Contents:  Introduction: o Previous work o Bug Flow Process diagram o Technologies Used  Requirements and conclusion o Details and Worked out solution  Demo Praveen Ashok and Karthik Fan 12/26/2015 7:40:43 AM 4 Team#2 Bugflow Enhancements

Introduction- What is Bugflow ? 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 5  Bugflow is a web-based tool.  It is a process-centric bug tracking tool.  It is developed and used internally by Tietronix.Tietronix

Existing Application 12/26/2015 7:40:43 AM 7 6  Bug Flow is a Java-J2EE application that runs on the Tie Flow Process Automation engine.  It controls routing and status of the bugs.  Each user has a “work list” that has a list of bugs currently assigned to him.

Roles: 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 7  User-Anyone who uses this tool  Admin-One who manages Projects  Sys Admin-Who manages Application

Work Flow Diagram 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 8 Saved Defect Work on Defect Validate the Defect Solution Review the rejection Review/Assign Defect Accept-Reject Defect StartEnd

Technologies Used 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements The Existing application uses  JSP  SQL Server 2000  Java Script  XHTML  J2EE  Display Tag

Requirements 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 10  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.

Reopen a new Bug 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 11  Any bug with the status “Withdrawn”, “Closed Unresolved”, or “Closed Resolved” can be reopened.  To reopen a closed bug all the versions of that bug also need to be closed.  If even any “one” version of the closed bug is open  We cannot reopen the bug.

Diagram for Reopen a closed Bug 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 12  R R*

Configure Column list 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 13  In this User’s are allowed to select his choice of columns on the work list.  The user’s choice of work list configuration is saved in the database.  If no choice is selected by the user the default settings are displayed.

Read & Unread 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 14  Work list is like the main page for the user, where in he can view bugs reported to him.  Many bugs, user cannot distinguish between read and unread bugs.  Work list -analogous to the inbox.

Read & Unread 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 15 Bug Reassign Work Item New Bug UNREAD Activity Reject/Assign/St art Working

Save Report Filters 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 16  Enter into the “Reports” tab -- we see a set of ten 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.  Solution to this would be to give a pull down list of existing reports and providing buttons with the option of saving a new report.

Save Report Filters 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 17  The selected values along with the parameter names are saved into database, also considering - the selection is made by admin/user. Selection Admin Private Public Normal User Private

Segregation of Global Data 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 18  Project has –Global and project specific values  Admin has the authority to manage project  Interfaces which need modification to segregate global data to project specific data are :  Priority  Severity  Operating system  Software version

Segregation of Global Data 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 19  We can manage a project by changing Category, Operating System, Priority, Severity, Software version.  When a new data is added it could be a global value and/or project specific value.  Admin can create global data – accessible to all projects and private data – Project specific.  User can create project specific data.

Segregation of Global Data 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 20 Category Operating System Priority Severity Software Versions Global Project Specific DATA

Lessons Learned 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 21  Team work.  Time management.  J2EE, Struts, Display Tag and workflow.

Problems faced 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 22  Installing Bug Flow tool.  Analyzing the existing code and Database Structure.  Narrowing our view –the code that we have to work on.

Project Outcomes: 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 23  Improving the Usability of the tool  Enhancing the functionality –as desired by customer.

Development Team: 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 24 RoleTeam Member Team Leader and DeveloperFan Yang WebmasterKarthik Testing & DebuggingRaja Praveen Research & DevelopmentAshok Kumar ImplementationAll ProgrammingAll DocumentationAll

12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 25 Demo

Special Thanks! 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 26  Dr. Kwok Bun Yue  Mr. Scott Hetherington

References: 12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 27    

12/26/2015 7:40:43 AMTeam#2 Bugflow Enhancements 28