Conceptual design : Conceptual design usually takes the form of pseudo code or a flowchart that lays out the ideal logic structures to provide a solution. Our conceptual design has focused on pseudo code in the past two chapters. Suspiciously absent were flowcharts which will be replaced with UML (Unified Modeling Language) in the next
chapter. UML is the standard for graphically modeling logic that will be implemented using object oriented programming design. Detail design : We are ready to code our solution using a programming language. We take the conceptual design as a starting point and using the syntax options of the programming language, code the logic structures into programming language structures. This process step also does not change significantly except we are now designing driver and custom classes in addition to just program logic statements. Testing : We will perform unit tests as we go. We always need to test and the testing of class objects is just as important as the testing of structured programming applications. Implementation : During implementation, we move into produc/tion the test average calculator program on to the PC of the person using it. The program is complete and ready to use. Maintenance : No program is written once and not revisited without some changes. With object orientated programming and its extensive use of reusable code, maintenance is make more efficient since a class code is shared and a change to that class can be made once and propagated across to all the programs that use the class object.
Figure 5: The programming process using object orientated design techniques CACTUS CASE STUDY The light bulb is starting to get a little brighter with his chapter’s coverage of object oriented programming. You are beginning to see how OOP can make a significant difference in programmer productivity and how classes can save a lot of time and maintenance down the road. Based on Cactus Books and Tapes web site requirements, the web payment service can be implemented in several programs. But more importantly, now that you understand more about inheritance, the WebService payment method can be inherited and expanded upon to fill in added function needed by the web site but not included in the web service. You have told the Chavez sisters that reusing the code from the credit card company and adding an overriding the class with additional members can accommodate many of the e-commerce functions needed to keep the web site secure and easy to use for the customer. Look at the following requirements and implement then into a new class called CBTPayment. You will need to create a driver class to test your new class members. To do this your program must input parameters to each of the new methods for testing. We only work on testing the class in this exercise. We need to show the Chavez sisters how this is going to work.
You've reached the end of your free preview.
Want to read all 35 pages?
- Fall '16
- Object-Oriented Programming, derived class