[[BackLinksMenu]]

[[TicketQuery(summary=GROUP_BOOK_MODEL_REDESIGN_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]

= Analysis =

== Overview ==
This group of tasks is about redesigning the book model of Sophie2 in accordance with the new model of resources. Since the model of the resources will be entirely different, the book model will change significantly as well. Currently it consists of the book, its pages and the page elements (frames, groups and book extras such as audio annotations and stickies). After the redesign, the model will be changed, with a better defined hierarchy of its elements, reflecting the new resources design as well. After this iteration, a complete design with a basic prototypical code as well as a schedule for the next weeks will be present.

== Task requirements ==
 * Analyze the current state of the book model:
  * What classes are present and how are they related?
  * What properties do the different elements have and are they all needed?
 * Provide a new hierarchy of classes that better reflects their relationship.
 * Provide a new design for the contents of the classes.
 * Provide a prototypcal skeletons of the classes.
 * Provide a schedule for the next iterations of this task:
  * Estimate how much time is needed for the complete refactoring.
  * Split the redesign into meaningful subtasks that can be completed in one week.

Keep in mind that this is closely related to the redesign of the resource model and should be done in parallel or after it. The change of the model will lead to refactoring the view and the logic. Take that into consideration when composing the schedule.

== Task result ==
 * Design diagrams of the new classes.
 * Prototypical code of the new clases (with tests included).
 * Schedule for the next actions to be taken.

== Implementation idea ==
Consider the design drafts created by milo:
 * All resources contain only immutable values.
 * Consider having a class Element that is a superclass for pages, frames, groups and stickies.
 * Consider creating a new module/package for the new model so that old things are not broken.

== Related ==
[http://pastebin.asteasolutions.net/f444cc8f1 The design drafts][[BR]]
[wiki:GROUP_RESOURCE_MODEL_REDESIGN_R0]

== How to demo ==
 * Show the design diagrams and the prototype classes.
 * Run any new tests created.

= Design =
^Describe your design here.

= Implementation =
^Describe and link the implementation results here (from the wiki or the repository).

= Testing =
^Place the testing results here.

= Comments =
^Write comments for this or later revisions here.