J2ME: Programaci�n para m�viles by ReF5Xi

VIEWS: 5 PAGES: 21

									   Quality Assurance and
Testing of J2ME Programs for
       Mobiles Phones
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
                  Introduction
J2ME was born in 1999.
This programming language is destined to limited
device following the Java philosophy: “write one,
run anywhere”.
Every device needs to implement a Java Virtual
Machine (JVM) that runs the byte-code.
                  Introduction
J2ME can be divided in:
• CDC (Connected Device Configuration): Systems
that are always connected: GPS, TV Decoder.
•CLDC (Connected Limited Device Configuration):
Systems with memory and processing restrictions.
CLDC integrates some libraries called MIDP
(Mobile Information Device Profile). The mobiles'
application based in MIDP are called MIDlets
Introduction
                  Introduction
A MIDlet can be interpreted as a process with three
states:
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
                   Life Cycle
One of the best development models for J2ME
applications is based in Object Oriented Model and
Prototype Model.
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
                     Planning
•Limits of CLCD 1.0 and 1.1 and limits of the
devices.
•Customer requirements.
•Development risk.
•Timetable.
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
   Design and Prototype implementation
• UML Design
• IDE
• Program size
• Prototype:
   • Correctness
   • Reliability
   • Efficiency
   • Integrity
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
                    1st Testing Phase
• Typical errors.
• Emulator's test
• Mobile's test
• 1st Review
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
2nd Design and application implementation
• Versions based in the interface.
• Versions based in Special devices.
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
                2nd Testing Phase
• List of mobiles phones and its characteristics.
• 2nd Review
   Quality Assurance and Testing of J2ME
       Programs for Mobiles Phones

1. Introduction
2. Life Cycle
2.1 Planning
2.2 1st Design and Prototype implementation
2.3 1st Testing Phase
2.4 2nd Design and application implementation
2.5 2nd Testing Phase
2.6 Maintenance
                   Maintenance
• Documentation.
• Reusability of classes.
• Internal projects.
Questions

								
To top