0% found this document useful (0 votes)
4 views1 page

Application Development Workflow Guide

The document outlines the application development flow, detailing key steps such as Business Requirement Document (BRD), UI/UX design, technical design, and production deployment. It emphasizes the importance of having proper technical documentation, access to non-production applications for testing, and administrator access to servers and source code when using an outsourced development team. The process culminates in maintenance and improvement after production deployment.

Uploaded by

heru herlambang
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views1 page

Application Development Workflow Guide

The document outlines the application development flow, detailing key steps such as Business Requirement Document (BRD), UI/UX design, technical design, and production deployment. It emphasizes the importance of having proper technical documentation, access to non-production applications for testing, and administrator access to servers and source code when using an outsourced development team. The process culminates in maintenance and improvement after production deployment.

Uploaded by

heru herlambang
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Application Development

Flow

1. BRD (Business
3. Technical 4. Architecture
Requirement 2. UI/UX
Design Review
Doc)

5. API
Sepecification

7. Non-
9. Production
8. Testing Production 6. Development
Deployment
Deployment

10. Maintenance
and
Improvement

Most important Thing if we use


Outsource Dev Team

1. Get the Technical Design (point number 3) Documentation – this is the basis (guideline) of the
application they will develop, so the dev team must follow this design. From this document we also can
estimate the budget for sever, storage etc.
2. Testing (point number 8) – need to have access to non-production application to double check of
testing, it will be good if we have our own QA engineer.
3. Administrator access to server and the Source code.

You might also like