RE: What do you do when "you have no business being a programmer" ?

["Reeve" <news@xxxxxxxxxx>]

This appears to be an interesting concept, like a data miner, and some of
the concepts are useful.  

In my case, I'm less worried about the technical/coding side than I am the
requirements side.  If I get the requirements right the first time and
understand the implications of what I'm doing, the development effort will
be more cost-effective because I'll provide more in the initial release and
have less rework to resolve the "user expectations <> developer
understanding" situation.

Besides, any given business process I examine might end up not being coded
or coded for another system.

-reeve

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
> Sent: Tuesday, March 02, 2004 10:06 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: What do you do when "you have no business being a
> programmer" ?
> 
> Reeve,
> 
> I was always intrigued by Rob Dixon's ERROS application, but I couldn't
> say
> if it would fit the bill....
> 
> http://www.erros.co.uk/
> 
> Eric DeLong
> Sally Beauty Company
> MIS-Project Manager (BSG)
> 940-898-7863 or ext. 1863
> 
> 
> 
> -----Original Message-----
> From: news@xxxxxxxxxx [mailto:news@xxxxxxxxxx]
> Sent: Monday, March 01, 2004 4:56 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: What do you do when "you have no business being a
> programmer"?
> 
> 
> You become a designer, of course.  And to think you thought the only
> forces
> in the universe were strong, weak, electromagnetic, and
> gravitational.how
> about the Peter Principal as the fifth?
> 
> 
> 
> Actually, I'm looking for feedback on upper-level CASE tools.
> 
> 
> 
> I need a tool (really, a better methodology with a supporting tool) I can
> use with users who know their business processes and rules thoroughly
> but
> are unable to present their knowledge of the rules, especially the
> exceptions to the rules, in an organized way.  By using a tool, I'll have
an
> organized way to enter rules and processes, and provide user-palatable
> output.  Then I'd like to take the user-level output (flow diagrams,
> explanations, etc.) and add additional detail (pseudocode, etc.), thus
> providing a programmer with a relatively complete flow/logic/control
> structure.  It looks like I need an "agile modeling" tool with mostly
> upper-level, but some lower-level, CASE capability.
> 
> 
> 
> It appears that having a tool like this will significantly simplify
handling
> user design change requests.  Going from nothing to something is hard
> enough; going from one place to another application programming-wise
> can be
> murder, and it's frequently programming quicksand.
> 
> 
> 
> Rational is out; it's more than I need in both cost and functionality.
> While UML is on its way to becoming the standard, that's not exactly the
> way
> I want to go.I think.  I'm looking at SmartCase and Visual Case; B-liner
is
> interesting and is cheap.  Any other suggestions?
> 
> 
> 
> Also, I'd appreciate any war stories on the proper way to utilize the
> methodology and the tools.
> 
> 
> 
> Thanks,
> 
> Reeve
> 
> 
> 
> 
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.