Module 9: Quality Attributes
From SoftwarePractice.org
Module 9 of the Foundations of Software Architecture course, based on A Software Architecture Primer by John Reekie and Rohan McAdam.
Contents |
[edit]
Text-reading questions
- Explain the difference between performance and scalability.
- In what ways are usability and architecture inter-related?
- How is a reliability scenario different from a usage narrative?
- What do you think the difference between reliability and availability is?
- Give two example scenarios or narratives that illustrate the importance of availability.
- What is ``security?
- Suggest some ways in which you might increase the testability of a complex software system.
[edit]
Exploration questions
- Name three networking strategies that aid security. Which is the most secure?
- Describe some additional tactics or patterns for enhancing security.
- Explain how a system could use XML or an RDBMS to enhance configurability. What are the trade-offs between the two?
- Why is logging important? What are some issues with logs?
- In what ways, that are not related to software architecture, can maintainability be enhanced?
- Have you ever successfully re-used software code written by other people? Explain why or why not, and how.
- What configuration would Blackboard (the software behind UTSOnline) need in each installation?
- What is wrong with this statement: "The FooBar system has reliability as its most important quality attribute, followed closely by performance."
- What are some ways in which usability can be enhanced? Focus specifically on techniques that have architectural impact or are supported by the architecture.
[edit]
Related articles
- (None listed.)
