Module - Design, Development and Creativity
Class or Article - Article
Lesson or Name - Racoon, L. B. S. (1995) The
chaos model and the
chaos cycle. ACM SIGSOFT
Software Engineering
Notes, 20, 12.
Additional Info - N/A
I am a big advocate of problem solving techniques having studies a design degree and currently studying a digital innovation masters. I believe to resolve any issue we should not be confined by the limitation of what we know or what a systems does and ever avenue should be explored. The idea of problem solving at all levels and that all problems are equal is something that I believe is a worthy persuit however in the world of business this can not be the case. Where timelines and money are on the line it is inevitable that some problems will take precedent and that not all issues, large or small can be treated equally. However a caveat to this is the smallest issues may have larger implication and vice versa which cause havoc on development teams working to resolve issues.
The idea of fractals and an iterative approach to development is quiet interesting to me, working to develop stage by stage building extensions on to capability and functionaliy in a way allows a project or programme to grow at a steady pace releasing functionality and ensuring that each components it created equally and with consideration and in turn when there are problems to be resolved equally this approach would work. Additionally developing in this manner means that the developers develop an intricuit knowledge of the system and could allow differnt style of coding (Big Ball of Mud) which is inevitable in large scale quick builds. Working this iterative phase with the user means they are getting what they want, when they want it or know it and that the system is coded througout to function and co-exist with itself across all stages.
Iterative design and release if certainly an approach I would like to be apart of on a project or to create multiple teams working on different sections or fractals withe the customer, then co-creating the systems and its integration points. This will certainly be something I will bare in mind for the next development project in my company and I will look out for it elsewhere aswel.
Quotes
Precis
In 'The chaos model and the chaos cycle' by Racoon the article focuses on the grey areas that frameworks generally overlook such as the developer specifically. Equally frameworks look at each phase of a lifecycle in terms of producing a complete lifecycle. I this article Racoon looks at the 4 stage Chaos model for linear problem solving 'Problem Definition, Technical Development, Solution Integration and Status Quo'. Racoons' aim is to understand the impact of one line of code on the entire project and believe the Chaos theory and fractals help to understand the sub process that impacts the entire process. Sub-processes are each values as approximately the same size and value meaning that they have the same value and impact on the process and project. Racoon explains the use of fractels and the chaos theory and how the chaos theory can in turn live within each fractal and as a result the chaos theory is iterative and holistically applied to the project. He goes on to explain that all levels of a project are connected through a web on interconnections througout the whole project like a spiders web and that one little line of code has impacts to each component it touches across all levels. No matter where in the program this error occurs it has the same weighting and requirement to be fixed. Equally Racoon explains that the user needs to be considered part of the project and understand the application of the development on to the users creating dialog moving at the one pace with each other in order to develop a system to the users needs and wants.
In summary and summered up well by Racoon 'lifecycle depicts the sequence of events within a project, while a model depicts the structure within a project' Each phase of a project in theory is equal and that each can be done in any sequence. Problems do not reside within any one phase and the simplicity of this understanding by the program shows the project or programmes perspective on projects.
In summary and summered up well by Racoon 'lifecycle depicts the sequence of events within a project, while a model depicts the structure within a project' Each phase of a project in theory is equal and that each can be done in any sequence. Problems do not reside within any one phase and the simplicity of this understanding by the program shows the project or programmes perspective on projects.
Reflection
I am a big advocate of problem solving techniques having studies a design degree and currently studying a digital innovation masters. I believe to resolve any issue we should not be confined by the limitation of what we know or what a systems does and ever avenue should be explored. The idea of problem solving at all levels and that all problems are equal is something that I believe is a worthy persuit however in the world of business this can not be the case. Where timelines and money are on the line it is inevitable that some problems will take precedent and that not all issues, large or small can be treated equally. However a caveat to this is the smallest issues may have larger implication and vice versa which cause havoc on development teams working to resolve issues.
The idea of fractals and an iterative approach to development is quiet interesting to me, working to develop stage by stage building extensions on to capability and functionaliy in a way allows a project or programme to grow at a steady pace releasing functionality and ensuring that each components it created equally and with consideration and in turn when there are problems to be resolved equally this approach would work. Additionally developing in this manner means that the developers develop an intricuit knowledge of the system and could allow differnt style of coding (Big Ball of Mud) which is inevitable in large scale quick builds. Working this iterative phase with the user means they are getting what they want, when they want it or know it and that the system is coded througout to function and co-exist with itself across all stages.
Iterative design and release if certainly an approach I would like to be apart of on a project or to create multiple teams working on different sections or fractals withe the customer, then co-creating the systems and its integration points. This will certainly be something I will bare in mind for the next development project in my company and I will look out for it elsewhere aswel.
Quotes
Comments
Post a Comment