-
Notifications
You must be signed in to change notification settings - Fork 0
Notes regarding "testing environment"
Mohamed Hassan (JOSEPH) edited this page May 4, 2023
·
14 revisions
Deconstruct the testing environment
upon moving and stabilization in production environment
and going live.
The bare metal of testing environment
should be cleaned and maintained for future projects after that.
Draw connectors between those components according to your plan.
- Frontend (WEB and MOBILE)
- Proxy
- APP-x, APP-y, ...
- MB-x, MB-y, ...
- DS-x, DS-y, ...
Where APP is defined according to a certain use case as:
- a REST API service OR
- a Scheduled Job
Where MB is defined as a message-broker from a certain type according to a certain use case
Where DS is defined as data storage and it could be either relational or non relational database according to a certain use case
- Overview
- University Role
- Architectural Components
- Legal and Ethical Development Specialization
- System Administration
- Software Deployment
- Git Repositories | Access Control
- Testing notes - Tester [QA]
- Daily Standups
- Onboarding process upon hiring newcomers
- Tickets Flow AKA Industrial Software Manufacturing Process
- Sprint
- Legal and Ethical Aspects of Contracts
- Human Resources Planning to the Software-Development-Unit
- Possible future moves of Human resources
- Notes to Managerial Positions
- Notes for Self Study During the University Phase
- Screening Interviews
- Search keywords for recruiters
- Email-Writing
- Job advertising template for recruiters
- Ethics of writing useful software
- How to do a complaint against someone in a safe way
- Internal and external communication tools within an organization
- Necessary amount of information technology knowledge for employees before work