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
the behavior of innermost components is encapsulated in high-er level abstractions.
Components are connected viarole links which map outgo-ing messages of one role into incoming messages of anotherrole and vice versa. Another basic concept for composition istheProcess Class whose roles represent tasks of the applica-tion; process classes are used in the requirement compositionprocess to coordinate the various selected components to mod-el the whole behavior of the application under development [9].Connecting a class role with one selected component via arole link initiates the retrieval from the SIB of the classes androles whose presence isNecessary in the application.
The design suggestions originated by one connection (eitherexplicit or implicitly suggested by RECAST) are the classesand roles Necessary and Optional interfaces. Repeating theconnection process, speci cation classes may be connectedinto complex aggregates until the desired speci cations arecomposed. In the Ithaca terminology, this process of composi-tion with associated graphical notations applies to all phases ofthe software process. Speci cation classes may themselves becomposed of classes at a deeper level of abstraction; corre-spondingly, the inner workings of one class is shown in termsof classes providing the class external behavior.
In the example of the Public Administration domain [19],the interaction and inner workings of a sample Public Admin-istration Of ce with private organizations or persons are mod-eled, representing institutions (Police Department, Cleaning &Services Department) which might be asked for their authori-zation when handling public events. Requests and authoriza-tions circulate in the form of documents: request and approval(or rejection) documents. The basicprocess class de ned in theSIB for this example is the‘Public Administration’ class; otherclasses are the ‘Person/of ce’, representing the of ce employ-ees or agents, the ‘Document’, the ‘Of cial Document’, and the‘External Of ce’. For these speci cation classes, the requiredinterfaces (Needed classes), the hierarchical innermost compo-nents at variousabstraction levels, and the acquaintances (Op-tional classes) are de ned in RECAST meta-level classes.Speci cation and meta-level classes appear in RECASTinter-face shown in Figure 2.
In designing RECAST user interface, the problem of orien-tation in the development information space quickly arises, asusually occurs when dealing with large class collections [15].Moreover, the architecture of RECAST has to take into accountcarefully the interaction with the SIB, with the Selection Tool,and with Vista. Therefore, as shown in Figure 2, RECAST pro-vides the application developer with three windows, one foreach tool of the Application Development Environment: a speci cation window (RECAST window), a design window, a selection window.
Within each window, each tool is working independently,and more subwindows are created either automatically or uponthe application developer’s requests. Each tool window con-tains the following information (here, we focus our attention tothe RECAST window):a) an area for combining componentsin thedevelopment document [14], eventually containing the
set of selected classes;b) an area for the pool of selected com-ponents;c) an area dedicated to provide assistance to the devel-oper.
Existing components must be provided to the user with hid-den details to improve orientation: irrelevant features shouldnot be presented, the set of elements displayed should be basedon the operations performed, and the detail should be adjust-able by the user at any moment. To this aim, in RECAST, vari-ous abstraction levels are considered.
The speci cation window of Figure 2 is divided in fourparts. The upper left part is used to interconnect components.Here, person/of ce has been selected by the developer, anddocument, with the base-role and the being-prepared role, hasbeen suggested by RECAST (shadowed area). The lower leftpart presents design guidelines, and the operations allowed tofollow these guidelines. The to-do list allows the developer toselect and de ne optional (P) roles, necessary (N) roles and tode ne the non-functional requirements; eventually, the COM-MIT option allows the developer to terminate the speci cationof ‘document’.
The right quadrants of Figure 2 are the interface betweenRECAST and the SIB and Selection Tool. It is possible to selecta set of components with the Selection Tool and to insert themin the pool of speci cation components. To each component, ameta-level class is associated which provides design guide-lines. In the example in Figure 2, given for ‘document’, thewindow of the Selection Tool shows the Is-A hierarchy of ‘doc-ument’; here, the user selects the ‘of cial-document’ class,which is therefore moved into the component pool area.
4Visual Scripting: Vista
Software components selected and identi ed at the speci ca-tion level by RECAST are tailored and composed into the cur-rent speci c application through the Visual Scripting Tool, Vis-ta.
Visual scripting is an approach to the interactive construc-tion of applications from reusable software components inwhich both the internal behaviour of applications as well astheir user interfaces can be directly edited and manipulated[23]. Vista is being developed as part of the Ithaca ADE by theCentre Universitaire d’Informatique of the University of Gene-va.
Vista is based on C++ and X, using the Motif user interfacetoolkit. The current version of Vista supports a small set of soft-ware components developed for demonstration purposes. It ispossible to develop, by scripting, very simple forms-based ap-plications that display information retrieved from a database.Transformation on retrieved information can be performed,and information can be propagated from one component to an-other. A variety of user interface components (buttons, sliders,etc.) can presently be scripted. Ongoing work is to support theuse of scripts as components (to permit the use of applicationsbuilt using Vista as components in larger systems), and, in col-laboration with Ithaca partners, the development of other com-ponents suitable for scripting.
An exploratory prototype of a visual scripting tool, calledVST, which was based on Unix commands and les as compo-
Application Data太大处理办法_计算机软件及应用_IT/计算机_专业资料。Application Data 太大处理办法 Application Data 是什么文件夹?Application Data 文件夹有什么...
当你创建 了一组Active Server Pages,那么你就是创建了一个application。 因此,一个Application就是在硬盘上的一组主页以及ASP文件,当一个Active Server Pages 加入...
一份铸就了11∕13成功率的Common Application Essay_其它_高等教育_教育专区。嘉文博译钱坤强老师写的Common Application Essay,看了收获挺大的,转起来,顶起来,...
applicationContext.xml详解_IT/计算机_专业资料。applicationContext.xml详解想必用过 Spring 的程序员们都有这样的感觉,Spring 把逻辑层封装的太完美了(个人 感觉 ...
Android Application Framework 简介 2010.07.20 主要内容 ? Android框架简介– ––– 库与框架对比 Android应用程序框架 Intent意图简介 IPC/Binder的结构 ? ...
application事件_计算机软件及应用_IT/计算机_专业资料。Application.CommandBars(1).Controls("工具(&T)").Controls("宏(&M)").Enabled = False '工具-宏...
使用Application对象 Application对象拥有与Application所有相关的集合,方法,以及事件。下面的部分你将学 会怎样使用Application对象来创建application变量和application事件。 ...
创建和读取简单数据类型变量 Application 对象创建变量的一般语法格式如下所示: Application(“变量名称”) = 变量值 对变量进行引用,从而获取变量的值: Application(...
外文翻译-Android Application Fundamentals_理学_高等教育_教育专区。Android Application FundamentalsAndroid Application Fundamentals Androidapplicationsare written in ...
01_Android Architecture and Application_理学_高等教育_教育专区。Android 的基础介绍Android Architecture 夏培勇 DQE工具组 xiapeiyong@hisense.com 一、Android简介...
热门文档