What does IT take to go Mobile

What management, organization and technology issues need to be addressed when building mobile application.

The introduction of a new information system involves much more than new hardware and software. A mobile strategy involves much than selecting mobile devices, operating system and applications. It also includes changes in business process, changing the way people work, skills, and the way a firm interacts with its customers. System builders must understand how a system will affect specific business processes and the organization as a whole.

I.                    Management Issues: Before firms go to mobile, Company should identify several issues toward management such as: System Solution Selection, Project Monitoring and Rationalization of the applications. Management also need defined clearly the benefit to company and customer against the developing any mobile application.

II.                  Organizational Issue: Before firms go to mobile, Company should identify several issues toward organizational such as: Global Processes Redesigning, Jobs redesigning, Employee Training and Change of corporate culture.

III.                Technology Issues: Before firms go to mobile, Company should identify several issues toward Technology such as: Deploy E-Business Software, Rich and rewards of far reaching changes of mobile features and applications, Automation from Technology – enable change and System Development Process.

How does user requirement definition for mobile applications differ from that in traditional systems analysis?

Requirement analysis also called requirements engineering which is the process of determining user expectations for a new or modified product.  These features, called requirements must be quantifiable, relevant and detailed. In software engineering such requirements are often called functional specifications. Requirements analysis is an important aspect of project management. Requirement analysis involves frequent communications with system users to determine specific features expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep and documentation of all aspects of the project from start to finish.

Traditional requirements are usually thought of as capabilities and constraints of the system. Many traditional requirements do provide context for business and users but usually not the main focus of the requirement rather than focus of system. Requirements be the sources of record for the system’s operation.

Describe the business processes changed by USAA’s mobile applications before and after the application were deployed.

USAA launched its Web in 1997 and went mobile 10 years later, with about 90% of its interactions with customers taking place on these two self-service channels. In 2001, USAA handle 183 million customer contacts through mobile channel alone, and expect the mobile channel will its primary point of contact with customers in next two years. In 2011 also, USAA Federal Savings bank processed $6.4 billion in deposits through this mobile applications. The mobile applications also displays loan 7 credit card balance, shopping services, homeowners & auto insurance policy information, Home Information, ATM & Taxi locators and a communities features that lets users see what others are posting about USAA on Twitter, Facebook and You Tube. USAA has 100 dedicated mobile developer writing apps for device using iPhone, iPad and Android systems, along with apps Blackberry and Windows Phone 7. USAA develop a smartphone accident report & claims applications that enables customers to snap a photo & submit a claim directly from the site of an accident.