1. PROG 24178 Developing Robust Modular Software.

2. Objectives What do we want? Programmatic Elements in a Business System. Logic Layer. Persistence (Data) Layer. Presentation Layer.

3. What does a customer want from a program? What does a customer want out of a program? (Class Discussion).

4. Coding can’t do it all for us? The maintainability of a program is tied closely to system and software design not coding. The reliability of a program cannot be confirmed without testing. The usability of a program is tied to the user interface design. The speed or throughput of a program is a function of design, coding, hardware.

5. Why are we here? We are going to learn how to use standard programming procedures and object-oriented techniques to deliver a maintainable and reliable program to satisfy well specified user requirements.

6. What does this involve? Object-Oriented Concepts. Understanding the object-oriented concepts helps us design better systems. Programming Algorithms. There are standard algorithms (recipes) for solving specific types of problems. The Java Syntax and API. Testing Techniques. You cannot be sure your system is reliable if it hasn’t been tested.

7. But I thought this was a Java Course. NO! It is not. It is the concepts, techniques and patterns that are more important. The same course could be taught with C# and Objective-C. The knowledge of how to implement an OO solution for a user problem is transferable to C# and Objective-C.

8. Components of a User Solution. Logic (Business Logic). Logic relating to actual business operation. When a customer transfers an amount from one account to another account, subtract transfer-amount and service charge from first account and add transfer-amount to second account. Data (Persistence). Important operations must be recorded so that they are retained even after program stops. Could be in a file or in a database. Presentation. Typically a pleasant and effective user interface must be provided so the data can be input and displayed.

9. Mixing The Elements. SYSTEM Module

10. Mixing The Elements Maintenance is difficult. If there is a change request or bug fix finding the logic is more difficult. This also goes for finding the Persistence and Presentation Code. Since Logic, Persistence and Presentation is tightly bound changing one might break the other.

11. Layering The Elements. SYSTEM Module

12. What we will learn. Weeks 1-7 The Logic Layer Important Object-Oriented concepts. syntax and APIs to help code the business logic of a program. Common tools to help with testing Object-Oriented programs. Weeks 8-14 Persistence and Presentation Concepts, syntax and APIs to help code the presentation and persistence layers. Final Project. Array-Handling.

13. Course Structure Outline and Class Plan. Evaluation and Plagiarism. Course website. Preferred Contact procedures.