issues - oosdteam

Issues

Manengement issues

These are the current management issues in the project:

It has proven hard to decide which features should be prioritized to implement in the time that is left before deadline. It is continuesly disscused in the group to make sure the right things are prioritized.
The report is being finalized and we are going to evaluate the work of team. It was hard to decide on how to do the evaluation of the individual teamembers in a way that everybody were comfortable with.

These are the management issues encountered this far in the project, and what have been done to solve them.

Week 3:

Not much work was carried out in parallel. The major task for this week became to review the schedule and delegate work to team members to facilitate parallel work.

Week 4:

Hard to find an informative way to present the time planning. A revision of the scheduling layout was done using the planning tool.

Week 5:

Still too little work was carried out in parallel. Delegation of tasks to team members to facilitate parallel work was made.

Week 6:

Some members of the group have lectures that collides with the planning of this course. Rework was made to the schedule to deal with collisions with other courses.

Week 7:

Too little time to finish the deliverable D3.4v1 (Object Oriented Analysis and Design). Negotiation was done to protruding the hand-in of the deliverable.
Too much time was spent on converting documents from Google docs to Latex. The framework for producing deliverables was modified from a combination of Google docs and Latex to an exclusionary use of Latex.

Week 8:

Many team members private schedules had serious conflicts with the groups schedule. A revision of the group schedule was made.

Week 11:

Flex proved to have a rather different structure than other high-level object oriented languages (like Java). Much research was made in Flex, Actionscript and Flash Media Server.
The setup of a working Flash Media Server showed to be impossible without administration privilegies. Privilegies for a server on the department of Computing Science were given by the support staff.

Week 12:

The maintenance of the Flash Media Server showed to be more complex than expected. Some research about the server and Windows Server 2003 was made.
The writing of D4 (Subcontract) showed to be somewhat hard without knowing enough about Flex. The deliverable was rewritten once.
The design made in earlier phases showed to be inapropirate to implement in Flex. A revision was made to the initial design.

Week 13:

It was decided to exclude database related userhandling from the final product. This was decided because we concluded that we did not have enough time to implement all the features in the initial design. We therefore dropped the user handling part of the application because it had the least to do with the post-it method.
To enable a more effecient division of the remaining work we had an meeting where we divided the responsibilities for the remaining deliverables.

Week 14:

Week 15:

A voice chat proved harder to implement than we thought and it was decided to drop that feature from the final product.

Week 16:

Allmost all team members where having their own version of the code where they where coding their part of the application individually of the others. It was decided to do a merge of the code but it was postponed due to lack of time.

Week 17:

The updated OOAD document proved to take longer than expected to write so it was decided with the supervisor to extend the deadline with three days.
Due to incorrect time estimations and unforseen delays It was decided to skip the testing phase.
It was decided to further postpone the merging of the code.

Week 18:

The merging of the code where finally done.
It was decided that some teamembers who had finished implementing their assigned parts should begin writing the final report to avoid lack of time later.

These are the current open issues in the coding of the application:

Remove the "remove" button from a group when it is placed in a second level group.
Investigate if you should be able to submit suggestions after the brainstorm phase has been passed.
Investigate if a scroolbar allways appears on a suggestion when the suggestion has much text.
Make a lone wolf take less space in the grading phase.
No check is made if a group has any childs before the grading phase.

Investigate if the "remove" button should have reduced size to make sure that post-its are not removed by mistake.
Investigate if there is a way to have a set width on a group and still see all added post-its.
Investigate SharedObject.lock().
A post-it should not be shared when it is droped on one of the post-it piles.
Make sure the right adjustment is the same for both suggestions and groups.

It should not be possible to drag a post-it outside the whiteboard.
It should be apparent with the post-it piles graphics that they are piles.
Investigate if fps should be increased/decreased to increase preformance.
Make netConn static in Sessionhandler.
A users gradings of post-its should be removed when the user logs out if the user has graded anything.
It should be noticiable for the users in a session when a user refreshes or closes the window.

Have a "publish text" instead of creating post-its when they are dropped on the whiteboard.