Your SlideShare is downloading. ×
ICSE-DAPSE 2013 talk
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

ICSE-DAPSE 2013 talk

149
views

Published on

Software developers and managers make decisions based on the understanding they have of their software systems. This understanding is both built up experientially and through investigating various …

Software developers and managers make decisions based on the understanding they have of their software systems. This understanding is both built up experientially and through investigating various software development artifacts. While artifacts can be investigated individually, being able to summarize characteristics about a set of development artifacts can be useful. In this paper we propose lifecycle models as an effective way to gain an understanding of certain development artifacts. Lifecycle models capture the dynamic nature of how various development artifacts change over time in a graphical form that can be easily understood and communicated. Lifecycle models enables reasoning of the underlying processes and dynamics of the artifacts being analyzed. In this paper we describe how lifecycle models can be generated and demonstrate how they can be applied to the code review process of a development project.

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
149
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ExtractingArtifact Lifecycle Modelsfrom Metadata HistoryOlga Baysal, Oleksii Kononenko, Reid Holmes, Michael W. GodfreyDavid R. Cheriton School of Computer ScienceUniversity of Waterloo, Canada{obaysal, okononen, rtholmes, migod}@uwaterloo.caDAPSE-13, May 21, 2013
  • 2. Problem SpaceBugzillaMaillinglistsSource ControlCodeSystems continually changeTests2
  • 3. Solution: Artifact Lifecycle Models!"#"$%&!"#"$%!"#"$%()*"+,-$ )*"+,-$ )*"+,-$A model that captures how asystem evolves over time3
  • 4. State 1State 2 State 3Outcome OutcomeOutcomequalitative/quantitativemeasurementsSolution: Artifact Lifecycle Models4
  • 5. Example: Code Reviewr? !" sr?#$%$&()*)$+,)sr–*)-./,!"#"$%"&$$"(%"&0)*)1/,)sr+*)-.2,)*+,-."&r+*)-.%,sr+)*)-,r–)*)$.3,sr–*)-,()!" sr–-.$,0)!" sr+%.2,3$, /-, $3, /.4, -.3,/01&"& 2-,"3*%!"4*+,-."& +01&31"&!"#$%&Firefox’s patch lifecycle11.8 hr8.9 hr5
  • 6. Example: Code Review6r? !" sr?#$%$&()*)$+,)sr–*)-./,!"#"$%"&$$"(%"&0)*)1/,)sr+*)-.2,)*+,-."&r+*)-.%,sr+)*)-,r–)*)$.3,sr–*)-,()!" sr–-.$,0)!" sr+%.2,3$, /-, $3, /.4, -.3,/01&"& 2-,"3*%!"4*+,-."& +01&31"&!"#$%&Firefox’s patch lifecycle11.8 hr8.9 hr!"#$%&%()*+%,!"#"$%"&$$"(%"&-+),)*+,-."&-+.,/01&"& 2-,"3*%!"4*+,-."& +01&31"&%/+$, +(, $-+%, ))+%, )+*, *+,!"#$%&.%+/,-+),-+0,WebKit’s patch lifecycle80 hr30 hr
  • 7. Other Applications7Issues – status (NEW, ASSIGNED,WONTFIX, CLOSED), priority (HIGH,NORMAL, LOW), componentSource code – LOCs added,LOCs removed, LOCsmodifiedDiscussions – CLOSED,UNANSWERED, REOPENED,DUPLICATE, PROTECTED
  • 8. Artifact Lifecycle Models• capture development artifact evolution;• state-based representation that is easy tounderstand and communicate;• provide means to organize and reason aboutthe data or processes hidden in the artifacts.8!"#"$%&!"#"$%!"#"$%()*"+,-$ )*"+,-$ )*"+,-$