The purpose of the Software Architecture Assessment is to review the current software architecture in light of requirements, and make sure the system will be able to target those requirements.
- Your customers are avoiding your new, shiny system because it performs poorly
- You experience a very poor uptime and the business loses money because of frequent crashes
- A core system is about to get deployed, and you know the business depends on it. You want to make sure it’s built right from the start and not have any “surprises”
The Software Architecture Assessment process often finds potential performance and reliability points of failure, and allows developers to improve the system and avoid the risk of not addressing system requirements.
The assessment process includes the following phases:
- Explore the system’s functional and non-functional requirements
- Examine the current system’s architecture
- Code review of specific, potentially problematic code blocks
- Discussing various options for mitigating problems found
By the end of the assessment process, you will get a detailed document that contains:
- A brief summary of the process that was carried out
- Description of the system and its architecture
- List of problems found during the assessment process
- Detailed recommendations and instructions for fixing these problems
Make sure the problems are actually fixed
Request a support consulting package which will ensure the recommended fixes are applied correctly and effectively by the development team.