1. ADF 2.0 Java School: Week 3 Day 1 Opening
Module Duration: 1 Hour
Faculty Notes:
Before the session, please ensure that team assignments and a seating plan have been posted in a highly visible place within the Plenary room, possibly on the door or on a flipchart inside the doorway. Direct participants to check which teams they are in and where they are sitting.
Participant Notes:
N/A
Application Delivery Fundamentals 2.0: Java Week 3 Open: Project Overview and Team Assignments
Copyright © Accenture 2012

2. ADF 2.0 Java School: Week 3 Day 1 Opening
Agenda
Week One and Two Recap
Welcome to the Simulation
Faculty Introductions
Objectives
What Can I Expect from the Simulation?
House Rules
Course Map
Looking Back
Q&A
Faculty Notes:
Run through the agenda with the participants.
Participant Notes:
N/A 2
Copyright © Accenture 2012

3. ADF Java 2.0: Week 1 Close
Week One Recap (1 of 26)
Module 2: Object-Oriented Concepts and Unified Modeling Language
Structural and Object-Oriented Analysis and Design is an approach that describes a system as a collection of objects and the interaction between them.
Classes and Interfaces are used to capture and leverage commonalities shared among categories of objects.
UML is a standard language for specifying, visualizing, constructing, and documenting the components of systems.
Use Case Diagrams are useful in determining initial system requirements and functionalities.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 3
Copyright © Accenture 2012

4. ADF Java 2.0: Week 1 Close
Week One Recap (2 of 26)
Module 3: Introduction to ADS/ADM and Software Analysis, Design and Build Overview
SDLC is a problem solving procedure for examining an information system and identifying processes for improving it.
ADS is Accenture’s proprietary suite for technology, solutions, and outsourcing projects.
ADM is a standard approach or framework for delivering value to clients through solutions and services.
The ADM defines Processes, Work Products and Roles which reference each other to form the foundation of the Methods.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 4
Copyright © Accenture 2012

5. ADF Java 2.0: Week 1 Close
Week One Recap (3 of 26)
Module 4: Programming Languages, Levels and Paradigms
Programming languages are collections of words, codes, and symbols, categorized into five language generations.
Virtual machines (VM) are software programs that provide code execution environments for programming languages.
Programming paradigms can be classified into four major types: Procedural, Declarative, Event Driven and Object Oriented.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 5
Copyright © Accenture 2012

6. ADF Java 2.0: Week 1 Close
Week One Recap (4 of 26)
Module 5: Software Development Environment and Tools
JDK: A set of software, tools, and libraries that need to be installed to write and compile Java applications.
JVM: A tool that executes the platform independent byte codes (.class).
Eclipse IDE: A set of Tools that assist in developing, testing, and debugging Java applications; Accenture’s IDE tool of choice.
JUnit: An open source Java testing framework shipped with Eclipse.
HttpWatch: A browser add-on that helps in monitoring HTTP requests.
Apache Tomcat: A tool used to deploy web applications.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 6
Copyright © Accenture 2012

7. Week One Recap (5 of 26) Module 6: Java Programming Language
ADF Java 2.0: Week 1 Close
Week One Recap (5 of 26)
Module 6: Java Programming Language
Java has five key characteristics, it is:
Object-oriented
Robust/Secure
Portable
High Performance
Multi-threaded
A class is like a blueprint.
Objects are like things made from the blueprint.
Objects are entities that serve as the basic building blocks of an OOP application.
An Object consists of State (form) and Behavior (function).
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 7
Copyright © Accenture 2012

8. Week One Recap (6 of 26) Module 7: Error Handling and Assertions
ADF Java 2.0: Week 1 Close
Week One Recap (6 of 26)
Module 7: Error Handling and Assertions
We perform error handling in Java using assertions. Assertions are used to:
Confirm specifications
Confirm the program
Test and debug the program
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 8
Copyright © Accenture 2012

