CSCI 479: Computer Science Design Project

CSCI 479: Computer Science Design Project

Department of Computer Science

Course Information

You can find the course syllabus here.

Deliverables and Time Line

Throughout the project life time (our semester), there will be a number of milestones where deliverables are expected. Because of the dynamic nature of the agile development process the deliverables and their dates may be revised.

Follow this link for a time line and deliverables.

Team literature survey paper (Wed 9/5)
Each team writes and presents a literature survey that consists of two parts. Part 1 should discuss mobile programming in general and part 2 should discuss team's specific platform (iOS, Android, and HTML5). The paper should be of length about 1,500 words and the presentation should be about 15 minutes per team.

Progress report (Wed 10/17)
Each team writes and presents a progress report that should address the following issues. The paper should be of length about 1,200 to 1,500 words, and the presentation of 15 minutes.
a) Current status of the project
b) Team plan for the second half of the semester
c) Any successful stories or difficulties during the first half of the semester
d) Any suggestions

Tutorial for your platform (team work) Due: 3:00 p.m. Monday 11/26 3:00 p.m. Monday 12/3

Final project presentation and demonstration (team work) Due: 3:00 p.m. Wednesday 11/28

Bucknell educational experience reflection paper (individual work) Due: 6:30 p.m. Friday, 12/7

Final presentation and demonstration announcement. The event date and time: Wednesday, 11/28, 3:00 p.m. for presentation and 4:00 p.m. for demonstration, location: Breakiron 165 and Breakiron lobby outside Break 165.

Student Learning Outcomes

  1. Students will be able to function effectively in a project team (CSAB d)
  2. Students will be able to use knowledge from previous courses in designing, implementing, and evaluating a culminating computing project. (CSAB b, c)
  3. Students will be able to organize, write, and deliver technical written document(s) and oral presentation(s) about the project. (CSAB f)

Related CSAB Student Outcomes

(b) An ability to analyze a problem, and identify and define the computing requirements appropriate to its solution

(c) An ability to design, implement, and evaluate a computer-based system, process, component, or program to meet desired needs

(d) An ability to function effectively on teams to accomplish a common goal

(f) An ability to communicate effectively with a range of audiences

Our Customer

We are very glad to have Dr. John Furia as our customer. Dr. Furia is an orthopaedic surgen at SUN Orchopaedic. More information can be found at SUN Orthopaedic

Follow this linke for a complete set of documents from the customer.

Links that we should connect from our app.

Code Examples

Follow this link for a list of code examples.

A work flow diagram illustrating the logic flow of the application. Updated (10/11/2012)! Thanks to Katie for her original and updated work!

Team online demonstration/prototype

Team iOS demo on YouTube.

Team Android demo on the web.

Team HTML5 demo on the web.

Exercises

Follw this link for a list of exercises. These exercises are designed to get us started on a subject. These concepts and structures in these exercises are needed in our projects, but they are far from complete.

Resources

App submission specifics: guidelines and discussions.

A draft of the About page.

The color scheme that we agreed on for apps on various platforms.

The following links show some of the images, photos, displays that are relevant to our projects.

The following two commands recursively change the file and directory permissions in the public web directory so others can access the files from the web.

Change permissions recursively for files:
find . -type f -exec chmod 644 {} \;

Change permissions recursively for directories:
find . -type d -exec chmod 755 {} \;

Follow this link for a list of resources that will help us develop the project. The resources are organized into three groups, iOS, Android, and HTML5.

Course SVN site where you and your team should keep revisions of the code.

Course Moodle site where you and your team can submit writings and presentations.

Discussion articles and posts on the subject of mobile apps in general, and comparisons among Android, HTML5, and iOS.

Our discussion on Design Patterns and the code examples

Peer Evaluation

This form is used to evaluate individual effort towards team activities.

Rubric

This rubric will be used to assess your presentations.

This rubric will be used to assess your writings.

Academic Responsibility

Bucknell University Honor Code

As a student and citizen of the Bucknell University community:
  1. I will not lie, cheat, or steal in my academic endeavors.
  2. I will forthrightly oppose each and every instance of academic dishonesty.
  3. I will let my conscience guide my decision to communicate directly with any person or persons I believe to have been dishonest in academic work.
  4. I will let my conscience guide my decision on reporting breaches of academic integrity to the appropriate faculty or deans.

Students are expected to read and abide by the principles clearly explained in the Student Handbook. Under no circumstance, should any student submit work that is not of his or her authorship. If a deadline is tight, or impossible, before getting desperate, talk to your instructor. It is better to be late than dishonest. Remember that your instructor's main goal is to give you the best opportunities to learn.

The university has a set of web pages that describe what we understand for Principles of Academic Responsibility and how it deals with cases of violations of these principles.

In addition to reading and understanding the university documents above, you are urged pay careful attention to the policy extensions applicable to courses in the Department of Computer Science.

Your instructor will make every effort to explain in detail the collaboration policy for each specific assignment. Before you start your work, make sure to read and understand this policy. Should any questions arise, contact your instructor immediately to have them clarified.


Last modified: Tue Aug 14 15:28:07 EDT 2012