Ch 6.1-4 Discussion Questions

  1. If controllers are managing user interactions then what is meant by View sending user events to the controller? What is the difference between user events and user interactions?
  2. What is meant by that client-server architecture is suitable when the load on a system is variable? What would be the issue with a constant load?
  3. The author mentions how some people dislike block diagrams in architectural documentation. What are more rigorous ways that can replace them?
  4. Why do non-functional requirements have a greater impact on the architectural choices in a project?
  5. Is it logical to start the design of the system architecture before the requirements specification is complete?
  6. How can we reflect functional and non-functional requirements when architecting software systems?
  7. Are databases for transaction processing systems ever stored offline? Would storing a database offline ever be beneficial for security reasons?
  8. When a programming language like Python is processed by a language processing software system, how is this software eventually converted into machine code. Does this take longer to translate than a language like C++, and if so, why would Python be used instead of C++?
  9. Should UML be used to describe software architectures?
  10. How to decide when architectural requirements directly conflict? For example, if both performance and maintainability were important requirements, what would the architecture be?
  11. How do you strike an effective balance between performance and security when you’re limited by either hardware or computing resources?
  12. What is an example of a layered model?
  13. If a system is to make use of multiple different architectural patterns, would only the dominant one be represented, or would there be a separate model for each?
  14. How common are these architecture diagrams in requirements engineering for contracts?
  15. How could we apply architecture patterns to our projects?
  16. How do language translators account for things like grammar and sentence structure?
  17. What are real-life examples of repository data architecture used for major companies?
  18. Is pipe and filter system commonly used in real life?
  19. What are the distinctions between layered architecture and application architecture?
  20. What notations should architectural models be described with?
  21. How important is it that we have a solid architecture design at this time of the semester? For our projects, is it completely necessary that we have a design we will not change any time in the future?
  22. Are there specific architectures you would recommend for our project (web-based survey one) specifically?
  23. What is the baseline to decide what architecture would be the right one for your system?
  24. What is the key difference between client-server architecture and repository architecture? They both seem to have the common feature of having a central server/repository that the clients can access services from.
  25. What are the advantages and disadvantages of the repository architecture pattern?
  26. How can architectural views be represented?
  27. Why would Model-View-Controller method makes it more complex in terms of coding? And why just in more simple systems?
  28.  From the Art Create team: Which system architecture pattern do you think our project would best fit into? (repository, client-server, or a mix of both?)
  29. What are the main points of architectural design we should worry about in each of our respective projects?
  30. Which architectural design is best for agile
Scroll to Top