This chapter starts with an overview of the design phase according to the functional and object o... more This chapter starts with an overview of the design phase according to the functional and object oriented methodology (FOOM) and presents the subphases and their products. Then, the chapter focuses on the design of transactions. First it describes what transactions are and how they can be identified and extracted from the object oriented data flow diagrams (OO-DFD). Afterwards, it explains how to map transaction diagrams to top-level descriptions, which detail their components and process logic. The transactions’ top-level descriptions will eventually become detailed descriptions of respective class methods. The chapter ends with additions to the data dictionary (DD) the class diagram due to the definition of the transactions.
Abstract The paper presents an interactive menu driven decision support system for Multiobjective... more Abstract The paper presents an interactive menu driven decision support system for Multiobjective Linear Programming (MOLP) problems. The main contribution of the system lies in the ease of interaction between the decision maker (DM) and the system which is achieved, in contrast with other systems, by DM directed construction of a weak order on system variables and objectives. In the interactive stage the DM points out which objective functions are to be improved relative to the candidate solutions presented. No tradeoff evaluations are required from the DM. In addition, priorities/preferences of variables and objectives can be modified throughout the solution process.
Chapter IV (Mapping Entity Relationship Diagrams to Class Diagrams) explains why it might be pref... more Chapter IV (Mapping Entity Relationship Diagrams to Class Diagrams) explains why it might be preferred to first create an ER diagram and then map it to a class diagram. The chapter then describes the mapping rules, demonstrating the mapping process with several comprehensive examples. Chapter V (Mapping Class Diagrams to Relational Schemas) explains the need to map a class diagram to a relational schema. Most of the chapter is dedicated to presenting and demonstrating the mapping rules based on which a relational schema (made of ...
In the analysis phase of the information system development, the user requirements are studied, a... more In the analysis phase of the information system development, the user requirements are studied, and analysis models are created. In most UML-based methodologies, the analysis activities include mainly modeling the problem domain using a class diagram, and modeling the user/functional requirements using use cases. Different development methodologies prescribe different orders of carrying out these activities, but there is no commonly agreed order for performing them. In order to find out whether the order of analysis activities makes any difference, and which order leads to better results, a comparative controlled experiment was carried out in a laboratory environment. The subjects were asked to create two analysis models of a given system while working in two opposite orders. The main results of the experiment are that the class diagrams are of better quality when created as the first modeling task, and that analysts prefer starting the analysis by creating class diagrams first.
This chapter deals with the design of the interfaces between the users and the system. First, it ... more This chapter deals with the design of the interfaces between the users and the system. First, it describes a method for the design of menus trees—for the entire system as well as for its subsystems. Then it describes how to design the inputs and outputs/reports of the systems. As a result, new classes of menus, forms, and reports are added to the class diagram.
... Decision Making Dov Shirtz, Ben Gurion University of the Negev Zigmund Bluvband, PhD, Advance... more ... Decision Making Dov Shirtz, Ben Gurion University of the Negev Zigmund Bluvband, PhD, Advanced Logistics Development Ltd ... He has published more than 70 papers and tutorials, and three books, latest "Quality Greatest hits" by Quality press. Dov Shirtz, ...
A method for subsystem design is described. The method extends the ADISSA methodology for system ... more A method for subsystem design is described. The method extends the ADISSA methodology for system analysis and design (see P. Shoval, Information Systems, vol.13, p.81-95, 1988), and involves (a) declaration of the transactions belonging to the subsystem, (b) the design of a submenu-tree interface, and (c) design of a database subschema. The method is supported by software tools part of ADISSA PC-based CASE tools.<<ETX>>
International journal of man-machine studies, Nov 1, 1990
A systematic method for designing a menu-tree interface is presented. The method is part of ADISS... more A systematic method for designing a menu-tree interface is presented. The method is part of ADISSA, a comprehensive systems analysis and design methodology, which is based on the use of modified hierarchical data flow diagrams (DFD). Thus, the functional structure of the designed menu-tree is consistent with the functional structure and the user-model of the system. The method consists of several steps, beginning with an initial menu-tree derived automatically from DFDs, which is then improved and modified, taking into consideration ...
This chapter starts with an overview of the design phase according to the functional and object o... more This chapter starts with an overview of the design phase according to the functional and object oriented methodology (FOOM) and presents the subphases and their products. Then, the chapter focuses on the design of transactions. First it describes what transactions are and how they can be identified and extracted from the object oriented data flow diagrams (OO-DFD). Afterwards, it explains how to map transaction diagrams to top-level descriptions, which detail their components and process logic. The transactions’ top-level descriptions will eventually become detailed descriptions of respective class methods. The chapter ends with additions to the data dictionary (DD) the class diagram due to the definition of the transactions.
Abstract The paper presents an interactive menu driven decision support system for Multiobjective... more Abstract The paper presents an interactive menu driven decision support system for Multiobjective Linear Programming (MOLP) problems. The main contribution of the system lies in the ease of interaction between the decision maker (DM) and the system which is achieved, in contrast with other systems, by DM directed construction of a weak order on system variables and objectives. In the interactive stage the DM points out which objective functions are to be improved relative to the candidate solutions presented. No tradeoff evaluations are required from the DM. In addition, priorities/preferences of variables and objectives can be modified throughout the solution process.
Chapter IV (Mapping Entity Relationship Diagrams to Class Diagrams) explains why it might be pref... more Chapter IV (Mapping Entity Relationship Diagrams to Class Diagrams) explains why it might be preferred to first create an ER diagram and then map it to a class diagram. The chapter then describes the mapping rules, demonstrating the mapping process with several comprehensive examples. Chapter V (Mapping Class Diagrams to Relational Schemas) explains the need to map a class diagram to a relational schema. Most of the chapter is dedicated to presenting and demonstrating the mapping rules based on which a relational schema (made of ...
In the analysis phase of the information system development, the user requirements are studied, a... more In the analysis phase of the information system development, the user requirements are studied, and analysis models are created. In most UML-based methodologies, the analysis activities include mainly modeling the problem domain using a class diagram, and modeling the user/functional requirements using use cases. Different development methodologies prescribe different orders of carrying out these activities, but there is no commonly agreed order for performing them. In order to find out whether the order of analysis activities makes any difference, and which order leads to better results, a comparative controlled experiment was carried out in a laboratory environment. The subjects were asked to create two analysis models of a given system while working in two opposite orders. The main results of the experiment are that the class diagrams are of better quality when created as the first modeling task, and that analysts prefer starting the analysis by creating class diagrams first.
This chapter deals with the design of the interfaces between the users and the system. First, it ... more This chapter deals with the design of the interfaces between the users and the system. First, it describes a method for the design of menus trees—for the entire system as well as for its subsystems. Then it describes how to design the inputs and outputs/reports of the systems. As a result, new classes of menus, forms, and reports are added to the class diagram.
... Decision Making Dov Shirtz, Ben Gurion University of the Negev Zigmund Bluvband, PhD, Advance... more ... Decision Making Dov Shirtz, Ben Gurion University of the Negev Zigmund Bluvband, PhD, Advanced Logistics Development Ltd ... He has published more than 70 papers and tutorials, and three books, latest &quot;Quality Greatest hits&quot; by Quality press. Dov Shirtz, ...
A method for subsystem design is described. The method extends the ADISSA methodology for system ... more A method for subsystem design is described. The method extends the ADISSA methodology for system analysis and design (see P. Shoval, Information Systems, vol.13, p.81-95, 1988), and involves (a) declaration of the transactions belonging to the subsystem, (b) the design of a submenu-tree interface, and (c) design of a database subschema. The method is supported by software tools part of ADISSA PC-based CASE tools.<<ETX>>
International journal of man-machine studies, Nov 1, 1990
A systematic method for designing a menu-tree interface is presented. The method is part of ADISS... more A systematic method for designing a menu-tree interface is presented. The method is part of ADISSA, a comprehensive systems analysis and design methodology, which is based on the use of modified hierarchical data flow diagrams (DFD). Thus, the functional structure of the designed menu-tree is consistent with the functional structure and the user-model of the system. The method consists of several steps, beginning with an initial menu-tree derived automatically from DFDs, which is then improved and modified, taking into consideration ...
Uploads
Papers by Peretz Shoval