"LOL ! .. or get me sued for revealing confidentail info ! " and then
"I knew one project manager ..." and then "It is normally in the
planning stages (of STD IT dept. development) than things go wrong."
So, it is all inside your head, and your experience dictates that
everyone else is wrong. Everyone else is simply supposed to believe
this as gospel? You seem to be prescribing starting out on a journey
without knowing what the destination is.
Planning is necessary. If you believe the 'agile' creed, it tends to
happen 'concurrently' (in collaboration) with coding or just
'afterwards' but for everyone else, it happens first. The key thing is
that it happens.
Take a real life application: in the UK, the vision (already partially
implemented) is that all GP practices, Primary Care Trusts,
Pharmacies, and others like VET practices work with a centralised
database, called the SPINE. Every agent requests or responds to
messages logge on the SPINE. E.G a GP logs a patients prescription
into the Spine, a pharmacy retrieves it therefrom etc. Google for more
information. This involves
1. working in collaboration with the SPINE people
2. abiding by the legislation and protocol governing the UK Data
Protection Act and medical ethics.
3. observing and working in line with the work practices of doctors,
nurses, vets etc.
4. safeguarding the accounting standards for claims from the NHS.
etc.
Technologically, I KNOW that APL can deliver the functionality without
any problems. Guess how many system there are that are coded in APL?
N-O-N-E!
Over to you: write a system for GP practices and/or pharmacies. There
are in excess of 20,000 of each of them and you can rent your software
for around =A3400 each per annum per pc.
If it is 20 times faster in APL, you should have no problem catching
up with existing developments and then soon overtake them and deliver
something that is better ... for =A38,000,000 per year in your pocket.
|
