Automated Testing of Computer Telephony Integrated Systems
|
|
- Isabel Candice Lindsey
- 3 years ago
- Views:
Transcription
1 An Automated Testing Environment for CTI Systems Using Concepts for Specification and Verification of Workflows Oliver Niese 1, Tiziana Margaria 1, Andreas Hagerer 1, Markus Nagelmann 1, Bernhard Steffen 2, Georg Brune 3 and Hans-Dieter Ide 3 1 METAFrame Technologies GmbH, Dortmund, Germany {ONiese, TMargaria, AHagerer, MNagelmann}@METAFrame.de 2 Chair of Programming Systems, University of Dortmund, Germany Steffen@cs.uni-dortmund.de 3 Siemens AG, Witten {Georg.Brune, Hans-Dieter.Ide}@wit.siemens.de Abstract. In this paper we present an automated testing environment for the system level test of Computer Telephony Integrated applications. Its novelty consists of a coordinative test management layer that instantiates a general-purpose environment for the specification and verification of workflows in the testing domain. This results in a test environment that does not only control the individual test tools but the whole life-cycle of functional system-level tests, comprising test design, test generation, test execution, test evaluation and test reporting. Special attention is devoted to the simplification of the test cases design and the checking of admissibility criteria, interdependencies between the actions of test cases, and assumptions about the state of the system's resources. The key features of our testing environment, coarse grain, workflow-like test case representation and the validation and formal verification capabilities, are illustrated along a concrete industrial application. 1 Introduction The increasing complexity of today's testing scenarios for telephony systems demands for an integrated, open and flexible approach to support the management of the overall test process, i.e. specification of tests, execution of tests and analysis of test results. Furthermore, systems under test (SUT) become composite (e.g. including Computer Telephony Integrated (CTI) platform aspects), embedded (due to hardware/software codesign practices), reactive, and run on distributed architectures (e.g. client/server architectures). As a consequence, it becomes increasingly unrealistic to restrict the consideration of the testing activities to single units of the systems, since complex subsystems affect each other and require scalable, integrated test methodologies. The requirements discussed in this paper exceed the capabilities of today's testing tools. To our knowledge there exist neither commercial nor academic tools providing comprehensive support for the whole system-level test process. In particular, most research on test automation for telecommunication systems concentrates on the generation of test cases and test suites on the basis of a formal model of the system: academic tools, like TORX [12], TGV [3], Autolink [5], as well as commercial ones like Telelogic Tau [10] presuppose the existence of fine-granular system models in terms of either automata or SDL descriptions, and aim at supporting the generation of corresponding test cases and test suites. This approach failed to enter practice in the scenario we are considering here, because it did not fit the current system design practice. In order to overcome this hurdle, we aim at a formal methods-controlled, component-based test design on top of a library of elementary but intuitively understandable test case fragments. This establishes a coarsegranular meta-level on which test engineers are used to think, test cases and test suites can be easily composed, test scenarios can be configured and initialized,
2 critical consistency requirements including version compatibility and frame conditions for executability are easily formulated, and consistency is fully automatically enforced via model checking and error diagnosis. Already after a few months of cooperation this coarse-granular test management support was successfully put into practice, drastically strengthening the pre-existing test environment, and without requiring any fine granular formal model of the involved systems, which, in fact, does not exist in the considered scenario. We are not aware of any other test environment systematically addressing the needs of coordinating the highly heterogeneous test process, let alone on the basis of formal methods. The paper is organized as follows: Sect. 2 describes our application domain, system level testing of telephony systems, presents a concrete scenario, and introduces the requirements to the corresponding integrated testing environment. Sect. 3 presents our test coordinator tool and outlines the foundations of its design and analysis core. Sect. 4 illustrates the use of the environment. Finally, Sect. 5 draws some conclusions. Test Coordinator LAN Switch Application PC s ISDN Network Application Server Fig. 1. Structure of a CTI system 2 System-Level Testing of Telephony Systems As a typical example of an integrated CTI platform, Fig. 1 shows a midrange telephone switch and its environment. The switch is connected to the ISDN telephone network or, more generally, to the public service telephone network (PSTN), and acts as a normal telephone switch to the phones. Additionally, it communicates directly via a LAN or indirectly via an application server with CTI applications that are executed on PCs. Like the phones, CTI applications are active components: they may stimulate the switch (e.g. initiate calls), and they react to stimuli sent by the switch (e.g. notify incoming calls). In a system level test it is therefore necessary to investigate the interaction between such subsystems. Typically, each participating subsystem requires an individual test tool. Thus in order to test systems composed of several independent subsystems one must be able to coordinate a heterogeneous set of test tools in a context of heterogeneous platforms. This task exceeds the capabilities of today's commercial test management tools: they typically cover only the needs of specific subsystems and of their immediate periphery. The remainder of this section explains and structures the corresponding central requirements for practiceoriented test management along the typical life cycle of tests: test case design, test organization, and test coordination.
3 2.1 Development and Design of Test Cases The design of test cases, i.e., specifying which control or inspection activities must be performed on the system-under-test (SUT) and in which order, should neither require programming skills nor any knowledge of how to apply/use a specific test tool. In particular, concrete requirements concern the following areas: Definition Test cases should be graphically specifiable at the level of SUT-usage. The system should provide a set of elementary, universal building blocks that correspond to actions stimulating the subsystems or to verification actions of some state changing behavior of the subsystems. Such building blocks should be combined graphically to yield executable test cases. Furthermore, a generalization of their use by means of parameters should be supported. Reuse A macro mechanism should support the reuse of (partial) test cases. This automatically supports a hierarchical design style. Validation Consistency checks of tests cases at design time should guide the designer towards building (only) plausible test cases. Variation Rule-based controlled as well as randomized parameter variation should enhance the expressiveness of the test results. 2.2 Test Organization The central organizational aspects of the test process are: Version control Beside the test cases themselves, many other files referenced and used in test cases have to be organized, e.g. configuration files and test documentation. All these files evolve throughout the test process. Therefore, it is important to capture the history of changes and the dependencies between versions. Configuration management It is mandatory, especially when considering integrated tests, that the SUT is in a well defined state before a test will be executed. This is a non-trivial task due to the heterogeneity and distribution of the components and their complex interactions. Therefore, initialization is a distributed problem and, in general, the initialization of one component affects the state of the others. Structuring of tests The set of test cases must be structured to provide a simple mechanism to build test suites from test cases according to a variety of criteria, e.g. regression test or feature test for a particular test suite. eliminate redundant test cases. This may dramatically reduce the execution time of test suites which is important in a scenario in which new versions of the switch software must continuously be validated against the CTI applications. 2.3 Test Execution Coordination Basically, an automated test environment must support the following aspects of an execution of test cases: Initialization SUT components and test tools must be set into a well-defined starting state. Fast reinitialization in case of repetition of a test case must be possible. Execution Test tools of different abilities and different interconnection variants that are executed distributedly must be controlled: test engineers must be able to control each tool's activities and to determine state and state changes of SUT components for verification purposes. Reactions of SUT components on stimuli must be retrieved and evaluated. The evaluation results shall control succeeding test case steps. Timing constraints must be taken into account when stimulating a SUT component. Reporting Reporting shall record a test run and shall facilitate documentation and tracking of defects by providing sufficient details. A characterization of the SUT, i.e., versions of SUT components and of test tools, must be documented. Result and data of each step of the test case must be logged. The status of a test run must be summarized.
4 3 The Test Coordinator The realization of an adequate management layer for an automated test environment was attacked according to pragmatic criteria, of vital importance in an industrial development environment: first of all, the test environment should offer a viable execution environment (Test Execution Coordination Requirements), ease the test design phase (Test Design Requirements), then scale up to the required complexity (Test Organization Requirements). Fig. 2. Structure of the test environment Formally, test cases can be modeled as workflows and specified graphically as flow graphs whose nodes represent elementary actions governing the stimulation of SUT components, and whose edges represent branching conditions steering the flow of control. Accordingly, we built on an existing general purpose environment for the management of complex workflows, METAFrame Technologies' Agent Building Center (ABC) [2,4,7]. This way we were able to demonstrate in a short time the practical satisfiability of the kernel requirements concerning test design and test coordination. In fact the currently available Test Coordinator which constitutes the test management layer of the test environment (see Fig. 2) includes a specialization of the ABC for this application domain, i.e. system level testing of telephony systems. As it will be described in Sect. 4, the test management layer has already proved to be capable of coordinating different control and inspection activities of integrated system-level tests. Fig. 2 shows the general architecture of the Test Coordinator. The SUT is composed of several subsystems, e.g. a telephone switch in cooperation with a CTI application. Each subsystem is controlled via its own test tools 1. The test tools have access to external interfaces as well as to some internal ones. They are steered by the Test Coordinator. 3.1 ABC's Enabling Characteristics The Agent Building Center already encompasses most of the features a testing environment requires: Workflow management The ABC enables the specification, classification, verification, and execution of workflows, in particular comprising graphical specification of workflows, using elementary building blocks to which application specific interpretations and execution statements are assigned. support of taxonomies of building blocks as well as of workflows. consistency checking by means of model checking. control flow driven execution of workflows by means of a tracer module. 1 Test tools can be e.g. a proprietary hardware tracer for testing the switch or GUI test tools such as Rational SQA Robot [9] or Mercury Winrunner [8] for the test of applications.
5 Version control A version control system access layer is part of the ABC. Communication mechanisms A CORBA access layer is integrated in the ABC. This provides access to the use of processing capabilities of remote applications in building blocks Extensibility The ABC can be extended by means of adapters that provide new functionality and hide implementation details to the workflow management environment. Furthermore, the following characteristics of the ABC were identified to be of major importance: Behavior-Oriented Development In general, application development in the ABC, which goes far beyond the domain of CTI applications [2,7], consists of behavior-oriented combination of building blocks on a coarse granular level. Building blocks are identified on a functional basis, understandable to application experts, and usually encompass a number of classical programming units (be they procedures, classes, modules, or functions). They are organized in application-specific collections (palettes). In contrast to (other) component-based approaches, e.g., for object-oriented program development, ABC focuses on the dynamic behavior: (complex) functionalities are graphically stuck together to yield flow graph-like structures embodying the application behavior in terms of control. This graph structure is independent of the paradigm of the underlying programming language. In particular, we view this flow graph structure as a control-oriented coordination layer on top of the enforced dataoriented communication mechanisms. Accordingly, the purely graphical combination of building blocks' behaviors happens at a more abstract and intuitive level. Incremental Formalization The successive enrichment of the application-specific development environment is two-dimensional. Beside the library of application-specific building blocks, which dynamically grows whenever new functionalities are made available, ABC supports the dynamic growth of a hierarchically organized library of constraints, controlling and governing the adequate use of these building blocks within application programs. This library is intended to grow with the experience gained while using the environment, e.g., detected errors, strengthened policies, and new building blocks may directly impose the addition of constraints. It is the possible looseness of these constraints which makes them highly reusable and intuitively understandable. Here we consciously privilege understandability and practicality of the specification mechanisms over their completeness. Library-Based Consistency Checking Throughout the behavior-oriented development process ABC offers access to mechanisms for the verification of libraries of constraints via model checking. The model checker individually checks hundreds of typically very small and application- and purposespecific constraints over the flow graph structure. This allows concise and comprehensible diagnostic information in the case of a constraint violation, in particular as the information is given at the application rather than at the programming level. Taken together, these characteristics of the basic tool were actually the real enablers for the project results, in particular, as they provided a means to seamlessly coordinate the cooperation between ABC team, CTI experts, test designers, and test engineers. 3.2 Domain Modeling: the Testing Application Some effort had to be spent for instantiating the ABC as required for the integrated test of CTI systems, i.e., to implement the actual Test coordinator. This mainly consisted of the design of some applicationspecific building blocks (in the domain of system testing called test blocks) and the formulation of the general framework which must be enforced during test case design and test suite design. Test Building Blocks The ABC team, the CTI experts, and the test designers define and also classify the test blocks occurring in the testing experiments, typically according to domain-specific criteria like tool or application they relate to, software version, or specific hardware or software requirements, origin (where they were developed). Here, the classification mostly reflects a test block's intent for the specific application area. The resulting classification scheme is a simplified version of the taxonomies used in [2] and [6]. Test blocks available for the design of test cases are organized in so called palettes, as shown in Fig. 3.
6 Preparation of Consistency Checks The palettes are central to build models (test models), and they constitute a vocabulary for the definition of constraints in terms of modal formulas. Typically, the design of the classification scheme and of the constraints goes hand in hand with the definition of aspect-specific views and filters: both are mutually supportive means to an application specific structuring of the design process. A more formal and detailed description of the constraints definition and expressiveness is given in [14]. Here it suffices to know that in the ABC test models are subject to local and global constraints which, in conjunction, offer means to identify critical patterns in the test model already during the early design phase. Local Constraints Local constraints specify single test blocks in the context of their immediate neighbors: they capture a test block's branching potential as well as its admissible subsequent parameterization. Their correctness is checked by means of specific algorithms, which can be activated at need. The verification of local constraints is invoked automatically during the verification process of global properties. Global Constraints Global constraints allow users to specify causality, eventuality and other relationships between test blocks, which may be necessary in order to guarantee frame conditions for e.g., executability and version compatibility. A property a test model has to fulfill is a global constraint if it does not only involve the immediate neighborhood of a test block in the test model 2, but also relations between test blocks which may be arbitrarily distant and separated by arbitrarily heterogeneous submodels. The classification of constraints into local and global is important, since each kind requires a specific treatment. The on-line verification during the design of a new test, however, captures both kinds of constraints. The treatment of global properties is required in order to capture the essence of the expertise of designers about do's and don'ts of test creation, e.g. which test blocks are incompatible, or which can or cannot occur before/after some other test blocks. Such properties are rarely straightforward, sometimes they are documented as exceptions in thick user manuals, but more often they are not documented at all, and have been discovered at a hard price as bugs of previously developed tests. They are perfect examples of the kind of precious domain-specific knowledge that expert designers accumulate over the years, and that is therefore particularly worthwhile to include in the test design environment for successive automatic reuse. In the ABC such properties are gathered in Constraint Libraries which can be easily updated and which are automatically accessed by ABC 's model checker during the verification step. 4 The Integrated Testing Environment ITE The ITE, Integrated Testing Environment, is the result of the instantiation of the ABC in the domain of system-level integrated tests. It is an environment for automated and integrated testing primarily dedicated but not limited to CTI systems. A short description of its operation is contained in [15]. In the following we concentrate on test design, verification, and execution. 4.1 Test Case Design As shown in Fig. 3, accessible from the Test Coordinator's GUI, the test blocks occurring in test cases are presented to the test designers and test engineers according to their organization in palettes. Test designers construct test cases graphically, by drag-and-drop of the desired test blocks from the palettes onto the test graph canvas. The control flow design to steer the execution is also done graphically, by defining the workflows contained in the test case graph. This is done by connecting the test blocks through edges, and the data and events steering the branching, done by configuring each test block's internal parameters. 2 The neighbourhood consists of the set of all the predecessors/successors of a test block along all paths in the model.
7 Fig. 3. Design of test cases: a test graph and a test block palette For the CTI system to be tested, a library of test blocks has been issued that includes test blocks representing and implementing, e.g. Common actions Initialization of test tools, system components, test cases and general reporting functions, Switch-specific actions Initialization of switches of different extensions, Call-related actions Initiation and pick up of calls via a PBX-network or a local switch, CTI application-related actions Miscellaneous actions to operate a CTI application via its graphical user interface, e.g., log-on/log-off of an agent, establish a conference party, initiate a call via a GUI, or check labels of GUI-elements. 4.2 Test Case Verification Test case design is constantly accompanied by verification of the correctness and consistency of the test graph in an aspect-driven fashion: the testing expert chooses one or more constraints of interest out of the constraint library, expressing single aspects of the test case under construction, checks online the correctness of the current test graph wrt. these constraints, and modifies it in case of mistakes. As shown in Fig. 4, a constraint violation has been detected for the test case under design. Concrete information concerning the mistake and its possible location is also provided. This is iterated until all relevant aspects have been treated. Due to the on-line verification with the model checker, constraint violations are immediately detected at design time, without need of actually executing the test case.
8 Fig. 4. Checking a test case's consistency Typical constraints stored in the ITE's constraint library are: Legal Test Cases This constraint class defines the characteristics of a correct test case independently of any particular system-under-test. Specifically, testing implies an evaluation of the runs by means of verdicts. This leads to constraints like Every test run, i.e. every path in the test graph, must at least encounter passed or failed.. Particularly, the constraint Once a verdict is assigned it cannot be changed. ensures, that verdict points are disposed in a non-ambiguous and non-contradictory way along each path in the graph. POTS Test Cases This constraint class defines the characteristics of the correct functioning of Plain Old Telephone Services (POTS), which build the basis of any CTI application behavior (e.g., Digitstest-blocks are only allowed to appear after a corresponding offhook-test-block, making sure that the phone is always properly initialized, An onhook can only be executed when an offhook was initiated for this device before.). Fig. 4 demonstrates a model checker-produced counterexample for this property in terms of a violating path. Service Specific Test Cases In addition to POTS, modern midrange telephone systems include an amazing number of additional services: signaling of an additional incoming call (a feature known as Call Waiting), displaying the caller's number for incoming calls in ISDN systems (Calling Number Delivery), and many more. Testing such a telephone system means evaluating the correct behavior of a set of phones in the context of one or more of those activated features, which is again described as a collection of sets of constraints.
9 4.3 Test Execution In the ITE, designed test cases are immediately executable by means of ABC's tracer module. Starting at a dedicated test block, the tracer proceeds from test block to test block. Fig. 5. Execution of a test case: start phase Fig. 5 and Fig. 6 show an example of the stepwise execution of a test case. Here we consider a distributed call center application, in this case a client-server CTI application called ACD Agent, which runs on different computers than the Test Coordinator. In this test we emulate a human call center agent with identifier AGENT 500 and handle some actions via the GUI of the PC application. Window 3 of Fig. 5 shows one of the windows appearing on this agent's computer screen: the agent can e.g. configure his workplace and take up or release a work session. The test case graph for this CTI application is shown in Window 1. The Test Coordinator's Tracer-window (Window 2) controls the execution of the test case: the test block executed last is highlighted in the test graph window (in this case the start node) and its name is displayed in the box of the Tracer-window underneath the label Current.
10 Fig. 6. Execution of a test case: execution phase In Fig. 6 a call that has been initiated by the test tool Hipermon via an S0-interface (at test block s0makecall) is assigned to the agent AGENT 500. In the highlighted test block, the emulated human agent answers the call. Some information concerning the caller is displayed in Window 3, the original window of the agent's CTI application. When executing a test graph, a detailed report is prepared in form of a test protocol. For each test block executed by the tracer, all relevant data (its execution time, its name, the version of the files associated with the test block, the block's parameter assignments, and the processed data) are written to the protocol for later analysis and reuse. 5 Conclusion We have presented a new coarse grain approach to automated integrated testing, which combines three paradigms: workfllow-oriented, library-based test design in a visual programming environment on a coarse granular level, incremental formalization through successive enrichment of a special-purpose environment for application-specific test development and execution, and library-based consistency checking, allowing the continuous verification of application- and aspect-specific frame conditions by means of model checking. The resulting Integrated Testing Environment (ITE) for automated testing has been illustrated along the functional testing of a Call Center application, a real life industrial example. `Conditio sine qua non for the acceptance of the environment on the field was the low threshold for the introduction of the new testing methodology: neither initial complex preparations like the (complete) formal specifications of the SDL approach, nor (drastic) changes of habit are required. Together with the immediate improvement in productivity and quality resulting from the shift of the level of operation
11 from loose manually operated actions and scripting directives to the aspect- and application specific coarse granular graphical design of global flows on the basis of elementary test actions convinced the testing experts and system engineers of the power of the new approach: the ITE was put into operation already nine month after the constituting meeting for the project. Currently, we are focusing on the careful evaluation of the ITE during its practical use in Siemens test laboratories in order to evaluate its impact in more detail and to identify the most significant points for improving the overall test process. References 1. S. Gladstone: Testing Computer Telephony Systems and Networks, Telecom Books, B. Steffen, T. Margaria, V. Braun: The Electronic Tool Integration Platform: Concepts and Design, Int. Journ. on Software Tools for Technology Transfer (STTT), Vol. 1 N. 1+2, Springer Verlag, November 1997, pp J.-C. Fernandez, C. Jard, T. Jeron and C. Viho: An Experiment in Automatic Generation of Test Suites for Protocols with Verification Technology, Science of Computer Programming, 29, B. Steffen, T. Margaria, V. Braun, and N. Kalt: Hierarchical service definition, Annual Review of Communication, Int. Engineering Consortium (IEC), Chicago (USA), 1997, pp M. Schmitt, B. Koch, J. Gabowski, and D. Hogrefe: Autolink - A Tool for Automatic and Semiautomatic Test Generation from SDL-Specifications, Technical Report A-98-05, Medical Univ. of Lübeck, Germany, T. Margaria, B. Steffen: Backtracking-free Design Planning by Automatic Synthesis in META- Frame, Proc. FASE'98, Int. Conf. on Fundamental Aspects of Software Engineering, Lisbon, LNCS 1382, Springer Verlag, 1998, pp B. Steffen, T. Margaria: METAFrame in Practice: Intelligent Network Service Design, In Correct System Design -- Issues, Methods and Perspectives, LNCS 1710, Springer Verlag, 1999, pp Mercury Interactive: Winrunner Rational, Inc.: The Rational Suite description, Telelogic: Telelogic Tau Object Management Group: The Common Object Request Broker: Architecture and Specification, Revision 2.3, Object Management Group, J. Tretmans and A. Belinfante: Automatic testing with formal methods, In EuroSTAR'99: 7 th European Int. Conference on Software Testing, Analysis & Review. EuroStar Conferences, Galway, Ireland, November 8--12, S.-L. Chou, Y.-B. Lin: Computer Telephony Integration and its Applications, IEEE Communications Surveys & Tutorials, Vol. 3, No. 1, O. Niese, B. Steffen, T. Margaria, A. Hagerer, G. Brune, H.-D. Ide: Library-based Design and Consistency Checking of System-level Industrial Test Cases, to be presented at FASE 2001, Int. Conference on Fundamental Approaches to Software Engineering. Genova (I), Apr. 2-6th Proceedings appear as Volume of the Lecture Notes in Computer Science, Springer Verlag, Heidelberg (D). 15. O. Niese, M. Nagelmann, A. Hagerer, K. Strunck, W. Goerigk, A. Erochok, B. Hammelmann: Demonstration of an Automated Integrated Testing Environment for CTI Systems, to be presented at FASE 2001, Int. Conference on Fundamental Approaches to Software Engineering. Genova (I), Apr. 2-6th Proceedings appear as Volume of the Lecture Notes in Computer Science, Springer Verlag, Heidelberg (D).
Demonstration of an Automated Integrated Test Environment for Web-based Applications
Demonstration of an Automated Integrated Test Environment for Web-based Applications Tiziana Margaria 1,2, Oliver Niese 2, and Bernhard Steffen 2 1 METAFrame Technologies GmbH, Dortmund, Germany TMargaria@METAFrame.de
More informationEfficient Regression Testing of CTI-Systems: Testing a complex Call-Center Solution
Efficient Regression Testing of CTI-Systems: Testing a complex Call-Center Solution Andreas Hagerer 1, Tiziana Margaria 1, Oliver Niese 2, Bernhard Steffen 2, Georg Brune 3 and Hans-Dieter Ide 3 1 METAFrame
More informationAutomated Functional Testing of Web-based Applications
Automated Functional Testing of Web-based Applications Oliver Niese 1, Tiziana Margaria 1,2, Bernhard Steffen 2 1 METAFrame Technologies GmbH, Borussiastr. 112, 44149 Dortmund, Germany, {oniese,tmargaria}@metaframe.de
More informationjeti: A Tool for Remote Tool Integration
jeti: A Tool for Remote Tool Integration Tiziana Margaria 1, Ralf Nagel 2, and Bernhard Steffen 2 1 Service Engineering for Distributed Systems, Institute for Informatics, University of Göttingen, Germany
More informationComponent-based Development Process and Component Lifecycle Ivica Crnkovic 1, Stig Larsson 2, Michel Chaudron 3
Component-based Development Process and Component Lifecycle Ivica Crnkovic 1, Stig Larsson 2, Michel Chaudron 3 1 Mälardalen University, Västerås, Sweden, ivica.crnkovic@mdh.se 2 ABB Corporate Research,
More informationIFS-8000 V2.0 INFORMATION FUSION SYSTEM
IFS-8000 V2.0 INFORMATION FUSION SYSTEM IFS-8000 V2.0 Overview IFS-8000 v2.0 is a flexible, scalable and modular IT system to support the processes of aggregation of information from intercepts to intelligence
More informationSERENITY Pattern-based Software Development Life-Cycle
SERENITY Pattern-based Software Development Life-Cycle Francisco Sanchez-Cid, Antonio Maña Computer Science Department University of Malaga. Spain {cid, amg}@lcc.uma.es Abstract Most of current methodologies
More informationSoftware Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: 0306211(Computer Programming 2).
0305203 0305280 0305301 0305302 Software Engineering/Courses Description Introduction to Software Engineering Prerequisite: 0306211(Computer Programming 2). This course introduces students to the problems
More informationMDE Adoption in Industry: Challenges and Success Criteria
MDE Adoption in Industry: Challenges and Success Criteria Parastoo Mohagheghi 1, Miguel A. Fernandez 2, Juan A. Martell 2, Mathias Fritzsche 3 and Wasif Gilani 3 1 SINTEF, P.O.Box 124-Blindern, N-0314
More informationAbstract. Introduction
CODATA Prague Workshop Information Visualization, Presentation, and Design 29-31 March 2004 Abstract Goals of Analysis for Visualization and Visual Data Mining Tasks Thomas Nocke and Heidrun Schumann University
More informationManaging Large Imagery Databases via the Web
'Photogrammetric Week 01' D. Fritsch & R. Spiller, Eds. Wichmann Verlag, Heidelberg 2001. Meyer 309 Managing Large Imagery Databases via the Web UWE MEYER, Dortmund ABSTRACT The terramapserver system is
More informationService Level Agreements based on Business Process Modeling
Service Level Agreements based on Business Process Modeling Holger Schmidt Munich Network Management Team University of Munich, Dept. of CS Oettingenstr. 67, 80538 Munich, Germany Email: schmidt@informatik.uni-muenchen.de
More informationComponent visualization methods for large legacy software in C/C++
Annales Mathematicae et Informaticae 44 (2015) pp. 23 33 http://ami.ektf.hu Component visualization methods for large legacy software in C/C++ Máté Cserép a, Dániel Krupp b a Eötvös Loránd University mcserep@caesar.elte.hu
More informationA Mind Map Based Framework for Automated Software Log File Analysis
2011 International Conference on Software and Computer Applications IPCSIT vol.9 (2011) (2011) IACSIT Press, Singapore A Mind Map Based Framework for Automated Software Log File Analysis Dileepa Jayathilake
More informationScalability is the best solution. The new Social Alarm Management System 7 Professional.
Scalability is the best solution. The new Social Alarm Management System 7 Professional. 2 Efficiency through customising Ideal solutions for your success To ensure immediate responses to emergency calls,
More informationThe Role of Computers in Synchronous Collaborative Design
The Role of Computers in Synchronous Collaborative Design Wassim M. Jabi, The University of Michigan Theodore W. Hall, Chinese University of Hong Kong Abstract In this paper we discuss the role of computers
More informationLightweight Data Integration using the WebComposition Data Grid Service
Lightweight Data Integration using the WebComposition Data Grid Service Ralph Sommermeier 1, Andreas Heil 2, Martin Gaedke 1 1 Chemnitz University of Technology, Faculty of Computer Science, Distributed
More informationModeling the User Interface of Web Applications with UML
Modeling the User Interface of Web Applications with UML Rolf Hennicker,Nora Koch,2 Institute of Computer Science Ludwig-Maximilians-University Munich Oettingenstr. 67 80538 München, Germany {kochn,hennicke}@informatik.uni-muenchen.de
More informationMetaGame: An Animation Tool for Model-Checking Games
MetaGame: An Animation Tool for Model-Checking Games Markus Müller-Olm 1 and Haiseung Yoo 2 1 FernUniversität in Hagen, Fachbereich Informatik, LG PI 5 Universitätsstr. 1, 58097 Hagen, Germany mmo@ls5.informatik.uni-dortmund.de
More informationComparison of Request Admission Based Performance Isolation Approaches in Multi-tenant SaaS Applications
Comparison of Request Admission Based Performance Isolation Approaches in Multi-tenant SaaS Applications Rouven Kreb 1 and Manuel Loesch 2 1 SAP AG, Walldorf, Germany 2 FZI Research Center for Information
More informationHow can I manage all automation software tasks in one engineering environment?
How can I manage all automation software tasks in one engineering environment? With Totally Integrated Automation Portal: One integrated engineering framework for all your automation tasks. Answers for
More informationBasic Trends of Modern Software Development
DITF LDI Lietišķo datorsistēmu programmatūras profesora grupa e-business Solutions Basic Trends of Modern Software Development 2 3 Software Engineering FAQ What is software engineering? An engineering
More informationArchitecture Design & Sequence Diagram. Week 7
Architecture Design & Sequence Diagram Week 7 Announcement Reminder Midterm I: 1:00 1:50 pm Wednesday 23 rd March Ch. 1, 2, 3 and 26.5 Hour 1, 6, 7 and 19 (pp.331 335) Multiple choice Agenda (Lecture)
More informationDie Mobiliar Insurance Company AG, Switzerland Adaptability and Agile Business Practices
Die Mobiliar Insurance Company AG, Switzerland Adaptability and Agile Business Practices Nominated by ISIS Papyrus Software 1. EXECUTIVE SUMMARY / ABSTRACT The Swiss insurance company Die Mobiliar is the
More information(Refer Slide Time: 01:52)
Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This
More informationTotal Exploration & Production: Field Monitoring Case Study
Total Exploration & Production: Field Monitoring Case Study 1 Summary TOTAL S.A. is a word-class energy producer and provider, actually part of the super majors, i.e. the worldwide independent oil companies.
More informationPatterns for Business Object Model Integration in Process-Driven and Service-Oriented Architectures
Patterns for Business Object Model Integration in Process-Driven and Service-Oriented Architectures Carsten Hentrich IBM Business Consulting Services, SerCon GmbH c/o IBM Deutschland GmbH Hechtsheimer
More informationSoftware Engineering Introduction & Background. Complaints. General Problems. Department of Computer Science Kent State University
Software Engineering Introduction & Background Department of Computer Science Kent State University Complaints Software production is often done by amateurs Software development is done by tinkering or
More informationQuality Management. Lecture 12 Software quality management
Quality Management Lecture 12 Software quality management doc.dr.sc. Marko Jurčević prof.dr.sc. Roman Malarić University of Zagreb Faculty of Electrical Engineering and Computing Department of Fundamentals
More informationModel Driven Development of Inventory Tracking System*
Model Driven Development of Inventory Tracking System* Gan Deng, Tao Lu, Emre Turkay Andrey Nechypurenko Aniruddha Gokhale, Douglas Schmidt ISIS, Vanderbilt University Siemens Nashville, TN 37221 Germany
More informationBusiness-Driven Software Engineering Lecture 3 Foundations of Processes
Business-Driven Software Engineering Lecture 3 Foundations of Processes Jochen Küster jku@zurich.ibm.com Agenda Introduction and Background Process Modeling Foundations Activities and Process Models Summary
More informationModel-based Testing of Automotive Systems
Model-based Testing of Automotive Systems Eckard Bringmann and Andreas Krämer ICST 08 Presented by Julia Rubin on November 21, 2012 Multidisciplinary Business 2 Supply Chain of Components 3 Innovation
More informationMaster of Science Service Oriented Architecture for Enterprise. Courses description
Master of Science Service Oriented Architecture for Enterprise Courses description SCADA and PLC networks The course aims to consolidate and transfer of extensive knowledge regarding the architecture,
More informationAn Aspect-Oriented Product Line Framework to Support the Development of Software Product Lines of Web Applications
An Aspect-Oriented Product Line Framework to Support the Development of Software Product Lines of Web Applications Germán Harvey Alférez Salinas Department of Computer Information Systems, Mission College,
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationTurning Emergency Plans into Executable
Turning Emergency Plans into Executable Artifacts José H. Canós-Cerdá, Juan Sánchez-Díaz, Vicent Orts, Mª Carmen Penadés ISSI-DSIC Universitat Politècnica de València, Spain {jhcanos jsanchez mpenades}@dsic.upv.es
More informationPhysical Security Information Management Software - Concepts - Solutions
Physical Security Information Management Software - Concepts - Solutions A system is only as secure as its weakest link Technical Management Security Information Management ViPRO.solutions Communications
More informationMigrating Legacy Software Systems to CORBA based Distributed Environments through an Automatic Wrapper Generation Technique
Migrating Legacy Software Systems to CORBA based Distributed Environments through an Automatic Wrapper Generation Technique Hyeon Soo Kim School of Comp. Eng. and Software Eng., Kum Oh National University
More informationA Model for Component Based E-governance Software Systems
A Model for Component Based E-governance Software Systems A.SHRABAN KUMAR 1, G.JAYARAO 2,B.SHANKAR NAYAK 3, KBKS. DURGA 4 A.ESWARA RAO 5 1,2,3,4 Associate Professor CSE, St.MARTIN S ENGINEERING COLLEGE,
More informationObject Oriented Programming. Risk Management
Section V: Object Oriented Programming Risk Management In theory, there is no difference between theory and practice. But, in practice, there is. - Jan van de Snepscheut 427 Chapter 21: Unified Modeling
More informationNetworking Systems (10102)
Networking Systems (10102) Rationale Statement: The goal of this course is to help students understand and participate in the significant impact of computer networking in their lives. Virtually any career
More informationDatabase Scheme Configuration for a Product Line of MPC-TOOLS
Database Scheme Configuration for a Product Line of MPC-TOOLS Benjamin Klöpper, Tobias Rust, Bernhard Vedder, and Wilhelm Dangelmaier Heinz Nixdorf Institute, University of Paderborn, Fürstenallee 11,
More informationWhite Paper July 2010 Desktop Video Conferencing
White Paper July 2010 Desktop Video Conferencing Industry trends and deployment best practices Abstract Desktop video conferencing can be defined as the use of video conferencing software on a personal
More informationA Symptom Extraction and Classification Method for Self-Management
LANOMS 2005-4th Latin American Network Operations and Management Symposium 201 A Symptom Extraction and Classification Method for Self-Management Marcelo Perazolo Autonomic Computing Architecture IBM Corporation
More informationAN INTELLIGENT TUTORING SYSTEM FOR LEARNING DESIGN PATTERNS
AN INTELLIGENT TUTORING SYSTEM FOR LEARNING DESIGN PATTERNS ZORAN JEREMIĆ, VLADAN DEVEDŽIĆ, DRAGAN GAŠEVIĆ FON School of Business Administration, University of Belgrade Jove Ilića 154, POB 52, 11000 Belgrade,
More informationFigure 1 - Automated Test Lifecycle Methodology (ATLM)
The Automated Testing Life-cycle Methodology (ATLM) i Elfriede Dustin Software project managers and software developers building today's applications face the challenge of doing so within an ever-shrinking
More informationA Framework of Model-Driven Web Application Testing
A Framework of Model-Driven Web Application Testing Nuo Li, Qin-qin Ma, Ji Wu, Mao-zhong Jin, Chao Liu Software Engineering Institute, School of Computer Science and Engineering, Beihang University, China
More informationINTERNATIONAL JOURNAL OF PURE AND APPLIED RESEARCH IN ENGINEERING AND TECHNOLOGY
INTERNATIONAL JOURNAL OF PURE AND APPLIED RESEARCH IN ENGINEERING AND TECHNOLOGY A PATH FOR HORIZING YOUR INNOVATIVE WORK A SYSTEMATIC REVIEW OF AUTOMATED SOFTWARE TESTING TOOLS A. NIRMAL KUMAR 1, DR.
More informationPortable Cloud Services Using TOSCA
Institute of Architecture of Application Systems Portable Cloud Services Using TOSCA Tobias Binz, Gerd Breiter, Frank Leymann, and Thomas Spatzier Institute of Architecture of Application Systems, University
More informationExtending the Internet of Things to IPv6 with Software Defined Networking
Extending the Internet of Things to IPv6 with Software Defined Networking Abstract [WHITE PAPER] Pedro Martinez-Julia, Antonio F. Skarmeta {pedromj,skarmeta}@um.es The flexibility and general programmability
More informationDesign with Reuse. Building software from reusable components. Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14 Slide 1
Design with Reuse Building software from reusable components. Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14 Slide 1 Objectives To explain the benefits of software reuse and some reuse
More informationSoftware Life-Cycle Management
Ingo Arnold Department Computer Science University of Basel Theory Software Life-Cycle Management Architecture Styles Overview An Architecture Style expresses a fundamental structural organization schema
More informationTowards an Automated Pattern Selection Procedure in Software Models
Towards an Automated Pattern Selection Procedure in Software Models Alexander van den Berghe, Jan Van Haaren, Stefan Van Baelen, Yolande Berbers, and Wouter Joosen {firstname.lastname}@cs.kuleuven.be IBBT-DistriNet,
More informationA Contribution to Expert Decision-based Virtual Product Development
A Contribution to Expert Decision-based Virtual Product Development László Horváth, Imre J. Rudas Institute of Intelligent Engineering Systems, John von Neumann Faculty of Informatics, Óbuda University,
More informationA Service-oriented Architecture for Business Intelligence
A Service-oriented Architecture for Business Intelligence Liya Wu 1, Gilad Barash 1, Claudio Bartolini 2 1 HP Software 2 HP Laboratories {name.surname@hp.com} Abstract Business intelligence is a business
More informationNetwork functions virtualization and software management
ericsson White paper Uen 284 23-3248 December 2014 Network functions virtualization and software management LEVERAGING THE FULL POTENTIAL WITH NETWORK SLICING Network Functions Virtualization technology
More informationSIMATIC IT Production Suite Answers for industry.
Driving Manufacturing Performance SIMATIC IT Production Suite Answers for industry. SIMATIC IT at the intersection of value creation processes With SIMATIC IT, Siemens is broadening the scope of MES. Plant
More informationEL Program: Smart Manufacturing Systems Design and Analysis
EL Program: Smart Manufacturing Systems Design and Analysis Program Manager: Dr. Sudarsan Rachuri Associate Program Manager: K C Morris Strategic Goal: Smart Manufacturing, Construction, and Cyber-Physical
More informationTRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW
Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of
More informationTeCReVis: A Tool for Test Coverage and Test Redundancy Visualization
TeCReVis: A Tool for Test Coverage and Test Redundancy Visualization Negar Koochakzadeh Vahid Garousi Software Quality Engineering Research Group University of Calgary, Canada Acknowledging funding and
More informationManaging and Tracing the Traversal of Process Clouds with Templates, Agendas and Artifacts
Managing and Tracing the Traversal of Process Clouds with Templates, Agendas and Artifacts Marian Benner, Matthias Book, Tobias Brückmann, Volker Gruhn, Thomas Richter, Sema Seyhan paluno The Ruhr Institute
More informationTMOS Secure Development and Implementation
TMOS Secure Development and Implementation Overview TMOS the foundation and architecture for F5 s application delivery controllers running on the BIG-IP platform brings a wealth of security to existing
More informationMDA Transformations Applied to Web Application Development 1
MDA Transformations Applied to Web Application Development 1 Santiago Meliá 1, Andreas Kraus 2, and Nora Koch 2, 3 1 Universidad de Alicante, Spain 2 Ludwig-Maximilians-Universität München, Germany 3 F.A.S.T
More informationProGUM-Web: Tool Support for Model-Based Development of Web Applications
ProGUM-Web: Tool Support for Model-Based Development of Web Applications Marc Lohmann 1, Stefan Sauer 1, and Tim Schattkowsky 2 1 University of Paderborn, Computer Science, D 33095 Paderborn, Germany {mlohmann,sauer}@upb.de
More informationSCADE System 17.0. Technical Data Sheet. System Requirements Analysis. Technical Data Sheet SCADE System 17.0 1
SCADE System 17.0 SCADE System is the product line of the ANSYS Embedded software family of products and solutions that empowers users with a systems design environment for use on systems with high dependability
More informationAgile Software Development Methodologies and Its Quality Assurance
Agile Software Development Methodologies and Its Quality Assurance Aslin Jenila.P.S Assistant Professor, Hindustan University, Chennai Abstract: Agility, with regard to software development, can be expressed
More informationAn Agent-Based Concept for Problem Management Systems to Enhance Reliability
An Agent-Based Concept for Problem Management Systems to Enhance Reliability H. Wang, N. Jazdi, P. Goehner A defective component in an industrial automation system affects only a limited number of sub
More informationCHAPTER 1 INTRODUCTION
CHAPTER 1 INTRODUCTION 1.1 Background The command over cloud computing infrastructure is increasing with the growing demands of IT infrastructure during the changed business scenario of the 21 st Century.
More informationIntroduction to Service Oriented Architectures (SOA)
Introduction to Service Oriented Architectures (SOA) Responsible Institutions: ETHZ (Concept) ETHZ (Overall) ETHZ (Revision) http://www.eu-orchestra.org - Version from: 26.10.2007 1 Content 1. Introduction
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,
More informationPBX IVR ACD. 7011Koll Center Parkway, Suite 150 Pleasanton, CA 94566-3140. Phone: (925) 461-4510 Fax: (925) 461-4520 SUPERVISOR, MANAGER
In today s competitive environment, reducing customer service telephone-based customer interaction overhead, improving call handling quality, and maximizing the effectiveness of customer service is a must.
More informationNEW. ProduCt information
NEW ProduCt information Your customers expect you to provide optimal service with maximum availability. We can help. ELSBETH Communication Manager (ECM) is the innovative solution for centralized management
More informationEfficient Management of Tests and Defects in Variant-Rich Systems with pure::variants and IBM Rational ClearQuest
Efficient Management of Tests and Defects in Variant-Rich Systems with pure::variants and IBM Rational ClearQuest Publisher pure-systems GmbH Agnetenstrasse 14 39106 Magdeburg http://www.pure-systems.com
More informationa new generation software test automation framework - CIVIM
a new generation software test automation framework - CIVIM Software Testing is the last phase in software development lifecycle which has high impact on the quality of the final product delivered to the
More informationSistemi ICT per il Business Networking
Corso di Laurea Specialistica Ingegneria Gestionale Sistemi ICT per il Business Networking Software Development Processes Docente: Vito Morreale (vito.morreale@eng.it) 17 October 2006 1 The essence of
More informationAn E-learning Service Management Architecture
An E-learning Service Architecture Theodore K. Apostolopoulos Anna Kefala Department of Informatics Athens University of Economics and Business 76 Patission st., 10434 Athens, Greece Tel.: +30 210 8203234,
More informationPeter Mileff PhD SOFTWARE ENGINEERING. The Basics of Software Engineering. University of Miskolc Department of Information Technology
Peter Mileff PhD SOFTWARE ENGINEERING The Basics of Software Engineering University of Miskolc Department of Information Technology Introduction Péter Mileff - Department of Information Engineering Room
More informationEnsuring Interoperability with Automated Interoperability Testing
Ensuring Interoperability with Automated Interoperability Testing Olaf Bergengruen, Rhode & Schwarz Francois Fischer, FSCOM Tuncay Namli, SRDC Thomas Rings, University of Göttingen Stephan Schulz, Conformiq
More informationADAPTIVE SOA INFRASTRUCTURE BASED ON VARIABILITY MANAGEMENT. Peter Graubmann, Mikhail Roshchin
70 ADAPTIVE SOA INFRASTRUCTURE BASED ON VARIABILITY MANAGEMENT Peter Graubmann, Mikhail Roshchin Abstract: In order to exploit the adaptability of a SOA infrastructure, it becomes necessary to provide
More informationPerformance Testing Uncovered
Performance Testing Uncovered First Presented at: NobleStar Systems Corp. London, UK 26 Sept. 2003 Scott Barber Chief Technology Officer PerfTestPlus, Inc. Performance Testing Uncovered Page 1 Performance
More informationMulti-Agent Model for Automation of Business Process Management System Based on Service Oriented Architecture
Multi-Agent Model for Automation of Business Process Management System Based on Service Oriented Architecture Soe Winn, May Thwe Oo Abstract Business process automation is an important task in an enterprise
More informationSOACertifiedProfessional.Braindumps.S90-03A.v2014-06-03.by.JANET.100q. Exam Code: S90-03A. Exam Name: SOA Design & Architecture
SOACertifiedProfessional.Braindumps.S90-03A.v2014-06-03.by.JANET.100q Number: S90-03A Passing Score: 800 Time Limit: 120 min File Version: 14.5 http://www.gratisexam.com/ Exam Code: S90-03A Exam Name:
More informationVerification of Component-Based Software Application Families
Verification of Component-Based Software Application Families Fei Xie 1 and James C. Browne 2 1 Dept. of Computer Science, Portland State Univ., Portland, OR 97207 xie@cs.pdx.edu 2 Dept. of Computer Sciences,
More informationMiddleware- Driven Mobile Applications
Middleware- Driven Mobile Applications A motwin White Paper When Launching New Mobile Services, Middleware Offers the Fastest, Most Flexible Development Path for Sophisticated Apps 1 Executive Summary
More informationReconfigurable Architecture Requirements for Co-Designed Virtual Machines
Reconfigurable Architecture Requirements for Co-Designed Virtual Machines Kenneth B. Kent University of New Brunswick Faculty of Computer Science Fredericton, New Brunswick, Canada ken@unb.ca Micaela Serra
More informationA Knowledge-based Product Derivation Process and some Ideas how to Integrate Product Development
A Knowledge-based Product Derivation Process and some Ideas how to Integrate Product Development (Position paper) Lothar Hotz and Andreas Günter HITeC c/o Fachbereich Informatik Universität Hamburg Hamburg,
More informationSoftware Development Kit
Open EMS Suite by Nokia Software Development Kit Functional Overview Version 1.3 Nokia Siemens Networks 1 (21) Software Development Kit The information in this document is subject to change without notice
More informationGEDAE TM - A Graphical Programming and Autocode Generation Tool for Signal Processor Applications
GEDAE TM - A Graphical Programming and Autocode Generation Tool for Signal Processor Applications Harris Z. Zebrowitz Lockheed Martin Advanced Technology Laboratories 1 Federal Street Camden, NJ 08102
More information1. PUBLISHABLE SUMMARY
1. PUBLISHABLE SUMMARY ICT-eMuCo (www.emuco.eu) is a European project with a total budget of 4.6M which is supported by the European Union under the Seventh Framework Programme (FP7) for research and technological
More informationABSTRACT INTRODUCTION MATERIALS AND METHODS
JOURNAL OF AGRICULTURE & SOCIAL SCIENCES 1813 2235/2005/01 2 156 160 http://www.ijabjass.org Design and Implementation of Network Operational Management Systems for Integrated and Automated Management
More informationTowards service awareness and autonomic features in a SIPenabled
features in a SIP-enabled network 1 Towards service awareness and autonomic features in a SIPenabled network Guillaume Delaire Laurent Walter Goix Giuseppe Valetto Telecom Italia Lab Outline 2 Context
More informationSymphony Plus Cyber security for the power and water industries
Symphony Plus Cyber security for the power and water industries Symphony Plus Cyber Security_3BUS095402_(Oct12)US Letter.indd 1 01/10/12 10:15 Symphony Plus Cyber security for the power and water industries
More informationService-Oriented Architecture and Software Engineering
-Oriented Architecture and Software Engineering T-86.5165 Seminar on Enterprise Information Systems (2008) 1.4.2008 Characteristics of SOA The software resources in a SOA are represented as services based
More informationTool Support for Software Variability Management and Product Derivation in Software Product Lines
Tool Support for Software Variability Management and Product Derivation in Software s Hassan Gomaa 1, Michael E. Shin 2 1 Dept. of Information and Software Engineering, George Mason University, Fairfax,
More informationSoftware Development Under Stringent Hardware Constraints: Do Agile Methods Have a Chance?
Software Development Under Stringent Hardware Constraints: Do Agile Methods Have a Chance? Jussi Ronkainen, Pekka Abrahamsson VTT Technical Research Centre of Finland P.O. Box 1100 FIN-90570 Oulu, Finland
More informationEvaluating OO-CASE tools: OO research meets practice
Evaluating OO-CASE tools: OO research meets practice Danny Greefhorst, Matthijs Maat, Rob Maijers {greefhorst, maat, maijers}@serc.nl Software Engineering Research Centre - SERC PO Box 424 3500 AK Utrecht
More informationNASCIO EA Development Tool-Kit Solution Architecture. Version 3.0
NASCIO EA Development Tool-Kit Solution Architecture Version 3.0 October 2004 TABLE OF CONTENTS SOLUTION ARCHITECTURE...1 Introduction...1 Benefits...3 Link to Implementation Planning...4 Definitions...5
More informationEnterprise Architecture: Practical Guide to Logical Architecture
Objecteering Practical Guides Enterprise Architecture: Practical Guide to Logical Architecture Author: Version: 1.0 Copyright: Softeam Softeam Consulting Team Supervised by Philippe Desfray Softeam 21
More information2 (18) - SOFTWARE ARCHITECTURE Service Oriented Architecture - Sven Arne Andreasson - Computer Science and Engineering.
Service Oriented Architecture Definition (1) Definitions Services Organizational Impact SOA principles Web services A service-oriented architecture is essentially a collection of services. These services
More informationReference Guide for Security in Networks
Reference Guide for Security in Networks This reference guide is provided to aid in understanding security concepts and their application in various network architectures. It should not be used as a template
More information