2. ENTERPRISE APPS
SpeciďŹc
 client
 requirements
Â
Focused
 on
 produc5vity
Â
Solve
 problems
 or
 pain
 points
Â
Listen
 to
 clients
 needs
 and
 address
 the
 core
Â
issues
Â
â˘âŻ User
 experience
 is
 important
Â
Â
â˘âŻ
â˘âŻ
â˘âŻ
â˘âŻ
2
Â
3. POTENTIAL PROBLEMS
â˘âŻ Understanding
 the
 full
 requirements
 and
Â
scope
 of
 work
Â
â˘âŻ Managing
 expecta5ons
Â
Â
â˘âŻ SoDware/hardware
 integra5on
Â
â˘âŻ User
 Tes5ng
 and
 sign-ÂâoďŹ
Â
3
Â
7. DESIGN PHASE
â˘âŻ System
 design
Â
Â
â⯠Ac5vity
 diagram
Â
â⯠Use
 case
Â
â⯠Database
 API
 design
Â
â˘âŻ
â˘âŻ
â˘âŻ
â˘âŻ
Wire-Ââframing
Â
Proto-Ââtyping
Â
UX/Experience
 mapping
Â
Design
 Mock-Ââups
Â
7
Â
8. DEVELOPMENT PHASE
â˘âŻ
â˘âŻ
â˘âŻ
â˘âŻ
â˘âŻ
Â
Â
Development
 execu5on
 planning
Â
Execu5on
 of
 work
Â
Internal
 tes5ng
 (by
 developers)
Â
Internal
 Quality
 Control
 Tes5ng
 (PM
 &
 CD)
Â
User
 Acceptance
 Tes5ng
 (UAT)
Â
8
Â
9. MAINTENANCE AND UPDATE PHASE
â˘âŻ User
 feedback
Â
â⯠Focus
 groups
Â
Â
â⯠Online
 feedback
Â
â⯠Error/bug
 reports
Â
â⯠AppStore
 reviews
Â
â˘âŻ Iden5fy
 new
 features
 based
 on
 feedback
Â
9
Â
10. KEY AREAS IN THE DEVELOPMENT PROCESS
â˘âŻ Project
 Management
Â
â˘âŻ Prototyping
Â
â˘âŻ Tes5ng
Â
10
Â
15. WHAT HAPPENS IF THINGS GO WRONG?
â˘âŻ
â˘âŻ
â˘âŻ
â˘âŻ
Donât
 panic
Â
Always
 build
 with
 a
 plan
 B
Â
Be
 upfront
 with
 your
 clients
Â
Â
Address
 problems
 as
 soon
 as
 they
 arise
Â
15
Â