By Topic

Assessment of Software Tools, 1996., Proceedings of the Fourth International Symposium on

Date 22-24 May 1996

Filter Results

Displaying Results 1 - 22 of 22
  • Author index

    Publication Year: 1996
    Save to Project icon | Request Permissions | PDF file iconPDF (36 KB)  
    Freely Available from IEEE
  • Status of software tools developed in Japan

    Publication Year: 1996 , Page(s): 89 - 92
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (416 KB)  

    This paper overviews software tools developed in Japan and briefly describes some selected ones. Japanese computer manufacturers' software tools have evolved from mainframe to workstation/PC and to client/server environments, and from structured methods to object-oriented, from lower CASE to upper, and from forward engineering to re-engineering. A few CASE products by independent software vendors are well received. Componentware, re-engineering, and other technologies have been developed View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • JANUS: Software Tools - Looking Back/Looking Forward

    Publication Year: 1996
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (36 KB)  

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • EMERALD: software metrics and models on the desktop

    Publication Year: 1996 , Page(s): 111 - 112
    Cited by:  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (164 KB)  

    BNR, NORTEL, and Bell Canada have jointly developed the Enhanced Measurement for Early Risk Assessment of Latent Defects (EMERALD) system for decision support, integrating software measurements, quality models, and delivery of results to the desktop of software developers in a timely manner (J.P. Hudepohl et al., 1996). It has been applied to a very large system with more than 12 million lines of code within procedures. The prerequisite infrastructure for reliability improvement includes a strong configuration management system, a flexible source code library system, a thorough problem reporting system, and widespread networking of the desktop systems of developers. Such systems are not part of EMERALD per se, but EMERALD would have been impossible without them View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software tool assessment-an Australian perspective

    Publication Year: 1996 , Page(s): 93 - 94
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (148 KB)  

    A national perspective on software tool assessment can be derived by comparing objective economic needs with the interests of the software tool community. Australia's unique combination of size, small population and small location suggest a preference for open tools that support distributed development, which compares interestingly with actual practice View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using software metrics tools for maintenance decisions: a classroom exercise

    Publication Year: 1996 , Page(s): 47 - 58
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (916 KB)  

    We explore the use of software metrics tools to guide software maintenance decisions. A senior undergraduate class was given a copy of QUIPU, an implementation of the X.500 directory standard, and asked to determine which component of the system would be the best to rewrite in order to improve the overall quality of the entire software system. We describe the course structure and the information and tools provided to the students. The primary tool used by the students was Rigi, a program understanding tool. We present the methodology and results of one of the successful groups of students. Based on the experiences of the students, we conclude with suggestions for tool designers View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Object-oriented modeling in Metaview

    Publication Year: 1996 , Page(s): 109 - 110
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (176 KB)  

    We investigate the capability of Metaview, a meta CASE system, to define object oriented CASE environments. An innovative feature of Metaview is the use of aggregation as a mechanism for linking method fragments. This approach is illustrated in the specification of our environment to support OMT, one of the most popular object oriented development methods View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • CAME tools-lessons learned

    Publication Year: 1996 , Page(s): 113 - 114
    Cited by:  Papers (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (148 KB)  

    The tools that realize and support the software measurement process will be denoted as computer assisted software measurement and evaluation tools (CAME tools). The paper presents a classification and characterization of the CAME tools on the basis of an analysis of more then twenty tools in the Software Measurement Laboratory at the University of Magdeburg View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A characterization of OOA tools

    Publication Year: 1996 , Page(s): 59 - 67
    Cited by:  Papers (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (596 KB)  

    Despite unification of tools supporting object oriented analysis (OOA) there is still a variety of tools making it hard to select one of them for a given environment. Clearly, if one is willing to apply a certain favorite OOA method, the choice would be restricted to tools supporting that method. However, there are usually several such tools and no clear criteria for selecting between them without extensive experimentation. But this, in general, is impossible due to time restrictions. The paper deals with the selection problem and poses a set of OOA tool characteristics that can be used for tool description and thus form a base for an efficient tool comparison. In order to show how this set of characteristics may be applied, we give, as an example, a characterization of OMTool View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The CARE toolset for developing verified programs from formal specifications

    Publication Year: 1996 , Page(s): 24 - 35
    Cited by:  Papers (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (876 KB)  

    The paper describes the CARE toolset for interactive development of verified programs from formal specifications. The software engineer begins by giving a characterization of the application domain in the form of a mathematical theory. CARE tools are then used to progressively design a program by sketching out the program structure and gradually filling in the details. At any stage the correctness of the partial design can be checked by using one of the CARE tools to generate proof obligations. Another tool gives access to pre-proven parameterised design templates which encapsulate useful programming knowledge. When the design is complete, a third CARE tool is used to automatically synthesize a source code program which-if all the proof obligations can be discharged-is guaranteed to meet its formal specification. The knowledge base of CARE can be extended by users in a soundness-preserving manner to include reusable domain theories, library routines, design templates and proof tactics. The CARE toolset includes a fully automatic resolution-based theorem prover which will discharge many of the simpler proof obligations, and a general-purpose interactive theorem prover for the rest View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • If yesterday is tomorrow, this must be Toronto [Internet software]

    Publication Year: 1996 , Page(s): 116 - 118
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (192 KB)  

    The author uses examples of Quarterdeck software to show that the pace of innovation in Internet software outstrips the ability of any single company or tool set to keep pace. The author points out the validity of both standards based programming and technical innovation in advance of standards with the intent of achieving market advantage. He emphasizes that one must be prepared to make use of new (not necessarily home grown) tools, make alliances and yet one must also be on the lookout for the next coming set of innovations, and the tools to cope with them View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Assessing software tools in the telecommunications industry

    Publication Year: 1996 , Page(s): 71 - 72
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (96 KB)  

    The paper describes practical aspects of assessing software tools to be used in developing large-scale telecommunications systems View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Assessing the potentials of CASE-tools in software process improvement: a benchmarking study

    Publication Year: 1996 , Page(s): 104 - 108
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (348 KB)  

    CASE tools have been thought as one of the most important means for implementing the derived quality programs. Two basic questions should be answered to find the right CASE tool: what attributes the CASE tools should exhibit and how the existing tools can be ranked according to their capability to support the quality program goals. We propose our solution based on the concept of software benchmarking. First, we summarise the QR method, and then we report on how it was applied in CASE tools assessment. Next we derive appropriate benchmark sets for CASE tools on the base of the CMM, the standard ISO 9000 and the MBNQA-criteria. We propose and implement a framework for CASE tools evaluation and selection View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Defining a set of criteria for the assessment of tool support for CMM-based software process improvement

    Publication Year: 1996 , Page(s): 77 - 86
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1120 KB)  

    Researchers as well as practitioners agree that the quality of a software product relies to a high degree on the quality of the software process. Therefore recent research efforts in software engineering focus on software process assessment and improvement (SPAI). Numerous approaches like the CMM, Bootstrap, SPICE, AMI were developed. An important factor influencing success and progress of the implementation of a SPAI approach in an organization is its software engineering tools environment. The aim of the paper is to determine a set of criteria concerning the assessment of the suitability of a tools environment for the promotion of CMM-based SPAI. We base our investigations on the 316 CMM Key Practices. We structure them according to the issues they address. For each issues cluster we determine the functionality to be provided and artifacts to be managed by a tool as assessment criteria. The degree of fulfillment of a certain criteria depends on if and how the associated function or artifact is provided. Our investigations result in the definition of 12 evaluation criteria. Examples are the necessity to provide computerized process representations or to provide meta process support like process monitoring or process evolution. After defining the criteria we determine their importance for reaching the CMM Maturity Levels and for supporting the Key Practices associated to the CMM Common Features View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SoftTrak: an industrial case study

    Publication Year: 1996 , Page(s): 37 - 46
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (564 KB)  

    SoftTrak is a project performance management tool based on earned value tracking of a software project's progress. Performance management tools are needed to report problems back to management. SoftTrak looks to the functional work completed as compared to the work estimation and tracks projects by comparing the actual accomplishments against the planned activities. Projected completion date and effort based on the historical data reported for the project are an integral part of the outputs. SoftTrak was developed by Soft Quest Systems in conjunction with input received from leading industries in Israel. The paper describes the process by which a software development project tracking methodology, using SoftTrak, was defined and later evaluated by B.V.R. Technologies View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Assessment of tools in the telecommunications industry: a customer perspective

    Publication Year: 1996 , Page(s): 69 - 70
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (164 KB)  

    The Information Technology Procurement and Supplier Quality department of Bell Canada is responsible for the procurement of complex software products. To assess and manage the risks related to these acquisitions, we have developed methods and tools that combine process capability assessment and software product assessment. This provides us with a generic view of the deployment of software tools among our suppliers. The paper presents two points related to software tools in telecommunications companies. The first one is the characteristics of the telecommunications industry that influence the introduction of software tools. The second point is the introduction process of software tools viewed as a new technology for a software development organization View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Thesaurus: a tool for reusing software objects

    Publication Year: 1996 , Page(s): 99 - 103
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (340 KB)  

    So far software reusability has not yet had practical application in the professional world. The reusability concept represents a direct link between productivity and software quality. In this paper a software tool is described, “Software Thesaurus” (ST), whose main purpose is to develop software, reusing objects produced previously in other software projects. This tool is defined by a new repository metamodel which supports the classification and retrieval of essential software objects defined by current object oriented methodologies, 4th generation languages, and GUI. This article presents both free text information and a software indexing system in order to classify all the objects necessary to develop a software application. The ST presents an original method to carry out typical software tasks i.e. analysis, design, and implementation through the combination of computer aid and reusability View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Methodology of a CASE-tool assessment

    Publication Year: 1996 , Page(s): 97 - 98
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (184 KB)  

    This paper investigates the efficiency of international CASE tools, which were offered on the German market in 1994. In considering a catalogue of more than 400 criteria, which has been developed in cooperation with industry, 17 CASE tools are evaluated in the scope of a case study. Both the specific requirements of a CASE user and the common requirements derived from the ISO 9000 are taken into account as well View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An expert system for the verification of finite-element calculations

    Publication Year: 1996 , Page(s): 18 - 23
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (528 KB)  

    A prototype expert system for the verification of finite-element analysis data with a graphical hypertext user interface for use in industry and academia is presented. This tool assists novice users in identifying problems and errors associated with finite-element simulations. Due to the use of object-oriented programming paradigms, no changes in program architecture other than the definition of new methods are required when porting the knowledge based expert system to be used with other finite-element solvers. The main knowledge base used in the error and problem identification is easily expandable by incorporating error reports from users. A complete system, supporting a wide variety of potential problems, can thus be incrementally assembled by a knowledge engineer. A separate knowledge base can be generated for each finite-element package which is to be supported by the expert system. The problem of usability of the expert system is addressed using hypertext output that can be accessed with state-of-the-art browsers. This technology effects the acceptance, readability and operation of any software tool in a positive way View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The role of tools in development of a data warehouse

    Publication Year: 1996 , Page(s): 139 - 145
    Cited by:  Patents (5)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (592 KB)  

    We discuss the tools required for building a data warehouse. We describe key features of each tool. Software tools for data warehousing include data modeling, database management systems, data extraction and migration, data validation, metadata, and job schedulers. We also describe project management methods we have developed for building a data warehouse. Specific tailoring of traditional software development methodology for data warehouse projects is proposed including dependent work break down structures and a method of estimation and prioritization. Throughout the paper, we present our experience of a 25 gigabyte data warehouse project which has accomplished an initial delivery to over 400 users View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Java and JDBC: tools supporting data-centric business application development

    Publication Year: 1996 , Page(s): 121 - 138
    Cited by:  Patents (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1244 KB)  

    Software porting, maintenance, distribution and installation form the bulk of application deployment costs. These high costs have been substantially exacerbated by the move to client server computing. No longer can an application be installed on one system for use by the entire user community. Now it must be installed on all desktops in the enterprise and, at most companies, this will be mean that the software must be ported to and tested on Windows 3.1, Macintosh, Windows95, Windows NT, and often a variety of UNIX systems. The trend towards making business data available to both internal and external users across intranets and the Internet transforms an expensive problem into a completely intractable one. To further complicate the matter, there is an emerging trend in many application domains to move from 2 dimensional windowed user interfaces to high information bandwidth 3 dimensional data visualization and virtual reality systems. These applications are either very difficult or impossible to write using standard GUI builders, generators, or the current breed of portable GUI class libraries. We propose a new architecture for data visualization, discovery, and delivery and argue that the existing development model, and the tools supporting that model, are unaffordable and don't scale to Internet scope delivery numbers View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Exploratory analysis tools for tree-based models in software measurement and analysis

    Publication Year: 1996 , Page(s): 7 - 17
    Cited by:  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (880 KB)  

    The paper presents our experience with the adaptation and construction of exploratory analysis tools for tree-based models used in quality measurement and improvement. We extended a commercial off-the-shelf analysis tool to support visualization, presentation, and various other exploration functions. The user-oriented, interactive exploration of analysis results is supported by a new tool we constructed for this specific purpose. These tools have been used successfully in supporting software measurement and quality improvement for several large commercial software products developed in the IBM Software Solutions Toronto Laboratory View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.