Classification Design

Slides:



Advertisements
Similar presentations
Faceted Classification Complex subjects from simpler components.
Advertisements

Tempo Words Words that indicate how fast to play..
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Module 10b: Wrapup IMT530: Organization of Information Resources Winter, 2007 Michael Crandall.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Subject languages part 2: Structure. Structure of subject languages Alphabetical representation and classified representation. Synthetic structure and.
Subject languages Scope and structure Semantics and syntax.
Understanding Task Orientation Guidelines for a Successful Manual & Help System.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Why classification matters The foundations of bibliographic classification.
1 MeSH & Principles of Classification April 13, 2005.
Faceted Classification
Metadata standards Guidelines, data structures, and file formats to facilitate reliability and quality of description.
Ontology Development in the Sciences Some Fundamental Considerations Ontolytics LLC Topics:  Possible uses of ontologies  Ontologies vs. terminologies.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models. System modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
Of 39 lecture 2: ontology - basics. of 39 ontology a branch of metaphysics relating to the nature and relations of being a particular theory about the.
Classroom Assessments Checklists, Rating Scales, and Rubrics
INF 384 C, Spring 2009 Ontologies Knowledge representation to support computer reasoning.
Definition of a taxonomy “System for naming and organizing things into groups that share similar characteristics” Taxonomy Architectures Applications.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Semantic web course – Computer Engineering Department – Sharif Univ. of Technology – Fall Knowledge Representation Semantic Web - Fall 2005 Computer.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Subject languages, part 1 Scope. Goals of subject languages Ranganathan: To provide a helpful sequence of documents, so that: Readers discover topics.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Advanced Gene Selection Algorithms Designed for Microarray Datasets Limitation of current feature selection methods: –Ignores gene/gene interaction: single.
INF 384 C, Spring 2009 Faceted Classification Complex subjects from simpler components.
BY: MIA SASFAI THE TAXONOMY OF EDUCATIONAL OBJECTIVES Benjamin Bloom.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Faceted classification
Classroom Assessments Checklists, Rating Scales, and Rubrics
Structuring Classifications
Object-oriented and Structured System Models
Chapter 11: Modes of Rhetoric
ece 627 intelligent web: ontology and beyond
Ontology From Wikipedia, the free encyclopedia
Classroom Assessments Checklists, Rating Scales, and Rubrics
Abstract descriptions of systems whose requirements are being analysed
Indexing, or assigning subject terms to documents
Metadata standards Guidelines, data structures, and file formats to facilitate reliability and quality of description INF 384 C, Spring 2009.
Ontology Reuse In MBSE Henson Graves Abstract January 2011
System models October 5, 2005.
Attributes and Values Describing Entities.
Patterns of Organization
Critical Analysis CHAPTER 7.
An Introduction to Software Engineering
Subject languages, part 1
KNOWLEDGE REPRESENTATION
Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany
Modes of Discourse May serve as the primary mode of composition for an essay, or a smaller component of a larger essay.
Cognitive Processes PSY 334
4. Principles of Psychology Teaching
Attributes and Values Describing Entities.
Information Analysis, Organization, and Presentation
Informatics 122 Software Design II
Building a Bridge from High School Writing to First-Year Writing to Writing in the Major Noreen Lape Associate Provost of academic Affairs/ Director.
Presentation transcript:

Classification Design Creating subject languages INF 384 C, Spring 2009

Outline What is being represented? Defining the domain of representation. What overall structure best fits the domain? Determining the general form of the subject language. How should concepts be arranged within the structure? Ordering concepts at each level of the classification. INF 384 C, Spring 2009

Defining a subject domain A subject language represents a domain of knowledge as a system of related concepts. Last week, for example, you decided that “lawn maintenance” and “sustainable urban gardening in Austin” were represented by a particular group of concepts. But how do you determine what “lawn maintenance” is? INF 384 C, Spring 2009

Defining domains as discourse communities Hjorland and Albrechtsen argue that information systems should be based on discourse communities of academic disciplines. Psychology = what psychology researchers say, because this is the closest we can get to the “reality” of psychology. INF 384 C, Spring 2009

Representing competing ideas But a behaviorist psychologist and a psychologist who adopts a psychoanalytic perspective may have widely differing views, even on basic concepts. Hjorland and Albrechtsen contend that a domain analysis should uncover these schools of thought that exist within a discipline, in order to represent them within an information system. INF 384 C, Spring 2009

Understanding the significance of domain analysis The domain analytic approach acknowledges problems with the semantic validity of information systems and asserts the need for systematic and rigorous justification for knowledge representations. The domain analytic approach clarifies that a subject may have many interpretations and provides a means for validating some of those interpretations. INF 384 C, Spring 2009

Understanding the limitations of domain analysis The domain analytic approach ignores concerns related to an information system’s audience and purpose. The domain analytic approach doesn’t explain how a designer of subject languages should decide between competing approaches to the subject. INF 384 C, Spring 2009

Performing a domain analysis Find documents that help you determine ontology (important things), epistemology (important problems, theories, methods and practices), and social structures in the selected domain. For example: FAQs, beginners’ guides, and textbooks. Bibliographies. Professional organizations. Online user forums. Actual people! INF 384 C, Spring 2009

Using a domain analysis to make decisions A domain analysis can help you determine: Which sources of information are more important or representative than others. Which concepts to include in a subject language. How those concepts might be defined, labeled, and related to other concepts. INF 384 C, Spring 2009

Understanding your responsibility as a classificationist A domain analysis won’t actually make decisions for you; it will just provide information for you to use, in concert with your audience description, classification purpose, and your own goals and editorial judgment. Every classification is a type of argument for a particular interpretation of a subject. You need to own that! INF 384 C, Spring 2009

Types of classificatory structures Kwasnik identifies three types of structures: Hierarchies. Trees. Facets. INF 384 C, Spring 2009

Hierarchies A hierarchy groups concepts from most general to most specific: each branch inherits characteristics from its parents. Dogs exhibit all of the characteristics of mammals (and thus all characteritics of primates, and of vertebrates) plus additional characteristics. INF 384 C, Spring 2009

Trees According to Kwasnik, a tree is a looser form that shows a consistent principle of organization, but does not have the strict rules of inheritance and so forth that hierarchies have. Example: Grandparents Parents Children INF 384 C, Spring 2009

Facets Facets are fundamental, ideally orthogonal, categories of concepts. Concepts from different facets can be combined to form more complex concepts without needing to enumerate all possible combinations in advance. Example: By keeping processes and materials separate, we can describe roasting, braising, or frying any kind of food item, without enumerating each type of food for every process. INF 384 C, Spring 2009

Example facets From Aitchison, possible facets: Abstract entities. Attributes. Materials (constituent substances). Naturally occurring entities. Living entities/organisms. Artifacts (man-made). Parts/components. Agents/actors. Equipment/apparatus. Patients (recipients of actions). Products (of actions). Processes (intransitive actions). Operations (transitive actions). Place. Time. INF 384 C, Spring 2009

Arrangement within hierarchies Two forms: Showing multiple principles of division that relate children to their parent node (subfacets). Ordering via appropriate principles at each array (Ranganathan’s canons and such). INF 384 C, Spring 2009

Showing principles of division (subfacets) shoes high heels hiking boots mary-janes pumps running shoes sandals slingbacks stilettos wedges winter boots shoes (by season) winter spring (by function) hiking running (by style) boots pumps sandals (by feature) slingbacks mary-janes (by heel type) stilettos wedges (by heel height) high heels INF 384 C, Spring 2009

Ordering concepts at each level An “array” is a group of siblings (descriptors at the same level of hierarchy). These need to be ordered, even if you don’t need subfacets! Possible orders: General to specific. Chronological. Close to far away. Order of a process. INF 384 C, Spring 2009

Example: music tempos Allegro Andante Largo Moderato Presto Vivace (alphabetical) Largo Andante Moderato Allegro Vivace Presto (slowest to fastest) INF 384 C, Spring 2009

Your mission Continue doing research to define the subject. Continue compiling a list of potential concepts to include in your classification. For each potential concept, why should it be there? What is your basis for making this decision? Start thinking about how your concepts might be structured. INF 384 C, Spring 2009