Muutke küpsiste eelistusi

E-raamat: Oracle Application Express by Design: Managing Cost, Schedule, and Quality

Teised raamatud teemal:
  • Formaat - EPUB+DRM
  • Hind: 40,74 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Tagline: Balancing interrelated and complex design decisions in large APEX applications

Learn the many design decisions that must be made before starting to build a large Oracle Application Express (APEX) application for the cloud or enterprise.

One of APEX's key strengths is the fact that it is a Rapid Application Development (RAD) tool. This is also a major weakness when it tempts developers to start coding too soon. Small applications that consist of tens of pages can be coded without a lot of design work because they can be re-factored quickly when design flaws are discovered. Design flaws in large cloud and enterprise applications that consist of hundreds or thousands of pages are not so easy to re-factor due to the time needed to redevelop and retest the application, not to mention the risk of breaking functionality in subtle ways.

Designing a large application before coding starts is a profitable exercise because a thoughtful design goes a long way in mitigating cost overruns and schedule slippage while simultaneously enhancing quality. This book takes into account perspectives from other non-developer stakeholders such as maintenance developers, business analysts, testers, technical writers, end users, and business owners. Overlooking these perspectives is one of the chief causes of expensive rework late in the development cycle.

Oracle Application Express by Design illustrates APEX design principles by using architecture diagrams, screen shots, and explicit code snippets to guide developers through the many design choices and complex interrelationship issues that must be evaluated before embarking on large APEX projects. This book:
  • Guides you through important, up-front APEX design decisions
  • Helps you to optimize your design by keeping all stakeholders in mind
  • Explicit code examples show how design impacts cost, schedule, and quality
What You Will Learn
  • Pick and choose from the list of designs before coding begins
  • Bake optimal quality into the underlying fabric of an APEX application
  • Think and design from outside the developer’s narrow perspective
  • Optimize APEX application designs to satisfy multiple stakeholder groups
  • Evaluate design options through hands-on, explicit code examples
  • Define and measure success for large cloud and enterprise APEX applications
Who This Book Is For

APEX developers and development teams

About the Author xi
About the Technical Reviewer xiii
Acknowledgments xv
Introduction xvii
Chapter 1 Design Trade-Offs
1(6)
Stakeholders
2(2)
Trade-Offs and Quality
4(1)
The Human Side of Trade-Offs
5(1)
Summary
5(2)
Chapter 2 Inside vs. Outside of the Box
7(8)
Working Inside the Box
7(3)
Historical Perspective
7(2)
The Box: Pros and Cons
9(1)
Designing Inside and Outside of the Box
10(3)
Branding
10(1)
User Experience (UX)
11(1)
Updating the Database
11(1)
Road Map for Stepping Outside the Box
12(1)
Summary
13(2)
Chapter 3 Database Design for APEX
15(4)
Primary Keys
15(1)
Column Name Lengths
16(1)
Thick Database
17(1)
Summary
18(1)
Chapter 4 Many Light Pages vs. One Heavy Page
19(18)
APEX Wizards Build Many Light Pages
19(3)
Merging Many Light Pages into a Few Heavy Pages
22(3)
Light Pages vs. Heavy Pages: Picking the Correct Strategy
25(11)
Designing for End Users
25(1)
Designing for Roles
26(1)
Performance Issues
27(9)
Summary
36(1)
Chapter 5 Database Updates
37(14)
Architecture
37(3)
APEX in a Thick Database
40(4)
DEV vs. TEST and PROD Environments
44(1)
TAPI Helper Tools
44(3)
Optimistic Locking
47(3)
Summary
50(1)
Chapter 6 Cookie Applications
51(16)
APEX Cookie Application Architecture
51(9)
Cookie Name Attribute
54(1)
Global Application Items
55(3)
Login Application
58(1)
Sharing Regions and Pages Among Cookie Apps
59(1)
Parameters That Will Never Change
60(6)
Substitution Strings
61(3)
Application Items
64(1)
Parameter Table
64(1)
PL/SQL Constant Package
65(1)
Designing Cookie Application Environments
66(1)
Summary
66(1)
Chapter 7 Authorization
67(18)
The Need for Configuration
67(1)
Built-in Access Control Page
67(4)
Authorization Architecture
71(3)
Binding APEX Users to Components
74(5)
Finding the Value of APP_COMPONENT_NAME
74(3)
Coding the Authorization Scheme
77(2)
Authorization Granularity
79(1)
Coarse Grained
79(1)
Fine Grained
79(1)
A Mixture of Coarse and Fine Grained Authorization
79(1)
Authorization Configuration Pages
80(2)
Component Names
81(1)
Security
82(1)
Training the Configuration Team
82(1)
Authorization vs. Conditions
83(1)
Summary
83(2)
Chapter 8 GUI Design
85(18)
GUI Goals
86(4)
The Invisible GUI
86(1)
User Experience
87(3)
Your GUI Budget
90(3)
The Cost of a Click
90(1)
The Sloppy GUI
91(2)
Know Your User Community
93(9)
GUI Design for Multiple User Groups
94(4)
GUI Style: Conservative vs. Trendy
98(2)
GUI Layout and Terminology
100(2)
Summary
102(1)
Chapter 9 Error Handling
103(16)
APEX Error Environment
103(1)
System Errors
104(1)
User Errors
104(11)
JavaScript Validations
105(1)
JavaScript Validations with AJAX Calls
106(2)
APEX Computations and Validations
108(2)
Transaction API and Constraints
110(2)
APEX Error-Handling Function Mechanism
112(2)
The Prime Directives of Validation Logic
114(1)
Coding Errors
115(2)
Syntax Errors
115(1)
Logic Errors
116(1)
Risk Management
117(1)
Summary
118(1)
Chapter 10 Mobile
119(16)
Users First
119(10)
Internal Company Employees
120(5)
Retail Customers
125(4)
Device Choices
129(1)
Native vs. Browser/Server
129(2)
Native Applications
130(1)
Browser/Server Applications
130(1)
Hybrid Mobile Applications
131(1)
APEX in a Mobile World
131(3)
Responsive vs. jQuery Mobile
132(1)
One vs. Two APEX Apps
132(2)
Summary
134(1)
Chapter 11 Rules and Guidelines
135(10)
Why Standards?
135(3)
Consistency
135(1)
Standardize Low Value Decisions
136(1)
Repository for New Ideas
137(1)
Manage Stakeholder Expectations
137(1)
On-Boarding New Personnel
138(1)
Writing a Standards Document
138(6)
Terse and Concise
138(1)
Accessible with One or Two Clicks
139(1)
Template Driven
139(3)
Easily Updated and Extended
142(1)
Google Docs
143(1)
Summary
144(1)
Appendix A A Cloudy Crystal Ball 145(2)
Appendix B Things Not Covered 147(2)
Index 149
Patrick Cimolini is a senior APEX consultant with Insum Solutions Inc. of Montreal, Quebec, the largest North American consultancy that specializes in software development, project management, and training services for Oracle Application Express (APEX) projects. Patrick's formal training in engineering, project management, and business administration is complemented by more than 30 years of software development experience that has evolved through mainframe, client/server, and web platforms. His Oracle experience dates back to the early 1990s, and his APEX experience dates back to 2005. He is an Oracle Ace Associate.