9. ADF Java 2.0: Week 1 Close
Week One Recap (7 of 26)
Module 8: Reuse Procedural Programming Paradigm
There are many benefits to reusing code components more than once:
You only have to write the block of code once. Use the code as many times and wherever it is needed to perform the given task.
Reuse improves organization of the code. The overall program code is concise and clear. The code is more readable through the repeated use of code blocks.
Reused elements can be tested once as a separate unit then used with confidence throughout the program or system.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 9
Copyright © Accenture 2012

10. ADF Java 2.0: Week 1 Close
Week One Recap (8 of 26)
Module 9: Java Programming: Classes and Objects
Objects store their state in member variables and their behavior in methods.
Class and member access modifiers define the way classes and members can be accessed respectively.
Local variables contain the temporary state of a method.
Constructors are used to set the initial state of an object.
Garbage collection is the process of automatically clearing memory. Objects that have at least one reference variable that refers to them are not eligible for garbage collection.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 10
Copyright © Accenture 2012

11. Week One Recap (9 of 26) Module 10: Java Programming: Inheritance
ADF Java 2.0: Week 1 Close
Week One Recap (9 of 26)
Module 10: Java Programming: Inheritance
Inheritance allows the extension of an existing class to create specialized classes. By extending another class, the child class inherits all attributes and behavior of the parent class.
Creation of an object of a class calls both the object’s constructor and all the constructors in the hierarchy.
Overriding allows programmers and programs to alter a method’s behavior to fit the needs of the subclass.
Interfaces provide a template defining what a class does. “How” is left to the method implementation.
Composition relationships allow a class’ reference to be added as a member variable of another class.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 11
Copyright © Accenture 2012

12. Week One Recap (10 of 26) Module 11: Java Programming: Polymorphism
ADF Java 2.0: Week 1 Close
Week One Recap (10 of 26)
Module 11: Java Programming: Polymorphism
Polymorphism provides program flexibility supporting multiple implementations for a single method.
Dynamic binding supports the implementation of polymorphism.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 12
Copyright © Accenture 2012

13. Week One Recap (11 of 26) Module 12: Java Programming: Collections
ADF Java 2.0: Week 1 Close
Week One Recap (11 of 26)
Module 12: Java Programming: Collections
A collection is an object that groups together multiple elements into a single unit.
The Java Collections API is a set of interfaces and implementations.
The following interfaces are available in Java:
Collection interface
Set interface
List interface
Queue interface
Map interface
Comparable interface
Comparator interface
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 13
Copyright © Accenture 2012

14. ADF Java 2.0: Week 1 Close
Week One Recap (12 of 26)
Module 13: Java Programming: Exception Handling
An exception is an event that happens during program execution preventing the program from continuing normally.
An exception can be classified as:
Checked
Unchecked
An error is a critical problem caused by bad code or bad conditions design.
Exception Handling is a way we manage special events that change the normal flow of program execution.
Faculty Notes:
Recap the key modules of Week One with the participants.
Participant Notes:
N/A 14
Copyright © Accenture 2012

15. Week Two Recap (13 of 26) Module 14: Reuse OOP Well designed classes:
ADF Java 2.0: Week 1 Close
Week Two Recap (13 of 26)
Module 14: Reuse OOP
Well designed classes:
Have one (or a small number of similar) well defined functions (High Cohesion).
Share only the information they need to with other classes (Low Coupling).
Design patterns are re-usable solutions to a commonly occurring design problem.
Design patterns adhere to the principles of high cohesion and low coupling.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 15
Copyright © Accenture 2012

16. Week Two Recap (14 of 26) Module 15: Software Testing Overview
ADF Java 2.0: Week 1 Close
Week Two Recap (14 of 26)
Module 15: Software Testing Overview
Testing is everywhere and involves everyone.
Testing uses structured procedures to produce repeatable, reliable results.
Costs are reduced and quality is improved through early error detection and correction.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 16
Copyright © Accenture 2012

