Flexible Organizations Through Object-oriented and Transaction-oriented Information Systems

1997 ◽  
pp. 393-411
Author(s):  
Otto K. Ferstl ◽  
Elmar J. Sinz
Keyword(s):  
Information Systems ◽  
Object Oriented ◽  
Flexible Organizations

Causal Mapping for the Investigation of the Adoption of UML in Information Technology Project Development

2005 ◽  
pp. 233-262 ◽  
Author(s):  
Tor J. Larsen ◽  
Fred Niederman
Keyword(s):  
Information Technology ◽  
Information Systems ◽  
Object Oriented ◽  
Collection Method ◽  
Causal Mapping ◽  
Analysis And Design ◽  
Technology Project ◽  
Information Technology Project ◽  
Application Developers ◽  
Object Oriented Analysis

This research project gathered data about the use of UML and object-oriented analysis and design as the approach to the development of information systems. The data collection method consisted of interviews with information systems application developers with wide ranging differences in background. The authors used causal mapping for analysis of the data gathered. This chapter focuses on the authors’ experiences with causal mapping as a method for exploring issues and relationships. Causal mapping was also used to document tips on its use illustrating these with findings regarding UML and object-oriented analysis and design in particular.

Object Oriented Requirements Analysis

2011 ◽  
pp. 1-24
Author(s):  
Edward R. Sim
Keyword(s):  
Information Systems ◽  
Object Oriented ◽  
Systems Development ◽  
Requirements Analysis ◽  
Design And Development ◽  
New Techniques ◽  
System Validation ◽  
System Requirements ◽  
Object Oriented Analysis

The ability to correctly identify system requirements is seen by most Information Systems (IS) researchers and practitioners as essential to the design and development of effective information systems (Yadav, Bravoco et al. 1988; Vessey 1994). Requirements are used to drive all subsequent stages of systems development and are critical to system validation. Incorrect requirements or poorly specified requirements usually produce systems that require major revisions or are abandoned entirely (Pressman 1996). Recently, many new techniques and methodologies have been introduced to assist analysts and users in efforts to identify and specify system requirements (Coad, North et al. 1995) (Pancake 1995). One of the newest approaches to be used in this effort to improve requirements analysis is the application of object oriented analysis (OOA).

Is There a Difference Between the Theoretical and Practical Complexity of UML?

2011 ◽  
pp. 243-264
Author(s):  
Keng Siau ◽  
John Erickson ◽  
Lih Yunn Lee
Keyword(s):  
Information Systems ◽  
Object Oriented ◽  
Modeling Language ◽  
Modeling Languages ◽  
Theoretical Maximum ◽  
Complex Information ◽  
Practical Complexity

An on-going and major problem faced by information systems developers and business users alike is reaching a clear and consensual understanding of the system by both groups. This can be difficult because the businesses are (typically) process driven, while the systems are (increasingly) object-oriented. Enter modeling. Modeling is one way of presenting complex information in a way that enhances or eases understanding. But, even models can be extremely complex, and the underlying tools and modeling languages are not any less complex. This chapter investigates the possibility that modeling languages can be simplified by considering that not all of the “words” in the language are used all of the time. If theoretical (maximum) represents all the words in a modeling language, then this chapter suggests that there might exist a more use-based (we name it practical complexity) subset that represents an easier to learn and use subcomponent of the language.

Sign in / Sign up

Export Citation Format

Share Document