[kplato] Functional Breakdown (comments)

[Jim Sabatke]

I am really glad that you are bringing these things up.  If you aren't 
getting some of the discussions, there are probably others in the same 
boat.  A glossary is a great idea.

Jim

Chris Herrnberger wrote:

>On Monday 18 June 2001 20:03, Anders Johansson wrote:
>
>>These are clearly separate tasks, since it's not the same tire. They cannot
>>be the same task, since installing one tire does not mean that the other
>>one is also installed.
>>
>>A better example might be if you're running two projects on the same
>>platform, and there's a bug discovered on that platform (the scenario
>>actually occurred in the project I'm in now). Both projects will then
>>depend on that bug being fixed, and there you have a task that can belong
>>to two projects.
>>
>And the project manager who is charge of product development would not make 
>that disctintion as he manages one project, all projects, same as the CEO and 
>controller.  
>
>OK IM starting to get it. You lads are clearly using programming logic here, 
>and or industry specific (software/hardware practices) not general user 
>logic. Non issue, just need to sort the terms and their usage in my own mind. 
>
>The work I do these disctinctions as described would not reflect our working 
>reality nor the manner in which we would manage the project. That is not to 
>say it is either is wrong. This form of logic does have an impact though on 
>the apps design.
>
>Perhaps a glossary of terms where such terms are defined: ie: project, would 
>help non programmers such as me.
>
>Best and many thanks
>
>Chris h
>_______________________________________________
>kplato mailing list
>kplato@master.kde.org
>http://master.kde.org/mailman/listinfo/kplato
>
>

-- 
Jim Sabatke
SuSE 7.1 Linux
Kernel - 2.4.0
http://www.execpc.com/~jsabatke

"People tell me that I'm fading fast, that I can't last the whole night through" Janis Ian