17. Week Two Recap (15 of 26) Module 16: Unit Testing
ADF Java 2.0: Week 1 Close
Week Two Recap (15 of 26)
Module 16: Unit Testing
Unit Testing supports early error detection and correction.
Unit test conditions focus on low level system details.
Unit tests can provide full design coverage via statement, branch, and condition test coverage.
Test design includes determining the data and conditions needed to affirm the system does what it is supposed to do and does not do anything it is not supposed to do.
The JUnit testing framework provides a harness for the development and execution of Unit Tests and test suites.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 17
Copyright © Accenture 2012

18. Week Two Recap (16 of 26) Module 17: Assembly and Product Testing
ADF Java 2.0: Week 1 Close
Week Two Recap (16 of 26)
Module 17: Assembly and Product Testing
Assembly Testing verifies component interactions / functionality as a larger system.
Assembly Readiness Testing verifies minimum functionality needed to move to the next test stage.
Product Testing focuses on Business Requirements and Processes:
End-to-End viewpoint
Client Representative data
System Investigation Requests (SIRs) document and track defect identification and resolution.
Testing and Testing Processes change focus as testing moves from low-level to high-level Test Stages.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 18
Copyright © Accenture 2012

19. Week Two Recap (17 of 26) Module 18: Java I/O (Input/Output)
ADF Java 2.0: Week 1 Close
Week Two Recap (17 of 26)
Module 18: Java I/O (Input/Output)
A stream is a sequence of data between an input source and an output destination.
There are various types of streams, for example, input, output, byte, character, filter, data and buffered.
Programs write whole objects out to streams and then read them back.
Input and output streams are primarily byte-based. Readers and Writers are based on characters.
The difference between serialization and de-serialization is that in serialization an object is marshaled or deflated. In de-serialization data is unmarshaled or inflated.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 19
Copyright © Accenture 2012

20. ADF Java 2.0: Week 1 Close
Week Two Recap (18 of 26)
Module 19: Database Overview and Connectivity
Database Management Systems (DMBs):
Avoid data redundancy
Ensure data validity and stability
Improve security by controlling access
A Data Model is a set of rules to ensure the integrity of the database.
Constraints are rules applied to column(s) that prevent data entry errors, preserving data integrity.
Joins are to retrieve data from more than one table.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 20
Copyright © Accenture 2012

21. Week Two Recap (19 of 26) Module 20: JDBC
ADF Java 2.0: Week 1 Close
Week Two Recap (19 of 26)
Module 20: JDBC
JDBC is the Java industry standard for database-independent connectivity between the Java language and other databases.
JDBC helps connect Java-based applications to the database.
How to access databases through Java.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 21
Copyright © Accenture 2012

22. ADF Java 2.0: Week 1 Close
Week Two Recap (20 of 26)
Module 21: Introduction to Elements of Enterprise Architecture
Different tiers work together within an Enterprise Architecture model.
Different configurations and interactions within one-, two-, three- and n-tier architectures.
Each of the five physical tiers have their own separate responsibilities.
Physical and Logical independence can occur between multi-tier and multi-layer applications.
Each layer and tier has a different role within the Java EE application and each has its own distinct attributes.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 22
Copyright © Accenture 2012

23. Week Two Recap (21 of 26) Module 22: Enterprise Architecture Patterns
ADF Java 2.0: Week 1 Close
Week Two Recap (21 of 26)
Module 22: Enterprise Architecture Patterns
Java EE Patterns are categorized as either high-level design patterns or low-level architectural patterns.
Different pattern classifications are available in Java EE across the Presentation, Business and Integration Tiers.
Each tier has distinct responsibilities that are defined within Java EE Patterns.
The MVC framework is a pattern composed of three related elements dealing with an application's data model, UI, and control logic.
Different technology and patterns are used within Enterprise Applications and their relationships within tiers.
Different services are offered within each tier in the Enterprise Application.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 23
Copyright © Accenture 2012

