Software life cycle in Erlang

[Lennart Ohman]

Hi,
I am not clear over if the head-line "Prototyping model" means
that you are only trying to elaborate over the phases in
prototype development!? In that case I certainly agree with Thomas'
comments. In a prototype project one should really try to
get down implementing as soon as possible rather than trying to analyse
the problem fully first.
Otherwise, if we are not talking about a prototype but a fully
commercial system, then as you so correctly put it in your headline
"Life Cycle" one must not forget that initial development is actually not
the main part. It is the cost for making changes, extensions,
bug-fixes, trouble-shoot difficult problems, supporting customers and
understand how it all was done in years to come.

Best Regards,
Lennart

-------------------------------------------------------------
Lennart Ohman                   office  : +46-8-587 623 27
Sjoland & Thyselius Telecom AB  cellular: +46-70-552 67 35
Sehlstedtsgatan 6               fax     : +46-8-667 82 30
SE-115 28, STOCKHOLM, SWEDEN    email   : lennart.ohman@REDACTED 
________________________________________
From: owner-erlang-questions@REDACTED
[mailto:owner-erlang-questions@REDACTED] On Behalf Of Inswitch Solutions
Sent: Wednesday, January 25, 2006 3:13 PM
To: erlang-questions@REDACTED
Subject: Software life cycle in Erlang

Hi,
 
I'm trying to figure out the best model for software development in Erlang.
What do you think would be the right values for Analisys, Design,
Implementation and Testing phases?  
 
Prototyping model:
Analisys............... 20% 
Design................. 20%
Implementation.... 35%
Testing................. 25%
 
Any comments?
 
 
regards, Eduardo Figoli
 

Prepaid Expertise - Programmable Switches 
Powered by Ericsson Licensed Technology
Eng. Eduardo Figoli - Development Center - IN Switch Solutions Inc.
Headquarters - Miami-U.S.A. Tel: 1305-3578076 Fax: 1305-7686260
Development Center - Montevideo - Uruguay Tel/Fax: 5982-7104457
e-mail: eduardo@REDACTED