• Like
Scmad Chapter 01
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Scmad Chapter 01

  • 1,617 views
Published

Introduction for the Sun Certified Mobile Application Developer Exam …

Introduction for the Sun Certified Mobile Application Developer Exam
Simple Study guide not for commercial reasons

Published in Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Amigo, o ppt está errado, era pra ser o capítulo 01, e este é o 05. Fora isso, o material está excelente.
    []s Tom Hayden.
    Are you sure you want to
    Your message goes here
    Be the first to like this
No Downloads

Views

Total Views
1,617
On SlideShare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
87
Comments
1
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. By Marcel Caraciolo http://mobideia.blogspot.com Chapter 01 – Introduction to the Exam SCMAD Certification 45mm 61mm
  • 2. Agenda
    • Introduction
    • Java ME Platform
    • SCMAD Certification
  • 3. Introduction
    • Introduce the Java ME Platform
    • Introduce the SCMAD Exam
  • 4. What is Java ME Platform?
    • Subset of Java Platform
    • Execution environment
      • Resource – constrained devices
        • Mobile Phones
        • PDA’s
        • Set-top boxes
  • 5. Implementations
    • Specifications are defined by JSR’s
      • Java Specification Requests
    • Sun has a Windows/Unix development kit
    • Device vendors pack VM’s implementation on
    • devices
  • 6. Main parties involved
    • Companies involved
      • ARM
      • IBM
      • LG
      • Motorola
      • Nokia
      • RIM
      • Samsung
      • Sony Ericsson
  • 7. Java Editions
  • 8. Java ME Platform
    • Java SE defines a single VM and a single API
    • At Java ME VM’s are based on “Configurations
    • and “Profiles”. There are several VM types, to
    • support devices with different capabilities,
    • from cheap cellphones to TV setup-boxes with
    • high-speed network and wired power supply.
  • 9. Java ME Platform
    • Configurations define VM’s features (e.g.
    • floating point support, security model) and
    • basic API’s (e.g. classes at java.lang, java.util
    • packages). They are composed by a subset of
    • features from a regular VM and by some new
    • API’s.
    • Profiles address “Horizontal” market segments.
    • They define specific API’s for device set (e.g.
    • user interface, application life cycle,
    • persistence, events, etc.)
  • 10. CLDC: Connected Limited Configuration
    • Most limited configuration
    • Devices: Mobile phones and PDA’s with limited
    • power and connectivity
    • Based on a subset of Java SE 1.3 API’s
    • All other configurations are based on CLDC ( to
    • avoid market fragmentation)
  • 11.
    • Simplified security model
    • JNI is not allowed
    • No finalization ( Object.finalize())
    • No file system
    • No Reflection or Serialization
    • No Collections Framework
    • According to the version, floating support may
    • not be supported
    CLDC Restrictions
  • 12.
    • Closer to the Java SE than CLDC
    • Devices: Set-top boxes and PDA’s
    • No need for preverification
    • Inherit additional API’s from Java SE
    CDC: Connected Device Configuration
  • 13.
    • MIDP (Mobile Information Device Profile)
      • Designed for mobile phones
      • Provides GUI, persistence, networking, multimedia
      • Depends on CLDC
    • Personal Profile
      • Designed for PDA’s and Set-top boxes
      • Provides AWT for other Java SE API’s
      • Runs on CDC
    Available Profiles
  • 14.
    • Provides:
      • Application Life-Cycle
      • User interface
      • 2D games
      • Multimedia
      • Persistence
      • Networking
      • Notifications
      • Security
      • Internet Application distribution with digital signature
    MIDP: Mobile Information Device Profile
  • 15.
    • Defines supplementary API:
      • WMA (JSR – 120) – Wireless messaging API (SMS messages)
      • MMAPI (JSR-135) – Mobile Media API (support for audio,
      • video and media capture)
      • PIM and File API (JSR-75) – Access to device’s file system
      • and contact list.
      • Web Services (JSR-172) - SOAP calls and XML parsing
      • Java API’s for Bluetooth (JSR-82)
      • Scalable 2D Vector Graphics for Java ME (SVG Support)
      • Mobile 3D Graphics API for Java ME (JSR-184)
      • Mobile Internationalization API (JSR-238)
    Optional Packages
  • 16.
    • Define no new API’s
    • What it defines?
      • Requirements over other API’s aiming to reduce platform
      • fragmentation
      • Minimum hardware and performance requirements
    • Examples:
      • JTWI – Java Technology for the Wireless Industry
      • MSA - Mobile Service Architecture
    “ Umbrella” specifications
  • 17.
    • Specified API’s:
      • CLDC 1.0 (1.1 may be used)
      • MIDP 2.0
      • WMA 1.1
      • MMAPI 1.1 (conditional)
    • Some aspects left as optional by the API’s are
    • required by JTWI
    • Define device features requirements (e.g. screen
    • size, available memory).
    JTWI: Java Technology for Wireless Industry
  • 18.
    • Splits in “MSA Subset” and “MSA”
      • MSA Subset requires:
        • CLDC 1.1
        • MIDP 2.1
        • MMAPI 1.1
        • WMA 2.0
        • PDA API (File and PIM)
        • Java API’s for Bluetooth (Bluetooth and Obex) (conditional)
        • Mobile 3D Graphics API
        • Scalable 2D Vector Graphics API (SVG)
    MSA: Mobile Service Architecture
  • 19.
    • Besides Subset’s API’s, full MSA requires:
      • J2ME Web Services (Web Services and XML parsing)
      • Security and Trust Services API (Encryption, smart card access
      • (conditional), PKI access (conditional))
      • Location API (conditional)
      • SIP API (SIP protocol)
      • Content Handler API
      • Payment API
      • Advanced Multimedia Supplements (MMAPI extensions)
      • Mobile Internationalization (i18n)
    MSA: Mobile Service Architecture
  • 20.
    • SCMAD Certification
      • CX 310-110 Exam
    Sun Certified Mobile Application Developer Exam
  • 21.
    • Like other Sun certifications, this is a multiple
    • choice exam taken at Authorized Prometric
    • Testing Centers
    • Requirements: SCJP (Any version)
    • 150 minutes, 68 questions, Passing score 55%
    • Website:
    • http://www.sun.com/training/certification/java/scmad.xml
    SCMAD Certification
  • 22. SCMAD Certification Objectives
    • Main Objective: JTWI
      • ME Platform
      • JTWI requirements and features
      • CLDC features and differences (1.0 and 1.1)
      • MIDP security model
      • Networking at CLDC and MIDP
      • Application delivery model
      • MIDP’s persistence, notification, GUI, game
      • and sound API’s.
      • MMAPI 1.1
      • WMA 1.1
  • 23. Future Work
    • Next Chapter:
      • Tools and requirements for Java ME development
      • First Java ME mobile Application: Hello World MIDlet
      • Configurations and Profiles – Differences
  • 24. References
    • ALVES F. Eduardo. SCMAD Study Guide,
    • 27/04/2008.
    • JAKL Andreas, Java Platform, Micro Edition Part
    • 01 slides, 12/2007.
    • Sun Certification Mobile Application Developer
    • Website: [http://www.sun.com/training/certification/java/scmad.xml].