24. Week Two Recap (22 of 26) Module 23: Web-Based Programming
ADF Java 2.0: Week 1 Close
Week Two Recap (22 of 26)
Module 23: Web-Based Programming
Technologies such as HTML, CSS, and JavaScript assist in the development of the GUI.
HTTP and HTTPS provide the main internet communication protocols when requesting and receiving information from a web server.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 24
Copyright © Accenture 2012

25. ADF Java 2.0: Week 1 Close
Week Two Recap (23 of 26)
Module 24: Web-Based Programming (XML and XSLT)
XML is used for transmitting data to any device, is independent of language, is self-describing, and can be edited using a standard text editor.
Elements in a well-formed XML document must follow generic rules.
Valid XML should not contain any tags that are not permitted by the schema.
XML Transformation (XSLT) is designed to transform an input XML document into an output XML document to satisfy a specific goal.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 25
Copyright © Accenture 2012

26. ADF Java 2.0: Week 1 Close
Week Two Recap (24 of 26)
Module 25: Java EE Overview, Servlets and JSP
A Servlet enables communication between the front-end, business, and integration layers and must be deployed to a compliant Servlet container.
A Java Server Page is a combination of:
Snippets of Java code
Hyper Text MarkUp Language (HTML)
JavaScript
Cascading Style Sheets (CSS)
A Web Server transfers the client’s request to be processed by Application Server.
An Application Server processes the client’s request through the Model-View-Controller (MVC) pattern.
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 26
Copyright © Accenture 2012

27. Week Two Recap (25 of 26) Module 26: Introduction to Spring Framework
ADF Java 2.0: Week 1 Close
Week Two Recap (25 of 26)
Module 26: Introduction to Spring Framework
Spring is a lightweight container that makes Java EE and existing technologies easy to use.
The Spring Framework has seven modules. Each module has a set of functionalities and can be used independently.
Spring's Container uses IoC to manage components of the application.
Spring has two distinct containers:
BeanFactory
ApplicationContext
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 27
Copyright © Accenture 2012

28. Week Two Recap (26 of 26) Module 27: Spring MVC
ADF Java 2.0: Week 1 Close
Week Two Recap (26 of 26)
Module 27: Spring MVC
MVC is a fundamental design pattern for separating user interface logic from business logic.
The Spring Web MVC module is based on the MVC design Pattern.
Spring MVC’s key components are:
DispatcherServlet
Controller Classes
View Resolvers
Faculty Notes:
Recap the key modules of Week Two with the participants.
Participant Notes:
N/A 28
Copyright © Accenture 2012

29. ADF 2.0 Java School: Week 3 Day 1 Opening
Welcome!
Faculty Notes:
Welcome the participants to the Application Development Fundamentals 2.0: Java simulation activity.
Participant Notes:
N/A
Copyright © 2012 Accenture All Rights Reserved. 29
Copyright © Accenture 2012

30. Faculty Introductions [Optional Slide]
ADF 2.0 Java School: Week 3 Day 1 Opening
Faculty Introductions [Optional Slide]
<Faculty Member Name> <Simulation Role(s)>
<Facultyy Member Photograph>
<Facultyy Member Photograph>
Faculty Notes:
Introduce the Faculty members, ask each member to provide a brief biography/career history.
<If this slide isn’t used, introduce the Faculty on the Housekeeping slide.>
Participant Notes:
N/A
<Facultyy Member Photograph> 30
Copyright © Accenture 2012

31. ADF 2.0 Java School: Week 3 Day 1 Opening
Housekeeping
Faculty Notes:
Inform the participants of the in-house emergency procedures, fire exits, security protocols, etc.
Request that all phones and other personal electronic devices be switched off.
Provide participants with the locations of bathrooms, refreshments, and—if applicable—smoking areas.
Identify the various working locations and resources: Plenary Room (here), breakout rooms, refreshments, and printing facilities.
Explain the working hours for the simulation—start, finish, lunch and break times. These may vary from location to location and so are not described here.
Participant Notes:
N/A
Copyright © 2012 Accenture All Rights Reserved. 31
Copyright © Accenture 2012

