Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Oracle ADF Enterprise Application Development Made Simple: Second Edition
  • Toc
  • feedback
Oracle ADF Enterprise Application Development Made Simple: Second Edition

Oracle ADF Enterprise Application Development Made Simple: Second Edition

By : Sten E Vesterli
4.5 (10)
close
Oracle ADF Enterprise Application Development Made Simple: Second Edition

Oracle ADF Enterprise Application Development Made Simple: Second Edition

4.5 (10)
By: Sten E Vesterli

Overview of this book

Table of Contents (20 chapters)
close
close
Oracle ADF Enterprise Application Development – Made Simple Second Edition
Oracle ADF Enterprise Application Development – Made Simple Second Edition
Credits
Credits
About the Author
About the Author
Acknowledgment
Acknowledgment
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
The ADF Proof of Concept
The ADF Proof of Concept
Understanding the architecture of ADF
The Proof of Concept
The Proof of Concept case study
Getting started with JDeveloper
The Proof of Concept ADF Business Components
The Proof of Concept ADF user interface
The scheduled tasks page
Summary
2
Estimating the Effort
chevron up
Estimating the Effort
Gathering requirements
Deciding how to build it
Application architecture
Example Work Breakdown Structure
Estimating the solution
Adding it all up – the final estimate
Sanity check
From effort to calendar time
Summary
3
Getting Organized
Getting Organized
Skills required for an ADF project
Organizing the team
Gathering the tools
Structuring workspaces, projects, and code
Naming conventions
Summary
4
Productive Teamwork
Productive Teamwork
The secret of productivity
Version control with Subversion
Version control with Git
Avoiding conflicts
Focusing for maximum productivity
The Integrated Solution – Oracle Team Productivity Center
Working with Oracle Team Productivity Center
Summary
5
Preparing to Build
Preparing to Build
Creating common workspaces
Working with task flow templates
Working with page templates
Framework extension classes
Packaging your common code
Summary
6
Building the Enterprise Application
Building the Enterprise Application
Structuring your code
Building the Common Model
Organizing the work
Implementing the task management subsystem
Implementing the scheduling subsystem
Building the master application
Summary
7
Testing Your Application
Testing Your Application
Initial tests
User interface tests
Stress and performance tests
The Oracle alternative
Summary
8
Changing the Appearance
Changing the Appearance
Controlling appearance
Skinning overview
Skinning in practice
Summary
9
Customizing Functionality
Customizing Functionality
The reason for customization
The technology behind ADF customization
Applying customization layers
Making an application customizable
Performing customization
Summary
10
Securing Your ADF Application
Securing Your ADF Application
The security basics
Security decisions
Implementing ADF Security
Application roles
Implementing the user interface security
Implementing data security
Users and groups
Summary
11
Packaging and Delivery
Packaging and Delivery
The contents of a good deployment package
Preparing for deployment
Setting up the application server
Deploying the application
Scripting the build process
Summary
Internationalization
Internationalization
Automatic internationalization
Running your localized application
Localizing formats
More internationalization
Summary
Index
Index

Estimating the solution

With your Work Breakdown Structure in hand, you can start estimating the real work involved in each group of tasks. Estimate the effort needed to perform the task in hours or days (measured in ideal engineering hours, assuming concentrated, uninterrupted work on the task). Don't fall into the trap of estimating in duration—duration estimates will vary wildly depending on how much non-project work the person doing the estimate expects to be doing at the same time.

Tip

Use small tasks

If you find that a work package has an estimate of more than 80 hours, revisit the Work Breakdown Structure and split the task into smaller subtasks. An estimate of 80+ hours very often indicates an incomplete understanding of the task and carries a large risk of overrunning the estimate.

The individual subsystem work packages might break the 80-hour limit and are, therefore, divided into subpackages.

Top-down estimate

If you are an experienced project manager, you can probably produce a rough...

End of Section 6
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete