1. Bringing OOAD&P Together: A Synthesis Approach Daniel GouletRobert Dollinger Department of Mathematics and Computing University of Wisconsin-Stevens Point Stevens Point WI

2. Object-Oriented Concepts

3. Software Development Strategies

4. Software Development Concepts

5. Software Development Tools

6. PROBLEM: How do we, as faculty: Pull together all these ideas? Make sense out of these ideas? Give our students a Cohesive and Coherent approach to software development?

7. Our Solution – Goulet/Dollinger Information Systems Development Software Modeling & AnalysisSoftware Solution Construction Analysis of Business Requirements Analysis of Technical Requirements Computational Independent Model Platform Independent Model Analysis of Platform Requirements Platform Specific Model Code Design In Target Platform Business Model Requirements Model Analysis Model Design Model [Iterative / Incremental / Documentable / Traceable] Problem Solution

8. Our Solution in Two Diagrams 3-Tier Model Example Modified Unified Process Domain Class Manager UIForm HNDLR Domain HNDLR «dataAccess» DomainDA «dataManager» DomainDM Data Manager talks to the data source UIForm Domain Class Manager UIForm HNDLR Domain HNDLR «dataAccess» DomainDA «dataManager» DomainDM Data Manager talks to the data source UIForm User InterfaceProblem Domain Data Source

9. Our Pedagogical Approach Tools Cartouches

10. Cartouche: #4  Problem: How are events summarized in a graphical format?  Solver: Project Team  Primary Audience: Client / Sponsor  Secondary Audience: Project development team  Solution: Constructing a use case diagram modeling interactions / events / requirements.  Tool: Use Case Diagram  Product: Use Case Diagram showing the required interactions between actors and the system.

11. Tool #10:Use Cases & Use Case Diagrams Use case = a sequence of actions a system performs that yields an observable result of value to a particular actor.

12. The Organizational Structure:

13. The Traditional Approach Entity Data Access Data Source Each Entity class has its own Data Access class to interface with the Data Source

14. Functions of the Data Access Class The Data Access Class performs two types of tasks: Entity specific and Data Source specific Data Source (Relational, XML, Flat Files, Other) Data Access Entity Retrieve Delete Modify Save Connect Open Close

15. Proposed Approach Entity Data Source Data Manager One Data Manager Class that handles requests from all entities and can be sub-typed for each particular Data Source type (Relational, XML, Flat files or other)

16. How is done? The Data Manager is partly a code generator, and partly a Data Source manager Data Manager Use object reflection to automatically generate entity specific code for the: Save, Modify, Delete and Retrieve methods Provide Data Source specific code in sub-classes of the Data Manager: DBDataManger, XMLDataManager, FlatFileDataManager Retrieve Delete Modify Save Connect Open Close

17. Conclusions Proposed methodology: Used in classroom [3 years] Proved a useful tool in helping students acquire a practical view on the application development process that is:  Iterative  Incremental  Documentable  Traceable

18. Questions? ?