32. Course Objectives (1 of 2)
ADF 2.0 Java School: Week 3 Day 1 Opening
Course Objectives (1 of 2)
At the end of this course, you will be able to:
Describe the key roles and phases in the Software Development Lifecycle and the dependencies and touch points relative to your own work.
Write, compile, execute and test Java applications that satisfy an application design and requirements using ADM.
Execute and manage assignments from a work plan to meet all project requirements.
Faculty Notes:
Briefly review the course objectives with the participants.
Participant Notes:
N/A 32
Copyright © Accenture 2012

33. Course Objectives (2 of 2)
ADF 2.0 Java School: Week 3 Day 1 Opening
Course Objectives (2 of 2)
Communicate effectively when interacting with clients and colleagues to project credibility, demonstrate our core values and culture, and reinforce the positive perception of Accenture.
Faculty Notes:
Briefly review the course objectives with the participants.
Participant Notes:
N/A 33
Copyright © Accenture 2012

34. What can I expect from the simulation?
ADF 2.0 Java School: Week 3 Day 1 Opening
What can I expect from the simulation?
Faculty Notes:
Explain to the participants that this is a hands-on, immersive client simulation:
The Faculty will be facilitating and playing the parts of Project Management and Test Team.
The participants work in teams playing the Team Lead and Application Developer roles.
Emphasize that this is a risk-free environment, and that it is not a competition.
Desire2Learn (D2L), our course web site, will be used to facilitate the learning, controlling the flow of the course and acting as a resource library.
During the session, they will be expected to learn and demonstrate:
Application development and change control:
Application analysis and design deliverables review
Web-based application implementation and testing
Automated test script creation and execution
Change control and defect management
Project Management-related activities:
Status and issue reporting
Project on-boarding
Time reporting
Peer review
Executive meetings
Professional skills
Participant Notes:
N/A
Copyright © 2012 Accenture All Rights Reserved. 34
Copyright © Accenture 2012

35. ADF 2.0 Java School: Week 3 Day 1 Opening
House Rules DO
DON’T
Dress and behave professionally, you are on a client site
Leave the class without first notifying a Faculty member
Treat Faculty and your peers with respect
Interfere with other teams’ work
Value diversity in your teams
Be afraid of making mistakes
Ask questions
Cheat!
Faculty Notes:
Explain the ‘House Rules’ or code of conduct expected of participants.
Do:
Dress and behave professionally, as though you are on a client site.
Treat Faculty and your peers with respect.
Value diversity in your teams, everyone has something of value to offer. Listen to them.
Ask questions. The only stupid question is the one you didn’t ask.
Don’t:
Leave the class without first notifying a Faculty member. We need to know where you are in case of emergency.
Interfere with other teams’ work. This is disrespectful and unprofessional.
Be afraid of making mistakes. This is a safe learning environment—a degree of risk-taking is desirable. Mistakes are great—they provide us with feedback and give us direction and momentum.
Cheat! This includes copying solutions from other teams. By cheating, you are cheating yourself.
Note that breaching some of these rules could lead to disciplinary action and expulsion from the course.
Participant Notes:
N/A 35
Copyright © Accenture 2012

