| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Broker - estimating effort |
« View previous topic :: View next topic » |
| Author |
Message
|
| pm.person |
 Posted: Tue Dec 02, 2008 7:18 am Post subject: Message Broker - estimating effort |
 |
|
Newbie
Joined: 02 Dec 2008
Posts: 2
|
Hello. I am a project manager and a part of my current project involves Message Broker. I am trying to develop realistic estimates for some message flows that need to be developed. In most cases (some are quite complex), the flow involves three / four nodes - Database, Filter, Compute.
XLM input - XML output ; no mapping. I am told that average effort (including unit testing) should be 3 days.
Could anyone please comment on this - is this ambitious, generous, realistic? Any other insights are welcome. The idea is to provide the time required and not put people under pressure when we don't have to.
Thank you. |
|
| Back to top |
|
 |
| scravr |
| Posted: Tue Dec 02, 2008 8:35 am Post subject: Message Broker - estimating effort |
|
|
Partisan
Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021
|
in general for simple flow it take about 1 wk to develop (the first flow) and 2 days for unit test. then after first is OK it would take 3 days to develop and 2 days for test all other flows.
but i think you need to look at big picture: before you start design, think about major sub-flows: backup, error-reporting, reply, and more. then look into individual transaction and how they placed in overall design. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 02, 2008 9:13 am Post subject: Any Guestimates are useless unless |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
you have a decent ( ie as close to complete as possible) set of test data available from Day 1.
If you don't just like and decent programmer, they will spend > 50% of the dev time just creating the test data.
Designing Message Broker flows is just like any other Application Programming.
A Finger in the air guestimate is
20% Design, 30% coding & 50% Testing.
Unless things are pretty trivial.
Another factor (just like java programming etc) is the experience of your Flow developers you have board to do the work. Then the numbers may change.
Also if this is a greenfield site then the initial numbers will be longer.
If you are a decent project manager then you will know this already...
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Dec 02, 2008 9:43 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
A project manager who doesn't want to put people under undue pressure....
How do I get one of those?!!
 |
|
| Back to top |
|
|
| pm.person |
| Posted: Tue Dec 02, 2008 10:47 am Post subject: |
|
|
Newbie
Joined: 02 Dec 2008
Posts: 2
|
Thank you, everyone, for your help. I think I learnt most from:
"think about major sub-flows: backup, error-reporting, reply, and more. then look into individual transaction and how they placed in overall design.".
These are points that will help the less experienced in my team - they will help me to ask if these have been considered.
Best regards. |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Tue Dec 02, 2008 12:02 pm Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
From experience, a new site will take about 3-4 times as long for first flow than for others if similar transactions.
Also, if you need to develop some monitoring / management / error control then those will take as long as the rest of the project.
Initially, set 1 day aside for every database you want to connect to and 1 day for every established web service you need to connect to.
For every additional programmer on the job that must work together, add 10% additional time to co-ordinate communications.
For time difference between complex XML structures and simple ones also very different, especially during testing phase.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
