Anda di halaman 1dari 3

Requirements:1.Software requirementsFor android development we use software like Java development kit(JDK), Eclipse IDE, Android SDK.

2.ProgrammerWe should have programmers who have knowledge of Java and XML.
3.DesignersWe should have designers who can create really good interface so that people can find it easy to use
our app.
4.MachineWe can run android development tool on all flavors of computers like Linux, Mac OS, Windows.
An android device or smartphone is also useful but using software inbuilt emulators that allow to
develop and test.
IMPORTANT:-BASICALLY A TEAM OF MEMBERS LIKE MANAGER, DESIGNERS, DEVELOPERS, BACKEND
DEVELOPERS, TESTERS, SUPPORT MEMBERS

Risks:1.Risk of building an app that our target users don't wantIf we build an app with our own perspective without considering our client/customer perspective.
This may affect our client view as not considering their ideas and they may reject our app.
2.Risk of unsustainable growthThis risk should be taken consider if our app is used by too many people,i.e.,unsustainable growth
then we should have services and support to this many growing number of end users.
3.Risk of security breachesSecurity breaches are certainly nothing new, and apply to any type of web or mobile app.
The danger here lies in underestimating the need for proper security precautions within native apps.
This lack security protocols which may result in unauthoried access to data,application and so on..
4.Risk of getting deniedThis is when we do not take into consideration app store submission.
It is our developer responsibility to keep the app should be submitted and not be rejected in app store as per their terms.
5.Risk of tying ourself to a single platformChoosing an single platform for an app development may leads to decrease to our further success of our app.
We should build our app for every platform otherwise it will limits our future options.
6.Risk of app crashingWhat if our app crashes while operating?
So we have to build an app that doesnt crash and if crash then we should resolve it quickly by taking customer feedback.

Work Breakdown Structure:Plannin


g

Gathering
requirements.

Deciding how
much team
members
required.

Analysis

Analysing the
critical path.

Analysing the
estimation time
of each part of
project.

Designi
ng

Basic designing
of our app.

Future changes
in design.

Develop
ing

Start
programming
on the basic of
gathered
requirements.

Future changes
in program.

Testing

Testing small
part of coding
which has been
developed.

Testing whole
app after
building.

Planning how
we should start
making app.

Deciding if we
need any third
party
involvement.