36. ADF 2.0:Java - Week 3 Course Map
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6 (Saturday)
Week 3 Day 1 Opening
Weeks 1&2 Recap
(1:00)
Day 2 Opening (0:15)
Day 3 Opening (0:15)
Day 4 Opening (0:15)
Day 5 Opening (0:15)
Day 6 Opening (0:15)
Peer Review
(1:00)
Module 33 Revise Unit Test Cases
(1:45)
Accenture’s One Global Network
(1:00)
Working Cross-Culturally
(1:00)
Emergency Support Request
(3:45)
Build Phase Initiation
Requirement Review &
Test Case Creation
Module 28 Project Orientation
(1:00)
Module 35 Build Application Components, Execute Unit Test and Update Source Code
(2:45)
Module 35 Build Application Components, Execute Unit Test and Update Source Code, cont.
(2:45)
Team Status Meeting
Build and Test
Application Components
Module 32 Define
Unit Test Cases
(2:45)
Module 29 Review Application Design Deliverables
(2:00)
Module 34 Prepare for Unit Test
(2:00)
Team Status Meeting
Peer Review
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Setting Work Priorities
(1:00)
Productive Meetings
(1:00)
Emergency Support Request
(4:00)
Module 34 Prepare for Unit Test, cont.
(4:00)
Module 35 Build Application Components, Execute Unit Test and Update Source Code, cont.
(4:00)
Module 35 Build Application Components, Execute Unit Test and Update Source Code, cont.
(4:00)
Module 30 Perform Detailed Design Hand-off
(1:00)
Module 32 Define Unit Test Cases, cont.
(3:00)
Peer Review
Set up Environment
Module 31 Set Up Development Environment
(2:00)
Week 3 Close (0:20)
Peer Review
Peer Review
LEGEND:
Activity - Group
Simulation
Presentation / Demo / Activity
Presentation 36

37. ADF 2.0:Java - Week 4 Course Map
Day 1
Day 2
Day 3
Day 4
Day 5
Week 4 Day 1 Opening (0:15)
Day 2 Opening (0:15)
Day 3 Opening (0:15)
Day 4 Opening (0:15)
Day 5 Opening (0:15)
Problems Happen,
Solve Them
(1:00)
Prepare and Execute Product Test
Taking Steps to Establish Trust
(1:00)
Client Culture
(1:00)
Performance Feedback
(1:00)
Module 38 Prepare/ Support Product Test
(3:45)
Preparation for
Assembly Test and Finalize Build Deliverables
Change Control Management
Module 44 Finalize Change Request Approach with Project Manager
(2:45)
Module 46 Prepare for Assembly Test
(1:45)
Module 41 Receive
Change Request
(1:30)
Module 36 Prepare for Assembly Test
(2:45)
Peer Review
Team Status Meeting
Module 42 Analyze Change Request
(1:15)
Team Status Meeting
Module 47 Prepare/Support
Product Test
(1:00)
Team Status Meeting
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Lunch (1:00)
Module 36 Prepare for Assembly Test, cont.
(2:00)
Communication Basics
(1:30)
Module 42 Analyze Change Request, cont.
(2:00)
Module 45 Update Source Code/ Execute Unit Test
(4:00)
Module 47 Prepare/Support
Product Test, cont.
(1:00)
Transition Application Build
Week 4 Close (1:30)
Team Status Meeting
Module 39 Baseline Deliverables in Document Control
(1:00)
Module 37 Review Application Build Deliverables
(2:00)
Module 43 Document Change Request Approach
(2:00)
Performance Reviews and Final Assessment
(3:00)
Module 40 Conduct Post Transition Review
(1:30)
Team Lead Review
LEGEND:
Activity - Group
Simulation
Presentation / Demo / Activity
Presentation 37

38. ADF 2.0 Java School: Week 3 Day 1 Opening
Looking Back…
In today’s session, you may find it useful to review the following from Week One and Week Two:
M3: Introduction to ADS/ADM & Software Analysis, Design & Build Overview
M5: Software Development Environment and Tools
Faculty Notes:
Explain that the participants may benefit from a quick refresh of their notes from the first two weeks.
Participant Notes:
N/A 38
Copyright © Accenture 2012

39. Questions and Comments
ADF 2.0 Java School: Week 3 Day 1 Opening
Questions and Comments
Faculty Notes:
Ask the participants if they have any questions.
Participant Notes:
N/A
Copyright © 2012 Accenture All Rights Reserved. 39
Copyright © Accenture 2012