"Architecture assessment from classics to details", Dmytro Ovcharenko
Signaler
Partager
•0 j'aime•155 vues
![Tradeoff Analysis Method
QA-5 | Performance - As a UserRole1 I can create
new BE Event in [Project Name] Admin portal
under normal operation with average response
time 2 sec
QA-9 | Scalability - [Project Name] back-end can
handle a minimum of 1000 simultaneous users
without performance degradation
QA-19 | Reliability - When primary db server
fails, disaster recovery procedure will
immediately switch to secondary db node,
without data lost.
QA-27 | Supportability - As an Administrator of
[Project Name] I would like to receive alerts
when sub-system elements will be failed](https://image.slidesharecdn.com/fwdaysarchitectureassessments-230923153057-a768df6c/75/architecture-assessment-from-classics-to-details-dmytro-ovcharenko-12-2048.jpg?cb=1695483956)
![SoftServe Confidential
Example ATAM III
∙ R2 – Without defined LB we cannot scale horizontally, manage future application load
∙ R3 – One application node cannot handle 1000 simultaneous users, Performance results here.
∙ R4 – Handle more than 40K Cron tasks within a few hours, it can affect performance and availability of
[Project Name].
∙ R5 – Backups are not activated. It can affect availability and supportability of the system.
∙ R6 - To reach Performance requirements and mitigate network latency we should define CND approach.
AWS Cloudfront is a good candidate for CDN and it has a good integration with AWS S3.
∙ R7 – QA process is not defined on infrastructure level, there is no defined automating process of
deployment intermediate results of development.
∙ T1 – Basic infrastructure on Linode is a good start for quick up and run application server, it's also a good
choice for testing proposal.
∙ N1 - Cluster has the multi-core support, in this case we can run [Project Name] MeteorJS app utilizing all
the cores in this server.](https://image.slidesharecdn.com/fwdaysarchitectureassessments-230923153057-a768df6c/75/architecture-assessment-from-classics-to-details-dmytro-ovcharenko-14-2048.jpg?cb=1695483956)
"Architecture assessment from classics to details", Dmytro Ovcharenko
•0 j'aime•155 vues
Signaler
Partager
Télécharger pour lire hors ligne
We will talk about architecture assessment and SEI ATAM methodology in detail. We also review Quality Attribute Workshop on a high level and find differences between quantitative and qualitative analysis. The assessment process can be represented as a set of activities roughly split into assessment preparation, collection of the important data and stakeholders' inputs, architecture analysis, and, finally, presentation of findings and recommendations. Finally, we will review the assessment document and some examples.
Recommandé
Contenu connexe
Similaire à "Architecture assessment from classics to details", Dmytro Ovcharenko
Similaire à "Architecture assessment from classics to details", Dmytro Ovcharenko(20)
Plus de Fwdays
Plus de Fwdays(20)
Dernier
Dernier(20)
"Architecture assessment from classics to details", Dmytro Ovcharenko
- 1. September 2023 Leadership & Innovation prepared for IT is X-CHANGE
- 2. We cannot solve our problems with the same thinking we used when we created them
- 4. Architecture Assessment Flow: Big Picture
- 5. When we should run Assessment?
- 7. Attribute Driven Design: Simplify
- 10. ATAM Flow
- 11. Assessment Template Beyond Requirements Elicitation Current State Analysis Recommendation Roadmap
- 12. Tradeoff Analysis Method QA-5 | Performance - As a UserRole1 I can create new BE Event in [Project Name] Admin portal under normal operation with average response time 2 sec QA-9 | Scalability - [Project Name] back-end can handle a minimum of 1000 simultaneous users without performance degradation QA-19 | Reliability - When primary db server fails, disaster recovery procedure will immediately switch to secondary db node, without data lost. QA-27 | Supportability - As an Administrator of [Project Name] I would like to receive alerts when sub-system elements will be failed
- 13. Made Decisions Made and Unmade Decisions Sensitivity Tradeof f Risk Nonrisk Linode as a hosting platform S2, S3 R5, R7 N4 Single Application Node (4CPU’s, 4Gb RAM) is defined for supporting Parent Portal and all requests from mobile clients T1 R1, R2, R3 Using Meteor Cluster: Clustering solution for Meteor with load balancing and service discovery. S1 N1, N2 Single Crone Node is defined to handle more than 40K tasks each day. T1 R1, R4 Using AWS S3 for storing Family Media: Photos/Videos R6 N3
- 14. SoftServe Confidential Example ATAM III ∙ R2 – Without defined LB we cannot scale horizontally, manage future application load ∙ R3 – One application node cannot handle 1000 simultaneous users, Performance results here. ∙ R4 – Handle more than 40K Cron tasks within a few hours, it can affect performance and availability of [Project Name]. ∙ R5 – Backups are not activated. It can affect availability and supportability of the system. ∙ R6 - To reach Performance requirements and mitigate network latency we should define CND approach. AWS Cloudfront is a good candidate for CDN and it has a good integration with AWS S3. ∙ R7 – QA process is not defined on infrastructure level, there is no defined automating process of deployment intermediate results of development. ∙ T1 – Basic infrastructure on Linode is a good start for quick up and run application server, it's also a good choice for testing proposal. ∙ N1 - Cluster has the multi-core support, in this case we can run [Project Name] MeteorJS app utilizing all the cores in this server.
- 15. SoftServe Confidential Risk Analysis - PI Matrix Risk Priority depends on (Risk Exposure = Probability * Impact) 1. Assign P and I to the risk from the range of High, Med, Low 2. Calculate E = P * I 3. Use the PI Matrix to determine the risk priority: Probability I m p a c t Low (1) Medium (2) High (3) Low (1) 1 2 3 Medium (2) 2 4 6 High (3) 3 6 9
- 16. Thank you! We value your feedback n-ix.com Clients’ reviews