The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
The purpose of this panel is to present a broad range of best practices of SOA strategization and operationalization in the use of Web services in real-world SOA implementations. The focus is on the common challenges and issues encountered in SOA projects. Topics include, but are not limited to, tenets, methodology, architecture, service management, standards, tools, process, organization, governance,...
The purpose of this panel is to present a broad range of best practices of SOA strategization and operationalization in the use of Web services in real-world SOA implementations. The focus will be on the common challenges and issues encountered in SOA projects. Topics include, but are not limited to, tenets, methodology, architecture, service management, standards, tools, process, organization, governance,...
As the code written today becomes part of tomorrow's inexorably growing pile of legacy, preserving these stories becomes increasingly important. It's costly to rely on informal storytelling to preserve and communicate important decisions; it's incredibly costly to try to recreate those decisions and their rationale when the storytellers themselves are gone. Insofar as a software development organization...
To set the context for the discussion that follows, there are some fundamentals worth repeating. The author talked about each of these to some degree in previous columns, so let me summarize here: 1) all architecture is design, but not all design is architecture. A system's architecture is defined by its significant design decisions, where in the author's experience, "significant" is measured...
SEAM is an enterprise architecture method based on RM-ODP part 2. In this paper, we present an example of a SEAM hierarchical model where the behavioral part is formalized in Alloy. We introduce four kinds of actions and their relationships to properties that specify object state. We show that the Alloy formalization enables us to check that the SEAM model conforms to the required aspects of the universe...
Like RM-ODP [1], enterprise architecture (or EA for short) has its own perspectives as a basic construct for its architecture definition to represent areas of concern. In this paper, difference between RM-ODP and one concrete example EA, and applicability of Use of UML for ODP system specifications [2] (or UML4ODP in short) standard to the example EA, are discussed. Several additional diagrams that...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.