Common Dev

Java Week 1

Java Week 2

Java Week 3

Java Week 4

Java Week 5

The following are the notes for Common Development of the Java Course

• Different components of the diagrams
• Understanding the theory
• Class Diagram - Dependency Connectors [slide]
• 30 qs common dev good practices (100%) MCQ
• All design patterns
• Five steps to follow test driven development
• Will have a (mean) Liskov Substitution
• 2x N Tier questions
• Source Control will come up in the exam
  • what happens when you commit (creates a new copy)

• Sign off interview will require n-tier
• Sign off interview will include server affinity and database clustering

• Use Case Diagrams
• Entity Relationship Diagrams
• Activity Diagrams

• Everything is dealt as an object
• Class like a blueprint of how something could be, object is the realisation of the class
• Classes have behaviour and attributes

• Class Name, Attributes, Methods
• '-' is private, + is public (everything can see it), # is...
• passing argument is the ...(...)

• interfaces only have static and final attributes (examples of constant variables)

• Public abstract class User
• Public class Broker extends User (solid arrow)

• public interface Automated
• public class Broker implements Automated (dotted arrow)

• Dependency
• Association
• Aggregation
• Composition

• Attributes
• Methods

• Alway starts on the left
• Initial bar is longer than the others
• Actor / Class at the top
• Method is the arrow right
• Return value is the arrow left

Pillar	Description
Abstraction	Abstracting only the required information
Polymorphism	Relates to there being multiple forms or versions of the same type of thing and the same types of behaviour. Early Binding: Method Overloading Compile Time Late Binding: Method Overriding (where a parent i.e. interface defines method and child class defines solution) Runtime
Inheritance	Getting all the attributes from the parent class
Encapsulation	Grouping data, behaviours, classes together into logical groups

Commit with SVN you create a new version (you cannot rollback)

Made up of objects: Attributes & Behaviour

The act of grouping together data and

private - only visible to same class protected - public - visible to everything default

static means it belongs to the class itself

• Has get instance (generally speaking) (it is static)
• Needs a private constructor so it can only be created within itself
• Not suitable for users

• Public static
• To create a lot of objects of the same type
• Make the code less coupled and remove the 'new' keyword

• Has a max & min connection
• They are singletons (only one pool exists)
• Improves system performance (don't need to create connections every time)
• Limits the number of objects created (amount of memory used at a time)
• Always has 2 Lists (of available connections and of currently used connections)

• An object that observes the state of another object
• When you want one thing to happen when a state changes somewhere else
• notify() method

• e.g. undo button
• store information so that it can be executed at a later time
• <<Lightbulb switch example>>
• Invoker, Receiver, Client, Command
  • Invoker and Receiver 'don't know' about one another
• Doesn't have to be called Command and execute
• You can pass in values

• Used for converting one thing into another
• Will usually say adapter / converter

• A class should only have methods related to a certain task
• Can have more than one method ( Trade could have getInfo(), Update(), Add(), Delete() )

• A class should be open to extensions and close for modifications

• Classes should depend on abstract concepts rather than concrete implementations
• Have a general format and then pass any type of 'thing' in it.
• Extensions from a parent class should always reference the parent class and not the child class

75% of the code we write has to have tests written to it

Five steps to follow 1. Write the test 2. Make the test compile 3. Watch the test fail (most important) 4. Do just enough to make all tests pass 5. Refactor and generalise

• View - display info
• Model - business logic, data, real things
• Controller - delegating tasks between view and model
• Example of encapsulation

View - Presenter - Model - Used for automated testing P and M are for backline developers No relationship between view and Model

Client (Business Logic) __> Server (Database) A slow network

Central Repository holds the system Allows us to share projects in multiple groups

Stores client IP and what IP request their request was sent to (Server Affinity)

SVN://192.168.0.2:5500/kamran.adnan From Home: SVN://unix.fdmgroup.com:5500/kamran.adnan

Install JDK 8 followed by JRE (http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)

Maven: http://download.eclipse.org/technology/m2e/releases/1.6/1.6.2.20150902-0002

SVN: Install Software > Mars > Collaboration > Subversive SVN Team Provider

SVN Repository: svn://unix.fdmgroup.com:5500/kamran.adnan (No User / Password)

Show View > Package Explorer

Add the following to the Dependencies:

 <dependencies>
   <dependency>
     <groupId>junit</groupId>
     <artifactId>junit</artifactId>
     <version>4.11</version>
     <scope>test</scope>
   </dependency>
   <dependency>
     <groupId>org.mockito</groupId>
     <artifactId>mockito-all</artifactId>
     <version>1.9.5</version>
   </dependency>
   <dependency>
     <groupId>log4j</groupId>
     <artifactId>log4j</artifactId>
     <version>1.2.17</version>
   </dependency>
 </dependencies>

Install EclEmma (http://www.eclemma.org/installation.html)