Discussion Ch 5.1-5-3

System Modeling

  1. Are model diagrams used to describe very large systems (e.g. the Microsoft office suite, communities on the internet) or is this not feasible (e.g due to size or dynamic nature)? Are there facets of systems that are difficult or infeasible to capture through the described models?
  2. How do you know if an interaction is worth modeling?

  3. How do you know if modeling an existing system will make the system more clear to stakeholders?

  4. Crow’s foot notation seems much simpler than UML. What are the advantages and disadvantages of the two?

  5. For our projects should we design models to represent multiple perspectives?

  6. Which UML diagram types are better for which types of projects or should multiple diagram types be used when approaching any project?

  7. Is there an expectation in this class for us to use one of these models in our system design?

  8. Since the system stakeholders seem to be involved in decision making processes, should the developer change his/her choice of model based on the stakeholder’s wishes? Or should there be resistance to change?

  9. When are different modeling diagrams produced during the system design process?

  10. How many models are typically used when designing a small system?

  11. What are some considerations to make while deciding the boundaries of your system?

  12. Different models are used in different stages of the development process starting from requirements engineering to implementation to documentation. Can we discuss what kinds of models are best for what stages?

  13. How do developers create software with different boundaries, i.e. software that can be used by a child who can't read or an adult

  14. Is there a standard UML modeling software?

  15. Can we use lucid charts to make diagrams of these types of models, or must we use another tool?

  16. When possible, should you always provide a diagram when describing parts of your system?
  17. What is the difference between an activity diagram and a class diagram? When would one be more appropriate than the other?

  18. What is the difference between a use case diagram and a state diagram, and how do you choose between the two?

  19. What are the cost benefits of creating these diagrams? Do programmers in practice refer to these often?

  20. When should we avoid generalization?

  21. Is aggregation the illustrated version of inheritance?

  22. Is it important to have stick figures in the diagrams?

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2018-02-12 - JimSkon
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback