Pre-project analysis

First of all, Ivan has to analyze which mobile platforms customers use. To get this information Ivan worked closely with marketing director of the projects, and the last one provided him information about mobile traffic sources

Also, he provided a survey, he made by asking his customers, which platform they are using

After analyzing results, Ivan and Vladimir came to agreement that development should focus on iOS and Android only, because Windows Phone has very small part of users while development for a lot of other platforms is beside the purpose.

Ivan should understand whether a cross-platform application is convenient for the client or not. He will use Analytical Hierarchy Process (AHP) and Cause-loop-diagrams (CLD) to achieve that, however before he has to prepare PQR and CATWOE analysis to better understand the situation.

PQR and CATWOE for pre project analysis

Customer/Clients: Client, founder of e-commerce project; end-user of application

Actors: Technical and design department of mobile development studio, client

Transformation: Understand which approach of development mobile application to choose

World View: According to mobile development strategy choose an approach for developing

Owner: Client, founders of e-commerce project

Environment: Technical and usability requirements

In order to start doing a work, that will fully satisfy founders of e-commerce project [R] Ivan should provide them a strategy of deploying business on mobile [P] , by means of marketing research, made by his company and budget [Q]

Cause-loop-diagram (CLD) for choosing platform

This diagram can’t be fully represented as a loop diagram, because of the independence of key features. But this diagram represents the approach, company should apply in case they want to satisfy different types of ST.

For now, the prior client – is owner, Vladimir S. and the decision should fully cover his requests. In that case, it is evident, that cross-platform can increase covering the majority of target audience, without development costs variances, but with bad UX. As for the last one – it is no so important for client at that stage

Date: 2016-04-22; view: 809