Here’s an overview of the product audit activities your team can perform within the Knowledge sharing and deep code inspection stage.
1. Back-end software application
- Read the documentation
- Setup development environment on a local machine according to documentation
- Import project
- Configure access on SCM (source code management)
- Get project sources from the repository
- Assemble Project
- Follow the documentation and assemble the project locally
- Run the Project
- Follow the documentation and run the project locally
- Run integration tests
- Follow the documentation and run test locally
- Monitor Project Activity
- Follow the documentation and check Project activity
- Create a new feature
- Follow SDLC to develop a new feature
- Test new feature
- Run integration tests
- Perform regression tests
- Accept feature
- Final acceptance activities
- Deploy new feature
- Follow the documentation for CI/CD pipelines
2. Front-end software application (vue.js)
- Introduction to project architecture
- Setup development environment on a local machine
- Install Node.js
- Install Npm
- Import project
- Get project sources from the repository
- Assemble Project
- Install dependencies
- Set up developer server proxy in vue.js config
- Set up a local environment
- Developer build and local server: run command “npm run dev”
- Read the API documentation from swagger
- Create new feature
- Follow SDLC to develop a new feature
- Test new feature
- Follow QA to test a new feature
- Deploy new feature
- Follow the documentation for CI/CD pipelines
- Accept feature
- Final acceptance activities
3. CI/CD on AWS (DevOps scripts)
- The developer creates a separate branch from the development branch except for cases when the changes are a hot-fix for the production (in this case master branch must be used as a source branch)
- When changes are ready, the developer submits the merge request to the original branch that was used in step 1.
- After creating the merge request, integration tests and security tests are launched. If the tests didn’t pass, the code is returned to the developer for correction.
- After tests are done successfully the merge request goes for code review. If the code review didn’t pass, the code is returned to the developer for correction.
- The merge request is applied.
- Deploy to the development server is automatically started.
- Testing changes by the team. The detected errors are sent to the developer for correction.
- To do a release a merge request from the develop branch to the master branch should be created.
- Integration and security tests are launched.
- Merge request goes through code review and merges to master.
- Based on the master branch, the project manager to create a pre-production release of the git tag (*-rc\d).
- After git tag pre-production release is created the pre-release is automatically deployed to the staging server.
- The team conducts testing. The client gets acquainted with new or revised features. If bugs or errors are found, the code is returned to the developer for correction.
- Based on the master branch, the project manager to create a production release of the git tag (.*-release). Important: pre-release and release tag must be created on the same commit.
- After git tag production release is created the pre-release is automatically deployed to the production server.
- The team checks the functionality. If a critical error or bug is identified, a hotfix is immediately developed and deployed.
4. Business analyst view: Product knowledge transfer
Platform overview
- Roles/actors
- Roles associated operations
- Wallet engine
- APIs
Business processes
- Registration/authorization
- Onboarding
- Top-up/withdrawal/transfer
- Schedule payments
- POS
- Vouchers (prepaid)
- Invoices
- Currency exchange
Possible integrations
- Acquirer
- Bank
- Card processor
- KYC
- Others
Contact us if you’ve got any questions on the process.