 |
|
 |
|
The GOOP Methodology
GOOP Architecture
- Use Object Oriented methods for requirement analysis
- Apply Object Oriented analysis and design
- Document the result using UML
- Create classes to build reusable components
Scalability with Distribution
- Key parts of the application are isolated and can be run on different machines.
- Increases in functionality or performance minimize the impact on the existing GUI.
- Decoupling the different pieces of an application allow for easy expansions that do not adversely effect unrelated systems.
- Each object contains its own instance data, so invoking methods on one object does not affect other objects of the same class.
Maintainability
- As the application logic or GUI grows more complicated, the code is more difficult or impossible to modify if both the GUI and the application logic are in the same VI.
- Making changes or bug fixes to the GUI do not affect the application logic or vice versa.
- Change cycles for the GUI and the application logic are often different.
- By designing an application as a collection of components, the dependencies between the different parts of the system are reduced.
Reusability
- Decoupling the different pieces of an application makes reuse easier.
- Multiple GUIs would not be able to reuse application logic that is part of a top-level vi.
- Using a global variable to store state information makes it difficult to reuse a VI within the same application.
- If duplicate code or GUI is required within the same application, a separate global variable and corresponding set of VIs would have to be created.
|
|
|
|