RHDB
Release History Database Model
BY: Sundas Shabbir Ahmed
Kaim Khani
Sundas Shabbir Ahmed Kaim Khani 1
Presentation of Software Evolution Topic:
Agenda:
In this presentation my approach for integrating versioning system
information and Bug report data and populating a RHDB.
I will First introduce
• Versioning system and Bug tracking system
(From which we retrieve data)
• Then describe the model behind RHDB.
Sundas Shabbir Ahmed Kaim Khani 2
 CVS
• Is designed to handle revisions of textual information in repository
• Has been most used version control system.
• Currently it is been replaced by Subversion (SVN)
RHDB is based on Version system log file
 Versioning System
• Collect historical information of software.
• Can be applied to both CVS and SVN
• For each versioned file, the log file contains committed data
• Other data may include the version number (or revision), the timestamp,
author, the state , the number of lines added & removed, branches and the comments
Sundas Shabbir Ahmed Kaim Khani 3
Sundas Shabbir Ahmed Kaim Khani 4
 Bug Report
• Bugzilla is a bug tracking system
• keep track of issues detected in the software system
• A l bug report contains the information of:
• id -status (new, assigned, reopened, resolved, verified, closed)
• resolution (fixed, invalid, wontfix, notyet, remind, duplicate, worksforme),
• product & component- operating system & the platform -short description &
list of comments
• The bug reported to the several peoples such as: reporter, assigned to-QA-,
and a list of people interested in being notified of the bug fixing progress (CC)
Sundas Shabbir Ahmed Kaim Khani 5
Sundas Shabbir Ahmed Kaim Khani 6
Sundas Shabbir Ahmed Kaim Khani 7
 RHDB:
• is based on the CVS Versioning System and Bugzilla bug tracking system
Where the link between to sources are built as present in previous slide.
• Stores the extracted version & Bug report.
• was the First to link CVS artifacts an Bugzilla problem reports.
Sundas Shabbir Ahmed Kaim Khani 8
Sundas Shabbir Ahmed Kaim Khani 9
 RHDB Offer Some Benefits
• for Evolution analysis
• Qualified links between changes and bugs
• Files logically coupled via changes and bugs
• Branch. Merge revision data
Sundas Shabbir Ahmed Kaim Khani 10
Other approaches
• Hipikat
• softChange
• Kenyon framework
Sundas Shabbir Ahmed Kaim Khani 11
Sundas Shabbir Ahmed Kaim Khani 12
Sundas Shabbir Ahmed Kaim Khani 13

RHDB Release History Database Model

  • 1.
    RHDB Release History DatabaseModel BY: Sundas Shabbir Ahmed Kaim Khani Sundas Shabbir Ahmed Kaim Khani 1 Presentation of Software Evolution Topic:
  • 2.
    Agenda: In this presentationmy approach for integrating versioning system information and Bug report data and populating a RHDB. I will First introduce • Versioning system and Bug tracking system (From which we retrieve data) • Then describe the model behind RHDB. Sundas Shabbir Ahmed Kaim Khani 2
  • 3.
     CVS • Isdesigned to handle revisions of textual information in repository • Has been most used version control system. • Currently it is been replaced by Subversion (SVN) RHDB is based on Version system log file  Versioning System • Collect historical information of software. • Can be applied to both CVS and SVN • For each versioned file, the log file contains committed data • Other data may include the version number (or revision), the timestamp, author, the state , the number of lines added & removed, branches and the comments Sundas Shabbir Ahmed Kaim Khani 3
  • 4.
  • 5.
     Bug Report •Bugzilla is a bug tracking system • keep track of issues detected in the software system • A l bug report contains the information of: • id -status (new, assigned, reopened, resolved, verified, closed) • resolution (fixed, invalid, wontfix, notyet, remind, duplicate, worksforme), • product & component- operating system & the platform -short description & list of comments • The bug reported to the several peoples such as: reporter, assigned to-QA-, and a list of people interested in being notified of the bug fixing progress (CC) Sundas Shabbir Ahmed Kaim Khani 5
  • 6.
  • 7.
  • 8.
     RHDB: • isbased on the CVS Versioning System and Bugzilla bug tracking system Where the link between to sources are built as present in previous slide. • Stores the extracted version & Bug report. • was the First to link CVS artifacts an Bugzilla problem reports. Sundas Shabbir Ahmed Kaim Khani 8
  • 9.
  • 10.
     RHDB OfferSome Benefits • for Evolution analysis • Qualified links between changes and bugs • Files logically coupled via changes and bugs • Branch. Merge revision data Sundas Shabbir Ahmed Kaim Khani 10
  • 11.
    Other approaches • Hipikat •softChange • Kenyon framework Sundas Shabbir Ahmed Kaim Khani 11
  • 12.
    Sundas Shabbir AhmedKaim Khani 12
  • 13.
    Sundas Shabbir AhmedKaim Khani 13