Assignment Structure Overview
The following is an overview of the assignment structure in CSCI 479.
- CSCI 479 will have a few different types of assignments. These assignments are either individual work or team work. The types of assignments include writing, presentation, programming, and project management.
- The assignments are listed here first so everyone will have an idea what is to come. The assignments will be distributed, collected, and graded through our Google Classroom for this class. Please follow the dates in the Google Classroom. In the schedule late on this page, you will also see the links and the dates to the assignments.
- If an assignment is individual, everyone should complete and submit their own work, like any other individual class work. If an assignment is team, the work should be done by team. The Google Classroom assignment in this case is shared by the team members. The team needs to make sure the assignment is completed and submitted on time. Everyone in the team should contribute to the work. And everyone needs to submit a copy of the team work. You have learned some basic team work skills in you previous courses, e.g., CSCI 205. We will review some of the team work topics and practice them throughout this class.
- We will start with temporary teams. The temporary teams are to explore possible projects. Everyone will join one such team assigned randomly. Each team is to present their potential projects to the entire class, helping the class understand the project. The detailes are specified in the assignment.
- Based on results of this exploration, we will form project teams. Each team will then likely needs the following.
- A code repository, most likely a gitlab site at Bucknell. If you use Bucknell's gitlab setting, this site will be owned by one of the team members and shared with others including the instructors. The team may decide to use another service such as github. In any case, please make sure the instructors havefull access to the team repository. Note that the contents in Bucknell sites will be removed after your graduation.
- A project management site, such as Trello, or any other tools you feel comfortable. Again, make sure your instructors have full access to it.
- Optionally, a team may set up a website to describe and advertise their project. You can do it within the gitlab or github environment, or you can do it through your Bucknell student account, e.g., Bucknell's blog site. Note: If you make any project information public, make sure you get approval from your client.
List of Assignments
Here is the list of assignments. See the schedule for dates. Assignments are distributed, colleged, and graded through the course Google Classroom.
Initial Project Assessment
Temporary teams are set up on the first day of class. Each temporary team needs to complete this assingment by next Monday.
Team Milestones
Team Milestones should be submitted through the course Google Classroom.
- System Design Paper: Overview | Full report | Presentation
- 1st Progress Report: Report | Presentation
- 2nd Progress Report: Report | Presentation
- Final Report and Presentation: Report | Presentation
Individual Milestones
Individual work should be submitted through Google Classroom
- Individual Reflection Prompts (Due at 8 am on the specified dates):
- How do we form a good team?
- How should we present ourselves on the job market?
- How do we ensure a healthy, productive team? |Individual and team discussion | Team |
- How do we do code reviews? |Individual and team discussion | Team |
- How have our team been performing? | Individual and team discussion | Team |
- How do we make sure we’re not making the world worse?| Individual and team discussion |
- Are we ready for our final product?| Individual and team discussion |
- Individual Literature Survey | Draft | Peer review | Revision | Final |
- Final (Individual) Reflection | End of school designated finals period |