Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

XMLPipeDB Project: Final Report and Evaluation for Biological Informatics Special Studies, Exams of Histology

Instructions for students in a biological informatics course to submit a final report summarizing their work on the xmlpipedb project, including components worked on and an evaluation of their achievements. The document also outlines the criteria for evaluating the project's design, functionality, and other aspects, and explains how the final grade will be determined.

Typology: Exams

Pre 2010

Uploaded on 08/18/2009

koofers-user-rtj-1
koofers-user-rtj-1 🇺🇸

5

(2)

10 documents

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
B I O L 4 9 8 / C M S I 6 9 8
SP E C I A L ST U D I E S : BI O I N F O R M A T I C S
Spring 2006
Final Report and Evaluation
There is one last challenge posed by the uncon-
ventional and fluid nature of this course, and that
is how to determine the final grade. This last set
of deliverables is geared toward providing us
with a framework for making this last decision.
Statement of Work
Submit a 1–2 page report that summarizes the
work you have done, including but not limited to:
1. The components that you worked on in the
XMLPipeDB project.
2. The sections that you worked on in the final
class paper.
Conclude your report with an evaluation of your
work, describing what your goal was, how much
of it was achieved, and what follow-up work is
appropriate (whether to be performed by yourself
or by someone else). Note that “work” here does
not just involve software development; documen-
tation, testing, and evaluation are also fair game.
Overall Project Assessment
Evaluate the following components of XMLPi-
peDB (both software and paper) according to the
criteria described in the syllabus: design, func-
tionality, naming, comments (including external
documentation), and CVS use for the project, and
content, organization, writing, and polish for the
paper. Be specific where possible, for both good
and bad points (e.g., “Class xyz has duplicated
code in methods a and b,” “The way functional-
ity ghi is implemented is very flexible”):
xsd2db
xmlpipedbutils configuration
xmlpipedbutils import
xmlpipedbutils querying
uniprotdb postprocessor
godb postprocessor
gmbuilder
This information will be useful not only for
grading, but for helping set future work and ac-
tion items on the project.
Determination of Final Grade
Given all of this information, the final breakdown
of your grades will consist of:
10% homework Since there was only one
truly individualized assignment (the NAR data-
base report), and everyone did “submit,” this is
essentially a freebie.
20% overall paper — We will grade the overall
paper according to the criteria in the syllabus,
and this grade will be uniform for everyone.
25% individual paper contribution — Based on
your statement of work, assessment by others,
and CVS logs, we will grade your individual
sections according to the criteria in the syllabus
and assign this grade on a per-student basis.
20% overall project Similar to the overall
paper grade, but this time for the XMLPipeDB
project code, using the criteria for code de-
scribed in the syllabus.
25% individual project contribution Similar
to the individual paper grade, but this time per-
taining to the XMLPipeDB project code.

Partial preview of the text

Download XMLPipeDB Project: Final Report and Evaluation for Biological Informatics Special Studies and more Exams Histology in PDF only on Docsity!

B I O L 4 9 8 / C M S I 6 9 8

S P E C I A L S T U D I E S : B I O I N F O R M A T I C S

Spring 2006

Final Report and Evaluation

There is one last challenge posed by the uncon- ventional and fluid nature of this course, and that is how to determine the final grade. This last set of deliverables is geared toward providing us with a framework for making this last decision.

Statement of Work

Submit a 1–2 page report that summarizes the work you have done, including but not limited to:

  1. The components that you worked on in the XMLPipeDB project.
  2. The sections that you worked on in the final class paper. Conclude your report with an evaluation of your work, describing what your goal was, how much of it was achieved, and what follow-up work is appropriate (whether to be performed by yourself or by someone else). Note that “work” here does not just involve software development; documen- tation, testing, and evaluation are also fair game.

Overall Project Assessment

Evaluate the following components of XMLPi- peDB (both software and paper) according to the criteria described in the syllabus: design , func- tionality , naming , comments (including external documentation), and CVS use for the project, and content , organization , writing , and polish for the paper. Be specific where possible, for both good and bad points (e.g., “Class xyz has duplicated code in methods a and b ,” “The way functional- ity ghi is implemented is very flexible”):

  • xsd2db
  • xmlpipedbutils configuration
  • xmlpipedbutils import
  • xmlpipedbutils querying
  • uniprotdb postprocessor
  • godb postprocessor
  • gmbuilder This information will be useful not only for grading, but for helping set future work and ac- tion items on the project.

Determination of Final Grade

Given all of this information, the final breakdown of your grades will consist of:

  • 10% homework^ — Since there was only one truly individualized assignment (the NAR data- base report), and everyone did “submit,” this is essentially a freebie.
  • 20% overall paper^ — We will grade the overall paper according to the criteria in the syllabus, and this grade will be uniform for everyone.
  • 25% individual paper contribution^ — Based on your statement of work, assessment by others, and CVS logs, we will grade your individual sections according to the criteria in the syllabus and assign this grade on a per-student basis.
  • 20% overall project^ — Similar to the overall paper grade, but this time for the XMLPipeDB project code, using the criteria for code de- scribed in the syllabus.
  • 25% individual project contribution^ — Similar to the individual paper grade, but this time per- taining to the XMLPipeDB project code.