Requirements

From Awesome SOA project

Revision as of 00:51, 21 May 2007 by Vezhlys (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

This is requirements for our project, which was made by academic teacher.

The project reward consists of:

  • Soundness of the business vision -1 point
  • Excellence of conceptual and technical architecture - 1.5 points
  • Completeness of implementation - 1.5 point
  • Overall marketable value: look and feel, description etc. - think in www.strikeiron.com way about your service - 1 point

In addition:

  • Excellence of the project “process” site, such as project wiki - 4 points to share between the team members - you will decide yourself how you will split that
  • Peers’ praise - i.e. if other teams think your project is cool, they can award other teams giving maximum 4 points for a single team (out of 6 points total “team prize fund”, which each team is given to show their appreciation of others’ work). No team cannot use the prize fund to award themselves of course.

And more:

  • Within a team, it is possible to give up to 3 points voluntarily if someone feels he or she was slacking and was getting a free ride by the rest of the team. And vice versa - a “troika” (three members voting unanimously) have the powers to strip the fourth member by 3 points maximum if the latter will have underperformed yet thinks “well, no big deal…”.

The idea of the project is to think of some added value, which can be sold to some customers by providing them with a service (simple or aggregated/composite), which takes some data/functionality from somewhere and presents it in an SOA way (WS/SOAP or REST) in a clean and marketable way. Let me repeat - there must be a realistic business-value component involved in your solution. The more real - the better. You are free to choose the platform + tools, as long as they adhere to the WS/REST standards.

Each project needs to be implemented by a team of 4 people, please team-up and set up a point of contact (blog, wiki etc) to make the project transparent. Make sure you will be using social software to communicate - this is NOT optional. Please be quick to avoid being left behind and work in an incomplete team, which will mean less fun and more work for you. Unless you are a die-hard individualist, of course, but then you will face some problems anyway.

Additional rule: if someone is left behind to work alone (imagine that we have 29 people) then the last full team to register will need to ask someone from their ranks to volunteer and join the poor lone soul Image:icon_wink.gif.

Translation: be quick to team up.