Lesson plan
Software architect
A software architect is a software engineer responsible for moderate-level design choices related to overall system structure and behavior. It's a software architect's responsibility to match architectural characteristics (aka non-functional requirements) with business requirements. For example: * Having high customer satisfaction requires availability, fault tolerance, security, testability, recoverability, agility and performance in the system. * Doing mergers and acquisitions (M&A) requires extensibility, scalability, adaptability, and interoperability. * Constrained budget and time requires feasibility and simplicity. * Faster time-to-market requires maintainability, testability and deployability.
Article summary
A software architect is a software engineer responsible for moderate-level design choices related to overall system structure and behavior. It's a software architect's responsibility to match architectural characteristics (aka non-functional requirements) with business requirements. For example: * Having high customer satisfaction requires availability, fault tolerance, security, testability, recoverability, agility and performance in the system. * Doing mergers and acquisitions (M&A) requires extensibility, scalability, adaptability, and interoperability. * Constrained budget and time requires feasibility and simplicity. * Faster time-to-market requires maintainability, testability and deployability.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.