1 / 14

Teamwork Skills in Software Engineering

Teamwork Skills in Software Engineering. 樂倍達數位科技股份有限公司 Kung-Ming Fung kmfung@doubleservice.com 2006/12/20. Outline. Introduction Version Control Coding Standard Discussion ( Q&A ) References. Introduction. Why? 1 + 1 = 2 ??? How?. Version Control. Basic Functions Check-In 。

davidslopez
Download Presentation

Teamwork Skills in Software Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Teamwork Skills in Software Engineering 樂倍達數位科技股份有限公司 Kung-Ming Fung kmfung@doubleservice.com 2006/12/20

  2. Outline • Introduction • Version Control • Coding Standard • Discussion(Q&A) • References

  3. Introduction • Why? • 1 + 1 = 2 ??? • How?

  4. Version Control • Basic Functions • Check-In。 • Check-Out。 • Diff.。 • Mergence。 • History。 • Restore。

  5. Software • CVS(Concurrent Versions System)。 • SVN(Subversion)。 • VSS(Visual SourceSafe )。 • Client • TortoiseCVS。 • TortoiseSVN。

  6. Coding Standard • Reference:GNU Coding Standards。 • Naming Variables, Functions, Classes and Files。 • Coding Style。

  7. Naming • Include Type in Names int intMyWeight; bool blnIsLogin; • Include Units in Names uint32 uintTimeoutMsecs; uint32 uintMyWeightLbs; • Class Names • Use upper case letters as word separators, lower case for the rest of a word 。 • First character in a name is upper case 。 • No underbars ('_') 。

  8. Class Names class JjLinkList { … } • Method Names • Use the same rule as for class names 。 class NameOneTwo { public: int DoIt(); void HandleError(); }

  9. Constants • constants should be all caps with ‘_’ separators 。 const int A_GLOBAL_CONSTANT= 5; • Variables Declaration int intMyWeight;

  10. Coding Style • Comments • Comments Should Tell a Story 。 • Write Comments as You Code 。 • Style class NameOneTwo { public: int DoIt(); void HandleError(); }

  11. Reference: http://blog.auliabig.com/?p=13

  12. Discussion(Q&A)

  13. References • Teaching Teamwork Skills In Software Engineering Based On An Understanding Of Factors Affecting Group Performance, http://citeseer.ist.psu.edu/547996.html。 • CVS:http://www.nongnu.org/cvs/。 • SVN:http://subversion.tigris.org/。 • VSS:http://msdn2.microsoft.com/en-us/vstudio/aa718670.aspx。 • TortoiseSVN:http://tortoisesvn.tigris.org/。 • TortoiseCVS:http://www.tortoisecvs.org/。

  14. C++ Coding Standard ,http://www.possibility.com/Cpp/CppCodingStandard.html。 • GNU Coding Standards,http://www.gnu.org/prep/standards/standards.html。 • PHP Coding Standard ,http://www.dagbladet.no/development/phpcodingstandard/。 • Code Conventions for the Java Programming Language,http://java.sun.com/docs/codeconv/。

More Related