OpenPETRA Architecture Team

What is the Architecture Team?

A group of people within the openPETRA development team that looks at and improves architectural issues of various kinds.

Team Members

The openPETRA Architecture Team currently consists of christiank and MathiasG. They were nominated to that job by the the other openPETRA core developers at an openPETRA meeting in Carlisle (Nov.30th - Dec.2nd, 2010).

The members of the Architecture Team do not work full-time on architectural issues; rather they are 'normal' openPETRA developers who can be contacted about architectural issues and who are pro-actively looking for architectural issues as they go about their development work. They might work full-time on issues for a certain time as the need arises.

Purpose of the Architecture Team

The Architecture Team...

• proactively identifies issues in the architecture or development process of openPETRA and highlights them to the development team.
• investigates issues of the architecture or development process of openPETRA as identified by other development team members.

and...

• comes up with proposals on how to improve identified issues.
• implements changes to resolve or improve the identified issues themselves, or delegates the implementation of changes to another member of the development team, depending on whatever is seen as best and who/if somebody is available for that.
• creates and maintains documentation on the topics of
  • openPETRA architecture
  • development process of openPETRA

Discussions

Current Discussions

The list below contains discussions on current topics. There is no particular order unless priorities got assigned by the Architecture Team.

Please keep in mind that these are discussions only and might result in one or the other decisions!

Proposals are moved to this section once they become Discussions.

• The decision on that is to be made only by the Architecture Team!
• 'Status','Priority' and 'Responsible' and are to be assigned only by the Architecture Team!

• Inconsistent Error and Exception Handling
  • Status: Input requested (please feel free to contribute to this ongoing discussion!)
  • Priority: High
  • Responsible: ChristianK and ThiasG
• DB Discussions: Transaction Model, Savepoints, Locking; Exception Handling; Caching
  • Status: Discussion in progress
  • Priority: Middle-High
  • Responsible: ChristianK and ThiasG
• Changes to the Process and Workflows of openPETRA Development
  • Status: Discussion in progress
  • Priority: Middle-High
  • Responsible: ChristianK and ThiasG
• List of unused columns/tables in the database structure
  • Status: Input requested (feel free to contribute if you fall into category of people who are responsible)
  • Priority: Middle
  • Responsible: Everybody who works with the DB structure on a non-superficial level.
• Evaluation and Comparison of different logging Systems
  • Status: Firmer conclusions are required
  • Priority: Middle-Low
  • Responsible: WolfgangU
• Tools for Supporting the Process and Workflows of openPETRA Development
  • Status: Input requested (esp. in the List of Detailed Criteria section)
  • Priority: not yet assigned
  • Responsible: ChristianK and ThiasG with input from WolfgangB

Proposals for Potential Topics for Further Discussions

The list below contains proposals for discussions on topics that we might want to look at. There is no particular order unless priorities got assigned by the Architecture Team.

Please keep in mind that these are discussions only and might result in one or the other decisions!

You can add your own topics here - 'Status' and 'Responsible' are to be assigned only by the Architecture Team, though!

• Class naming - Should all classes start with "T"?
  • Status: Consider moving it to 'Current Discussions'
  • Responsible: ChristianK and ThiasG
• Decimal/Rounding Calculation Definition / Multiple Currencies
  • Status: Pending
  • Responsible: ThiasG with help from Wolfgang Uhr
• Unit test framework
  • Status: Proposal needs to be prepared
  • Responsible: ThiasG
• Directory structure - The current openPETRA directory structure does not fit together with architecture. Difficult for new people to find, what they are allowed to use and where to find classes.
  • Status: Proposal needs to be prepared
• Generated Files With Manual Code Blocks: Should be part of https://sourceforge.net/apps/mantisbt/openpetraorg/view.php?id=155
  • Status: Proposal needs to be prepared
  • Responsible: ThiasG
• Data Spread Over Many DB Tables vs. Same Data in One DB Table - Performance
  • Status: Proposal needs to be prepared
  • Responsible: ThiasG with Timotheus
• Database normalisation - For example the name of an account is stored in several tables and furthermore is used to link table entries and to define table relations. So it is difficult to change the names.
  • Status: Proposal needs to be prepared - exact scope needs to be determined
  • Comment: Each dataset should have an internal id and should be linked by the internal id (Thiasg 08:42, 24 January 2011 [UTC])
• Gathering of Statistics - Which Sites Use Which Functions of PETRA
  • Status: Proposal needs to be prepared
  • Responsible: ChristianK
  • Priority: Nice to have
• Business Layer
  • Status: Proposal needs to be prepared
  • Priority: None assigned
• GUI Generator: Simulator for Previewing of GUI (No Dev.Env. necessary?)
  • Status: Proposal needs to be prepared
  • Priority: None assigned

Decisions Taken

• Other Source Code Versioning System than git: Moving to Bazaar after evaluation (Dec. 7th, 2010, architecture team meeting).
  • Move to a Bazaar Repository completed on Dec. 14th, 2010, after two days of intensive evaluation.

Meeting Notes

• openPETRA meeting in Carlisle (Nov.30th - Dec.2nd, 2010)