The document outlines key considerations for software architecture design, including project scope, budgeting, time management, and various design principles and patterns. It discusses methodologies like Agile and Scrum, provides insights into the roles of project and product management, and emphasizes the importance of collaboration among stakeholders. Additionally, it covers technical aspects such as language and database selection, deployment strategies, and testing types.

1. SOFTWARE
ARCHITECTURE
POINTS TO CONSIDER WHEN DESIGNING A SOFTWARE
Foyzul Karim

2. OVERVIEW
• Scope
• Budget
• Time
• Plan

3. PROJECT
SCOPE
• Requirement analysis
• Project management
• Language selection
• Database selection
• Design principles identification
• SOLID
• DRY
• KISS
• YAGNI
• Design patterns identification
• State
• Strategy
• Repository
• Factory

4. PROJECT
SCOPE
• Project architecture
• Monolith
• Microservice
• Micro frontends
• Serverless
• Domain driven
• Test strategy
• Unit test
• Integration test
• Acceptance test
• Security test

5. PRODUCTIO
N SCOPE
• Infrastructure
• VPS
• Cloud
• Self managed
• Cloud managed
• Deployment
• Continuous integration
• Self managed (Jenkins etc.)
• GitHub, Azure DevOps
• Continuous delivery
• Self managed (GoCD etc.)
• BuildKite

6. PRODUCTIO
N SCOPE
• Scaling
• Horizontal
• Vertical
• Load balancing
• Security
• OAuth
• JWT
• Session
• Auth0/Okta/Cognito/AD
• Monitoring
• Azure AppInsight, AWS CloudWatch
• Datadog
• ELK

7. PROJECT SCOPE
SDLC, PROJECT MANAGEMENT METHODOLOGIES AND
CAREER IN PRODUCT MANAGEMENT

8. METHODOLOGIE
S
• Waterfall
• Agile
• Scrum
• Kanban

9. SCRUM
CEREMONIES
(WE
FOLLOW)
• Backlog grooming
• Sprint planning
• Daily standup
• Sprint demo
• Sprint ticket review
• Retrospective

10. KANBAN
CEREMONIES
(WE
FOLLOWED)
• Backlog grooming
• Backlog estimation
• Daily standup
• Biweekly demo
• Retrospective

11. CAREER IN
PROJECT
MANAGEME
NT
• How is software made anyway?
• Requirement  communication and
brainstorming
• Development  heavily depends on coding
• Release  heavily depends on DevOps
• Support  communication
• Salary
• Learning path
• Project Management Professional (PMP)
• Certified Associate in Project Management
(CAPM)
• Certified ScrumMaster (CSM)
• Professional Scrum Master (PSM I)

12. PRODUCT
MANAGER
(WHAT I
SAW)
• Collaborate with other stakeholders
(Analytics team, Sales, Marketing,
CX)
• Understand everything about the
product
• Imagine the feature and its impact
• Collaborate with the developers to
find out better solution / UX
• Knows SQL

13. DEVELOPMENT
& DEPLOYMENT
LANGUAGE,
DATABASE,
ARCHITECTURE,
DEVELOPMENT,
TESTING ETC.

14. THE HOLY
WAR OF …
• Which language is the best?
• Which framework is the best?
• Which database is the best?
• Which library is the best?

15. BEST
ANSWER
ONE COULD
GET IS …
• It depends
• Company
• Project
• Team
• Budget
• Maintenance

16. STOP
FIGHTING
• The decision is made by the
top management, not the developer

17. LET’S
DISCUSS
• Language selection
• JavaScript
• Python
• PHP
• C# / Java
• Database selection
• MySQL
• SQL Server
• MongoDB
• Postgres
• Design principles
identification
• SOLID
• DRY
• KISS
• YAGNI
• Design patterns identification
• State
• Strategy
• Repository
• Factory
• Project architecture
• Monolith
• Microservice
• Micro frontends
• Serverless
• Domain driven
• Test strategy
• Unit test
• Integration test
• Acceptance test
• Security test
• UI Test (cypress)

18. LET’S
DISCUSS
• Infrastructure
• VPS
• Cloud
• Self managed
• Cloud managed
• Deployment
• Continuous integration
• Self managed (Jenkins
etc.)
• GitHub, Azure
DevOps
• Continuous delivery
• Self managed (GoCD
etc.)
• BuildKite
• Scaling
• Horizontal
• Vertical
• Load balancing
• Security
• OAuth
• JWT
• Session
• Auth0/Okta/Cognito/AD
• Monitoring
• Azure AppInsight, AWS
CloudWatch
• Datadog
• ELK