Towards a Theory of Genericity Based on Government and Binding

Transcription

1 Towards a Theory of Based on Government and Binding ER 2006 Tucson Alexander Bienemann, Klaus-Dieter Schewe, Bernhard Thalheim Ariva.de Kiel & Massey University & Kiel University

2 Our main contributions of database and information systems based on stepwise refinement and intensions of already specified content Background of genericity: linguistics (government and binding) linguistics and Web IS (word fields, media types) programming languages (higher-order functions) during database and information systems development based on abstraction and refinement based explicit interpretation and implicit meaning of concepts to be used derived from our background and commonsense knowledge Theoretical basis through generic functions, generic composers Application in practice based on specification templates

3 Government and binding The best part of Chomsky s heritage General way of utterance statement: extract, transform, load Lexicon of basic concepts stylistic and phonological rules Phonological form D-structure α rules S-structure β rules 3 Logical form General way of utterance statement in foreign language: extract, transform, rephrase, load General way of forming ideas: reason, rephrase, conceptualize Layering of functionality, content: transport, structure, organise, communicate General way of collaborating: coordinate, communicate, cooperate

4 in Daily Life Submit a paper, a document,... expecting a confirmation, storage of submission Contribute content to something supplying to community and sharing it with certain obligations and responsibilities quality obligations for its correctness Inform somebody about something information must be based in information demand understandable, perceivable, integratable Join an association, community,... role of a member of the community commitment to coordination style and pattern certain behaviour in the future and collaboration Learn easy to grasp and simple to represent content gain content and knowledge, understand, and discover memorizing, able to perform some task, know this ability role of a learner or student supported by other actors who teach and instruct

5 in Daily Life Submit a paper, a document,... expecting a confirmation, storage of submission Contribute content to something supplying to community and sharing it with certain obligations and responsibilities quality obligations for its correctness Inform somebody about something information must be based in information demand understandable, perceivable, integratable Join an association, community,... role of a member of the community commitment to coordination style and pattern certain behaviour in the future and collaboration Learn easy to grasp and simple to represent content gain content and knowledge, understand, and discover memorizing, able to perform some task, know this ability role of a learner or student supported by other actors who teach and instruct

6 in Daily Life Submit a paper, a document,... additional actions, permanency Contribute content to something people context portfolio requirements Inform somebody about something intentions profile Join an association, community,... storyboard contracting in advance behaving in future Learn easy to grasp and simple to represent content profile and content abilities and content portfolio and functionality collaboration

7 Application of our theory to web information systems development 1. Extracting Requirements Content chunks representing content, concepts and topics Function chunks representing all functionality requirements board of the Media type requirements (data, content, functions, containers, performance, operational, maintainability, support, security ) Representation requirements (look and feel, grids and pattern) board requirements (usability, humanity, privacy, cultural, political, legal) 2. Conceptual modelling, specification 3. Logical and physical development

8 Surprising and Novel Observation: Database Specification Is Essentially Based on Generic specification of the database application (S, ) for structuring and functionality with S = (S, Σ S ) (structure and static integrity constraints) α-rules for extending (S, ) to (S = (S, Σ S ), F = (Alg(F), Σ F )) for the algebra generated from the basic functions F (retrieval, modification, and service functions) and dynamic integrity constraints Σ F or simply the ground schema (S = (S, Σ S ), F = (F, Σ F )) Mapping (S = (S, Σ S ), F = (F, Σ F )) to (S ABC = (S ABC, Σ SABC ), F ABC = (F ABC, Σ FABC )) is based on β-rules for ABC {SQL92, SQL : 1999, SQL : 2003, XML,...}

9 in Detail: Join a Society The joining process dimension Join a society Apply to join the society Apply Application Supporters, witnesses, advisors, attractors Trial period Members profile Admitted member Member with rights and obligations General facets of joining: Society-oriented selection of new members Admission process based on rules of societies in general Assignment process for temporal rights, obligations, roles

10 in Detail: Join a Society The actor and activity dimension Join a society... Join and contribute Join, admit to be a member Roles Rights Obligations Restrictions Communicate General facets of stories and scenarios of people being a member Behaviour like a member with rights, roles, obligations, permissions, restrictions Contribution of members in the society received, communicated, elaborated Documentation of the work Privacy of the work

11 in Detail: Join a Society The work dimension Join a society... Cooperate... Society task Portfolio Workflow Documents Coordinate Time Contract Restrictions Working, contributing, exchanging in a society Goals and intentions of the society are supported Tasks and portfolio of the society are driving behaviour Work products of the work in the society Coordination among the members of the society

12 in Detail: Join a Society The context dimension Join a society Society... Society task Portfolio Workflow Documents Document, behaviour rules Rules of the society Contract as xy citizen Restrictions and priorities based on profile of member based on functions of member Each society expects a certain behaviour Specific tasks, society profiles, Specific society atmosphere based on written/unwritten rules Specific styles and pattern of interaction and collaboration

13 What is The Essence? Abstraction Component abstraction Context abstraction Detail abstraction Component refinement Smith/Smith Refinement Context activation Detail development, Generalisation specialisation hierarchies Grouping, Class development Aggregation and decomposition

14 What is The Essence? Abstraction Comp. abstr. Context abstraction Detail abstr. Viewing, scoping, localisation context Temporal context abstraction context abstraction Usage context abstraction System context abstraction Commonsense context of concepts behind words used Work product context of documents consumed, produced, revised, displayed depending on visitors/members profile Generic rule context or generic story context History context resulting in and requiring adaptation Technical environment context depending on service, providers, users

