5 citations found. Retrieving documents...
Lloyd G. Williams and Connie U. Smith. Information requirements for software performance engineering. In H. Beilner and F. Bause, editors, Computer Performance Evaluation - Modelling Techniques and Tools, 8th Int. Conf. on Modelling Techniques and Tools for Computer Performance Evaluation, number 977 in LNCS, pages 86--101. Springer, 1995. Heidelberg.

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Performance Engineering Models of CORBA-based.. - Connie Smith And (1998)   (1 citation)  Self-citation (Williams Smith)   (Correct)

....feasibility and usefulness of using approximate solution techniques for the advanced system execution model. This could be accomplished by implementing additional solution techniques, or by using the software meta model to exchange model information with another tool for solution and evaluation [WILL95]. 8. ....

Lloyd G. Williams and Connie U. Smith, "Information Requirements for Software Performance Engineering," Proceedings 1995 International Conference on Modeling Techniques and Tools for Computer Performance Evaluation, Heidelberg, Germany, 1995,.


A Performance Model Interchange Format - Connie Smith And (1995)   (2 citations)  Self-citation (Williams Smith)   (Correct)

....without requiring extensive changes to them. The performance model solution process should be transparent to the user of the SPE tool. These SPE requirements led to the initial version of the PMIF (Smith, 1994a) They also led to an SPE meta model that defines the information requirements for SPE (Williams and Smith, 1995). The SPE meta model can be used by developers of CASE tools who wish to collect data and provide for tool inter operability with SPE tools to provide performance data for design analysis. It can also be used to exchange models among software performance modeling tools. Note that the SPE ....

....its benefits outweigh its disadvantages. A related part of this project used the EIA CDIF approach to define an SPE meta model that formally defines the software design information required for conducting an SPE study (EIA, 1994) The reasons for selecting the EIA CDIF approach are described in Williams and Smith, 1995). Because of the close relationship among the design information, the software model, and the system model, we use the same approach to define one type of system model: a queueing network model (QNM) The approach creates a QNM meta model defined in the same notation as the SPE meta model: the ....

[Article contains additional citation context not shown here]

Williams, L. G. and C. U. Smith, "Information Requirements for Software Performance Engineering," Proceedings 1995 International Conference on Modeling Techniques and Tools for Computer Performance Evaluation, Heidelberg, Germany, Springer, 1995.


A Basic Performance Model Interchange Format - Connie Smith And   Self-citation (Williams Smith)   (Correct)

.... 3 1997 by the authors changes to them. The performance model solution process should be transparent to the user of the SPE tool. These requirements led to the initial version of the PMIF [SMI94b] They also led to an SPE meta model that defines the information requirements for SPE [WILL95]. The SPE meta model can be used by developers of CASE tools who wish to collect data and provide for tool inter operability with SPE tools to provide performance data for design analysis. It can also be used to exchange models among software performance modeling tools. Note that the PMIF is ....

....and associative entities and, thus, overcomes limitations we encountered with the EIA CDIF graphical notation. The features of the OMT that we use maintain compatibility with the CDIF standard. The relevant elements of the OMT notation are defined in [RUMB91] and summarized in the appendix of [WILL95]. 2.2 Terminology Issues Performance model terminology varies considerably with modeling tools and textbooks on performance modeling. For example, the types of workloads are either described using the data processing terms of the workloads being modeled (e.g. timesharing, transaction, batch) or ....

[Article contains additional citation context not shown here]

Lloyd G. Williams and Connie U. Smith, "Information Requirements for Software Performance Engineering," Proceedings 1995 International Conference on Modeling Techniques and Tools for Computer Performance Evaluation, Heidelberg, Germany, September, 1995.


Performance Engineering Evaluation of Object-Oriented Systems .. - Smith, Williams (1997)   (13 citations)  Self-citation (Williams Smith)   (Correct)

....however, is not currently practical. It is too expensive for each CASE vendor to create their own modeling analysis component. Therefore, we seek a nearterm capability to interface CASE tools to existing modeling tools. A previous paper defined the SPE information that CASE tools must collect [Williams and Smith, 1995]. This paper illustrates the translation from Object oriented design models into performance models, and the use of the tool, SPE.ED TM, 1 for early life cycle performance evaluation of object oriented systems. SPE.ED is a performance modeling tool that supports the SPE process described in ....

....such as a class diagram and behavior descriptions for each class. However, our interest here is primarily in the use of scenarios as a bridge between Object Oriented Development and Software Performance Engineering. Thus, these additional models are omitted. 5. 1 Example Scenarios As described in [Williams and Smith, 1995], scenarios represent a common point of departure between object oriented requirements or design models and SPE models. Scenarios may be represented in a variety of ways [Williams, 1994] Here, we use Message Sequence Charts (MSCs) to describe scenarios in object oriented models. The MSC notation ....

[Article contains additional citation context not shown here]

L. G. Williams and C. U. Smith, "Information Requirements for Software Performance Engineering," in Quantitative Evaluation of Computing and Communication Systems, Lecture Notes in Computer Science, vol. 977, H. Beilner and F. Bause, ed., Heidelberg, Germany, Springer-Verlag, 1995, pp. 86-101.


Derivation of Petri Net Performance Models - From Uml Specifications   (Correct)

No context found.

Lloyd G. Williams and Connie U. Smith. Information requirements for software performance engineering. In H. Beilner and F. Bause, editors, Computer Performance Evaluation - Modelling Techniques and Tools, 8th Int. Conf. on Modelling Techniques and Tools for Computer Performance Evaluation, number 977 in LNCS, pages 86--101. Springer, 1995. Heidelberg.

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