文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > 高等教育 > 管理学 > Application Development through Reuse The ITHACA Tools Environment
侵权投诉

Application Development through Reuse The ITHACA Tools Environment

This paper presents the architecture and basic features of the Ithaca Application Development Environment based on a Software Information System for enhancing reusability of both software components and artifacts about development of these components. Obje

with Roles Model, and stored in the SIB as Application De-scriptions.

Classes and meta-level classes pertaining to the same appli-cation domain are clustered into an Application Frame. This al-lows the developer to consider groups of classes for reusability,instead of single components. The Application Frame drivesthe user in the development activities; RECAST navigatesalong a Frame to drive the process of components selectionfrom the SIB, transfer into the application developer work-space and reuse through re nements, modi cations, and spe-cializations [14]. The Application Frame has an associated setofkeywords that allows its identi cation in the SIB.

Meta-level classes describe:a) how the components can bereused, that is, can be selected, re ned, modi ed according totailoring primitives [10] for being adapted to the application;b)what design actions must, or could optionally, be performed bythe application developer during the various moments of thedesign process;c) the implications of the design actions per-formed by the application developer.

For example, in the Ithaca workbench domain of Public Ad-ministration Of ces [19], two basic reusable components arethe ‘document’ and ‘form’ classes. These are returned by RE-CAST as suggested components, when the designer selects the‘of ce’ class. The design actions associated to them specifyhow these components can be specialized to be adapted to theformat of documents handled in Public Administration Of ces:for example, which elds should be inserted to model the ‘pub-lic event request’ document, which models the documents pre-sented by organizations to get authorizations from the of ce.As a consequence of the user action of selecting the ‘of ce’component and upon the tool suggestion of reusing also ‘docu-ment’, the design suggestions contained in the meta-levelclasses specify that software modules or packages for editing,formatting, ling, circulating documents in the of ce shouldalso be selected by the developer and linked in the application.The implications of one action are, for example, the connec-tions to the ‘employee’ component modeling the of ce em-ployee handling the document.

Necessary and optional interface components are also re-turned as suggested components by RECAST in the localworkspace of the developer (see Figure 1): these can be:a) re-quired interfaces (components that need to be selected for agiven class to work correctly);b) component classes, that is, theinnermost components of a class providing the class externalbehavior;c) acquaintances (classes that are related to the se-lected class). Therefore, using the design suggestions incorpo-rated in meta-level classes, RECAST helps to complete thespeci cations withdefault speci cation classes and drives theapplication developer in tailoring the reusable components.Application-level classes and meta-level classes are repre-sented using the ORM formalism described here beneath.

3.2The Speci cation Model

As described so far, the Ithaca approach to application develop-ment is fully object-oriented. To this purpose, RECASTknowledge is described using an object-oriented speci cationmodel: the Object with Roles Model (ORM) [25]. The ORM

model is based on the concepts of object-orientation [4], whichare used not only in the Ithaca development language CooL,but also in notations for the analysis and design phases[3][5][28]: the class concept and the inheritance construct.In ORM, particular attention is given to the life-cycle of ob-jects belonging to a given class. The life-cycle description in aclass allows the developer to describe the possible evolution ofobjects belonging to that class through state transitions. Statesin ORM are abstract, describing in a synthetic way (with an as-sociated abstract state name) possible situations which an ob-ject can be in. Behaviors in a class are described consideringseparately different aspects in the evolution of an object. To thispurpose, ORM introduces the concept ofrole: a role typeRi isde ned as a set of propertiesPi, a set of operationsOi that canbe performed in a role, a set of abstract statesSi for that role,and a set of rulesRui, describing state transitions and con-straints on properties and possible transitions.An ORM class is de ned as follows:

class = (cname, Roles)

where

Roles = {R0, R1,..., Rn}

and

Ri = {rname, Pi, Si, Oi, Rui}

The base-roleR0 speci es general characteristics of theclass, different behaviors and their associated characteristicsare described in rolesR1,..., Rn.

The ORM model is used in RECAST both at the applicationlevel and at the meta-level. At the application level, each ORMclass speci es the behavior of possible components of an appli-cation. For instance, an of ce application component in the SIBat the application level is the ‘document’ class, with the follow-ing roles: base-role, preparing, delivering, approving, whichdescribe different aspects of the use of a ‘document’ object.At the meta-level, the guidelines of an Application Frame-work are described. In RECAST, we associate to each applica-tion-level class a meta-level class containing information usedto drive the developer in the speci cation of an application us-ing that class. Such information is partitioned, using the roleconcept, to consider different concerns separately; for instance,a document has logical contents aspects, layout aspects, distri-bution aspects that can be speci ed with different requirementsin different speci c applications.

Within each role, indications are given to the developer con-cerning other components to be interfaced with the componentbeing designed, according to different design choices guidedby state transitions from a meta-level abstract state to another.

3.3RECAST composition method and

interface

The ability to combine reusable components together in differ-ent ways to form different applications is recognized to be a keyissue to the achievement of software reusability [2]. Moreover,hierarchical decomposition methods are in widespread use [5],and Hierarchical Object Oriented Design methodologies areproving their effectiveness [16]. RECAST uses a componentcomposition method based onhierarchical composition where

上一页第5页

你可能喜欢

热门文档

相关文档

  • Application Data太大处理办法

    Application Data太大处理办法_计算机软件及应用_IT/计算机_专业资料。Application Data 太大处理办法 Application Data 是什么文件夹?Application Data 文件夹有什么...

  • 什么是Application

    当你创建 了一组Active Server Pages,那么你就是创建了一个application。 因此,一个Application就是在硬盘上的一组主页以及ASP文件,当一个Active Server Pages 加入...

  • 一份铸就了11∕13成功率的Common Application Essay

    一份铸就了11∕13成功率的Common Application Essay_其它_高等教育_教育专区。嘉文博译钱坤强老师写的Common Application Essay,看了收获挺大的,转起来,顶起来,...

  • applicationContext.xml详解

    applicationContext.xml详解_IT/计算机_专业资料。applicationContext.xml详解想必用过 Spring 的程序员们都有这样的感觉,Spring 把逻辑层封装的太完美了(个人 感觉 ...

  • Android Application Framework简介

    Android Application Framework 简介 2010.07.20 主要内容 ? Android框架简介– ––– 库与框架对比 Android应用程序框架 Intent意图简介 IPC/Binder的结构 ? ...

  • application事件

    application事件_计算机软件及应用_IT/计算机_专业资料。Application.CommandBars(1).Controls("工具(&T)").Controls("宏(&M)").Enabled = False '工具-宏...

  • 使用Application对象

    使用Application对象 Application对象拥有与Application所有相关的集合,方法,以及事件。下面的部分你将学 会怎样使用Application对象来创建application变量和application事件。 ...

  • Application对象

    创建和读取简单数据类型变量 Application 对象创建变量的一般语法格式如下所示: Application(“变量名称”) = 变量值 对变量进行引用,从而获取变量的值: Application(...

  • 外文翻译-Android Application Fundamentals

    外文翻译-Android Application Fundamentals_理学_高等教育_教育专区。Android Application FundamentalsAndroid Application Fundamentals Androidapplicationsare written in ...

  • 01_Android Architecture and Application

    01_Android Architecture and Application_理学_高等教育_教育专区。Android 的基础介绍Android Architecture 夏培勇 DQE工具组 xiapeiyong@hisense.com 一、Android简介...

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email