- Forward


Analytic Geometrty - Software Design Considerations


Prof. David Bernstein
James Madison University

Computer Science Department
bernstdh@jmu.edu

Print

Qualitative Goals: A Reminder
Back Forward
  • Adequate - Meets all of the requirements and satisfies all of the constraints
  • Reliable - Low probability of failure under normal operating conditions
  • Robust - Able to operate under a wide variety of condtions
  • Safe - Able to minmize the damage resulting from failure
  • Easy to Repair and Enhance
  • Easy to Understand/Document and Use
  • Easy to Re-use
High Level Design
Back Forward

What classes do we need?

High Level Design (cont.)
Back Forward

What are the relationships between classes?

High Level Design (cont.)
Back Forward

Can line segments cross or must they intersect at a point?

Low Level Design: Attributes
Back Forward

What collections should we use?

Low Level Design: Attributes (cont.)
Back Forward

Do we need other attributes (e.g., color, line thickness)?

Low Level Design: Methods
Back Forward

How should we retrieve components?

High Level Design Revisited
Back Forward

Should we change the class hierarchy or add any interfaces?

There's Always More to Learn
Back -