mdelvalle / cs371p-life Goto Github PK
View Code? Open in Web Editor NEWJohn Conway's Game of Life for cs371p-Object Oriented Programming
John Conway's Game of Life for cs371p-Object Oriented Programming
Initial grid changes after reading the input file.
Use assert to check pre-conditions, post-conditions, argument validity, return-value validity, and invariants. Worry about this last, but your program should run as fast as possible and use as little memory as possible.
The grader's GitHub account will have a public Git repository for unit tests and acceptance tests.
It is critical that you clone the grader's public repo into a different directory than the one you're using for your private repo.
Write acceptance tests before your write the code. When you encounter a bug, write an acceptance test that fails, fix the bug, and confirm that the acceptance test passes. Create at least 200 lines of acceptance tests. Tests corner cases and failure cases. In your acceptance tests include five other students' acceptance tests (another 200 lines for all five, at least). Push and pull only your acceptance tests to and from the grader's repository. Prepend - to the file names at GitHub (i.e. foo-RunLifeConway.in, foo-RunLifeFredkin.in, foo-RunLifeCell.in, and foo-RunLife.out). Reach consensus on the acceptance tests.
You must use Valgrind.
Check for dead cells around the grid
How to define abstract cells and what attributes and functions are public or private.
Figure out what attributes go to each class
Rename "makefile.c++" to "makefile".
Fill out the Google Form and submit the ZIP file to Turnin.
Figure out the scope of each function and variable
Figure out how to implement a grid
Set up a private Git repository at GitHub, named cs371p-life.
Invite the grader to your repository. Commit at least 5 times. Commit once for each bug or feature. If you cannot describe your changes in a sentence, you are not committing often enough. Write meaningful commit messages and identify the corresponding issue in the issue tracker (below). Create a tag for important milestones (e.g. without a cache, with a lazy cache, etc.). Create a log of the commits. Push frequently. It is your responsibility to protect your code from the rest of the students in the class. If your code gets out, you are as guilty as the recipient of academic dishonesty.
The grader's GitHub account will have a public Git repository for unit tests and acceptance tests.
It is critical that you clone the grader's public repo into a different directory than the one you're using for your private repo.
Write unit tests before you write the code. When you encounter a bug, write a unit test that fails, fix the bug, and confirm that the unit test passes. Write at least an average of 3 unit tests for each function. Tests corner cases and failure cases. Name tests logically. Push and pull the unit tests to and from the grader's repository. Prepend - to the file names at GitHub (i.e. foo-TestLife.c++ and foo-TestLife.out). Reach consensus on the unit tests.
You must use Valgrind.
Figure out a way to keep track of the ages and generations
Use Doxygen to document the interfaces.
The above documentation only needs to be generated for AbstractCell.h, ConwayCell.h, FredkinCell.h, Cell.h, and Life.h.
Comment each function meaningfully. Use comments only if you need to explain the why of a particular implementation.
Choose a coding convention and be consistent. Use good variable names. Write readable code with good indentation, blank lines, and blank spaces.
The GitHub repository comes with an issue tracker.
Create an issue for each of the requirements in this table. Create an issue for each bug or feature, both open and closed. Describe and label each issue adequately. Create at least 10 more issues in addition to the requirements in this table.
Improve the speed of the program
Figure out why the Cell class does not detect alive and dead cells properly
Wrong address pointers give segmentation faults
The UML diagram.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.