1. Project insights using mining software repositories
Hemant Pandey (Senior Software engineer)
Ridhi Jain (Senior Software engineer)
Adobe Systems

2. Abstract
Source control repositories, bug repositories, test artifacts repositories are most commonly available for most software projects.
The Mining Software Repositories (MSR) field analyzes and cross-links the rich data available in these repositories to uncover interesting and actionable information about software systems.
By transforming these repositories from static record-keeping ones into active repositories, we can guide decision processes in modern software projects. For example, data in source control repositories, traditionally used to archive code, could be linked with data in bug repositories to help practitioners propagate complex changes and to warn them about risky code based on prior changes and bugs.
We present possible application areas of mining software repositories and an way that helps to identify inter module dependency and critical areas (most bugs taking into account frequency and impact, bugs after ZBB etc.).

3. System design & implementation

4. Use case scenarios -1
Individual Contributor (Developer/Quality Engineer)
Recommend possible locations for change
Bug hotspots - Critical files that result in multiple failures very frequently
Propose expected module which causes failure (Integration with Testing Frameworks) – Test cases failures are fixed by some CL.
Commit log (CL) analysis - It also has valuable information e.g. which changes are similar, which issue is fixed by CL
Integration with knowledge management system
Integration with defect tracking system
Recommend required test suites to be run for a given set of changes in source code

5. Use case scenarios -2
Team Leads/Manager
Stakeholders contribution/Owner/Reviewer
Issues prioritization
Reporting
Understanding Team Dynamics
Integration/System bugs: Bugs filed after code freeze, their impact and resolution.
Timeline of change: Timeframe of breaks and their respective resolutions. Certain bugs like near the release date (higher weightage), etc.

6. Author Biography
Hemant Pandey (Author) is contributor in Adobe Systems Noida as a part of Core Technologies & Products team. He has experience in software development, testing specially automation frameworks, source code static analysis, dynamic instrumentation, system migration to new technologies. Working experience in SDLC i.e. SRS creation, designing systems, coding, unit testing, performance testing in waterfall model as well as Agile. Currently, working on Bug tracking/fixing process improvement as a one of the key area. In this work, intent of author is to minimize lifecycle of bug in different phases by using historical data.

7. Co-Author Biography
Ridhi Jain (Co-Author) is contributor in Adobe Systems Noida as a part of Core Technologies & Products team. She has experience in manual and automation testing.

8. Thank You!!!