|
The final submission is also via Campus Net. Note that this submission consists of two parts:
the group submission of the project and an individual submission with the individual contribuions
and reflections of each student.
The deadline for both parts of this submission is, Friday, December 19, 2014 at
24.00.
The group's submission should contain all necessary Eclipse projects split up in two zip files:
one for the ADT and one for the WTP. Moreover, it should contain all documentation, handbook, test,
and the example configuration.
Please also install this application on your group's web server (GlassFish 4.1 server with database), and set up a configuration, which could be used by Ekkart Kindler when testing your software (using your apps on his phone)
as discussed in your handbook.
The main rational is, that the group's software can be installed,
started, and used without any additional information. It should be able to
use the tool just based on the delivered handbook only (which is part of
the documentation).
In addition to that, please, create tagged versions of the software,
the examples, and the documentation in your group's repository, and
include the information where to find these tags in your repository to
the CampusNet submission.
The final submission should include:
- The code of the final software (as exported Eclipse projects).
This includes also the code that was generated automatically. The project
should be split up into two zip files: one for Andoid, the other for
web applications.
- All the non-generated code should have Java doc comments, and the authors
of the non-generated code should be indicated with the @author tag (if the
author tag is not the student number / SVN account, it needs to be
clearly stated which author tag stands for which student — see below).
- A complete example that demonstrates the capabilities of your software.
- Instructions on how to install the projects and how to
start them (could be part of the handbook). This includes running the software
on your group's GlassFish server as well as installing it on another
GlassFish server.
- Instructions on how to install the example and start and use
the example (could be part of the handbook).
- The revised and updated systems specification and the handbook should be
submitted in as PDF (if it is clearly indicated, the handbook can be part of
the systems specification).
Both documents should clearly indicate which parts were written by
which students, so that the individual contributions of the students
can be evaluated.
- Documentation of tests (JUnit test should
be submitted as code; for manual tests, it is enough if they are included
in some test reports).
- A list identifying which student has worked on which parts of
the project. This concerns the work on the major parts of the software
(in addition to the @author tags in the code) and organisational
and management work, or work on testing, which is not documented
somewhere else (this list does not need to include the work on the
different parts of the documentation and the handbook, since these are
authored, see 6.).
If the author tag in the code and documents deviates from the student number
(SVN account) of the student, this list should also clearly identify which
"tag" represents which student.
- In addition to the submission of the group, every student must submit
an individual document (as a PDF file) via CampusNet,
in which the student explains the own contributions to the project,
in which part he or she was involved, and in which other activities and duties (project
leader, responsibilities in the different phases, SVN, etc.) he or she was
involved during the project. And the student should reflect on
some of the made experiences during this project. This document should be 1-2
pages long and submitted by Dec. 19, 2400 via CampusNet (individually).
Please make sure that the submission is complete (everything that needs to be installed
on top of the Eclipse versions and extensions used in this course's tutorials
needs to be mentioned). Here is a check list for the final submission:
- Are all required files and documents included in the tagged version
(including an example)?
- Are the documents complete (and understandable)?
- Does the submission contain all necessary details for installing and starting
the groups software?
- Is the software running (when only installing the plug-ins from the submission)
on the Eclipse installations (ADT and WTP) required for this course.
- Are the buildpaths of the projects set up in such a way that the plugin projects
build and run on other computers. Are pathes to resources independent from a
specific computer? Make sure to test this!
- Are all references to out-dated or irrelevant plugins deleted?
- Are all output commands to the console deleted from the code (or only made
in debugging mode)?
- Does the software include the Java docs and, in particular, the @author
tags for all non-generated parts?
- Does the documentation include the information on the authors for the
different parts?
- Did every student submit his or her individual document (own contributions and reflections)?
|
