Assignment [[number]]
Due [[_format(due)]]
Due [[_format(due)]]
Each assignment consists of a series of reading, analysis, and writing activities. Assignments are to be completed by individuals, although you are encouraged to discuss your work with your classmates. In keeping with scholarly tradition, all that you claim as yours must be authentically your own, and you must cite your sources for anything that is not. As always, your work should represent best practices of college-level composition. Keep in mind that The Writing Center is free and available for all students.
All of your assignments belong in our shared folder on Google Drive. Within the Assignments folder of the shared folder, you will create a document named after yourself. Each assignment will have its own heading, in Heading 1 style, with the name “Assignment N”, where N is the assignment number. When you are satisfied with your work, submit the URL to that section of the document via Canvas. The process is shown in this video.
The components of the assignment will be evaluated using my triage grading rubric with equal weights per part unless otherwise specified. The deadline for each assignment is the beginning of the next class after it was assigned. Late work is always considered unsatisfactory.
Keep in mind that you can resubmit one assignment per week. Put a brief explicit changelog at the top of the assignment; that is, summarize what changes you made since the last submission. There is no need to keep the entire original submission, just describe in the changelog what changed. The process of submission is essentially the same: submit the URL to the resubmitted assignment's heading.
Assignments are posted in advance here to give you a sense of where we are going, but the specification of the assignment is not finalized until the class period when it is assigned.
In the assigned readings, “CC” refers to Martin's book, Clean Code.
This assignment will help you configure your system and prepare you for work in CS222. This video will walk you through some of the required steps. Note that the video is from January 2017; mentally replace the reference to “Blackboard” with
HelloWorld with a single public instance method, sayHello, that returns the String “Hello” when called. Take a screenshot of your passing test case and submit it as part of the assignment.String;isEmpty method that returns true if the list is empty and false otherwise;add method that adds to the end of the queue;remove method that removes from the beginning of the queue; andsize method that returns the number of elements currently in the queue.Note that Assignment 2 will be the first entry into your Assignments document; be sure to provide the link specifically to the Assignment 2 heading.
https://github.com/bsu-cs222/Queue. Continue the implementation from that point, completing the first four tasks in our shared task list, following the principles of TDD. Paste your QueueTest and Queue implementations into your Assignment 3 submission.WordCounter module of our in-class online word counter example. This is the module that, given a String, tells you how many words it contains.XPEpisode.pdf). Write a response comparing your understandings of Pair Programming and Test-Driven Development before and after the reading. Discuss with your Two-Week Project partner (or final project team, if appropriate for a resubmission) how you can incorporate this new understanding into your work, and briefly describe your plan.Submit a task list, in Kent Beck's TDD format, that you and your partner are using to drive the development of the model layer for the two-week project. Each item should clearly define a SMART unit test. Clearly indicate where you currently are in the task list, and include the data over which you are testing.
This is a group assignment and so it only needs to be in one person's document; the other group member should link to it from theirs.