Ossher, H., Harrison, W., Tarr, P.: Software engineering tools and environments: a roadmap. In: ICSE '00: Proceedings of the Conference on The Future of Software Engineering, New York, NY, USA, ACM Press (2000) 261--277  Home/Search   Document Not in Database   Summary   Related Articles   Check

....code. Any change to a UML model results in the automatic update of the code that is related to that model and vice versa. Existing tools that support different information models across the software lifecycle provide limited support for traceability and consistency management between artefacts [9, 10]. Specifically, current approaches do not provide developers with the flexibility to create relations across software artefacts of different types [11, 12, 13, 14] Olsson and Grundy [15] find that restricting software artefacts to a common data model does not sufficiently allow fuzzy ....

W Harrison, H Ossher, and P Tarr. Software engineering tools and environments: A roadmap. The Future of Software Engineering, 2000.

....to harmonize their specific features with current requirements. The aims of these approaches are increasing flexibility and adaptability of tools [38] distributing data and tool components on the internet [8] supporting cooperation of developers [6] enable data exchange between tools [24]. supporting creative tasks in software design [15] integrating development tools with tools for management and planning [39] In this paper, we investigate how the different and partly orthogonal aims can be combined in an agile software development environment, how such an environment ....

....repositories are expensive to buy, costly to install and often require highly skilled personnel, e.g. for user administration and schema management. Exchange formats like XML appear to be a lightweight solution to the problem, easier to use and more flexible for both tool developers and tool users [24]. Consequently, the requirements for agile upper CASE tools are numerous. 1. Diagrams and tools have to be easily accessible for all team members [46] This requires a central repository which provides distributed access. In such a distributed environment, tool components may be shared and ....

W. Harrison, H. Ossher, and P. Tarr. Software Engineering Tools and Environments: A Roadmap. In Finkelstein [19], pages 261-277.

.... process, e.g. requirements or design, with limited support to relate the information to other tools or parts of the process [1, 10] Tools that support multiple phases of development and multiple information models typically provide limited traceability and consistency management between artefacts [5, 9]. More elaborate support is usually found in low level representations like design or source code. For high level representations, support is very basic if even present at all. There has been a substantial amount of research put into issues such as inconsistency management [13] traceability ....

Harrison, W., Ossher, H. and Tarr, P. Software Engineering Tools and Environments: A Roadmap, The Future of Software Engineering, Finkelstein, A. Ed., ACM Press, 2000.

....research trends, and tool researchers of the relevant state of the art in commercial tools and various likely future research trends in tools development. Introduction The demand for computer software applications steadily increases as numbers of users, problem domains and application areas grow [42, 51, 95]. New applications of computing technology continue to emerge [51] such as E commerce [6] data warehousing [61] multi media systems, mobile computing [53] and groupware [31] many very demanding in terms of software size and complexity [13] Similarly, as computing hardware and networks become ....

....commercial tools and various likely future research trends in tools development. Introduction The demand for computer software applications steadily increases as numbers of users, problem domains and application areas grow [42, 51, 95] New applications of computing technology continue to emerge [51], such as E commerce [6] data warehousing [61] multi media systems, mobile computing [53] and groupware [31] many very demanding in terms of software size and complexity [13] Similarly, as computing hardware and networks become more powerful, the software that we run on them tends to grow to ....

[Article contains additional citation context not shown here]

Harrison, W., Ossher, H. and Tarr, P. Software Engineering Tools and Environments: A Roadmap, The Future of Software Engineering, Finkelstein, A. Ed., ACM Press, 2000.

....to generate the Perceval XML encoding. XSLT (XML Stylesheet Language Transformations) scripts are used to implement extensible code generation facilities. 7. Discussion A great deal of work has been done in recent times to address the problem of separation of concerns in software development [12]. Examples of such work include viewpoint based requirements, designs and tools [7, 8] subject oriented programming [11] hyper slices [24] and aspect oriented programming systems [15, 16, 14] Viewpoints have been used for various purposes, including requirements engineering, specification and ....

.... and tools [7, 8] subject oriented programming [11] hyper slices [24] and aspect oriented programming systems [15, 16, 14] Viewpoints have been used for various purposes, including requirements engineering, specification and design, user interface construction and in various software tools [7, 12]. Aspects are a specialisation of the general notion of a viewpoint i.e. a certain perspective on a software system. Viewpoints of one form or another are used in all development methods, including component development methods like Catalysis TM and SelectPerspective TM [1, 5] Unfortunately the ....

Harrison, W., Ossher, H. and Tarr, P. Software Engineering Tools and Environments: A Roadmap, The Future of Software Engineering, Finkelstein, A. Ed., ACM Press, 2000.

....WORK While CBDEs have yet to become a focus of widespread research, there are several previous research efforts that contribute technologies, principles and insights for CBDE design. An overview of the history and possible future of software engineering environments is given by Harrison et al. [11]. They consider multi view software environments to be one of the most promising recent trends. Every complex system has many concerns that have to be considered separately. This is best done by providing different, independent views of the various aspects of a system. Type and instance view in ....

Harrison, W., Ossher, H., and Tarr, P. Software Engineering Tools and Environments: A Roadmap. In The Future of Software Engineering. ACM, New York, 2000, 261-277.

....WORK While CBDEs have yet to become a focus of widespread research, there are several previous research efforts that contribute technologies, principles and insights for CBDE design. An overview of the history and possible future of software engineering environments is given by Harrison et al. [8]. They consider multi view software environments to be one of the most promising recent trends. Figure 4: Type Oriented Component Configuration. 11 Every complex system has many concerns that have to be considered separately. This can only be done by providing different, independent views of the ....

Harrison, W., Ossher, H., and Tarr, P. Software Engineering Tools and Environments: A Roadmap. In The Future of Software Engineering. ACM, New York, 2000, 261-277.

....engineering tool assumes it has overall control. However, such an approach precludes the easy integration of reverse engineering tools into toolsets commonly used in both academic research and in industry. In a UNIX like environment, the established troika of edit compile debug tools are common [34]. Representative tools in this group include emacs and vi for editing, gcc for compiling, and gdb for debugging. In a Windows NT environment, the tools may have different names, but they serve similar purposes. The only real difference is cost and choice. A recent case study [84] illustrates the ....

W. Harrison, H. Ossher, and P. Tarr. Software engineering tools and environments: A roadmap. In this volume, June 2000.

No context found.

Ossher, H., Harrison, W., Tarr, P.: Software engineering tools and environments: a roadmap. In: ICSE '00: Proceedings of the Conference on The Future of Software Engineering, New York, NY, USA, ACM Press (2000) 261--277

No context found.

H. Ossher, W. Harrison, and P. Tarr, "Software Engineering Tools and Environments: A Roadmap," Proceedings of the Conference on The Future of Software Engineering, pp. 263 - 277, Limerick, Ireland, 2000.

No context found.

Harrison, W., Ossher, H., and Tarr, P. Software Engineering Tools and Environments: A Roadmap. In Finkelstein, A., ed., The Future of Software Eng., 22nd Int. Conf. on Software Eng., Limerick, Ireland; ACM, New York, pp. 263-277. June, 2000.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC