Innovative Coders
Revision as of 08:56, 21 October 2012 by Shawnique Donaree Allison Warren (talk | contribs)
Innovative Coders (Team XIV)
Project Marking Percentage
- due immediately
Group work: 30% Individual work: 70% + ------------------------- Total 100%
Repository
- repo Github id:
Team Members
First Name | Last Name | Section | Seneca Id | Github ID | wiki id | IRC nick | Blog URL |
---|---|---|---|---|---|---|---|
Atieh | Mohammadi | B | amohammadi5 | Github:atiehm | Atieh Mohammadi | AtiehM | Journy Using C++ |
Shawnique | Warren | B | sdwarren1 | Github:nique12 | Shawnique Donaree Allison Warren | nique12 | Nique's World |
Svetlana | Molodtsova | B | smolodtsova | Github:s5molodtsova | Svetlana Molodtsova | sveta | Svetlana Molodtsova |
Prasanth | Vaaheeswaran | A | pvaaheeswaran | Github:vprasamth | Prasanth Vaaheeswaran | iampv | We're All Forked |
Tejaskumar | Patel | A | trpatel8 | Github:trpatel8 | Tejaskumar Ramanlal Patel | trpatel8 | Tejas Patel's OOP344 Blog |
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
- For indentation - 2 spaces will be used
- All safeguards for header files will use the following format: _IC_FILENAME_H
- Member variables should begin with an underscore (eg int _data)
- Blocks of code will follow the structure outlined below
- Label the start and finish when there are large blocks of code
- Briefly comment each function - outlining its purpose
Remember the class standards
- Declaring each variable separately
- Correct pointer placement (char* str)
meetings
- October 19, 2012. Group meeting room 1122. Time: 8.55 a.m. to 10.40 a.m.
Discussed coding rules and standards, grade distribution.