Download
lecture 7 designing classes n.
Skip this Video
Loading SlideShow in 5 Seconds..
Lecture 7 Designing Classes PowerPoint Presentation
Download Presentation
Lecture 7 Designing Classes

Lecture 7 Designing Classes

88 Views Download Presentation
Download Presentation

Lecture 7 Designing Classes

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Lecture 7Designing Classes CS140 Dick Steflik

  2. A Good Class • Should represent a single concept from a problem domain • domain = mathematics; point, rectangle, elipse • an abstraction of a real-life entity • BankAccount, CashRegister

  3. A cohesive Public Interface • Minimize Dependencies • Separating Accessors and Mutators • Minimize Side Effects

  4. Cohesive Public Interface • The methods of a class are like members of a soccer team, they all have to be working for the same thing • Ex: Cash register shouldn't have to keep track of coin values, this is better done by a Coin class. • this way Coin class could be easily adapted to different currencies and the cash register would still work

  5. Minimize Dependancies • Never do I/O in an object method • not all environments support the same I/O • ATMs done have console output; no console • Most consumer electronics products have limited I/o , especially for console output • In GUI apps you have the possibilities of AWT, Swing or Android GUI, this requies special I/O for each

  6. Separating Accessors and Mutators • An accessor retrieves a piece of state data • A mutator actually modifies the state by changing some piece of state data • A class that has only accessor methods is called immutable • String is immutable, i.e. there isn't a method that can modify the String • use for classes that represent values: strings, colors, currency... • In a mutator class separate the mutator and accessor methods, make each method do just one thing

  7. Minimizing Side Effects • Call by value Call by Referance • In Java, numbers and object references are passed by value; a Java method can mutate an object when it receives an object reference as an arguement

  8. Side Effects • An effect (intended or not) that is secondary to the one intended. • Side effects are not desirable. • they make code harder to debug • are often undocumented featuresclass myclass{ private int abc, def; int getVal (){ def++; return abc;}}in addition to returning the value of abc there is a side effect of def being modified, unless this is very well documented it will not be noticed by most people looking at the code

  9. side effects (more) public double getTotalBalance(Arraylist<String> accounts) { double sum = 0; while (studentNames.size() > 0) { BankAccount account = accounts.remove(0); sum = account.getBalance(); } return sum; }} this does return the total balance but also causes accounts to be emptied out. This may or may not be what was intended but is secondary to the primary purpose of the function

  10. Static Variables • accessible by all instances of a class • belong to the class not to any instance of the class • could be used for instance communicationclass airplane{ private static bool flag = false; private int myId = 1000; private static int lastId = 1000; private static int controller = 0; private int message = 0; public airplane() { myId = lastId++ ; ) public void takeControl { if (!flag) { flag = true; controller = myId; flag = false;} }

  11. Static Methods • methods that work on values not objects • For instance Math.sqrt(x) takes a double as its argument (which is a primitive not an object) and returns a double. The Math is the name of the static class and sqrt is a static method in that class. No object called Math has been instantiated. • You can make your own static functions but it should be minimized

  12. Packages • A package is a collection of related classes • A Java package is a mechanism for organizing Java classes into namespaces . Java packages can be stored in compressed files called JAR files, allowing classes to download faster as a group rather than one at a time. • Programmers also typically use packages to organize classes belonging to the same category or providing similar functionality. • JAR (Java Archive) files are a modified version of a .zip file • Packages are also used to avoid naming collisions (using the same variable name in two different places). By having each person in a project place their classes into their own package the package names will qualify identical names in different packages.

  13. Packages (more) • A class can always be referred to by its fully qualified name java.util.Scanner -or- by importing the package java.util.Scanner Scanner -or-by importing java.util.* Scanner • The fully qualified package name actually implies a directory structure • To make your own package, place your code into your desired directory structure, compile it then use the jar program in your java/bin directory to make a .jar file jar cf myPackage.jar *.class (this creates a file called myPackage.jar from all of the class files in the directory structure)