VERY IMPORTANT:

• Deactivate the access of all titles upon completing and delivering a project AKA end of deal, to act as a live documentation and be used later upon need under the supervision of the CTO and Java Architect.

• Another unit (Department) should be responsible for giving the Access control (Permission) to those titles using the assistance of Help Desk clerk.

• Reference

---

---

Business Analyst:

• Access to all analysis and diagrams which have been done so far to be able to start filling the backlog with the Product Owner and the Java Architect

---

UI/UX Designer:

• Access to planned wireframes and other resources like used images in web-frontend or mobile-frontend upon completion so the frontend can be constructed effectively in a proper way once the work of UI/UX Designer is done

---

Java Architect:

• Add architecture diagram here and have full access to everything for auditing purposes and measuring the variance with the plan upon need
• Merge feature-branch to master-branch as a 2nd approver

---

Developers [with 3 different specializations to eliminate the dirty business and manipulation which are done via mother fuckers thieves terrorists who steals the mental efforts of human resources and kill them later when they become old - also this way of specialization the human resource will grow steady in his/her career path, so the depth and breadth will grow up proportional with time in the proper direction besides becoming stable in his/her life and benefits his/her society]:

(Junior | Senior) Java Developers [Backend]:

• Access to backend components whether it has interface for integration (REST-API) or not as scheduled jobs made of Java with Spring-Boot

(Junior | Senior) JavaScript Developers [Web-Frontend]:

• Access to web-frontend component made of JavaScript with React

(Junior | Senior) Java Developers [Mobile-Frontend]:

• Access to mobile-frontend component made of Java with Android SDK

---

(Junior | Senior) System Admins [Linux Based]:

• Access to data-storage deployment scripts (schema initialization and structure filling periodically) if exists
• Access to backend components whether it has interface for integration (REST-API) or not as scheduled jobs which are made of Java with Spring-Boot
• Access to web-frontend component which are made of JavaScript with React
• Access to other configurations files like Nginx, ...
• If containerization model is adopted, then he/she shall have access to used Dockerfile and Kubernetes configurations files

Hint: Dockerfile and Kubernetes configurations files shall have a specific repository to maintain the version history before moving and applying to other components for centralization controlling purposes

---

(Junior | Senior) DevOps Engineers [Linux Based]: if automated deployment model is adopted

• Access to Jenkinsfile which is known as Jenkins configurations which are responsible of CI/CD periodical deployment delivery pipeline in testing environment

Hint: Jenkinsfile configurations files shall have a specific repository to maintain the version history before moving and applying to other components for centralization controlling purposes