System and method for global group reporting

• US 20060123389A1
• Filed: 11/17/2005
• Published: 06/08/2006
• Est. Priority Date: 11/18/2004
• Status: Active Grant

• Current Assignee: Parasoft Corporation
• Original Assignee: Parasoft Corporation
• Inventors: Kolawa, Adam K., Kucharski, Marek, Hicken, Wendell T., Pilch, Marek Michal, Hicken, Arthur R.
• Granted Patent: US 8,032,863 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 11/3616 using software metrics
• CPC Class Codes: G06F 11/3692 for test results analysis
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A system and method for collecting and correlating information about development of a computer software, including software tools reports. The system and method provides overview of entire software development lifecycle, provides decision support engine for project management, allows estimation of project timelines based upon empirical data, allows evaluation of project quality based upon empirical data, and correlates information from previous projects to estimate progress of current project (confidence factors). The system and method for collecting and correlating information about development of a computer software include collecting data from a plurality of software tools during each point in lifecycle of the computer software; storing the collected data in a database; and correlating the stored collected data to monitor the development of the computer software.

Claims

1. A method for collecting and correlating information about development of a computer software, the method comprising:

collecting data from a plurality of software tools during each point in lifecycle of the computer software;

storing the collected data in a database; and

correlating the stored collected data to monitor the development of the computer software.

2. The method of claim 1, further comprising collecting data from activities of a plurality of assigned roles responsible for the development of the computer software from respective computers of the plurality of assigned roles and correlating the collected data with the collected data from the plurality of software tools.

3. The method of claim 1, further comprising generating a confidence factor from the collected data, and displaying the confidence factor in a graphical user interface (GUI) customized for a respective role.

4. The method of claim 1, further comprising generating a plurality of graphical user interfaces (GUIs) for displaying portions of the correlated data, wherein each of the plurality of GUIs is drillable for displaying more detailed information on a selected data.

5. The method of claim 1, further comprising assessing workload, distribution of tasks and performance of users based on the correlated data.

6. The method of claim 1, further comprising utilizing the correlated data to monitor compliance of an organization with a given regulation.

7. The method of claim 1, further comprising utilizing the correlated data to manage a process of the development of the computer software.

8. The method of claim 1, further comprising utilizing the correlated data to manage quality of the development of the computer software.

9. The method of claim 1, further comprising estimating a completion data of a project based on the correlated data.

10. The method of claim 1, further comprising estimating whether a project is on budget based on the correlated data.

11. A method for collecting and correlating information about development of a computer software, the method comprising:

collecting data from a plurality of software tools during each point in lifecycle of the computer software;

collecting data from activities of a plurality of assigned roles responsible for the computer software from respective computers of the plurality of assigned roles; and

displaying respective portions of the collected data in a graphical user interface (GUI) customized for a respective role.

12. The method of claim 11, further comprising generating a project list and providing access to project status, project timeline, feature requests, and bugs.

13. The method of claim 11, further comprising generating a feature requests graph including the number of feature requests, the number of resolved feature requests, average tendency of reported feature request, and average tendency of resolved feature request.

14. The method of claim 11, further comprising generating a bugs graph including number of reported bugs and number of resolved bugs.

15. The method of claim 11, further comprising generating an average confidence factor graph depicting how the confidence factor is changing.

16. The method of claim 11, further comprising generating a list including a confidence factor for one or more of the group coding standards, performance, bugs, white box test, security tests, files checked in, black box test, maintainability, files compiled, usability, reliability, compiler warnings, integration feature, requests, and modules failed for a specified period of time.

17. The method of claim 11, further comprising generating a code base size graph including amount of code, files, and lines modified for a specified period of time.

18. The method of claim 11, further comprising generating a source code statistics graph including number of revisions made to source control files associated with a specified project during a specified date range.

19. The method of claim 11, further comprising generating a test graph including number of failed, passed, and incomplete test cases for executed tests including coding standards analysis, unit testing, regression testing, and the like.

20. The method of claim 11, further comprising generating a unit test coverage graph including total percentage of code coverage.

21. The method of claim 11, further comprising generating a manual test efforts graph including number of hours a specified tester worked, and amount of manual testing accomplished during the number of hours.

22. The method of claim 21, further comprising generating a manual test efforts table including amount of time spent on manual testing for a selected project and a selected developer, and a test effort by tester graph representing a percentage of a tester'"'"'s manual testing spent on various modules for a specified time period.

23. The method of claim 11, further comprising generating a source code statistics graph including number of revisions made to source control files associated with a specified project during a specified time period.

24. The method of claim 11, further comprising generating a coding standards violations graph including number of violations.

25. The method of claim 11, further comprising generating a test case report providing a means to compare number of errors detected against total number of test cases run during a specified time period, the test case report including total methods, partially tested methods, fully tested methods, methods with possible errors, and methods with errors.

26. The method of claim 11, further comprising generating an errors by severity graph depicting number of errors based on the severity level.

27. The method of claim 11, further comprising generating a coding standard violations details report depicting coding standards violations by violations type, by file, or by developer.

28. The method of claim 11, further comprising generating one or more of a white box test report and a black box test report, each including number of tested files, number of failed files, and number of passed files for a selected time period.

29. The method of claim 11, further comprising generating one or more of a white box coverage graph and a black box coverage graph, each including test coverage of files, actual number of tested units, and number of units need to be tested.

30. The method of claim 11, further comprising generating an integration tests graph including number of integration tests that were incomplete, failed, and passed.

31. A system for collecting and correlating information about development of a computer software comprising:

means for collecting data from a plurality of software tools during each point in lifecycle of the computer software;

a database for storing the collected data; and

a server for correlating the stored collected data to monitor the development of the computer software.

32. The system of claim 31, further comprising means for collecting data from activities of a plurality of assigned roles responsible for the development of the computer software from respective computers of the plurality of assigned roles, wherein the server correlates the collected data with the collected data from the plurality of software tools.

33. The system of claim 31, further comprising means for generating a confidence factor from the collected data, and a graphical user interface (GUI) for displaying the confidence factor.

34. The system of claim 31, further comprising a plurality of graphical user interfaces (GUIs) for displaying portions of the correlated data, wherein each of the plurality of GUIs is drillable for displaying more detailed information on a selected data.

35. The system of claim 31, further comprising means for assessing workload, distribution of tasks and performance of users based on the correlated data.

36. The system of claim 31, further comprising means for utilizing the correlated data to monitor compliance of an organization with a given regulation.

37. A system for collecting and correlating information about development of a computer software comprising:

means for collecting data from a plurality of software tools during each point in lifecycle of the computer software;

means for collecting data from activities of a plurality of assigned roles responsible for the computer software from respective computers of the plurality of assigned roles; and

means for displaying respective portions of the collected data in a graphical user interface (GUI) customized for a respective role.

38. The system of claim 37, further comprising means for generating a project list and providing access to project status, project timeline, feature requests, and bugs.