25
06/23/22 02:16 PM Team#2 Bugflow Enhancements 1

Team Members

Embed Size (px)

DESCRIPTION

Team Members. Fan Yang Email: [email protected] Role: Team Leader and Programmer Ashok Kumar Bodepudi Email: [email protected] Role: Research and Development & Programmer. Sridhar Karthik Sethupat Email: [email protected] Role: Webmaster and Programmer - PowerPoint PPT Presentation

Citation preview

Page 1: Team Members

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

1

Page 2: Team Members

Team Members

• Fan YangEmail: [email protected]: Team Leader and Programmer

• Ashok Kumar Bodepudi Email:

[email protected] Role: Research and

Development & Programmer

• Sridhar Karthik SethupatEmail: [email protected]: Webmaster and Programmer

• Raja Praveen BhavanamEmail: [email protected]: Testing and Programmer

04/20/23 01:17 AM

2

Team#2 Bugflow Enhancements

Page 3: Team Members

Mentor & Instructor

MentorScott HetheringtonTietronix Software, [email protected]

Instructor Dr. Kwok-Bun Yue

Professor, Computer Science and Computer Information Systems Chair, Division of Computing and Mathematics

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

3

Page 4: Team Members

Contents

Introduction Existing Application Flow Diagram Requirements Technologies used Demo of the application Detailed requirements with Prototypes Timeline References

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

4

Page 5: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

5

Page 6: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

6

Page 7: Team Members

Flow Diagram

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

7

Saved Defect

Work on Defect

Validate the Defect Solution

Review the rejection

Review/Assign Defect

Accept-Reject Defect

Start

End

Page 8: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

8

Page 9: Team Members

Technologies Used

The Existing application uses

• JSP• SQL Server 2000• Javascript• XHTML• J2EE• Display Tag

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

9

Page 10: Team Members

Demo of the application

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

10

Page 11: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

11

Page 12: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

12

Page 13: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

13

Page 14: Team Members

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

14

Page 15: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

15

Page 16: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

16

Page 17: Team Members

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

17

Page 18: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

18

Page 19: Team Members

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.

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

19

Page 20: Team Members

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

20

Page 21: Team Members

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

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

21

Page 22: Team Members

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

22

Page 23: Team Members

Timeline

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

23

Page 24: Team Members

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/

04/20/23 01:17 AM

Team#2 Bugflow Enhancements

24

Page 25: Team Members

Thank You.04/20/23 01:17 AM

Team#2 Bugflow Enhancements

25