meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ixc2024:impactassessment:technical [2024/05/24 11:12] – alestaixc2024:impactassessment:technical [2024/05/24 11:46] (current) – joof
Line 2: Line 2:
  
 Technical dimension is looking into how sustainable our product is in terms of technology. Here you will be taking a deeper look into its **implementation** and maybe get your hands slightly dirty. It is quite hard to determine technical sustainability if you were not involved in the process of development, or if you do not have access to the documentation. Technical dimension is looking into how sustainable our product is in terms of technology. Here you will be taking a deeper look into its **implementation** and maybe get your hands slightly dirty. It is quite hard to determine technical sustainability if you were not involved in the process of development, or if you do not have access to the documentation.
 +
 +{{:ixc2024:impactassessment:untitled_drawing_16_.png?400|}}
  
   - **Maintainability** - Dive deep into the code, and general structure of the project. Try putting yourself in the shoes of a new developer joining your team. Would they understand your code? Would they understand the structure? How easy would it be for him to join the team and start contributing? These questions will help you answer the first question - __How maintainable is your product?__    - **Maintainability** - Dive deep into the code, and general structure of the project. Try putting yourself in the shoes of a new developer joining your team. Would they understand your code? Would they understand the structure? How easy would it be for him to join the team and start contributing? These questions will help you answer the first question - __How maintainable is your product?__ 
Line 15: Line 17:
   - **Security**   - **Security**
   - **Scalability**   - **Scalability**
 +  - **Resilience** - Your system should design your system to remain operational in case of failures
 +    - Error Handling: You should use exception handling in error prone operations so as to minimize crashes. Most common ones are database and network operations.
 +    - Code: Having your code in a repository like GIT also serves as backup.
 +    - Recovery: Create a plan on how to quickly restore your system in the event that there is a total crash.
  
 +  - **Interoperability** - 
 +     
 +    - API Design: Create well-documented APIs to facilitate communication between frontend and backend. You can use tools like Postman to test your APIs and swagger for API documentation.
 +    - Standard Protocols: Use standard communication protocols and data formats (e.g., JSON, XML) to ensure compatibility with web, mobile and backend.