Difference between revisions of "OODE"
From Suhrid.net Wiki
Jump to navigationJump to search| Line 9: | Line 9: | ||
== When to use OO == | == When to use OO == | ||
| − | * For the systems where the user is in control e.g. decision support systems, CRM's, enterprise systems | + | * For the systems where the user is in control e.g. decision support systems, CRM's, enterprise systems. OO makes it easier to model such systems. |
| − | + | * Systems where long term extensibility is important. Again OO's concepts make it easier to incorporate extensibility. | |
| − | * Systems where long term extensibility is important. | ||
| − | |||
== What is OO Development == | == What is OO Development == | ||
Revision as of 07:13, 21 October 2011
Introduction
Why OO
- Modern systems are large and complex - lots of interconnected components, distributed and heterogeneous.
- OO is particularly useful to build such systems.
- Remember OO is not always the best approach, but is useful in the right setting.
When to use OO
- For the systems where the user is in control e.g. decision support systems, CRM's, enterprise systems. OO makes it easier to model such systems.
- Systems where long term extensibility is important. Again OO's concepts make it easier to incorporate extensibility.
What is OO Development
- Quite simply, the use of classes and objects in developing software and systems.
- OO Development implies using classes and objects throughout the construction process - requirements analysis, design, coding and testing.
