Creating A Domain Model Class Diagram
Assignment 3: Creating a Domain Model Class Diagram
Eustace Langley
Strayer University
Dr. Richard Brown
August 19, 2014
Creating a Domain Model Class Diagram Introduction
Many current approaches to system development use the term class rather than data entry and use the concepts and notation based on UML to model things in the problem domain. On my day to day activities, I have the privilege to use more than one particular operating system to complete a number of tasks. A UML domain model will relate objects in the system domain to each other and will also define concepts and terms. Whilst Objects in the domain model can be Physical and Abstract concept, it is imperative to recognize nouns and noun phrases when developing a domain model. Another key point to take into consideration is that, concepts, which may not ultimately become objects, may be listed for completeness and for further discussion.
In order to answer the research questions, this monogram will provide a narrative description of A Domain Model Class Diagram that includes: An overview of the diagram and an analysis of the different classes in the diagram. Further, this monogram illustrates a domain model class diagram Using Microsoft Visio I will create (University of Strayer Materials, July, 2014).
An overview of the diagram
Storytelling is how cultures survive and progress; it is the simplest and most effective way to pass knowledge from one person to another. It is also, the best way to communicate what a system should do, and to get everybody working on the system to focus on the same goal (Jacobson, Spence, & Bittner et al., 2011). Using Visio when designing class diagrams has its advanatages, a developer can easily transform the design into code: C#, C++, or Visual Basic .NET. Once created, the code can be placed into independent files or inside a Visual Studio .NET project. In addition to the code itself, class diagrams can generate documentation to
Eustace Langley
Strayer University
Dr. Richard Brown
August 19, 2014
Creating a Domain Model Class Diagram Introduction
Many current approaches to system development use the term class rather than data entry and use the concepts and notation based on UML to model things in the problem domain. On my day to day activities, I have the privilege to use more than one particular operating system to complete a number of tasks. A UML domain model will relate objects in the system domain to each other and will also define concepts and terms. Whilst Objects in the domain model can be Physical and Abstract concept, it is imperative to recognize nouns and noun phrases when developing a domain model. Another key point to take into consideration is that, concepts, which may not ultimately become objects, may be listed for completeness and for further discussion.
In order to answer the research questions, this monogram will provide a narrative description of A Domain Model Class Diagram that includes: An overview of the diagram and an analysis of the different classes in the diagram. Further, this monogram illustrates a domain model class diagram Using Microsoft Visio I will create (University of Strayer Materials, July, 2014).
An overview of the diagram
Storytelling is how cultures survive and progress; it is the simplest and most effective way to pass knowledge from one person to another. It is also, the best way to communicate what a system should do, and to get everybody working on the system to focus on the same goal (Jacobson, Spence, & Bittner et al., 2011). Using Visio when designing class diagrams has its advanatages, a developer can easily transform the design into code: C#, C++, or Visual Basic .NET. Once created, the code can be placed into independent files or inside a Visual Studio .NET project. In addition to the code itself, class diagrams can generate documentation to
References: Satzinger, J.W., Jackson, R., & Burd, S.D (2012). System analysis and design in changing world (6th Ed.). Cengage Learning/Course Technology Jacobson, I., Spence, I., & Bittner, K. (2011). USE-CASE 2.0, The Guide to Succeeding with Use Cases. file:///C:/Users/Eustace/Downloads/Use-Case+2_0_Jan11.pdf Scott W. Ambler (2005). The Elements of UML(TM) 2.0 Style Bumstead, D. (2009). The essentials: Sandwiches and sleep. Journals of Famous Loafers, 5, 565-582. doi:12.2847/CEDG.39.2.51-71