| Chung, L., Katalagarianos, P., Marakakis, M., Mertikas, M., Mylopoulos, J., and Vassiliou, Y., "From Information System Requirements to Designs: a Mapping Framework", Information Systems, Vol. 16, No. 4, 1991, pp. 429-461. |
....management tools directly support high level executives in analyzing and changing the way an orgnaization achieves its goals. Obviously, this requires the representation of non functional goals as well as the representation of the ways how process alternatives contribute to these goals [CKM 91]. Such non functional requirements can emerge from informal or semi formal discussions [HJR90] or they can be axiomatically derived from economic theories, such as the theory of value added chains [PM85] The following figure, expanded from one shown in the chapter by John Mylopoulos (cf. also ....
Chung, L., Katalagarianos, P., Mertikas, M., Mylopoulos, J., Vassiliou, Y. (1991). From information systems requirements to designs: a mapping framework. Information Systems 16, 4.
No context found.
Chung, L., Katalagarianos, P., Marakakis, M., Mertikas, M., Mylopoulos, J., and Vassiliou, Y., "From Information System Requirements to Designs: a Mapping Framework", Information Systems, Vol. 16, No. 4, 1991, pp. 429-461.
No context found.
K. L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos and Y. Vassiliou, "From Information System Requirements to Designs: A Mapping Framework," Information Systems, vol. 16, no. 4, 1991, pp. 429--461.
....for the rest of the discussion we will speak of goal satisficing [42] 3 to suggest that generated software is expected to satisfy within acceptable limits, rather than absolutely, non functional requirements. 2 An earlier version of portions of this and the next section have appeared in [13]. 3 [42] actually uses the term to refer to decision methods that look for satisfactory solutions rather than optimal ones. The term is adopted here in a broadened sense since in the context of non functional requirements, even the notions of a solution or optimality of a solution may be ....
....be generated by the simple example we have been introducing piecemeal. In the bigger picture of information system development, a source object, say a component of a requirements specification, is mapped into one (or possibly several) target object(s) say components of a design specification [13]. The dependencies among these objects are shown through dependency links on the left and right hand sides of Figure 2.1. The use of the goal structure generated by the designer from non functional requirements, possibly with the help of methods, is intended to help her select among alternatives ....
[Article contains additional citation context not shown here]
K. L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos and Y. Vassiliou, "From Information System Requirements to Designs: A Mapping Framework," Information Systems, vol. 16, no. 4, 1991, pp. 429-- 461.
....programmers are called programming in the many. In between, object management tasks such as version and configuration management are the domain of programming in the large [48] Here, we only sketch an in thesmall and an in the many model. In a Telos model used intensively throughout DAIDA [16] [33] programming in the small is understood as a set of interrelated design decisions which transform design objects into other design objects, supported by design tools. Design tools are modeled by the special kinds of design decisions they support. Design goals are a special kind of design ....
Chung, K., Katalagarianos, P., Marakakis, M., Mertikas, M., Mylopoulos, J., and Vassiliou, Y. From Information System Requirements to Designs: A Mapping Framework. Technical Note 53, Computer Systems Research Institute, University of Toronto, November 1989.
....are systematically integrated into the development. They are represented as potentially conflicting or synergistic goals. In one of the top goals of Figure 1, for instance, Security is the sort and Account is the parameter which typically represents information items such as attributes [8, 9]. Now the developer can decompose the goal either on its sort or on its parameter. 2 We used the Subsort method to decompose the goal into three other goals for accuracy (the faithful reflection of information) confidentiality (guarding against unauthorized disclosure) and availability ....
K. L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos and Y. Vassiliou, "From Information System Requirements to Designs: A Mapping Framework." Information Systems, 16(4), 1991, pp. 429--461.
No context found.
K. L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos, Y. Vassiliou, "From Information System Requirements to Designs: A Mapping Framework." Information Systems, Vol. 16, No. 4, September--October 1991, pp. 429--461.
No context found.
K. L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos, Y. Vassiliou, "From Information System Requirements to Designs: A Mapping Framework." Information Systems, Vol. 16, 1991.
....in the requirements of efficiency (e.g. complexity theory, queuing theory) and reliability (e.g. fault tolerance, formal verification, recovery) has progressed quite far. Recently, some information system specific requirements such as data accuracy and security have also been investigated [Chung et al. 1991, Mylopoulos et al. 1992] A third approach is the half axiomatic, half empirical derivation of non functional requirements from processoriented theories of the firm, such as the theory of Critical Success Factors developed by Jack Rockart at MIT or the theory of value added chains introduced by ....
Chung, L., Katalagarianos, P., Mertikas, M., Mylopoulos, J., Vassiliou, Y.: From information systems requirements to design: a mapping framework. Information Systems 16, 4.
No context found.
K. Lawrence Chung, Panagiotis Katalagarianos, Manolis Marakakis, Michalis Mertikas, John Mylopoulos and Yannis Vassiliou, "From Information System Requirements to Designs: A Mapping Framework." Information Systems, Vol. 16, No. 4, 1991, pp. 429--461.
....it is the job of the systems analyst to not only formulate realistic functional and non functional requirements but also educate the user. detailed in [Vassiliou90] while the overall framework, its motivation, and an extensive example of a requirements specification and its design are given in [Chung91a]. In the present paper, we focus on NFRs their representation and utilization and their achievement by (composition of) methods which can cooperate or conflict, and present a detailed illustration of our goal oriented methodology. Systematic goal oriented approaches, in which the types of ....
....generalization, and classification. 3 Representation of Accuracy Requirements 4 Informal accuracy requirements are often ambiguous and inconsistent. For a formal specification, we may start with this initial definition: accuracy as a requirement for an 4 This section is adapted from [Chung91a]. information system reflects the faithfulness of the information maintained by the system with respect to the application domain . Unfortunately, this definition is not quite formal: what do reflects and faithfulness mean, and what is information Below we clarify our definitions; in ....
L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos, and Y. Vassiliou, From Information System Requirements to Designs: A Mapping Framework, Information Systems, Vol. 16, No. 3. Also Technical Report CSRI--245, Univ. of Toronto, Sept. 1990.
No context found.
K. Lawrence Chung, Panagiotis Katalagarianos, Manolis Marakakis, Michalis Mertikas, John Mylopoulos and Yannis Vassiliou, "From Information System Requirements to Designs: A Mapping Framework. " Information Systems, Vol. 16, No. 4, 1991, pp. 429--461.
No context found.
K. Lawrence Chung, Panagiotis Katalagarianos, Manolis Marakakis, Michalis Mertikas, John Mylopoulos and Yannis Vassiliou, "From Information System Requirements to Designs: A Mapping Framework." Information Systems, Vol. 16, No. 4, 1991, pp. 429--461.
....looks appealing to programmers. The system will be extended with a mapping tool. The aim of the mapping tool is to map the specification of his problem to an expression of the refinement meta language. A such tool will be interactive. Such mapping tools have been developed in other frameworks in [11], 91] for mapping requirements to designs. The system incrementally will increase its programming knowledge. Design decisions will be shifted from the programmer to the system. 7.4 Contributions This thesis presents a new schema based method of programming in logic which advances previous work ....
L. Chung, P. Katalagarianos, M. Marakakis, M. Mertikas, J. Mylopoulos and Y. Vassiliou, From Information System Requirements to Designs: A Mapping Framework, Information Systems, Volume 16, No. 4, 1991, pp.429-461.
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