1. Agile Methodology for Mobile
Software Development
By Crossover International Co. Ltd.

2. Abstract
• New Advances in mobile computer technology
• The rapid growth of wireless networks has
introduced new applications and concerns in
computer science and industry.
• The unique requirements and constraints associated
with mobile systems have brought new challenges
to software development for such environments

3. Challenges that has to cope with
• Wireless communication issues
– availability and disconnection, bandwidth variability,
heterogeneous networks, and security risks;
• Mobility issues
– address migration, and management of location-dependent
information;
• Portability issues;
• Various standards, protocols and network technologies;
• Limited capabilities of terminal devices
– factors pertaining to low power, risks to data integrity,
smallsized user interfaces, and low storage capacities;
• Special privacy and customizability needs;
• Strict time-to-market requirements.

4. Home Grounds For Agile and Plan-Driven Methods
Area Plan-Driven Methods Agile Methods
Developers Plan-oriented; adequate skills; Agile, knowledgeable,
access to external knowledge collocated, and collaborative
Customers Access to knowledgeable, Dedicated, knowledgeable,
collaborative, representative, collocated, collaborative,
and empowered customers representative, and empowered
Requirements Knowable early; largely stable Largely emergent; rapid change
Architecture Designed for current and Designed for current requirements
foreseeable requirements
Refactoring Expensive Inexpensive
Size Larger teams and products Smaller teams and products
Primary High assurance Rapid value
objective

5. Mapping Agile Home Ground Themes to Traits
Observed in Mobile Software Development
Ideal Agile
Rationale Mobile software
Characteristic
High environment Due to high change of High uncertainty, dynamic
volatility requirements, less need for environment: Hundreds of new
upfront design & planning, need mobile phones produced each
for an incremental and iterative year
development approach.
Small Small teams are able to react Majority of mobile software is
development more rapidly, share information, developed in micro or SME
teams need less documentation , etc. companies, or development
teams.
Identifiable To avoid business Potentially unlimited number of
customer misunderstanding end-users. Business customer
easier to identify, e.g. distributor.
Object-oriented Most tools that support agile E.g., Java and C++ used; some
development development exist for object problems in proper tooling e.g.
environment oriented platforms. for refactoring and test-first
approach

6. Mapping Agile Home Ground Themes to Traits
Observed in Mobile Software Development (Cont.)
Ideal Agile
Rationale Mobile software
Characteristic
Non-safety Failures do not cause loss of Majority of existing mobile software is
critical software lives. More agility can be for entertainment purposes. Mobile
pursued. terminals are not reliable.
Application-level Large embedded systems While mobile systems are complex
software require extensive and highly dependent, mobile
communication & verification applications can be standalone
mechanisms. applications.
Small systems Less upfront design needed Mobile applications vary in size, but
are generally less than 10000 lines of
code.
Short For the purposes of rapid Development cycles vary. Typical
development feedback mobile applications and services
cycles can be developed within a 1-6
month time-frame.

7. Top-down Iterative Incremental Process
Consisting of the following tasks:
• Prioritization of the Requirements:
– Performed at the start of the process and repeated at the
end of each iteration.
– Requirements are ordered according to their relevance to
the current scope and level of abstraction
– Focusing the design process on satisfying requirements of
higher significance.

8. Top-down Iterative Incremental Process
Consisting of the following tasks:
• Prioritization of the Requirements:
– At the start of the process, abstraction is at its highest level
and the scope encompasses the whole lifecycle
– Requirements with lifecycle-level impacts are given
precedence;
– as design progresses to lower levels of abstraction, priority is
gradually shifted to requirements with finer-grained
aspects.

9. Top-down Iterative Incremental Process
Consisting of the following tasks:
• Iterative Design Engine: (Performed in each
iteration)
– Selection of the design approaches to be used in the
current iteration, include:
• Instantiation: instantiating an already available process
metamodel;
• Artifact-oriented: devising a seamless complementary chain
of artifacts and building the process around it;
• Composition: using one of the already available libraries of
process patterns;
• Integration: integrating features, ideas and techniques from
existing methodologies.

10. Top-down Iterative Incremental Process
Consisting of the following tasks:
• Iterative Design Engine: The following tasks are
performed in each iteration:
– Application of the selected design approaches aimed at
defining the methodology at the current scope and level
of abstraction
– Revision, refinement and restructuring of the methodology
built so far.
– Specification of the level of abstraction for the next
iteration, and definition of the scope and intended level of
detail.
– Revision and refinement of the requirements.

11. Gradual refinement of our proposed methodology

12. Gradual refinement of our proposed methodology

13. References

14. References

15. Case Study

16. Where is Dr. Sun?
搜尋孫中山
• iPhone and Android phone apps for
the Campaign on 1911 Revolution
• With Augmented Reality (AR) and
interactive user experience
• Guide users on a virtual journey
through 30 designated spots related
to the history of the 1911 Revolution
and Dr Sun Yat-sen in Hong Kong.

17. Where is Dr. Sun?
搜尋孫中山
Augmented Reality (AR)
• 30 check points with GPS
locating function.
• Take photos with the
stamp through the AR
function
• To ensure the function
goes well, Crossover did
the site visit both
individually and with the
client.

18. Where is Dr. Sun?
搜尋孫中山
Q&A and Badges
Collection
• Answer the Multiple
choice questions for
each checkpoint and
earn a badge
• Get the Final Badge
within a specific area
(within 60m from the
last spots)

19. Where is Dr. Sun?
搜尋孫中山
History Timeline
• Using the format of
Newspaper to show the
history of Dr. Sun
• Able to link to the spots
for some specific events

20. Where is Dr. Sun?
搜尋孫中山
Sharing the checkpoints
you have been to
• Facebook or
• Twitter

21. Where is Dr. Sun?
搜尋孫中山
Local notification
function (for iPhone) and
Widget (for Android) to
alert users if a historical
event had been
happened to-date

22. Thank you!
Contact Us
Contact Person : Alex Hung
Email : alex@crossover-int.com
Tel : (852) 2869 6603
Fax : (852) 3909 1901
Address : 15/F, Wang Fu Building, 5 Chatham
Court, Tsim Sha Tsui, Kowloon
Website : http://www.crossover-int.com