Source Code Control. Quiz with Explainations. Hans-Petter Halvorsen, M.Sc.

Size: px

Start display at page:

Download "Source Code Control. Quiz with Explainations. Hans-Petter Halvorsen, M.Sc."

Rodney Carroll
6 years ago
Views:

1 Source Code Control Quiz with Explainations Hans-Petter Halvorsen, M.Sc.

2 Questions 1. What is SCC? 2. List at least 5 different SSC Systems 3. Why do we need a SCC/Version Control System? 4. What is Distributed Version Control System (DVCS)? 5. What is TFS? 6. What is main differences between TFVC (Built-in Version Control System in TFS) and Git? 7. What is a Bug Tracking System? 8. List different Bug Tracking Systems (at least 3) 9. What different software releases do we have? 10. List at least 3 centralized SCC systems and 3 DVCS systems

3 What is SCC?

4 Source Code Control/Version Control What is it? A version control system keeps track of all work and all changes in a set of files (typically your code files, but also other files) Allows several developers (potentially widely separated in space and time) to collaborate All Software Developers need it!! 4

5 Typical SCC Features Checkout, Checkin/Commit Branching, Merging File Locking (avoid concurrent access) Label/Tag Change/Change List Conflict Revision, Iteration 5

6 SCC Features Checkout, Checkin/Commit Branching, Merging File Locking (avoid concurrent access) Label/Tag Change/Change List/History Conflict 1.0 Braching Work with Bug Fix Bug Fix Released 2.0 Released Label/Tag it Work with new Release Merging etc. Branching in TFS: 6

7 List at least 5 different SSC Systems

8 SCC Systems SVN Concurrent Versioning System 8

visualstudio.com) TFVC or Git GitHub (www.github.

9 Web-based SCC Hosting Services Visual Studio Online (formerly Team Foundation Services) ( TFVC or Git GitHub ( Bitbucket ( Mercurial or Git 9

10 Why do we need a SCC/Version Control System?

11 Why SCC? Keept track of code and files from multiple developers, because each developer create a small part of the total software solution, or multiple developers work on the same piece of code It is important to keep track of different versions of the same files, e.g. if we have made some mistakes and we need an older version of the same code. We could also create different braches, e.g one branc for Customer 1 and another branch for Customer 2, and maybe at some point we need to merrge those two into on product.

12 What is Distributed Version Control System (DVCS)?

13 Centralized/Client Server architecture A server stores the current version(s) of a project and its history, and clients connect to the server in order to "check out" a complete copy of the project, work on this copy and then later "check in" their changes DVCS - Distibuted Version Control System With a distributed version control system, there isn t one centralized code base to pull the code from. Different branches hold different parts of the code. Git is a DVCS. Other version control systems, such as SVN and CVS, use centralized version control, meaning that only one master copy of the software is used. Peer-to-peer approach

14 Centralized/Client Server architecture Client Client Client Network Client Repository Server Repository: Source Code Database

15 Distibuted Version Control System Repository peer-to-peer peer-to-peer Repository Repository Repository: Source Code Database Repository

16 What is TFS?

17 Team Foundation Server SDLC Management (SDLC Software Development Life Cycle) Software Team Collaboration Source Code Management Supports Agile, Scrum, CMMI Integrated Test Tools Bug Tracking System Automated Builds Built in Team Foundation Version Control (TSVC) + Support for Git repositories Built-in support for TFS in Visual Studio (Team Explorer) Plug-in for Eclipse (Team Explorer Everywhere) MSSCCI Provider for other IDEs like LabVIEW, etc. 17

18 What is main differences between TFVC (Built-in Version Control System in TFS) and Git?

19 TFS vs. Git Team Foundation Version Control (TFVC) uses a single, centralized server repository to track and version files. Local changes are always checked in to the central server where other developers can get the latest changes. Git is a Distributed Version Control System (DVCS) that uses a local repository to track and version files. Changes are shared with other developers by pushing and pulling changes through a remote, shared repository.

20 Git Has become very popular today Distributed Version Control System Initially designed and developed by Linus Torvalds (Linux Guru) (2005) Git is Free of use CVS and SVN is easier to use than Git for beginners 20

21 What is a Bug Tracking System?

Bugs A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to

22 Bugs A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways They found a bug (actually a moth) inside a computer in 1947 that made the program not behaving as expected. This was the first real bug. 22

23 Why Find Bugs early? Cost per defects Software Development Life Cycle (SDLC) 23

24 Bug Tracking System Keep track of bugs in software. Testers (or others) can report bugs, Developers and/or Managers can prioritize the list of bugs, etc. You can relate a spesific bug to a spesific release, etc. All these features are part of a Bug Tracking System.

25 List different Bug Tracking Systems (at least 3)

26 Bug Tracking Systems Team Foundation Server Jira Bugzilla Clearquest 26

27 What different software releases do we have?

28 Software Releases Start Alpha Release Beta Releases RC (Release Candidate) RTM (Release To Manufacturing) Finished Note! other terms are also used 28

29 Alpha Requirements/Design Plans made and approved Beta Building structure finished, Inside work on track RC Foundation finished, building structure started A proof that you can do it, PoC (Proof of Concept) Furniture, Flowers and small adjustments missing RTM Ready for Sale or Move in 29

30 Software Releases Before the software is released Alpha Release(s) (Internal release, not public) Beta Release(s) ( Developer Preview, Consumer Preview ) RC - Release Candidate(s) ( Release Preview ) RTM Release To Manufactoring Maintenance (after the software is released) Patches (small fixes) SP - Service Packs (lots of small fixes and pathes bundle together), SP1, SP2, R1, R2,.. Start Planning next Release 30

31 List at least 3 centralized SCC systems and 3 DVCS systems

32 Centralized/ Client Cerver architecture TFS CVS SVN (Subversion) LibreSource DVCS Git Mercurial Bazaar Monotone BitKeeper 32

References Software Development - A Practical Approach Halvorsen, Hans-Petter, 2015 Essentials of Software Engineering Frank Tsui; Orlando Karam; Barbara Bernal, 3 ed.

33 References Software Development - A Practical Approach Halvorsen, Hans-Petter, 2015 Essentials of Software Engineering Frank Tsui; Orlando Karam; Barbara Bernal, 3 ed., Jones & Bartlett Learning Software Engineering I. Sommerville, 10 ed.: Pearson, 2015 Software Engineering. Modern Approaches E. J. Braude and M. E.Bernstein, 2 ed.: Wiley,

Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway www.

35 Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway Blog:

Source Code Control & Bug Tracking

http://home.hit.no/~hansha/?page=software_development O. Widder. (2013). geek&poke. Available: http://geek-and-poke.com Source Code Control & Bug Tracking Hans-Petter Halvorsen O. Widder. (2013). geek&poke.