Using functional design for large Java application(!)

[seanjohnstone]

My colleague and I are experienced Java programmers used to using UML for our design and specification. We also both have a history of C, C++, Fortran, Pascal, etc.

Our new team leader comes from the old-school of thought and does not fully understand OO concepts and insists that our pending enterprise Java application be designed and modelled using functional methodologies. He favours JSP and insists on us producing a linear and hierachical functional tree for the application. He comes from a stong C and Fortran background but does not understand Java.

How can we further convince him that such an approach will not benefit the implementation, let alone be possible? We have already spoken of the problem of modelling reflexive relationships, interfaces, threads and other concepts but he refuses to listen - insisting that he wants a functional linear design that he can understand...?

Sean.

 

[palbano]

>> Our new team leader

Who hired him? How did he get hired?

>> insists that our pending enterprise Java application be
>> designed and modelled using functional methodologies.

Poor leadership qualities.

>> How can we further convince him
>> but he refuses to listen

Again... poor leadership qualities, talk to the person that placed him in charge. It’s their mistake, so explain that he is unqualified for the position, and ask them to fix their mistake. If they won’t it sounds like you are between a rock and a hard place with no desirable result in sight.

If things continue as they are you will either have a garbage project or you will quit. Neither is a desirable result.

With that said, this subject is off topic for this forum. We have one here called Overcoming Obstacles Getting My Work Done, click here: forum655 You will get a landslide of input from that forum.


-pete

 

[ITChrism]

Hi Sean,

I recommend encouraging your fearless leader to read through David Taylor's "Object-Technology: A Manager's guide".

http://www.amazon.com/exec/obidos/tg/detail/-/0201309947/

I am convinced that this investment in that book will pay off. It is an easy, good read pointing out the advantages of approaching software development the OO way.

Good luck!
chrism

 

[DonQuichote]

In the book "eXtreme Programming Explained", Kent Beck points out that the cost of change has changed over the years. In the "old" procedural days, a program was one giant routine, so any change could affect anything. With the Object Oriented development systems of today, much more separation and independence is possible.

In case of the eXtreme Programming methodology, this leads towards a shift from "do it the first time right" (because changes were expensive) to "adapt to the situation" (because changes are cheap and situations tend to change).

What I am trying to say is that the structure of a language (procedural, OO or functional) does have an influence of how to run a project effectively.

I think your boss may need a literature update.

Best regards