220,688 research outputs found

    Specification of cell fate in the sea urchin embryo: summary and some proposed mechanisms

    Get PDF
    An early set of blastomere specifications occurs during cleavage in the sea urchin embryo, the result of both conditional and autonomous processes, as proposed in the model for this embryo set forth in 1989. Recant experimental results have greatly illuminated the mechanisms of specification in some early embryonic territories, though others remain obscure. We review the progressive process of specification within given lineage elements, and with reference to the early axial organization of the embryo. Evidence for the conditional specification of the veg(2) lineage subelement of the endoderm and other potential interblastomere signaling interactions in the cleavage-stage embryo are summarized. Definitive boundaries between mesoderm and endoderm territories of complex. the vegetal plate, and between endoderm and overlying ectoderm, are not established until later in development. These processes have been clarified by numerous observations on spatial expression of various genes, and by elegant lineage labeling studies. The early specification events depend on regional mobilization of regulatory factors resulting at once in the zygotic expression of genes encoding transcription factors, as well as downstream genes encoding proteins characteristic of the cell types that will much later arise from the progeny of the specified blastomeres. This embryo displays a maximal form of indirect development. The gene regulatory network underlying the embryonic development reflects the relative simplicity of the completed larva and of the processes required for its formation. The requirements for postembryonic adult body plan formation in the larval rudiment include engagement of a new level of genetic regulatory apparatus, exemplified by the Hox gene complex

    Temporal validation of extended workflow processes by means Petri Nets with Clocks

    Get PDF
    At present the business processes have temporary requirements within their specifications. Logistics, e-commerce, are examples of these, among others. The time involved in business processes is important regarding the interaction of the actors. The sound of the technology involved in building these processes plays a key role in assessing the risk of implementation. The possibility of having technologies with elements for such specifications is vital to accurately model of reality. Workflow (Wf) is the technology of wide acceptance and recognition that can improve business processes. The Wf architecture has the Interface 1, which lets you define process through its processes definition language (PDL), but has no elements to express temporary restrictions of this kind. Our works present a theoretical framework in which there is an extension of the grammar of the WPDL to allow the specification of time variable. It also establishes a correspondence between the PD and its underlying Petri Net with Clocks (PNwC) preserving its semantic. The correspondence is specified by means of the RAISE Specification Language (RSL). The correlation between these formalisms lets you define business process with temporary restrictions validated.Workshop de Ingeniería de Software y Bases de Datos (WISBD)Red de Universidades con Carreras en Informática (RedUNCI

    Temporal validation of extended workflow processes by means Petri Nets with Clocks

    Get PDF
    At present the business processes have temporary requirements within their specifications. Logistics, e-commerce, are examples of these, among others. The time involved in business processes is important regarding the interaction of the actors. The sound of the technology involved in building these processes plays a key role in assessing the risk of implementation. The possibility of having technologies with elements for such specifications is vital to accurately model of reality. Workflow (Wf) is the technology of wide acceptance and recognition that can improve business processes. The Wf architecture has the Interface 1, which lets you define process through its processes definition language (PDL), but has no elements to express temporary restrictions of this kind. Our works present a theoretical framework in which there is an extension of the grammar of the WPDL to allow the specification of time variable. It also establishes a correspondence between the PD and its underlying Petri Net with Clocks (PNwC) preserving its semantic. The correspondence is specified by means of the RAISE Specification Language (RSL). The correlation between these formalisms lets you define business process with temporary restrictions validated.Workshop de Ingeniería de Software y Bases de Datos (WISBD)Red de Universidades con Carreras en Informática (RedUNCI

    OntoWeaver S: supporting the design of knowledge portals

    Get PDF
    This paper presents OntoWeaver-S, an ontology-based infrastructure for building knowledge portals. In particular, OntoWeaver-S is integrated with a comprehensive web service platform, IRS-II, for the publication, discovery, and execution of web services. In this way, OntoWeaver-S supports the access and provision of remote web services for knowledge portals. Moreover, it provides a set of comprehensive site ontologies to model and represent knowledge portals, and thus is able to offer high level support for the design and development process. Finally, OntoWeaver-S provides a set of powerful tools to support knowledge portals at design time as well as at run time

    Integrating web services into data intensive web sites

    Get PDF
    Designing web sites is a complex task. Ad-hoc rapid prototyping easily leads to unsatisfactory results, e.g. poor maintainability and extensibility. However, existing web design frameworks focus exclusively on data presentation: the development of specific functionalities is still achieved through low-level programming. In this paper we address this issue by describing our work on the integration of (semantic) web services into a web design framework, OntoWeaver. The resulting architecture, OntoWeaver-S, supports rapid prototyping of service centred data-intensive web sites, which allow access to remote web services. In particular, OntoWeaver-S is integrated with a comprehensive web service platform, IRS-II, for the specification, discovery, and execution of web services. Moreover, it employs a set of comprehensive site ontologies to model and represent all aspects of service-centred data-intensive web sites, and thus is able to offer high level support for the design and development process

    Development of a client interface for a methodology independent object-oriented CASE tool : a thesis presented in partial fulfilment of the requirements for the degree of Master of Science in Computer Science at Massey University

    Get PDF
    The overall aim of the research presented in this thesis is the development of a prototype CASE Tool user interface that supports the use of arbitrary methodology notations for the construction of small-scale diagrams. This research is part of the larger CASE Tool project, MOOT (Massey's Object Oriented Tool). MOOT is a meta-system with a client-server architecture that provides a framework within which the semantics and syntax of methodologies can be described. The CASE Tool user interface is implemented in Java so it is as portable as possible and has a consistent look and feel. It has been designed as a client to the rest of the MOOT system (which acts as a server). A communications protocol has been designed to support the interaction between the CASE Tool client and a MOOT server. The user interface design of MOOT must support all possible graphical notations. No assumptions about the types of notations that a software engineer may use can be made. MOOT therefore provides a specification language called NDL for the definition of a methodology's syntax. Hence, the MOOT CASE Tool client described in this thesis is a shell that is parameterised by NDL specifications. The flexibility provided by such a high level of abstraction presents significant challenges in terms of designing effective human-computer interaction mechanisms for the MOOT user interface. Functional and non-functional requirements of the client user interface have been identified and applied during the construction of the prototype. A notation specification that defines the syntax for Coad and Yourdon OOA/OOD has been written in NDL and used as a test case. The thesis includes the iterative evaluation and extension of NDL resulting from the prototype development. The prototype has shown that the current approach to NDL is efficacious, and that the syntax and semantics of a methodology description can successfully be separated. The developed prototype has shown that it is possible to build a simple, non-intrusive, and efficient, yet flexible, useable, and helpful interface for meta-CASE tools. The development of the CASE Tool client, through its generic, methodology independent design, has provided a pilot with which future ideas may be explored

    Modelling data intensive web sites with OntoWeaver

    Get PDF
    This paper illustrates the OntoWeaver modelling approach, which relies on a set of comprehensive site ontologies to model all aspects of data intensive web sites and thus offers high level support for the design and development of data-intensive web sites. In particular, the OntoWeaver site ontologies comprise two components: a site view ontology and a presentation ontology. The site view ontology provides meta-models to allow for the composition of sophisticated site views, which allow end users to navigate and manipulate the underlying domain databases. The presentation ontology abstracts the look and feel for site views and makes it possible for the visual appearance and layout to be specified at a high level of abstractio

    Detecting Conflicts and Inconsistencies in Web Application Requirements

    Get PDF
    Web applications evolve fast. One of the main reasons for this evolution is that new requirements emerge and change constantly. These new requirements are posed either by customers or they are the consequence of users’ feedback about the application. One of the main problems when dealing with new requirements is their consistency in relationship with the current version of the application. In this paper we present an effective approach for detecting and solving inconsistencies and conflicts in web software requirements. We first characterize the kind of inconsistencies arising in web applications requirements and then show how to isolate them using a modeldriven approach. With a set of examples we illustrate our approach
    • …
    corecore