Introduction

Tugba

Description

• fiche de synthèse - matière potentielle : the performance requirements

Transmission and Drive Train Fluid Requirements TO-4 INTRODUCTION From the early 1970's through 1990, Caterpillar Inc. has recommended that its customers use API CD oils meeting Caterpillar's TO-2 Friction Performance Specification to lubricate Powershift transmissions and final drives. The fluids that met this specification were engine oils that provided good oxidation stability, foam and rust control and piece part cleanliness. In addition to these features, the TO-2 specification ensured good clutch performance wherever bronze friction discs were used.

• clean toluene
• drive train fluid requirements
• matic thm-4l60
• -4 fluids
• 2.0 test method
• rod
• oil
• section

Sujets

• Centerless grinding
• Caterpillar
• Section
• Requirement
• Performance

Informations

• Publié par: assi0
• Nombre de lectures: 13
• Langue: English
• Poids de l'ouvrage: 1 Mo

Extrait

Version Control Systems
21.12.2011
Tuğba Külahcıoğlu
Software Engineering – Fall 2011 Topics
• Version Control Software
– What does it do?
– Why do we need it?
– How does it work?
• Tools Comparison
• Subversion (SVN)
– The Problem of File-Sharing and Solutions
– Basic Work Cycle
– Using SVN with Eclipse
• Visualization - Gource
21.12.2011 Software Engineering - Fall 2011 2 Topics
• Version Control Software
– What does it do?
– Why do we need it?
– How does it work?
• Tools Comparison
• Subversion (SVN)
– The Problem of File-Sharing and Solutions
– Basic Work Cycle
– Using SVN with Eclipse
• Visualization - Gource
21.12.2011 Software Engineering - Fall 2011 3 What is Version Control Software? [1]
• Version Control Software is a set of programs
that manage changes to computer files, such
as documents, images and source code.

• Also known as:
– Revision control software
– Version management software
– Source control software
– Configuration management software

21.12.2011 Software Engineering - Fall 2011 4 What does it do? [2]
• Automates:
– Storing,
– Retrieval,
– Logging,
– Identification,
– Merging of revisions.
21.12.2011 Software Engineering - Fall 2011 5 Why do we need it? [1]
21.12.2011 Software Engineering - Fall 2011 6 How does it work? [3]
• Basic Setup
– Repository, Server, Client, Working Copy/Working
Set, Trunk/Main, Baseline
• Basic Actions
– Add, Revision, Head, Check out, Check in/Commit,
Change log/History, Update/Sync, Revert/Undo
• Advanced Actions
– Branch, Diff/Change/Delta, Merge, Conflict,
Resolve, Locking, Breaking/Stealing the lock
21.12.2011 Software Engineering - Fall 2011 7 Basic Setup [3]
• Repository
– The database storing the files
• Server
– The computer storing the repository
• Client
– The computer connecting to repository
• Working Set/Working Copy
– Local directory of files where changes are made

21.12.2011 Software Engineering - Fall 2011 8 Basic Setup [3]
• Trunk/Main
– The primary location for code in the repository
• Baseline
– An approved revision of a file from which
subsequent changes can be made

21.12.2011 Software Engineering - Fall 2011 9 Basic Actions [3]
• Add
– Put a file into the repo for the first time
• Revision
– What version a file is on
• Head
– The latest revision in the repository

21.12.2011 Software Engineering - Fall 2011 10