Discussion Locked

Decision Criteria

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have just begun my first job and I am in charge of designing and developing a system that centralizes information and helps Drilling Engineers hone in on solutions when working on their rigs. Basically I am going to be creating the interface for 20 modules that the drilling engineer can go through.

Right now I am in the process of determining selection criteria for choosing the development environment I will use to build this system. The four environments we narrowed it down to are VB, .net, Java, HTML/XML/ASP. The solution created has to be able to be online as well as stand alone. So far the criteria I have come up with include:
-Cost (is additional software needed)
-Security
-Operability (able to run on internet & stand alone)
-Speed of programming/productivity (I might have to learne new languages)
-Future needs vs. Current Business needs (has to be completed in by end of 2002)
-Ease of integrating (spreadsheets, docs, 3rd party exe, databases, etc)
-Maintenance of system
-Scalability

I would appreciate any help anyone can offer, as this is my first job out of school. I am a bit nervous about the whole process.

Aryana

5 replies

by sridharpandu

I suggest that you consider PowerBuilder 8 (PB). It addresses all u r concerns.

Cost - Though you might have to buy licenses for all u r developers, deployment is done using runtime licenses which can be freely distributed along with u r app.Security - Use Oracle it complies with ISO/IEC 15408 standards

Operatability - PB apps can have Client server or Browser based deployments.

Productivity - Also PB combines RAD with OO capabilities incresing developer productivity thereby reducing cost.

Business Needs / Maintenance - PB apps are easy to maintain because of its modularity and incorprating changes is not clumsy.

Integrating - Supports OLE, Active X, COM, COM +, EJB etc allowing you to plug and play!!!

Scalability -Incoporate fail over clustering and load balancing features at the hardware, app server and database level

by timthetoolman

Hi Aryana,

Yep, you seem to be doing the right thing by defining the criteria. I'd add "Risks of potential choice" and "Current level of Support"

Then I'd draw it up as a matrix, and rank all the options and add their ranking into the matrix.
Ranking some may be difficult. In some cases purely subjective but if you can back up your decision with any facts, then you'll be ok.

You could add weightings if you need to - for instance cost may be far more important to you than Scalability(or not depending how you see it...)

Add them up and see how it pans out.

An interesting note, however... VB and ASP have both converged in .NET and so if you went with Visual Studio.NET you'd automatically get three of your four options!

My personal preference right now is for the other .NET language, C#.

Its still in beta, though and wouldnt rate well on your "Risk" criteria :-)

It would rate extremely well on many of the others, though.

Hope it goes well for you!
Cheers,
Tim.

by aryana79

This was a great answer and provided me with two more criteria. My boss liked everything that I had come up with. Thanks for your help Tim!!

This discussion is closed to new replies.