|
Object Oriented Role Analysis And Modeling
The OOram (Object-oriented Role Analysis and Modeling) is a method, based on the concept of ''role'', for performing object-oriented modeling. (Presented at OOPSLA 1996 Workshop: ''Exploration of Framework Design Principles'') Originally (1989) coined ''Object Oriented Role Analysis, Synthesis and Structuring'' (OORASS), the method focuses on describing patterns of interaction without connecting the interaction to particular objects/instances. OOram was originally developed by Trygve Reenskaug (1996), a professor at the University of Oslo and the founder of the Norwegian IT company Taskon. The use of "roles" in OOram is similar in application to that of agent-oriented programming. Enterprise models created according to OOram may have a number of views, with each view presenting certain aspects of a model.Terje Totland (1997)5.2.8 Object-Oriented role analysis and modeling (OOram)Thesis, Norwegian University of Science and Technology (NTNU), Trondheim. The following ten views are p ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Taskon
{{Unreferenced, date=December 2009 Taskon was a Norwegian IT enterprise which developed systems using object-oriented technology Object-oriented programming (OOP) is a programming paradigm based on the concept of " objects", which can contain data and code. The data is in the form of fields (often known as attributes or ''properties''), and the code is in the form of p .... The company also provided advisory and consultancy services, products, and training within the field of object-oriented systems' development. Formed in 1986 by Trygve Reenskaug, Taskon's expertise was in the area of analysis, design, and implementation of component-based systems. As one of the UML Partners, Taskon helped with the standardization of the Unified Modeling Language (UML). The company's flagship product was OOram, a software package for the analysis and design of Object-Oriented systems, with support for the role-modeling concept. In addition to providing support for the modeling of complex sy ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
OOPSLA
OOPSLA (Object-Oriented Programming, Systems, Languages & Applications) is an annual ACM research conference. OOPSLA mainly takes place in the United States, while the sister conference of OOPSLA, ECOOP, is typically held in Europe. It is operated by the Special Interest Group for Programming Languages (SIGPLAN) group of the Association for Computing Machinery (ACM). OOPSLA is an annual conference covering topics related to object-oriented programming systems, languages and applications. Like other conferences, OOPSLA offers various tracks and many simultaneous sessions, and thus has a different meaning to different people. It is an academic conference, and draws doctoral students who present peer-reviewed papers. It also draws a number of non-academic attendees, many of whom present experience reports and conduct panels, workshops and tutorials. OOPSLA has been instrumental in helping object-oriented programming develop into a mainstream programming paradigm. It has also helpe ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Trygve Reenskaug
Trygve Mikkjel Heyerdahl Reenskaug (born 21 June 1930) is a Norwegian computer scientist and professor emeritus of the University of Oslo. He formulated the model–view–controller (MVC) pattern for graphical user interface (GUI) software design in 1979 while visiting the Xerox Palo Alto Research Center (PARC). His first major software project, "Autokon," produced a successful computer-aided design – computer-aided manufacturing (CAD/CAM) program which was first used in 1963, and continued in use by shipyards worldwide for more than 30 years. Reenskaug described his early Smalltalk and object-oriented programming conceptual efforts as follows: He has been extensively involved in research into object-oriented methods and developed the Object Oriented Role Analysis and Modeling (OOram) and the OOram tool in 1983. He founded the information technology company Taskon in 1986, which developed tools based on OOram. The OOram ideas matured and evolved substantially into the BabyU ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Kantega
Kantega is a Norwegian software corporation founded in 2003 with headquarters in Oslo. Kantega primarily develops bespoke software based on Java and lightweight application frameworks. It also has offices in Trondheim and Bergen. Kantega is a sponsor member of Liberty Alliance and WS-I. History Kantega was founded as an employee-owned company in 2003. However, the company can trace it roots back to Taskon—a Norwegian IT company founded in 1986. This company developed its own object orientation methodology ( OORam) and OO design tools, which had some international success. Taskon contributed its object-oriented methodology to the Object Management Group during the standardization process of UML, as part of a joint standards proposal with IBM and Ptech. Taskon merged with Numerica in 1998, and with Internet Aksess in 1999, which had launched the world's first public mobile web bank on September 24, 1999 using the emerging WAP standard. In December 1999, the company was bought by ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Agent-oriented Programming
Agent-oriented programming (AOP) is a programming paradigm where the construction of the software is centered on the concept of software agents. In contrast to object-oriented programming which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of agents. History Historically, the concept of agent-oriented programming and the idea of centering software around the concept of an Agent was introduced by Yoav Shoham within his Artificial Intelligence studies in 1990. His agents are specific to his own paradigm as they have just one method, with a single parameter. To quote Yoav Shoham from his paper in 1990 for a basic difference between AOP and OOP: :...agent-oriented programming (AOP), which can be viewed as a specialization of obje ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Enterprise Model
Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization. It deals with the process of understanding an organization and improving its performance through creation and analysis of enterprise models. This includes the modelling of the relevant business domain (usually relatively stable), business processes (usually more volatile), and uses of information technology within the business domain and its processes. Overview Enterprise modelling is the process of building models of whole or part of an enterprise with process models, data models, resource models and/or new ontologies etc. It is based on knowledge about the enterprise, previous models and/or reference models as well as domain ontologies using model representation languages. F.B. Vernadat (1997)Enterprise Modelling Languages ICEIMT'97 Enterprise Integration - Internation ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Object Modeling Language
An object-modeling language is a standardized set of symbols used to model a software system using an object-oriented framework. The symbols can be either informal or formal ranging from predefined graphical templates to formal object models defined by grammars and specifications. A modeling language is usually associated with a methodology for object-oriented development. The modeling language defines the elements of the model. E.g., that a model has classes, methods, object properties, etc. The methodology defines the steps developers and users need to take to develop and maintain a software system. Steps such as ''Define requirements'', ''Develop code'', and ''Test system''. It is common to equate the modeling language and the modeling methodology. For example, the Booch method may refer to Grady Booch's standard for diagramming, his methodology, or both. Or the Rumbaugh Object Modeling Technique is both a set of diagrams and a process model for developing object-oriented syst ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
View Model
A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of ''views'' to be used in the construction of a system architecture, software architecture, or enterprise architecture. A ''view'' is a representation of a whole system from the perspective of a related set of concerns.ISO/IEC/IEEE 42010:2011, Systems and so— Architecture description Since the early 1990s there have been a number of efforts to prescribe approaches for describing and analyzing system architectures. These recent efforts define a set of views (or viewpoints). They are sometimes referred to as architecture frameworks or enterprise architecture frameworks, but are usually called "view models". Usually a ''view'' is a work product that presents specific architecture data for a given system. However, the same term is sometimes used to refer to a view ''definition'', including the particular viewpoint and the corr ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose, developmental modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system. The creation of UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design. It was developed at Rational Software in 1994–1995, with further development led by them through 1996. In 1997, UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005, UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then the standard has been periodically revised to cover the latest revision of UML. In software engineering, most practitioners do not use UML, but instead produce informal hand drawn diagrams; these diagrams, however, often include elements from UML. History Before UML 1 ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
