Contents

Systems Methodology

This represents a value-rich model of how purposeful system developments may take place. It also has powerful connections with the human information processing system.

"Necessity is the mother of invention; invention is the father of necessity."

Vision

The mission statement!
Explicit declaration of the purpose of the system.

But what does it all mean?

Meaning

Recognition of the intended:
  • environment
  • market
  • context
  • scope

These have to be recognised before it is possible to start any meaningful planning.

Planning

Proper preparation and prior planning prevents piss-poor performance. Project planning should include:
  • risk analysis
  • integrity
  • development methodologies
  • interfaces with the environment, structure, methods.
  • scenarios, rehearsal, role-play.
  • test plans

All of this work is necessary to fully realise what the system constraints may be.

Constraints

System constraints from such things as:
  • government legislation,
  • business rules, 
  • limitations of technology e.g. hardware and software tools
  • Procedures for quality standards

With these known, full-scale development of the product or system can go ahead.

Development

Getting closer; some tangeable results will start to emerge at this stage.
  • analysis and design
  • prototyping
  • programming
  • testing, testing, testing

All this needs to be done before the product/system can be produced

Production

Implementation of full-scale production, leading to action that completes the cycle.

Action

Do it!

Delivery and fullfillment of the original vision.

Add your own comment to this page

Your name would be appreciated:

Please let us have your email address so we can respond privately to your feedback (if appropriate).
It won't be shown anywhere on this website (that's a promise):

Please add your comment here, and then click on the button below: