ASTM E2145 - 07(2013) Standard Practice for Information Modeling (Withdrawn 2017).pdf

《ASTM E2145 - 07(2013) Standard Practice for Information Modeling (Withdrawn 2017).pdf》由会员分享，可在线阅读，更多相关《ASTM E2145 - 07(2013) Standard Practice for Information Modeling (Withdrawn 2017).pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、Designation: E2145 07 (Reapproved 2013) An American National StandardStandard Practice forInformation Modeling1This standard is issued under the fixed designation E2145; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the year of l

2、ast revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope*1.1 Information models are increasingly important in theanalysis, design, and sharing a common understanding ininformation

3、 engineering, in business process improvement, inbuilding information systems, in developing informaticsstandards, and in many other uses.21.2 The purpose of this practice is to identify best practicesfor the creation, use, and assessment of various types ofinformation models.1.3 Included in this pr

4、actice are recommended organiza-tional policies and procedures, where modeling is best usedand recommended modeling methods, best practices and evalu-ation criteria.1.4 Excluded from this practice are detailed specificationsof modeling techniques that are specified or described in othersources.2. Re

5、ferenced Documents2.1 ANSI Standards:3ANSI X3.172-1990 Dictionary for Information SystemsIEEE 1320.1-1998 Standard for Functional ModelingLanguageSyntax and Semantics for IDEF0IEEE 1320.2-1998 Standard for Functional ModelingLanguageSyntax and Semantics for IDEF1X (Object97)2.2 ISO Standards:3ISO 86

6、01-88 Data Elements and Interchange FormatsRepresentation of Dates and TimesISO/IEC 1087 Terminology WorkVocabulary-Part 1:Theory and ApplicationISO/IEC 11179 Information TechnologySpecification andStandardization of Data Elements, Parts 1-6ISO/IEC 19501:2005 Information technologyOpen Dis-tributed

7、ProcessingUnified Modeling Language (UML)Version 1.4.2ISO/IEC 2382 Information Processing SystemsVocabulary2.3 Other Documents and Standards:4Unified Modeling Language Specification version 1.5,March 20033. Terminology3.1 The following sections present terms, definitions, andacronyms found in this p

8、ractice and in various modelingactivities. These terms and definitions are referenced or derivedfrom ANSI X3.172 or ISO/IEC 2382 unless otherwise cited.3.2 Definitions:3.2.1 activity, na group of logically related tasks per-formed for a purpose.3.2.2 alternate key attribute, nin a logical data model

9、, anycandidate key of an entity other than the primary key.3.2.3 application model, na representation or descriptionof the application software, programs, or components neededto support a business function.3.2.4 attribute, na characteristic of an object or entity (seeISO/IEC 11179).3.2.5 attribute v

10、alue, na representation of an instance ofan attribute (see ISO/IEC 11179).3.2.6 behavior, nin the object-oriented methodology, be-havior constitutes the observable effects of an operation orevent, including any results generated or obtained; and repre-sented by operations, methods, and state machine

11、s (see UML1.5).3.2.7 business model, na representation of the strategy,situation, environment, objectives, direction, and similar char-acteristics of a business enterprise or business area.3.2.8 business process model, na representation of busi-ness processes, often where these processes are success

12、ivelydecomposed to describe component activities, to identify theevents to which the business shall respond, and to identify theresults produced.1This practice is under the jurisdiction of ASTM Committee E31 on HealthcareInformatics and is the direct responsibility of Subcommittee E31.25 on Healthca

13、reData Management, Security, Confidentiality, and Privacy.Current edition approved March 1, 2013. Published March 2013. Originallyapproved in 2001. Last previous edition approved in 2007 as E2145 07. DOI:10.1520/E2145-07R13.2An information model in the context of this standard is any representation

14、ofprocess, data, etc., used in any aspect of information technology or informationmanagement.3Available from American National Standards Institute (ANSI), 25 W. 43rd St.,4th Floor, New York, NY 10036, http:/www.ansi.org.4Available from Object Management Group. OMG Headquarters, 250 FirstAvenue, Need

15、ham, MA 02494. http:/www.omg.org.*A Summary of Changes section appears at the end of this standardCopyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United StatesNOTICE: This standard has either been superseded and replaced by a new version or withdra

16、wn.Contact ASTM International (www.astm.org) for the latest information13.2.9 column, na physical data model and relational data-base structure that is analogous to the attribute of a logical datamodel.3.2.10 concept, na unit of thought constituted throughabstraction on the basis of characteristics

17、common to a set ofobjects (see ISO/IEC 1087).3.2.11 conceptual model, nan abstract representation ofany type of model used to identify the principal componentsand relationships of the subject of the model, and avoidingunnecessary or confounding detail.3.2.12 context, na designation or description of

18、 the appli-cation environment or discipline in which a name is applied orfrom which it originates (see ISO/IEC 11179).3.2.13 data, na representation of facts, concepts, or in-structions in a formalized manner, suitable for communication,interpretation, or processing by humans or automatic means(see

19、ISO/IEC 11179).3.2.14 data dictionary, na database used for data thatrefers to the use and structure of other data; that is, a databasefor the storage of metadata (see ANSI X3.172-1990).3.2.15 data element, na unit of data for which thedefinition, identification, representation and permissible value

20、sare specified by means of a set of attributes (see ISO/IEC11179).3.2.16 data model, na description of the organization ofdata in a manner that reflects an information structure (seeISO/IEC 11179).3.2.17 data steward, na person or organization delegatedthe responsibility for managing a specific set

21、of data resources,(see ISO/IEC 11179).3.2.18 dependent entity, nin a logical data model, anentity that inherits one or more identifying attributes fromanother entity.3.2.19 domain, nthe set of possible data values of anattribute (see ISO/IEC 2382); also the identification, descrip-tion or scope of a

22、 segment of industry or commerce, or of aprogram, project, or problem.3.2.20 encapsulation, vthe packaging of an objects datawith its corresponding methods with access via a controlledmessaging interface (see UML 1.4).3.2.21 entity, nany concrete or abstract thing of interest,including associations

23、among things (see ISO/IEC 2382).3.2.22 external schema, nan external schema is the rep-resentation of data at the system architecture presentation layeras viewed by the user when interacting or communicating withthe information system.53.2.23 foreign key attribute, nin a logical data model, anattrib

24、ute or combination of attributes of a child or categoryentity whose values match those in a primary key of a relatedor generic entity instance.3.2.24 function, nan activity, process or transformationidentified by a verb that describes that which would beaccomplished.3.2.25 independent entity, nin a

25、logical data model, anentity that does not inherit identifying attributes from anotherentity.3.2.26 inheritance, vthe transmission of characteristicsfrom a parent process, entity, or object to its children (see UML1.4).3.2.27 internal schema, na schema of the ANSI ThreeSchema architecture in which v

26、iews of the information arerepresentations of data structure at the system architecture datalayer.3.2.28 key attribute, nin a logical data model, an attributeused to identify an instance of an entity.3.2.29 key inheritance, vthe transmission of a key attri-bute from a parent or independent entity to

27、 a child or dependententity.3.2.30 lexical, npertaining to words or the vocabulary of alanguage as distinguished from its grammar and construction(see ISO/IEC 11179).3.2.31 location model, na representation or description ofthe components and interrelationships of a real or virtuallocation.3.2.32 lo

28、gical model, nan expansion of a conceptualmodel, or a derivation from a physical model, that provides alevel of detail sufficient to design or effect a business solution.3.2.33 metadata, ndata that describes other data (seeISO/IEC 11179).3.2.34 model, na representation in whatever form of a realor e

29、nvisioned object, action, or process.3.2.35 modeling, vthe process of creating, revising, docu-menting and presenting a model.3.2.36 model view, na collection of models pertaining to aparticular domain and from the perspective of a particularindividuals role or viewpoint.3.2.37 non-key attribute, ni

30、n a logical data model, anattribute that is not the primary or part of a composite primarykey of an entity.3.2.38 object, nany part of a conceivable or perceivableworld (see ISO 1087).3.2.39 object class, na set of objects, ideas, abstractions,or things in the real world that can be identified with

31、explicitboundaries and meaning and whose properties and behaviorfollow the same rules (see ISO/IEC 11179).3.2.40 object-oriented methodology, nany of the formalmodeling methods or techniques that employ objects to de-scribe data and the methods or processes acting on those dataas a single unit for a

32、nalysis, design, or development (see UML1.5, ISO/IEC 11179).3.2.41 organizational model, na representation or descrip-tion of the components and interrelationships of an organiza-tion or organizational component.5ANSI Standards Planning and Requirements Committeea layered model ofdatabase architectu

33、re comprising a physical schema, a conceptual schema, and userviews.E2145 07 (2013)23.2.42 physical model, na derivation from a logicalmodel, or a physical implementation, providing a highlydetailed definition of the solution needed to carry out theactivities in business area.3.2.43 primary key attr

34、ibute, nin a logical data model, thecandidate key selected as the unique identifier of an entity.3.2.44 property, na peculiarity common to all members ofan object class (see ISO/IEC 11179).3.2.45 relational data methodology, nany of several mod-eling and information management methods and techniques

35、that employ structured relationships among entities or tables.3.2.46 row, na physical data model and relational databasestructure that contains a single instance of data in a table.3.2.47 structured analysis and design, n any formalizedmethodology for the analysis, design, development or lifecyclema

36、nagement of information systems where processes and dataare initially treated individually and subsequently integrated ina system architecture.3.2.48 subject area, na subject area is a portion of anentire data model which is created to facilitate understanding ofa specific functional area or compone

37、nt task.3.2.49 table, na physical data model and relational data-base structure that is analogous to the entity of a data model.3.2.50 technology model, na representation or descriptionof the hardware, system software, and network componentsneeded to support the business area.3.2.51 view, na collect

38、ion SQL queries stored in a rela-tional database under assigned names and represented as atemporary or virtual table that does not permanently store thedata it presents.3.3 Acronyms:3.3.1 ANSIAmerican National Standards Institute3.3.2 ASTMAmerican Society for Testing and Materials3.3.3 CORBACommon O

39、bject Request Broker Architec-ture3.3.4 CRCClass, Responsibility and Collaboration Ap-proach3.3.5 DFDData Flow Diagram3.3.6 ICOMInput, Control, Output and Mechanisms asused in IDEF activity modeling3.3.7 IDEFIntegrated Definition Language3.3.8 IDEF0The IDEF activity modeling language3.3.9 IDEF1XThe

40、IDEF data modeling language3.3.10 IDOIntegrated Delivery Organization3.3.11 IEInformation Engineering diagramming method-ologies3.3.12 IECInternational Electrotechnical Commission3.3.13 ISAInformation Systems Architecture3.3.14 ISOInternational Organization for Standardization3.3.15 NISTNational Ins

41、titute of Standards and Technol-ogy3.3.16 OMGObject Management Group3.3.17 RDBRelational Database3.3.18 RDBMSRelational Database Management System3.3.19 SADTStructured Analysis and Design Technique3.3.20 SMLStandardized Modeling Language3.3.21 SQLStructured Query Language3.3.22 SSADMStructured Syste

42、ms Analysis and DesignMethodology3.3.23 UMLUnified Modeling Language4. Summary of Practice4.1 This practice describes policies and procedures, bestpractices for the creation, use, and assessment of informationmodels.4.2 The foundation for these information modeling bestpractices is derived from Donn

43、abedians structure, process andoutcome quality constructs (1).64.2.1 StructureStructure constructs identify or describethe organization component where modeling activities occur,the composition of the modeling method or tool, its languageand syntax, and the resources allocated to perform modelingpro

44、cesses, for example human resources, technology, materiel,etc.4.2.2 ProcessProcess constructs identify or describe theappropriate use of modeling, the effective use of modelingmethods, and the correct employment of the modeling tech-nique.4.2.3 OutcomeA quality information model that providesa meani

45、ngful and usable representation of past, present, orfuture reality, and can be assessed by five dimensions (2) ofmodel quality:4.2.3.1 Conceptual CorrectnessThe model accurately re-flects functional or business concepts where all models arerepresentations of real or envisioned objects or concepts. T

46、hemodel shall accurately describe the intended structures orprocesses or both.4.2.3.2 Conceptual CompletenessThe model contains suf-ficient objects to describe the full scope of the functional orbusiness domain under consideration. The model describes thefull scope or an element of the structures or

47、 processes of aconcept or both.4.2.3.3 Syntactic CorrectnessThe objects in the model donot violate syntactic rules of the modeling language. Eachmodeling method has a predefined language typically consist-ing of visual structures and symbols where these structures andsymbols are assembled and interp

48、reted according to a clearlydefined and unambiguous set of rules. These rules shall bewidely recognized in the industry and preferably be standard-ized (3). The modeling methodology and processes shalladhere to these rules. The model shall effectively communicateits representations and descriptions

49、to anyone who understandsthe modeling method and syntax.4.2.3.4 Syntactic CompletenessAll essential functional orbusiness concepts are captured at appropriate points in the6The boldface numbers in parentheses refer to the list of references at the end ofthis standard.E2145 07 (2013)3modeling process and represented in the model products. Amodeling method may use different objects, symbols or struc-tures at different times in the modeling process. The modelshall display the a