ISEM530-Week4.pptx

ISEM 530 Entity Relationship Diagram Domain Model Class Diagram  Use Case Diagrams (review) https://vitechcorp.com/resources/GENESYS/onlinehelp/desktop/Views/ Use_Case_Diagram.htm  Problem Domain Problem domain is the system or “area”...

ISEM 530 Entity Relationship Diagram Domain Model Class Diagram  Use Case Diagrams (review) https://vitechcorp.com/resources/GENESYS/onlinehelp/desktop/Views/ Use_Case_Diagram.htm  Problem Domain Problem domain is the system or “area” of a business that is “broken”, or needs developed. “Things” are the items users need and use to accomplish the tasks that need to be documented. Examples: Products, sales, shippers, invoice, etc.  Domain Classes The “things” are modeled as domain classes or entities. Identified by: Brainstorming Techniques Noun Techniques  Brainstorming Group identifies things in all categories: Tangible Roles OU (organizational units) Devices Locations Events  Brainstorming Group identifies things in all categories: Tangible Book Car  Brainstorming Group identifies things in all categories: Tangible Roles Employee Customer Patient  Brainstorming Group identifies things in all categories: Tangible Roles OU (organizational units) Division Department (IT Dept, Nursing Dept, etc.) Section  Brainstorming Group identifies things in all categories: Tangible Roles OU (organizational units) Devices Sensor Timer Printer  Brainstorming Group identifies things in all categories: Tangible Roles OU (organizational units) Devices Locations Events Logon/Logoff Purchase Order placed  Brainstorming Group identifies things in all categories: Tangible Roles OU (organizational units) Devices Locations East/West/North/South Warehouse vs factory Store  Steps to Brainstorm 1. Identify user/use cases 2. Write down with user all things they use/do for each use case 3. Use the categories to probe deeper into roles and relationships 4. Involve both users and stakeholders; individual interviews / group interviews. 5. Merge results (assume group of you are conducting multiple concurrent sessions. 6. Eliminate duplicates and compose a list.  Domain Classes The “things” are modeled as domain classes or entities. Identified by: Brainstorming Techniques Noun Techniques  Noun Technique Identify problem domain things (classes) using a list of all the nouns that are revealed in discussions or documentation. Popular Systematic Long lists result and somethings not important Helpful when users/user groups not available. Still uses categories previous identified.  Steps Noun Technique 1. Go to your use cases and identify all nouns in your system 2. Use data from other systems in the company (procedures, reports, forms, etc.) to add nouns 3. Modify and consolidate list as your build it (is it necessary?) 4. Create your master list of every noun you identified and kept. 5. Review with uses/stakeholders/teams Sample list of Nouns  Build you UML Class Diagrams Each domain class will have Attribute Identifier (key) Combined attributes  Build the UML Class Diagrams Each domain class will have Attribute-describes one piece of information Identifier (key)-uniquely identifies an instance of the class Combined attributes- Two or more attributes combined into one structure to simplify the model. (E.g., address Key Graphic viewInstantiatio n  Associations Associations are natural relationships between the things. Multiplicity: Number of associations between classes. 1-to-1 1-to-many many-to-1 many-to-many  Cardinality Cardinality is number of relationships (associations) in entity relationship diagrams ERD models things as data entities ERD models are not UML but used in MBSE. Cardinality symbols use crow’s feet Symbols The Entity Relationship Diagram 6 Minutes  More ERD (part 2) https://youtu.be/hktyW5Lp0Vo?si=Yu0GiuxvN8J P7a6Y 14 minutes  Domain Model Class Diagram Class – classification of things (objects) Domain Class – classes of objects in problem domain Class Diagram – A UML diagram showing classes and associations. Domain Model Class Diagram – Diagram of classes from the problem domain Summary / Comparison UML Class Diagrams 12 Minutes ERD for Banking Domain Class Diagram Side by Side comparison  Class and Assignment(s)  Class and Assignment(s)