The Sixth Core 20123 - OOP344

OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

The Sixth Core (XIII)

Project Marking Percentage

• due immediately

Group work:      35%        (25 <= xx <= 50)
Individual work: 65% +      (50 <= xx <= 75) 
-------------------------
Total           100%

Repository

• repo Github id: XIII-SixCor

Team Members

Team Name (The Sixth Core)

First Name	Last Name	Section	Seneca Id	wiki id	IRC nick	Blog URL
Amir Mohammad	Mobasseri	B	ammobasseri	ammobasseri	ammobasseri	Amir's Blog
Saeid	Ahankoub	B	sahankoub	Saeid Ahankoub	sahankoub	C++ Blog
Prateek	Chadha	B	prateek	Prateek Chadha	aviat0r	prateek chadha
Rocco	Pietrangelo	A	rmpietrangelo	WikiID	IrcNick	oop344-seneca
[[User: | Mark Anthony]]	Hom		mahom			[ ]

Issues and Status

Issue description and/or number (1)

• Assigned to: FULLNAME
• Code review by: FULLNAME
• Status:

  (being developed/pull request/being reviewed/pushed to master)

• comments:

Issue description and/or number (2)

• Assigned to: FULLNAME
• Code review by: FULLNAME
• Status:

  (being developed/pull request/being reviewed/pushed to master)

• comments:

Coding Rules

• Use Safegaurd for header files with the format of _XIII_FILENAME_H_
• Data members in any classes start with underscore(_), for example _data
• Use Capital letter for the second (third, forth, ...) word of variables with compound words
• Use meaningfully variable names
• Use 2 spaces for indentation
• Use only SPACE BAR for indentation (do not use Tab)
• Use curly-braces for all kinds of loops, if statements, switch, etc. For example,

 if (condition){
   code;   
 } // end if

• Comment shortly and properly, specially at the end of long scopes
• You can use extra spaces to align statements or blank line between parts of the code that you are going to put comment

meetings

• latest will be on top

1. We need to make a meeting time for our group so we can discuss the issues and get organized.
2. topic and date1
3. topic and date2