15 What Do We Need, What To Develop? with a specification frame based on α- and β rules based on α- and β rules composition functions for generic functions consistent with α- and β rules enhanced by coiteration, higher-order polymorphism and structural recursion Generic documents or media types Generic bindings based on co-development of refinement through α- and β rules and Exploration for DB and IS Application in practice

16 workflow suite: set of workflows bundled together by an association schema maintained by consistency requirements Specification frame Description: general CSP expression based on generic functions Context explicitly specified Applicability: circumstances Interactions: requires media types for its support Consequences: non-applicability of other workflows or restrictions Strategies: mapping based on a number of α-rules, β-rules to map to workflow instantiations Related generic workflows

17 Functionalisation (S, F, Σ, s 0 ) Generic Functions specification of structuring S = (S, V ) database schema S = (T S, Σ S ) T S : set of types according to the type system Σ S : set of static integrity constraints, set of views V upon S function application F, set of dynamic integrity constraints Σ on S, distinguished initial state s 0

18 Functionalization Space with Three Dimensions Refinement (S 1, F 1, Σ 1, s 1 0)... (S 2, F 2, Σ 2, s 2 0) Context embedding Instantiation

19 governor G Developing Generic Governors function G : C GW WS generic workflow GW context C workflow suite WS Practical purposes: term rewriting rules for the governors Define generic workflow Apply α- and β rules Restrict by governors 3

20 Examples of Basic Generic Workflows Data Accessor Description: encapsulates physical access details into logical access expose logical operations, encapsulate physical operations; expose logical resources, encapsulate physical resources; normalize and format data; encapsulate platform details; encapsulate optimization details Context: advanced ETL logic, MVC grid Applicability: hide physical access complixity/optimization/semantics Structure: layered proxy frame (AccessPath.QueryExpression, TransformExpression, ResultForm) ConcreteDataAccessor(DataAccessor(operationSet(Params)), PhysicalDBDriver) Interactions: sequence diagram with objects (AnApplicat, AConcreteDBAcc, APhysDBDriver) ControlBlock(StartOpA; StartPhysOpA; ReturnPhysResA; ReturnOpA) Consequences: (-) limits application control of data access; (+) independence, optimization, swappable Strategies: α-rule (GenFct MVC grid), β-rule(mvc grid Program) define versatile logical operations; incorporate enhancements and optimization points; guard against inefficient application usage; guard for errors and exceptions Related Pattern: JDBC, ODBC access pattern; adapter pattern, actract factory pattern

21 Examples of Basic Generic Workflows Active Media Type Object Description: encapsulate data model and access details within media types container object relieve application code of any db interaction Context: schema matching; initialize, refresh, save, list; ETL Applicability: mask legacy, hide complexity, grouping into combined objects, containers supporting sessions Structure: application(activecontainerobject (Structure, QueryAnswerForm(MediaTypeObject))) specific logging facilities Interactions: MSC between applications, containers and media objects depending on policies for data modification and bindings through protocols and workflows Consequences: (-) spreads access across, limits application control (+) clean application code, application code independence, grouping data access Strategies: α-rules: db schemata and procedures, domain logic, separate collections from objects β-rules: connection management, state maintenance Related Pattern: XML exchange documents, EJB, bean-managed persistence

22 Examples of Basic Generic Workflows Media Type Collaborator Description: encapsulation of media type collaboration Context: schema matching; determine appropriate media types, issue the queries, parse the query results, deliver the results Applicability: versatility of schemata mappings Structure: application(ownmediatypes, MediaObjectSuiteManager) MediaObjectSuite(MediaObjectSuiteManager, Profiler, CollaboratingMediaObjectSuite) Interactions: application.read(mediaobjectsuite); mediaobjectsuite.find(profiler); mediaobjectsuite.collaborate(collaboratingmediaobjectsuite); mediaobjectsuite.create(collaboratingobjects) Consequences: (-) limits application control of access (+) clean application code, database independence Strategies: α-rules: profiling, suite workspace creation β-rules: identity matching, aggregation detection, inheritance orchestration Related Pattern: Java data object (JDO), container-managed persistence

23 Examples of Basic Generic Workflows Service Description: stack orthogonal features that address data access issues with increasing level of abstraction Context: abstraction in terms of less abstract objects; domain object mapping; data conversion; data operation mapping; resource management; distribution; caching; authorization; logging Applicability: separatability of features, incremental levels, build gradually Structure: application(..., ImportServiceMediaType); service(exportmediatypes, ImportServiceMediaTypes) with competences accessservice(exportmediatypes) functional expression on services with access service as basic service Interactions: delegation to inner services with semaphores Consequences: (-) layer interaction and initialization complexity (+) functional decomposition, feature modularization, feature detail encapsulation, layer pluggability Strategies: α-rules: top-down understanding, sequentialization/algorithmication β-rules: stub layering, isolation of layer initializations Related Pattern: architecture pattern, abstraction pattern

24 Applicable? Internet and cable net information-intensive services Cottbusnet and 35 other website projects Codesign of structuring, functionality, and interactivity Content-on-interest + Content-on-profile-and-portfolio + Delivery-on-context!!! + Adaptation-on-context!!! Intelligent personalized internet in set-top-box-based TV Codesign of structuring, functionality, distribution and interactivity TV/Radio-on-interest + Cinema-on-demand + Internet-onprofile + Internal-communication-among-users

25 Our achievements and contribution of database and information systems based on stepwise refinement and intensions of already specified content Background of genericity: linguistics (government and binding) linguistics and Web IS (word fields, media types) programming languages (higher-order functions) during database and information systems development based on abstraction and refinement based explicit interpretation and implicit meaning of concepts to be used derived from our background and commonsense knowledge Theoretical basis through generic functions, generic composers Application in practice based on specification templates