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