Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Go Midjets Automate your Advantage http://www.gomidjets.com Automation: Why, When and How Tamir Gefen [email_address]
<ul><li>Automation: Why? </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How <...
<ul><li>Reason 1: Prevent costly mistakes </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li><...
<ul><li>Reason 2: Reduce time-consuming    manual tasks </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><...
<ul><li>Reason 3: “Information Islands” </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></u...
<ul><li>Information islands: products </li></ul><ul><li>Example: From product  A  to product  B </li></ul><ul><li>Automati...
<ul><li>Information islands: platforms </li></ul><ul><li>Example: Interoperability </li></ul><ul><li>Automation </li></ul>...
<ul><li>Information islands: IDEs </li></ul><ul><li>Example: Integrating product with IDE </li></ul><ul><li>Automation </l...
<ul><li>Reason 4:   Collaboration </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul>...
<ul><li>Information islands: </li></ul><ul><li>Collaborating all together </li></ul><ul><li>Automation </li></ul><ul><li>W...
<ul><li>On regular basis: hourly/daily/weekly etc. </li></ul><ul><li>By trigger (pre or post operations) </li></ul><ul><li...
<ul><li>Standardize a well-designed process </li></ul><ul><li>Streamline that process </li></ul><ul><li>Evaluate thoroughl...
<ul><li>1. Standardize a well-designed process </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When <...
<ul><li>2. Streamline that process </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul...
<ul><li>2. Streamline that process: </li></ul><ul><li>“ Walking skeleton” </li></ul><ul><li>Automation </li></ul><ul><li>W...
<ul><li>3. Evaluate thoroughly the relative fit of the automation technology to the process parts </li></ul><ul><li>Automa...
<ul><li>3. Evaluate technology </li></ul><ul><li>Users perspective </li></ul><ul><ul><li>Architecture and OS (portability)...
<ul><li>3. Evaluate technology </li></ul><ul><li>Developer perspective (you!) </li></ul><ul><ul><li>IDE / programming lang...
<ul><li>4. Automate the appropriate pieces with proper technology  </li></ul><ul><li>Automation </li></ul><ul><li>Why </li...
<ul><li>First standardize, streamline,  </li></ul><ul><li>and evaluate,  </li></ul><ul><li>Before you decide to automate <...
<ul><li>Practice </li></ul>
<ul><li>Recommended baselines – the problems: </li></ul><ul><ul><li>ClearCase does not catch that event </li></ul></ul><ul...
When baseline is recommended… 1. Send email 2. Track history
So, How to Catch the Event…?
<ul><li>A Resolution </li></ul>Pre-trigger Post-trigger Text file write read “ cleartool chstream”
Pre-trigger Rec. BL Post-trigger Rec. BL = V   If true: do nothing A resolution: the Equation X   Else: Send email and add...
<ul><li>Command-line interface? </li></ul><ul><li>Overkill process </li></ul><ul><li>Overriding information </li></ul><ul>...
<ul><li>Automation: Summary </li></ul>
<ul><li>Thank You! </li></ul>Go Midjets Automate your Advantage http://www.gomidjets.com [email_address]
Upcoming SlideShare
Loading in …5
×

“Automation in development processes: why, when and how

412 views

Published on

On March 23rd, GoMidjets’ seminar “Accelerating development and Configuration management processes by automation“ took host at IBM.

The presentation is divided to two parts:
1. Automation in development processes: why, when and how
2. Practical example from Rational ClearCase world: a trigger that announces a new recommended baseline that combine all the issues discussed

Published in: Technology
  • Be the first to comment

  • Be the first to like this

“Automation in development processes: why, when and how

  1. 1. Go Midjets Automate your Advantage http://www.gomidjets.com Automation: Why, When and How Tamir Gefen [email_address]
  2. 2. <ul><li>Automation: Why? </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  3. 3. <ul><li>Reason 1: Prevent costly mistakes </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  4. 4. <ul><li>Reason 2: Reduce time-consuming manual tasks </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  5. 5. <ul><li>Reason 3: “Information Islands” </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  6. 6. <ul><li>Information islands: products </li></ul><ul><li>Example: From product A to product B </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  7. 7. <ul><li>Information islands: platforms </li></ul><ul><li>Example: Interoperability </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  8. 8. <ul><li>Information islands: IDEs </li></ul><ul><li>Example: Integrating product with IDE </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  9. 9. <ul><li>Reason 4: Collaboration </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  10. 10. <ul><li>Information islands: </li></ul><ul><li>Collaborating all together </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  11. 11. <ul><li>On regular basis: hourly/daily/weekly etc. </li></ul><ul><li>By trigger (pre or post operations) </li></ul><ul><li>Manually… (cannot scheduled) </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>Automation: When?
  12. 12. <ul><li>Standardize a well-designed process </li></ul><ul><li>Streamline that process </li></ul><ul><li>Evaluate thoroughly the relative fit of the automation technology to the process parts </li></ul><ul><li>Automate the appropriate pieces with proper technology </li></ul>Automation: How? <ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  13. 13. <ul><li>1. Standardize a well-designed process </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  14. 14. <ul><li>2. Streamline that process </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  15. 15. <ul><li>2. Streamline that process: </li></ul><ul><li>“ Walking skeleton” </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  16. 16. <ul><li>3. Evaluate thoroughly the relative fit of the automation technology to the process parts </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  17. 17. <ul><li>3. Evaluate technology </li></ul><ul><li>Users perspective </li></ul><ul><ul><li>Architecture and OS (portability) </li></ul></ul><ul><ul><li>User interface </li></ul></ul><ul><ul><li>Performance </li></ul></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  18. 18. <ul><li>3. Evaluate technology </li></ul><ul><li>Developer perspective (you!) </li></ul><ul><ul><li>IDE / programming language </li></ul></ul><ul><ul><li>Support and community </li></ul></ul><ul><ul><li>Package and deployment? </li></ul></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  19. 19. <ul><li>4. Automate the appropriate pieces with proper technology </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  20. 20. <ul><li>First standardize, streamline, </li></ul><ul><li>and evaluate, </li></ul><ul><li>Before you decide to automate </li></ul><ul><li>Automation </li></ul><ul><li>Why </li></ul><ul><li>When </li></ul><ul><li>How </li></ul>
  21. 21. <ul><li>Practice </li></ul>
  22. 22. <ul><li>Recommended baselines – the problems: </li></ul><ul><ul><li>ClearCase does not catch that event </li></ul></ul><ul><ul><li>ClearCase does not track history of recommended baselines </li></ul></ul>
  23. 23. When baseline is recommended… 1. Send email 2. Track history
  24. 24. So, How to Catch the Event…?
  25. 25. <ul><li>A Resolution </li></ul>Pre-trigger Post-trigger Text file write read “ cleartool chstream”
  26. 26. Pre-trigger Rec. BL Post-trigger Rec. BL = V If true: do nothing A resolution: the Equation X Else: Send email and add to history To download the triggers: http://bit.ly/9zHehO
  27. 27. <ul><li>Command-line interface? </li></ul><ul><li>Overkill process </li></ul><ul><li>Overriding information </li></ul><ul><li>Unpredictable (“what if”) </li></ul>… and When not?
  28. 28. <ul><li>Automation: Summary </li></ul>
  29. 29. <ul><li>Thank You! </li></ul>Go Midjets Automate your Advantage http://www.gomidjets.com [email_address]

×