3. Introduction to Modeling 1. Plan for Today's Class 2 ... - Courses

More documents

Recommendations

Info

3. Introduction to Modeling Page 10 of 12 XML Spy tries to do. • But schemas developed without a stage of conceptual design are rarely very useful because they are too closely tied to the particular instances used, which may not be representative. • Sometimes schemas went through a stage of conceptual design but once the schemas are implemented the conceptual information isn't available to schema users; expectation is that the schemas are sufficient 20. Implementing a Conceptual Model as a Physical One • A model is purely theoretical until it is encoded in a technology that lets it operate in the real world again. • This is a two-stage process: encoding conceptual models as physical ones, and then applying formatting or style transformations to create instances with desired properties • When instances implemented in different technologies are generated or re-generated from models, they can more readily interoperate because of their common conceptual components 21. Tools • Tools can be as simple and informal (pencil and paper) or complex and formal (CAD and CASE software) • There is no single tool suitable for all users and purposes • Tools can be general purpose, not tied to specific methodologies (word processors, spreadsheet, presentation packages) • General purpose tools can use templates to support specific notations or processes • Tools can be dedicated to particular notations or processes 22. Artifacts • Artifacts are the things that a methodology produces that communicate the results of the modeling activity • Models are often communicated as prose documents with some mixture of graphics and text • Models can be most useful when they are communicated using artifacts that are "notation-neutral" or that are capable of being transformed into other forms or syntaxes • A focus on artifacts is a key principle of Document Engineering 23. The Modeling Artifacts of Document Engineering file://C:\Documents%20and%20Settings\glushko\My%20Documents\SIMS%20Courses\le... 1/26/2005
3. Introduction to Modeling Page 11 of 12 • Analyzing the Context –UML use case diagrams • Analyzing/Designing Business Processes – Worksheets, UML Activity and Sequence Diagrams • Applying Patterns to Business Processes – Document Checklist • Analyzing Documents – Document Inventory • Analyzing Document Components – Consolidated Table of Content Components • Assembling Document Components – UML Class Diagram • Assembling Document Models – UML Class Diagram or Spreadsheet • Implementing Models – XML Schemas 24. UML as a Modeling Notation • The Unified Modeling Language (UML) is a graphical language for visualizing, specifying, constructing and documenting the structure and behavior of (software) systems • UML is the synthesis of a variety of object-oriented modeling concepts and notations and is now endorsed by the Object Management Group. It is a language in that it can be used to define different types of models • UML has a number of standard notations or diagram types that all are based on the same underlying meta-model (and it can also be used to define additional notations) • Put another way... one UML description of a model can be used to produce numerous artifacts that use different notations, each of which highlights a different aspect of the model • We will use just enough UML in this course to help us analyze and design models for documents and business processes 25. XML as a Modeling Notation • XML has rapidly emerged as a preferred format for creating models that are vendor and notationneutral • XML's key benefits from this perspective are the ease with which XML instances can be transformed and the use of models expressed as XML schemas to guide code generation by serving as templates for program objects • Using the concepts introduced in this lecture, XML is a meta-modeling language or maybe even a meta-meta-modeling language; each XML schema language is a meta-language for creating models that are expressed as DTDs or as instances of other schema language types • But as we've seen in lectures and assignments XML schema languages impose constraints on the models they are used to create and they may be too low-level in many respects file://C:\Documents%20and%20Settings\glushko\My%20Documents\SIMS%20Courses\le... 1/26/2005
Page 1 and 2: 3. Introduction to Modeling Page 1
Page 9: 3. Introduction to Modeling Page 9

3. Introduction to Modeling 1. Plan for Today's Class 2 ... - Courses

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?