1. System Context and Domain Analysis Large Scale Software Architecture Chapter 6 Danial moazen Prof:Dr.Abdollahzadeh

2. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade2 Conceptual Diagrams Not suitable to write viewpoints due to Lack of formality Lack of specific modeling conventions Variability in stakeholders Some guidelines should be followed Identify the stakeholders The information to convey Level of information to communicate Use of conceptual diagrams should be limited to communication with individual external to the software development team Others should learn basics of UML Project management Support teams Test organizations Managers not directly involved

3. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade3 Context Viewpoint Contains only The system External entities with their interfaces The system’s interface with external entities Is effective for start of a discussion of the entire system, top level design review, a training session on the system Can be supplemented with actor to actor interfaces Additional columns can be added to indicate performance, data throughput, protocols utilized,… Can be used at several levels in doing the system architecture and design

4. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade4

5. 5 Context viewpoint

6. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade6

7. 7 Domain Analysis Three Viewpoints For each use case A set of analysis interaction views A focused analysis view An overall analysis view Should be kept to the core set of use cases to identify key domain elements. Use cases should be prioritized. Works best when both the problem domain and components are not well understood.

8. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade8 Analysis process

9. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade9 Other techniques Brain storming Start with a set of documents (coming from standards, marketing,…)then brain storm Identify scenarios,create interaction views, then brain storm Start with a set of standard system interactions produced by standards Use CRC cards

10. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade10 Analysis viewpoints Analysis interaction viewpoint Identifies class-to-class and class-to-actor interactions involved in a specific scenario or path through use case Analysis focused viewpoint Defines a set of associated classes that participate in a use case, a set of use cases or a subset of overall view Analysis overall viewpoint Provides an agreed-upon understanding of problem domain, independent of any implementation details Provides a common representation for the set of entities in the problem domain along with their relationships, attributes and behavior.

11. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade11 Analysis interaction view

12. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade12 Analysis interaction viewpoint

13. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade13 Focused view

14. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade14 Focused viewpoint

15. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade15 Analysis overall view

16. danial moazen,CEIT department amir kabir university,LSS Archtecture course,DR. Abdollahzade16 Analysis overall viewpoint