Object And Process Modeling, And Stragies For System Analysis And Problem Solving
1094 Words5 Pages
System Analysis and System Requirements
Object Modeling, Process Modeling, and Strategies for System Analysis and Problem Solving
April 6, 2005
A class can be described as a collection of objects of similar type. These objects often share the same attributes, operations, methods, relationships, and semantics. Additionally, once a class is defined any number of objects can be created and associated to that class. For example, beagles and boxers represent different breeds (i.e. instances) of "dogs" which also can be viewed as a distinct class. Furthermore, defining classes, as part of the object modeling process is not that different from the traditional system analysis process, which seeks to achieve a goal (i.e. object modeling seeks to understand a solution; whereas, system analysis which seeks to understand a problem).
Attributes are data fields that represent some property of the containing object that is shared by all instances of the object's class. Attributes normally have names (e.g., "Address") and Types (e.g., "String" or "Boolean"). An example of this would be the "Address" of a "User." In addition, attributes define the characteristics of the class that, collectively, capture all the information about the class.
Encapsulation represents packaging several items together into one unit. In addition the application of encapsulation involves keeping the external representation of an entities properties and methods independent of its actual implemented use. Encapsulation therefore, allows an entity to be leverage by other parts of an application without the fear of changes in the implementation use causing a snowball effect.
Logical Process modeling is a technique for organi...
... middle of paper ...
...ct model vs. the traditional approach that represents these requirements in the form of data structures and views. In addition to its difference from the traditional system methods, OOA provides the following distinct benefits: maintainability, reusability, and productivity. OOA has proven to be an effective method for conducting System Analysis and Development, and will undoubtedly flourish as more and more organizations seek alternatives to the complex and rigid traditional methods.
Jennerich, B. (1990). Joint Application Design: Business Requirements Analysis for
Successful Re-engineering. UNISPERE. Retrieved April 5, 2005, from http://www.bee.net/bluebird/jaddoc.htm
Yourdon, E. (1989). Modern Structured Analysis. Yourdon Press Computing Services.
Retrieved April 4, 2005, from http://pages.cpsc.ucalgary.ca/~jadalow/seng613/sasd_summary.html