A Journey in So,ware Development An overview of methods and tools (part 3)

Transcription

1 A Journey in So,ware Development An overview of methods and tools (part 3) Mathieu Acher Maître de Conférences

2 Material h=ps://github.com/acherm/teaching/tree/master/pdl/ 2

3

4 Document, refactor Execute your tests Debug.. Write test.. Documenting And so on! Refactoring Debugging Testing With modern IDE and tools!

5 Resources refactoring.com PDL h:p://junit.sourceforge.net/doc/cookstour/ cookstour.htm (How Junit is implemented) Good news 20 th december for C1 5

6

7

8

9 So,ware Engineering 9

10 So,ware Engineering (back) Versions (Time) Variants (Functionalities) Time to Market! 10

11 The 3 Dimensions of So,ware ConfiguraPon Management [Estublier et al. 95] The Revision dimension EvoluMon over Mme The Concurrent AcMviMes dimension Many developers are authorized to modify the same configuramon item The Variant dimension Handle environmental differences Even with the help of sophismcated tools, the complexity might be daunmng Try to simplify it by reifying the variants of an OO system 11

12 Versioning of source code CollaboraPve sovware engineering To master sovware development by very large developer teams parallel implementamons (experiments, vendors) Goals Increase producmvity of developers and sovware robustness Low- down development costs Manage sovware system configuramon to control sovware systems evolumon evolumon tracking (Mme- machine) issue and bug tracking

13 Versioning : What for? History of versions back to an older version in case of errors AlternaPve versions (branching) different design/implementamons (maybe experimentals) for the same module CollaboraPve access by many developers audit modificamon history how many commits by X? when most of the commits are done?...

14 Concurrency management with a simple picture

15 Doing nothing! Concurrency control Lock- Modify- Unlock (PessimisMc) SCCS, RCS Decrease producmvity Copy- Modify- Merge (OpMmisMc) Conflicts resolumon when concurrent modificamons (which are actually rare) Merge, SelecMon, CVS, SVN : Client level resolumon Policy- based Merging and validamon process for each code contribumon

16 Trunk main development Branches AlternaMves to trunk Revisions Concept of Version Different design/implementamon (experimental), vendor- specific Sequence of versions Tags Symbolic references to revisions (Tiger, LongHorn, ) Represent a public release (R), a milestone (M) Branch merging

17

18 SubVersion: Architecture Admin (command: svnadmin) Central repository r4 commit Working copy checkout update import file:// svn://, svn+ssh:// edit read r3 r2 Editor (command svn) Editor (command svn)

19 Main commands Editor svn svnlook svnshell System Administrator svnadmin svndumpfilter svnlook svnshell Server «User» focus svnserve, mod_dav_svn for Apache HTTPD

20

21

22

23 «Git» -noun an unpleasant or contemptible person -Oxford English Dictionary

24

25

26 Git version control system designed to handle very large projects with speed and efficiency mainly for various open source projects, most notably the Linux kernel. h:p://git.or.cz/

27 Git Advantages Resilience No one repository has more data than any other Speed Very fast operamons compared to other VCS (I m looking at you CVS and Subversion) Space Compression can be done across repository not just per file Minimizes local size as well as push/pull data transfers Simplicity Object model is very simple Large userbase with robust tools

28 Some Commands Gehng a Repository git init git clone Commits git add git commit Get changes with git fetch (fetches and merges) git pull Propagate changes with git push

29

30 Mainly based on the content of (one of the best introduction of Git/SVN)

31

32 Impacts My proposal: use exismng system like github CollaboraMve work You will keep your work somewhere You will be able to demonstrate your skills Not in this course Code reviews ConMnuous integramon