R1x g02 enterprise architecture i
Download as PPTX, PDF0 likes26 views
1. UML is a standardized modeling language used to visualize, specify, construct, and document a system. 2. UML includes structural elements like classes, interfaces, components as well as behavioral elements like use cases, interactions, state machines. 3. UML diagrams like class, sequence, activity diagrams are used to represent different views of a system based on its design, implementation, processes, and deployment.
R1x g02 enterprise architecture i
- 2. In other words do you think that Organizations need to be Architected ? Why ?
- 3. Imagine if we want to make a cake at home then at a restaurant, then at a factory, will it differ ?
- 5. UML, short for Unified Modeling Language, is a standardized modeling language consisting of an integrated set of diagrams
- 6. The building blocks of UML can be defined as : • Things • Relationships • Diagrams
- 7. Things can be : • Structural • Behavioral • Grouping • Annotational
- 8. Structural Things Structural things define the static part of the model. They represent the physical and conceptual elements. • Class − Class represents a set of objects having similar responsibilities. • Interface − Interface defines a set of operations, which specify the responsibility of a class.
- 9. Collaboration −Collaboration defines an interaction between elements. Use case −Use case represents a set of actions performed by a system for a specific goal. Component −Component describes the physical part of a system. Node − A node can be defined as a physical element that exists at run time.
- 10. Behavioral Things A behavioral thing models of the dynamic parts of UML models. Interaction − Interaction is a group of messages exchanged among elements to accomplish a specific task. State machine − State machine is useful when the state of an object in its life cycle is important. Events are external factors responsible for state change
- 11. Grouping Things Package − Package is the only one grouping thing available for gathering structural and behavioral things. Annotational Things Annotational things can be defined as a mechanism to capture remarks, descriptions, and comments of UML model elements.
- 12. Relationship It shows how the elements are associated with each other and this association describes the functionality of an application. There are four kinds of relationships available. • Dependency : Dependency is a relationship between two things in which change in one element also affects the other. • Association : describes how many objects are taking part in that relationship.
- 13. Generalization Generalization can be defined as a relationship which connects a specialized element with a generalized element. Realization a relationship in which two elements are connected. One element describes some responsibility, which is not implemented and the other one implements them, exists in case of interfaces.
- 14. UML plays an important role in defining different perspectives of a system. These perspectives are : • Design • Implementation • Process • Deployment The center is the Use Case view which connects all these four. A Use Case represents the functionality of the system. Hence, other perspectives are connected with use case.
- 15. Design of a system consists of classes, interfaces, and collaboration. UML provides class diagram, object diagram to support this. Implementation defines the components assembled together to make a complete physical system. UML component diagram is used to support the implementation perspective.
- 16. Process defines the flow of the system. Hence, the same elements as used in Design are also used to support this perspective. Deployment represents the physical nodes of the system that forms the hardware. UML deployment diagram is used to support this perspective.
- 17. UML Diagrams UML diagrams are the ultimate output of the entire discussion. All the elements, relationships are used to make a complete UML diagram and the diagram represents a system. UML includes the following nine diagrams : • Class diagram • Object diagram • Use case diagram • Sequence diagram • Collaboration diagram • Activity diagram • Statechart diagram • Deployment diagram • Component diagram
- 18. 1- Class diagram is a static diagram. used for visualizing, describing, and documenting different aspects of a system also for constructing executable code of the software application, because they are the only UML diagrams, which can be mapped directly with object-oriented languages. C#, C++, Java, PHP, …etc
- 20. 2-Object diagrams are derived from class diagrams so object diagrams are dependent upon class diagrams. Object diagrams also represent the static view of a system but this static view is a snapshot of the system at a particular moment.
- 22. 3-Component diagram is a special kind of diagram in UML, It does not describe the functionality of the system but it describes the components used to make those functionalities. Thus from that point of view, component diagrams are used to visualize the physical components in a system. These components are libraries, packages, files, etc.
- 24. 4-Deployment diagram vs component diagram component diagram and deployment are closely related. • Component diagrams are used to describe the components (libraries, packages, ..etc) • deployment diagrams shows how they are deployed in hardware(computer, server, ...etc).
- 26. 5-Use Case diagram the most important aspect is to capture the dynamic behavior. Dynamic behavior means the behavior of the system when it is running/operating. Only static behavior is not sufficient to model a system rather dynamic behavior is more important than static behavior. Used to gather the requirements, get an outside view, Identify the external and internal factors influencing the system, Show the interaction among the requirements and actor.
- 28. 6-Interaction diagram Describe some type of interactions among the different elements in the model. This interaction is a part of dynamic behavior of the system. This interactive behavior is represented in UML by two diagrams known as Sequence diagram and Collaboration diagram. The basic purpose of both the diagrams are similar. Sequence diagram emphasizes on time sequence of messages. collaboration diagram emphasizes on the structural organization of the objects that send and receive messages.
- 30. 7-State Chart It describes different states of a component in a system. The states are specific to a component/object of a system. Activity diagram is a special kind of a State chart diagram. As State chart diagram defines the states, it is used to model the lifetime of an object. useful to model the reactive systems. Reactive systems can be defined as a system that responds to external or internal events
- 32. 8-Activity diagram The basic purposes of activity diagrams is similar to other four diagrams. It captures the dynamic behavior of the system. Other four diagrams are used to show the message flow from one object to another but activity diagram is used to show message flow from one activity to another. Activity diagram is sometimes considered as the flowchart. Although the diagrams look like a flowchart, they are not. It shows different flows such as parallel, branched, concurrent flow of system.
- 34. There is a prominent difference between DFD and Flowchart. The flowchart depicts flow of control in program modules. DFDs depict flow of data in the system at various levels(incoming data, outgoing data and stored data), DFD does not contain any control or branch elements.
- 37. 1-Auditing tool : it tells you what, when, who changed that 2-Balanced Scorecard : it monitors strategic goals against performance to improve the work and communication 3-Calnedar : it stores the schedule, events, meetings, view and record tasks
- 38. 4-Dashboard diagram : it models the percentage of each one of the requirements and their priorities 5-decision tree diagram : it is comfortable for stakeholders to know the options they can choose from in each case 6-Documentation : create a pdf or docx file contains all the details and diagrams you need
- 39. 7- Gap analysis matrix : A gap analysis is then performed to assess, if there is any gap that prevents from achieving business needs by comparing the identified current state with the desired outcomes. 8-Heat map : A Heat Map is a visual representation of data in a table to highlight the data points of significance. For example, if you have month wise data on sale of products over the last one year, you can project in which months a product has high or low sales. 9-Organizational chart diagram : Help the business analyst to know how to communicate in performing a specific task.
- 40. 10-Traceability window : it gives a view for the elements connection, and can hide all the relationships and show only the relationships of the selected element if needed. 11-Value Chain : It allows the chain to be broken down into its constituent activities allowing the evaluation of costs, resource and value to be determined and potentially improved
- 41. A framework is a taxonomy or structure with the essential elements. A methodology is a process that has input and output.
- 42. 1-The Open Group Architecture Framework (TOGAF): is a set of models and tools for developing a broad range of IT architectures, providing guidelines for making that choice. 2-Gartner EA Framework 3-Federal Enterprise Architecture Framework (FEAF) 4-The Zachman Framework for Enterprise Architectures Custom 5-Microsoft Solutions Framework (MSF) : directly address the most common causes of technology project failure – improving success rates, solution quality, and business impact.
- 43. 1-Agile : is a cyclical process, iteration based. 2-Scrum : defines a project management framework in which development activities of requirements gathering 3-Extreme (XP) : you only do what you need to do to create value for the customer, not caring about financial , marketing or sales 4-Top-Down, Bottom-up : is a sequential design process, often used in project management and software development processes