| D. Harel. On Visual Formalisms. Communications of the ACM, 31(5), 1988. |
....used and it is accepted by the industry as the standard language for software analysis and design. UML is a graphical language. Software concepts are represented visually as icons. Harel has presented interesting arguments in favor of using a visual representation in software development in [43]. A UML model is usually composed of several diagrams. This division of a model into di#erent diagrams is an important mechanism to manage software complexity. Each diagram represents a di#erent aspect or view of a system. We can see many examples of these diagrams in the sound recorder case ....
D. Harel. On visual formalism. Communications of ACM, 31(5):514--530, 1988.
....other langauge elements can be handled. In complex cases the integration of various UML diagrams may lead to large diagrams which are di cult to handle and to understand. Therefore, for practical use, structuring concepts for graphs should be incorporated in the presented approach (cf. e.g. [35, 22, 15, 7, 9]) For being able to use our approach in practice, adequate transformation tools are needed. It should be investigated in which way existing tools can be employed to achieve this aim. A further interesting question is how far the presented integration approach can be used for consistency ....
David Harel. On visual formalisms. Communications of the ACM, 31(5):514-530, 1988.
....4.2 Behavioural Diagrams Basic components are specified using views. Such a view may be given as a triple (SPECIFICATION, ABSTRACTION and OPERATIONS parts) or using the STS derivation principles [21] as a couple (SPECIFICATION part and a STS) These STSs may be related to Statecharts ([13], or UML ones) but for some di#erences: STSs are simpler (but less expressive) than Statecharts; STSs model sequential components (concurrency is done through external structuring and the computation of a structured STS from subcomponents STSs [4] STSs are built using conditions which ....
David Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
Shieber, Stuart M. 1994b. On Loebner's lessons. Communications of the ACM, 37(6):83--84.
....generative. These business requirements are not the business functions, but rather the functional and non functional requirements of a system to support the business functions. STRUCTURE MATTERS From the beginnings of software engineering, structure has been the foundation of good architecture [Parn72], Dijk68] There are some basic tenets that can be used to guide the architecture centered deployment [Clem96] n Systems can be built in a rapid, cost effective manner by importing (or generating) large externally developed components. n It is possible to predict certain qualities about a ....
....are independent of a specific software development method, programming language, hardware environment, and to a large extent the application domain. These enabling techniques have been known for years. Many were developed in the 1970 s in connection with publications on structured programming [Parn72], Parn85] Although the importance of these techniques has been recognized in the software development community for some time, it is now becoming clear of the strong link between system architecture and these enabling principles. Patterns for software architecture are explicitly built on these ....
"On the Criteria to be Used in Decomposing Systems into Modules," D. Parnas, Communications of the ACM, Vol. 15, pp. 1053--1058, December 1972.
No context found.
D. Harel. On Visual Formalisms. Communications of the ACM, 31(5), 1988.
No context found.
D. Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
Harel, D., On visual formalisms. Communications of the ACM, 1988. 31(5): p. 514-530.
No context found.
D. Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--531, May 1988.
No context found.
D. Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
"On the Criteria to Be Used in Decomposing Systems into Modules," Parnas, David, 1972. Communications of the ACM 5(12):1053-1058.
No context found.
Harel, D. On Visual Formalism. Communications of the ACM , volume 31, number 5, page 171-187, May 1988.
No context found.
J. Harold McBeth: On the Reference Counter Method, Communications of the ACM, Vol. 6, No. 9, September 1963, p. 575.
No context found.
David Harel, On visual formalisms, Communications of the ACM, Volume 31, No 5 (1988) 514-530.
No context found.
Harel David, On visual formalisms, Communications of the ACM, Volume 31, Number 5, May 1988, pp. 514-530. 19
No context found.
David Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--530, May 1988.
No context found.
D. Harel. On visual formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
D. Harel: On Visual Formalisms. Communications of the ACM, 31(5), Mai 1988, S. 514 -- 530.
No context found.
D. Harel. On visual formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
David Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
D. Harel. On visual formalisms. Communications of the ACM, 31(5):514--530, 1988.
No context found.
D. Harel. On Visual Formalisms. Communications of the ACM, 31(5):514--530, May 1988.
No context found.
Gotlieb, C. Sorting on computers. Communications of the ACM 6, 5 (May 1963), 194--201.
No context found.
D. Harel. On visual formalisms. Communications of the ACM, 31(5): 514-- 530, 1988
No context found.
D. Harel. On visual formalisms. Communications of ACM, 31(5), May 1988.
First 50 documents Next 50
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