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

Gathering requirements

The first step is to gather the requirements to build the software. This can be done in many different ways depending on your organizational culture and environment, detailed as follows:

  • If you are subject to regulatory requirements (for example, in the aerospace or pharmaceutical business), you need a very formal method

  • If you are outsourcing development to an external supplier, you need the exact requirements

  • If development will be handled by an in-house IT department, you might get by with less formal requirements

At the formal end of the spectrum, you need a complete list of all of the requirements that you can test against. If your organization is used to a more informal approach, you might only produce a fairly complete list of use cases or user stories. For a technology replacement project, where you replace a legacy application developed in, for example, Oracle Forms, the requirements might be simply, "it should work like the old system."

Tip

Know the requirements...

End of Section 2
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