Information Technology Reference
In-Depth Information
Customer
Order
class name
name
address
1
0
..*
date
status
attributes
association
calcTax
c alcTotal
calcTotalWeight
1..*
1
operations
Payment
abstract class
amount
1
role name
generalization
multiplicity
line item
1..*
Credit
Cash
Check
OrderDetail
Item
number
type
extDate
cashTendered
name
bankID
quantity
taxStatus
shippingWeight
description
0..* 1
authorized
calcSubTotal
calcWeight
getPriceforQty
getWeight
authorized
Fig. 6.2
Class diagram (Miller 2003 )
requirements document for this enterprise. Subsequently, we ought to provide for
system-context interaction, subsystem delineation and vocabulary development.
We will, however, bypass these steps. Our abstraction level eliminates the analyst.
We cannot effectively discuss system-context interaction or model construction.
Additionally, the OOA process is too abstract to allow subsystems to be properly
distinguished. The vocabulary consists of concepts such as: class, relationship,
instance, attribute, constraint, transition network, state, transition, etc. Such a
vocabulary allows us to go straight into class elaboration.
In the analysis phase, a model of the real-world application is developed
showing its important properties. It abstract concepts from the application domain
aid in the describing of what the intended system must do, rather than how it will
be done. Most proponents of object-oriented analysis (OOA) claim that the use of
object-oriented concepts in the analysis phase (i.e., OOA) increases the under-
standing of problem domains, that OOA promotes a smooth transition from the
analysis phase to the design phase, and that OOA provides a more natural way of
organizing specifications (Coad and Yourdon 1990 ). Extant object-oriented
approaches can be classified into three categories (Monarchi and Puhr 1992 ):
combinative approaches use different modeling techniques in different stages of
the system development process; adaptive approaches apply existing techniques
(e.g., data-flow diagram and entity-relationship approach) in object-oriented ways
to analyze the problem domain; and pure approaches adopt an object-oriented
perspective in systems analysis and design.
 
Search WWH ::




Custom Search