1. Data Design and Implementation

2. Definitions of Java TYPES Atomic or primitive type A data type whose elements are single, non-decomposable data items - e.g, an int or a float variable Composite type : A data type whose elements are composed of multiple data items e.g. A CLASS 2

3. Structured composite type  Structured composite type:  An organized collection of components. The organization determines how to access the components of the collection  E.g. An Array or A Tree 3

4. Atomic (Simple) and Composite Data Types 4

5. Java’s Built-In Types 5

6. The Java Class Construct composite, unstructured data types.  is used to create composite, unstructured data types.  It is composed of :  1. named data fields ( instance variables) 2. methods. 2. methods. 6

7. An array differs from a class :  An array is a homogenous structure, whereas classes are heterogeneous structures. E.g. an array of integers has only integers in it. A class has variables of different types and methods  7

8. Accessing components  A component of an array is accessed by its position in the array e.g. board[2] [3] 8

9. Arrays  Because array components are accessed by position,  an array is a structured composite type. 9

10. Component of square:  A component of a class is accessed by an identifier (the object created of it).  Square sq = new Square(10,20, 40, Color.Red);  int x = sq.getX();  We access the parts of the class with an object 10

11. 11  Because class components are accessed by creating an object,  an class is a unstructured composite type.

12. Definitions Data abstraction: The separation of a data type’s logical properties from its implementation  A doctor sees (abstracts) the person as patient. E.g. name, height, weight of a person  An employer sees (abstracts) a person as Employee. E.g.name, age, health, degree of study, of a person. 12

13. Data encapsulation  We can abstract the important characteristics of Person  and store all the characteristics of a person in Person class  The Person class can be used by both the Doctor or Employer classes or ……..others 13

14. Abstract Data Type  An abstract data type is an interface  a) it defines a collection of data e.g. an array of clients  b)and the particular operations that are allowed on that array  ( through methods ) 14

15. 15 An ADT :  therefore has a name E.G. A STACK, A QUEUE, An ARRAYLIST  A domain of values(data) - the elements in the stack, items stored in the array in the ArrayList  a set of operations that can be performed (methods) on the data ABSTRACT DATA TYPES – ADT’ s

16. Collections- Details  A collection is an object that serves as a repository for other objects.  MOST ADT are Collections - since they store the data they are operating on  The Java Collections Framework contains classes that represent collections of objects. 16

17. Collections & ADT’s  In general, a collection refers to a class whose role is to: provide methods to add, remove and  provide methods to add, remove and  manage the elements that are in the collection. 17

18. Collections - ArrayList  The ArrayList class in the Collections Framework is implemented with an array.  There is also a SortedArrayList, which maintains the array in sorted order 18

19. Collections & ADT’s  Collections can be implemented in a variety of ways. Array  The ArrayList uses an Array methods and contains methods that perform operations on array. e.g. Adding or deleting items etc. 19

20. ADT’s  ADT’s can be implemented with both e.g. arrays or linked lists.  The choice of an array or a linked list depends upon the implementation 20

21. The ArrayList Class  IS Part of the java.util package.  An ArrayList list can grow and shrink depending on need.  When the array is full, its size is doubled 21

22. ARRAYLIST  ArrayList class: you store variables of type Object.  Or now type T - a generic type built on class Object  22

23. ArrayList  An ArrayList has a size() method - how many objects it is currently holding  It has other methods :  add, remove, find, isEmpty etc. See:  http://docs.oracle.com/javase/6/docs/api/java /util/ArrayList.html http://docs.oracle.com/javase/6/docs/api/java /util/ArrayList.html 23

24. ArrayList Operations 24

25. Use Arraylist – unsorted - when:  The amount of space required may change from one execution of the program to the next.  The position of an element in the array list has no relevance to the application.  There is no order to the items stored 25

26. 26 Collection Interface & Map Interface

27. 27 LIST & SET INTERFACEs

28. 28

29.  public interface List extends Collection  {  E get(int index);  E set(int index, E element);  boolean add(E element);  void add(int index, E element);  E remove(int index);  boolean addAll(int index, Collection c);  int indexOf(Object o);  int lastIndexOf(Object o);  ListIterator listIterator(); ListIterator listIterator(int index); } 29

30. Collection Interface-List inherits these methods  public interface Collection extends Iterable {  int size();  boolean isEmpty();  boolean contains(Object element);  boolean add(E element);  boolean remove(Object element);  Iterator iterator();  boolean containsAll(Collection c);  boolean addAll(Collection c);  boolean removeAll(Collection c);  boolean retainAll(Collection c);  void clear();  public T[] toArray(T[] a); 30

31. Designing ADTs this term  Determine the general purpose of your program. application program performs.  List the specific types of operations the application program performs. 31

32. DESIGNING AN ADT  Decide first which ADT to use:  an ArrayList, A Stack? Depends on the problem  Identify a set of public methods to be provided by the ADT class to perform the desired operations 32

33. Designing ADTs  Identify potential error situations and classify into 1. Those that are handled by throwing an exception 2. Those that are ignored. 33

34. Designing ADTs 6. Define the needed exception classes. 7. Decide on a protection level for the identified data. 8. Implement the ADT. ( Using the ARRAYLIST OR STACK 9. Create a test driver and test your ADT. 34

35. 35 Analysis of List Implementations In both array and linked implementations, many operations are similar in efficiency Most are O(1), except when shifting or searching occurs, in which case they are order O(n) except when shifting or searching occurs, in which case they are order O(n)