This page discuss about the the team organization and
software methodology associated with ePub.
Team Organization:
ePub
has a four member team which is relatively small. We would not like to
have a strict hierarchy of roles.
ePub team believes in FLAT organizational structure which allows
ideas and opinions to flow up from the bottom without layers of managers
filtering or re-interpreting them. We stress on fair division of labor and
every member has an equal responsibility in terms of getting work done. Every
member of the team is responsible to stick to the project schedule, check and
update the schedule with the project, project homepage, project design,
coding, and documentation. The work load will be divided taking into account
each members availability.
Software Development Model
Most projects embrace a fixed
methodology, ePub uses what's best for it.
ePub will follow the classical waterfall model in
the earlier phase (project definition and project design ) of the project and
the iterative model in the later phase ( development and testing ) of the
project. Using this approach we can spend a good amount of time in learning
and understanding the requirement of the system which will result in a good
and detailed design before starting the implementation. All implementation
will be done incrementally. Features will be added one at a time followed by a
test, build and release cycle. Every time a new module is added, the entire
product is built from scratch and tested to ensure product integrity. Only
after the code passes all these tests it is integrated with the rest of the
code in the source control repository. After every major feature addition, the
product is reviewed by the customer and changes are made to the product
following an iterative process till the customer is satisfied.
