The feasibility study is essentially this: you define what you require; we ascertain whether we can do it - is it feasible? Sometimes the answer is no; but mostly, yes.

Quite simple really, you let us know what you require, let us know the budget we have to work with, then we can calculate whether we are able to deliver a product that meets your requirements.

As always, you will find there are trade-offs.  Not to worry, since there are many ways to achieve something close to what you want, it just takes negotiation.  As an example, an industry standard project would provide additional modules or functionality for additional cost - the project is complete from a systems analysts viewpoint, but a client may only need certain features, so for a reduced price, the customer gets his requirements met.  More often than not, the issues lie with the project being too large for the budget, so our job is to see what features can be built in at a later stage or increase the budget.  Since we all too often now the software is sold on subscription basis per month, we have managed to almost eliminate costing issues as costs are now spread over a term making an easier target.  Monthly subscription-based purchases also allow the client to invest in updates and newer technology.  There will be an upfront cost, but it would be significantly lower than a perpetual license.

So, we can see the feasibility of a project can easily be attained from a cost perspective; now we only need to concentrate on the features aspect.  This part is most likely staged over a term suitable for the client and can allow the client to become more familiar with the day-to-day working of the system and be better able to provide live feedback which can be incorporated into the system.

Back To Overview: OverView

Previous Article:

Next Article: Analysis

Please note all prices displayed on this website are quoted in US$. If you require other currencies, please advise.