Complex Software Problem Solving by Means of Abstractive Techniques

摘要

Studies have shown that a large number of medium to large scale software intensive system development are cancelled. The primary reasons include the loss, lack or mis-understanding the problem to be "solved" - from customer to engineers and even amongst the engineers themselves. The Object Boundary/Context modelling process is key to immediate "system" understanding of the problem space at the highest level, enabling a "context" for formulating plans and requirements elicitation. Furthermore, it provides a communication point between all stakeholders and enables the correction of misunderstandings at the earlier stages of a software intensive system development. The model does not seek to supplant conventional formal analysis/architecture/design but acts as the earliest model to ensure that complex software problems do not turn "wicked".