Mobile Application Development Methodology V3

Development Period.

This document is intended to be used as a guide for the methodologies of developing mobile applications.

Introduction

Needs Assessment

Offline / Online Development

Design

Application Dsitribution

Signing Process

Regular Updates

Storyboarding

Server / Client UML Flow

Test

Needs Assessment


Design

Application Distribution

Signing Process

Regular Updates

Storyboarding


Test

This phase will put forward the scenarios about how the application will be used in real life.

In this phase the following questions has to be answered:

• Which user features, functions will be developed for which segment?•Which services will be integrated to the application ?• How will the segmented users use the application in real time?• What are the usability scenarios for the application? (During walking, in the car, busy environment, working environment, etc.)• Define Offline/Online information• Which platforms will be supported?• Decide application distribution method• Decide device which spesific features are going to be used (SSL, Accelarator etc.) • Decide which resolutions are going to be supported.

Resource:• Project Manager (Customer)• Marketing and Sales (Customer)

Needs Assessment

Used to determine the interface and other structural characteristics and the workflow of the application.


• How will be the flow chart of the application?• What kind of information will be included in which page?• Which model will be used for content presentation?• In which page, which content, buttons will be used?• Will datas be configured as dynamic or static ?

In this phase, the following items have to be determined:

• The structures of the pages in application• Navigations of the buttons and pages• Flow of the pages in application scope •User Experiences on different platforms

Resource:• Project Manager (Customer)• Marketing and Sales (Customer)• Usability Expert (Mobinex)

Storyboarding

Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test


• Definition of the resources that will provide the dynamic datas • The signature of services such as web service, rss, json that will be used in application •Decide error code messages (Network based error codes etc.)

Resource:• Technical Analyst (Customer)• Application Developer(Mobinex)


Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test

The operations on data resources and their usage.

The visual design of the application interface.

In this phase the following questions has to be answered:• What will be the “Brand Name” for the application? (Name of the application, Brand Name, Brand Image, etc.)• If there is a document about the brand of the company, should be taken in to consideration• How the segments will be designed?• What are the visual and audio media that will be used in the application?• What type of mobile will be used for this application?•Also different User Experiences for different platformsshould be considered.

In this phase, the following items have to be determined:•Design of the objects under the criterias of Touch screen – keyboard usage •Two design may required if its going to support both Touch Screen and Other.• Multi Resolution Support

Resource:• Visual Designer (Mobinex)• Usability Expert (Mobinex)

Design

Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test

Flow phase from offline application to online versionby integrated the dynamicdatas.


• What are the success criteria for application performance?• Which delivery method will be used for this application? (Wap-push, SMS, download..)

In this phase, the following items have to be determined:•Design of the objects under the criterias of Touch screen – keyboard usage • Multi Resolution Support• In order to not loose time dumy Web Services may be needed.

Resource:• Application Developer (Mobinex)


Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test

Testing phase of the developed application.


•What will be the Test Cases(Writing test cases shouldstart at the begining of the development and willevolving in each step.)•Does the application fulfill the established performance requirements?• Which problems has occurred during test?• Which problems can occur during application delivery?• What will be the backward compatibilty tests?

Considerations:•Departments who is going to develop the applicationand test should be different• What will be the criterias of testing.

• e.g. Is it going to be tested with online test toolsor with real devices.

Resource:• Test Group (Customer)• System Administrator (Mobinex)• Test Group (Mobinex)

Test

Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test


•Does the application meets the certain criteria such as functionality, visuality and/or usability ?•In which mobile platform, the signing process will be operated ?•Does any changes in functionality, visuality and/or usability in the application, after the signing process ?

Resource:• Test Group (Customer)• Application Developer(Mobinex)• Test Group (Mobinex)

Signing Process

Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test

The process of encoding a digital certificate into theapplication.

Application delivery to the segmented users.

In this phase the following questions have to be answered:

• How will the application be delivered? (WAP Push, SMS Pull, wap download etc.)• How to avoid the difficulties during the application delivery?• How to get reports when distributing application over alternative distribution channels.

In this phase, the following items have to be determined:

• Distribution channels and processes about getting the application by subscribers• Integration with the Contact Center interface should have done, if needed.

Resource:• Test Group (Customer)• Application Developer (Mobinex)

• Test Group (Mobinex)•Support Person (Mobinex)


Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test

The organization structure required to do the periodic content updates of the application.


• What will be the application update period?• Who will be responsible for updates?• What is needed for application update?

Resource:•Marketing and Sales (Customer)• Support Person (Mobinex)

Regular Updates

Needs Assessment


Design


Signing Process

Regular Updates

Storyboarding


Test

Terms and Conditions

About Mobinex

Mobinex, as the leading provider of mobile applications and on-device solutions, is dedicated to increasing revenues of mobile operators, content providers, media companies and enterprises with compelling user experiences.

About Smartface Platform

Company's flagship product Smartface Platform enables fast publishing of mobile applications which combines handset functionality, network and content features, and rich user interface. Smartface Platform helps mobile ecosystem to empower mobile data services and allow for the user experience to be customized over-the-air.

Updated May 2010

Copyright © 2009 Mobinex, Inc. All rights reserved. This document and the software which it describes are furnished under license and may only be used in accordance with the terms of such license. The content of this guide is for informational use only and should not be construed as a commitment by Mobinex. Mobinex assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication.No part of this manual may be copied, photocopied, reproduced, translated or converted to any electronic or machine-readable form without the prior written permission of Mobinex.

http://www.mobinex.biz

http://www.mobinex.biz/

http://www.mobinex.biz/

Mobile Application Development Methodology V3

Documents

Transcript of Mobile Application Development Methodology V3