Presentation is loading. Please wait.

Presentation is loading. Please wait.

By: Taylor Helsper.  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions.

Similar presentations


Presentation on theme: "By: Taylor Helsper.  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions."— Presentation transcript:

1 By: Taylor Helsper

2  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions

3  What is this lecture? ◦ Part of a CSE 4000 Independent Study Course ◦ “Practical Issues in Software Engineering”  What’s the point? ◦ To provide practical information to students in Software Engineering topics Note: The products referenced in these slides are merely examples used to teach and there are other alternatives available. This is not an endorsement of the products.

4  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions

5  Why? ◦ Communication  Developer –> Developer  Tester –> Developer ◦ Statistics  Progress Reporting

6  What to use? ◦ Bugzilla - http://www.bugzilla.org/http://www.bugzilla.org/ ◦ FogBugz - http://www.fogcreek.com/http://www.fogcreek.com/ ◦ BugZap- http://www.bugzap.org/http://www.bugzap.org/ ◦ DefectManager - http://www.tierasoft.com/http://www.tierasoft.com/ …

7  Web based bug tracking tool  Has all necessary features ◦ Multi-user ◦ Tracking ◦ Simple

8  Lets try it out Username: dcsp@mailinator.comdcsp@mailinator.com Password: msstate https://landfill.bugzilla.org/bugzilla-4.0-branch/

9  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions

10  What is it? ◦ Tracks progress of software development throughout it’s lifecycle  Why? ◦ Statuses ◦ Customer Communication ◦ Keeps people active

11  What to use? ◦ Microsoft Project http://www.microsoft.com/project/ http://www.microsoft.com/project/ ◦ Team Software Process Spreadsheet http://www.sei.cmu.edu/tsp/ http://www.sei.cmu.edu/tsp/ ◦ Excel ◦ iTeamwork http://www.iteamwork.com/ http://www.iteamwork.com/

12

13

14  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions

15  What is version control? Repository class1.cpp v3 main.cpp v1 class1.h v1 class2.h v1 class2.cpp v2 class2.cpp v1 class1.cpp v2

16  What is version control? Repository User 1 User 2 User 4 User 3

17  Why? ◦ Multiple people work on projects ◦ Automatic backups ◦ Authentication ◦ Tracking

18  What to use? ◦ Current Version Control (CVS) ◦ Subversion (SVN) ◦ Mercurial ◦ Git

19  4 Basic Actions ◦ Checkout ◦ Commit ◦ Update ◦ Resolve

20  Checkout ◦ Sets up access to a repository ◦ Retrieves all files for local access Creates Local Copy Repository

21  Commit / Add ◦ All editing is done locally, after checkout Local CopyRepository

22  Update ◦ Updates your local copy with changes Local CopyRepository

23  Resolve ◦ What if two people change and commit the same file? User 1 Repository User 2 main.cpp

24  Where to get it? ◦ TortoiseSVN http://tortoisesvn.tigris.org/ http://tortoisesvn.tigris.org/ ◦ Integrate with your IDE  Netbeans  Eclipse …

25  Example ◦ CodeQuiz repositorysvn://codequiz.com/CodeQuiz1 usernamedbms passwordmsstate This example SVN server is no longer live.

26  Use Bug Tracking  Use Version Control  Use Progress Tracking when necessary

27 Information came from my general knowledge due to experience and classes here at MSU. All images used have the appropriate links below them.

28


Download ppt "By: Taylor Helsper.  Introduction  Bug Tracking  Progress Tracking  Version Control  Conclusion  Questions."

Similar presentations


Ads by Google