Увійти

Готові списки джерел за темами / Software architecture consistency / Статті в журналах

Статті в журналах з теми "Software architecture consistency"

Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Software architecture consistency.

Автор: Grafiati

Опубліковано: 23 червня 2021

Оновлено: 9 лютого 2022

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся з топ-50 статей у журналах для дослідження на тему "Software architecture consistency".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Переглядайте статті в журналах для різних дисциплін та оформлюйте правильно вашу бібліографію.

1

Yu, Haobo, Lee Breslau, and Scott Shenker. "A scalable Web cache consistency architecture." ACM SIGCOMM Computer Communication Review 29, no. 4 (October 1999): 163–74. http://dx.doi.org/10.1145/316194.316219.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

2

Lafaye, Jean-Yves, and Georges Louis. "A metric for evaluating software architecture and communication models consistency." RAIRO - Theoretical Informatics and Applications 39, no. 2 (April 2005): 361–90. http://dx.doi.org/10.1051/ita:2005023.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

3

Zhou, Xue Yao, Ning Jiang Chen, and Dan Dan Hu. "Behavior Consistency Verification for Evolution of Aspectual Component-Based Software." Advanced Materials Research 765-767 (September 2013): 1231–35. http://dx.doi.org/10.4028/www.scientific.net/amr.765-767.1231.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Aspect-Oriented Software Architecture (AOA) is a high-level abstraction and integration blueprint of aspectual component-based software. A semantic model of aspectual component-based software is proposed to provide behavior description and semantic foundation for the consistency verification of software architecture dynamic evolution. By using the semantic model of Pi-calculus, a set of the consistency verification methods of dynamic evolution from multiple aspects are introduced. Finally, a case study shows the effect of these methods.

4

Heckel, R., and G. Engels. "Relating functional requirements and software architecture: separation and consistency of concerns." Journal of Software Maintenance and Evolution: Research and Practice 14, no. 5 (2002): 371–88. http://dx.doi.org/10.1002/smr.261.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

5

Ali, Nour, Sean Baker, Ross O’Crowley, Sebastian Herold, and Jim Buckley. "Erratum to: Architecture consistency: State of the practice, challenges and requirements." Empirical Software Engineering 23, no. 3 (September 14, 2017): 1868–69. http://dx.doi.org/10.1007/s10664-017-9542-0.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

6

Elzain and Wu. "Software Defined Wireless Mesh Network Flat Distribution Control Plane." Future Internet 11, no. 8 (July 25, 2019): 166. http://dx.doi.org/10.3390/fi11080166.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Wireless Mesh Networks (WMNs), have a potential offering relatively stable Internet broadband access. The rapid development and growth of WMNs attract ISPs to support users’ coverage anywhere anytime. To achieve this goal network architecture must be addressed carefully. Software Defined Networking (SDN) proposes new network architecture for wired and wireless networks. Software Defined Wireless Networking (SDWN) has a great potential to increase efficiency, ease the complexity of control and management, and accelerate technology innovation rate of wireless networking. An SDN controller is the core component of an SDN network. It needs to have updated reports of the network status change, as in network topology and quality of service (QoS) in order to effectively configure and manage the network it controls. In this paper, we propose Flat Distributed Software Defined Wireless Mesh Network architecture where the controller aggregates entire topology discovery and monitors QoS properties of extended WMN nodes using Link Layer Discovery Protocol (LLDP) protocol, which is not possible in multi-hop ordinary architectures. The proposed architecture has been implemented on top of POX controller and Advanced Message Queuing Protocol (AMQP) protocol. The experiments were conducted in a Mininet-wifi emulator, the results present the architecture control plane consistency and two application cases: topology discovery and QoS monitoring. The current results push us to study QoS-routing for video streaming over WMN.

7

Dambietz, Florian M., Christoph Rennpferdt, Michael Hanna, and Dieter Krause. "Using MBSE for the Enhancement of Consistency and Continuity in Modular Product-Service-System Architectures." Systems 9, no. 3 (August 17, 2021): 63. http://dx.doi.org/10.3390/systems9030063.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Within emerging markets, ensuring the competitiveness of manufacturing companies is crucial to their success. The integration of new business possibilities, such as Product-Service-Systems (PSS) can provide one suitable solution. Especially within the architecture development process, large amounts of interconnected data and data types need to be processed and versioned. This leads to a significant lack of data consistency and continuity along the development process of modular PSS architectures. This lack of consistency and continuity leads to a process being prone to errors, representing a significant negative impact onto the company’s value-added stream. We provide one possible solution to these issues by presenting a PSS architecture modularization approach based upon the modularization methods of the Integrated PKT-Approach. Using concepts of Model-Based Systems Engineering (MBSE) for modelling these architectures, automated and dynamic analyses of the architecture for the iteration and harmonization of the PSS architecture under development are enabled. The at first generically described approach is further detailed in the second part of this contribution by applying it to an industry case study for mobile laser welding systems. As a result, a clear support for the visualization of architecture iteration aspects as well as for the enhancement of data consistency and continuity is given.

8

Wang, Yongdong, and Lawrence A. Rowe. "Cache consistency and concurrency control in a client/server DBMS architecture." ACM SIGMOD Record 20, no. 2 (April 1991): 367–76. http://dx.doi.org/10.1145/119995.115855.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

9

Zhang, Yang, Shixin Sun, Dongwen Zhang, Jing Qiu, and Zhihong Tian. "A consistency-guaranteed approach for Internet of Things software refactoring." International Journal of Distributed Sensor Networks 16, no. 1 (January 2020): 155014772090168. http://dx.doi.org/10.1177/1550147720901680.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

The software architecture of Internet of Things defines the component model and interconnection topology of Internet of Things systems. Refactoring is a systematic practice of improving a software structure without altering its external behaviors. When the Internet of Things software is refactored, it is necessary to detect the correctness of Internet of Things software to ensure its security. To this end, this article proposes a novel refactoring correction detection approach to ensure software security. Control flow analysis and data flow analysis are used to detect code changes before and after refactoring, and synchronization dependency analysis is used to detect changes in synchronization dependency. Three detection algorithms are designed to detect refactoring correctness. Four real-world benchmark applications are used to evaluate our approach. The experimental results show that our proposed approach can ensure correctness of Internet of Things software refactoring.

10

Park, Woo-Chan, Cheong-Ghil Kim, Duk-Ki Yoon, Kil-Whan Lee, Il-San Kim, and Tack-Don Han. "A consistency-free memory architecture for sort-last parallel rendering processors." Journal of Systems Architecture 53, no. 5-6 (May 2007): 272–84. http://dx.doi.org/10.1016/j.sysarc.2006.10.010.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

11

Gong, Yiwei, Sietse Overbeek, and Marijn Janssen. "Integrating Semantic Web and Software Agents." International Journal of Systems and Service-Oriented Engineering 2, no. 1 (January 2011): 60–76. http://dx.doi.org/10.4018/jssoe.2011010104.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Software agents and rules are both used for creating flexibility. Exchanging rules between Semantic Web and agents can ensure consistency in rules and support easy updating and changing of rules. The Rule Interchange Format (RIF) is a new W3C recommendation Semantic Web standard for exchanging rules among disparate systems. Yet, the contribution of RIF in rules exchange between Semantic Web and software agents is unclear. The BDI architectural style is regarded as the predominant approach for the implementation of intelligent agents. This paper proposes a development for integrating RIF and BDI agents to enhance agent reasoning capabilities. This approach consists of an integration architecture and equivalence principles for rule translation. The equivalence principles are demonstrated using examples. The results show that the approach allows the integration of RIF with BDI agent programming and realize the translation between the two systems.

12

Hu, Xiaomei, Lilan Liu, and Tao Yu. "A hierarchical architecture for improving scalability and consistency in CVE systems." International Journal of Parallel, Emergent and Distributed Systems 26, no. 3 (June 2011): 179–205. http://dx.doi.org/10.1080/17445760.2010.495722.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

13

Saadi, Abdelfetah, Youcef Hammal, and Mourad Chabane Oussalah. "A CSP-Based Approach for Managing the Dynamic Reconfiguration of Software Architecture." International Journal of Information Technologies and Systems Approach 14, no. 1 (January 2021): 156–73. http://dx.doi.org/10.4018/ijitsa.2021010109.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Software applications are composed of a set of interconnected software components running on different machines. Most of these applications have a dynamic nature and need to reconfigure structure and behavior at run-time. The dynamic reconfiguration of software is a problem that must be dealt with. Reconfiguring this kind of applications is a complicated task and risks to take software at an undesirable situation. In this paper, the authors present a solution whose objective is to provide a complete support for reconfiguring and formally verifying consistency of dynamic updates of software before performing them. The aim is to provide highly available systems with the ability to safely modify their structure and behavior at run-time. The proposed approach is based mainly on the use of the meta-model concept for reconfiguration structural checking, and the CSP language, refinement technique, and the FDR model checking tool for the verification of reconfiguration behavioral consistency. The authors have also developed a tool prototype that validates and implements their proposals.

14

Weidlich, Matthias, and Jan Mendling. "Perceived consistency between process models." Information Systems 37, no. 2 (April 2012): 80–98. http://dx.doi.org/10.1016/j.is.2010.12.004.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

15

Liu, Yubo, Hongbo Li, Yutong Lu, Zhiguang Chen, Nong Xiao, and Ming Zhao. "HasFS: optimizing file system consistency mechanism on NVM-based hybrid storage architecture." Cluster Computing 23, no. 4 (December 11, 2019): 2501–15. http://dx.doi.org/10.1007/s10586-019-03023-y.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

16

Bril, RJ, and AJ Van de Goor. "Software transparent cache consistency scheme for a VMEbus-based system." Microprocessors and Microsystems 12, no. 9 (November 1988): 513–18. http://dx.doi.org/10.1016/0141-9331(88)90117-2.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

17

Zhou, Shu, Rong Hu Zhang, and Yong Zhong. "The Novel Methods of Software Architecture Based on the UML and B Methods." Advanced Materials Research 121-122 (June 2010): 215–21. http://dx.doi.org/10.4028/www.scientific.net/amr.121-122.215.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

The paper proposed a novel methods of Software Architecture Based on the UML and B methods in order to solve the aspects of the architecture of the Statute strengths and weaknesses of existing language software architecture. By the defined rules will be relatively independent of each other sub-components or connections to the executable code refinement. Finally, a concrete example to verify the feasibility of the method. The method is entirely possible refinement in the software architecture, the process of implementation, both retained the use of a systematic analysis of UML design system modeling capabilities and powerful object-oriented model of clear and concise notation, but also against the software model can be formalized The refinement process of validation, the combination of these two methods found a good balance point, making software architecture allows us to design the same time, the architecture design can ensure the consistency and reliability.

18

Wei, Sheng, and Miodrag Potkonjak. "Self-Consistency and Consistency-Based Detection and Diagnosis of Malicious Circuitry." IEEE Transactions on Very Large Scale Integration (VLSI) Systems 22, no. 9 (September 2014): 1845–53. http://dx.doi.org/10.1109/tvlsi.2013.2280233.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

19

Wei, Xueliang, Dan Feng, Wei Tong, Jingning Liu, and Liuqing Ye. "NICO: Reducing Software-Transparent Crash Consistency Cost for Persistent Memory." IEEE Transactions on Computers 68, no. 9 (September 1, 2019): 1313–24. http://dx.doi.org/10.1109/tc.2018.2876829.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

20

Chen, J. Y. J., and S. C. Chou. "Consistency management in a process environment." Journal of Systems and Software 47, no. 2-3 (July 1999): 105–10. http://dx.doi.org/10.1016/s0164-1212(99)00030-8.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

21

Kung, Chenho. "Process interface modeling and consistency checking." Journal of Systems and Software 15, no. 2 (May 1991): 185–91. http://dx.doi.org/10.1016/0164-1212(91)90055-b.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

22

Xiong, Jin. "Metadata Consistency in DCFS2." Journal of Computer Research and Development 42, no. 6 (2005): 1019. http://dx.doi.org/10.1360/crad20050618.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

23

Derrick, John, Eerke Boiten, Howard Bowman, and Maarten Steen. "Viewpoints and consistency: translating lotos to Object-z." Computer Standards & Interfaces 21, no. 3 (August 1999): 251–72. http://dx.doi.org/10.1016/s0920-5489(99)00010-0.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

24

Kuwada, Hayato, Kenji Hashimoto, Yasunori Ishihara, and Toru Fujiwara. "The consistency and absolute consistency problems of XML schema mappings between restricted DTDs." World Wide Web 18, no. 5 (April 13, 2014): 1443–61. http://dx.doi.org/10.1007/s11280-014-0285-1.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

25

Nejati Sharif Aldin, Hesam, Hossein Deldari, Mohammad Hossein Moattar, and Mostafa Razavi Ghods. "Strict Timed Causal Consistency as a Hybrid Consistency Model in the Cloud Environment." Future Generation Computer Systems 105 (April 2020): 259–74. http://dx.doi.org/10.1016/j.future.2019.11.038.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

26

Etzion, Opher. "Flexible consistency modes for active databases applications." Information Systems 18, no. 6 (September 1993): 391–404. http://dx.doi.org/10.1016/0306-4379(93)90015-s.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

27

Romanescu, Bogdan, Alvin Lebeck, and Daniel J. Sorin. "Address Translation Aware Memory Consistency." IEEE Micro 31, no. 1 (January 2011): 109–18. http://dx.doi.org/10.1109/mm.2010.99.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

28

Mišovič, Milan, and Oldřich Faldík. "Applying of component system development in object methodology." Acta Universitatis Agriculturae et Silviculturae Mendelianae Brunensis 61, no. 7 (2013): 2515–22. http://dx.doi.org/10.11118/actaun201361072515.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

In the last three decades, the concept and implementation of component-based architectures have been promoted in software systems creation. Increasingly complex demands are placed on the software component systems, in particular relating to the dynamic properties. The emergence of such requirements has been gradually enforced by the practice of development and implementation of these systems, especially for information systems software.Just the information systems (robust IS) of different types require that target software meets their requirements. Among other things, we mean primarily the adaptive processes of different domains, high distributives due to the possibilities of the Internet 2.0, acceptance of high integrity of life domains (process, data and communications integrity), scalability, and flexible adaptation to process changes, a good context for external devices and transparent structure of the sub-process modules and architectural units.Of course, the target software of required qualities and the type robust cannot be a monolith. As commonly known, development of design toward information systems software has clearly come to the need for the software composition of completely autonomous, but cooperating architectural units that communicate with each other using messages of prescribed formats.Although for such units there were often used the so called subsystems and modules, see (Jac, Boo, Rumbo, 1998) and (Arlo, Neus, 2007), their abstraction being gradually enacted as the term component. In other words, the subsystems and modules are specific types of components.In (Král, Žeml, 2000) and (Král, Žeml, 2003) there are considered two types of target software of information systems. The first type – there are SWC (Software Components), composed of permanently available components, which are thought as services – Confederate software. The second type – SWA (Software Alliance), called semi Confederate, formed during the run-time of the software system and referred to as software alliance.In both of these mentioned publications there is delivered deep philosophy of relevant issues relating to SWC / SWA as creating copies of components (cloning), the establishment and destruction of components at software run-time (dynamic reconfiguration), cooperation of autonomous components, programmable management of components interface in depending on internal components functionality and customer requirements (functionality, security, versioning).Nevertheless, even today we can meet numerous cases of SWC / SWA existence, with a highly developed architecture that is accepting vast majority of these requests. On the other hand, in the development practice of component-based systems with a dynamic architecture (i.e. architecture with dynamic reconfiguration), and finally with a mobile architecture (i.e. architecture with dynamic component mobility) confirms the inadequacy of the design methods contained in UML 2.0. It proves especially the dissertation thesis (Rych, Weis, 2008). Software Engineering currently has two different approaches to systems SWC / SWA. The first approach is known as component-oriented software development CBD (Component based Development). According to (Szyper, 2002) that is a collection of CBD methodologies that are heavily focused on the setting up and software components re-usability within the architecture. Although CBD does not show high theoretical approach, nevertheless, it is classified under the general evolution of SDP (Software Development Process), see (Sommer, 2010) as one of its two dominant directions.From a structural point of view, a software system consists of self-contained, interoperable architectural units – components based on well-defined interfaces. Classical procedural object-oriented methodologies significantly do not use the component meta-models, based on which the target component systems are formed, then. Component meta-models describe the syntax, semantics of components. They are a system of rules for components, connectors and configuration. Component meta-models for dynamic and mobile architectures also describe the concept of rules for configuration changes (rules for reconfiguration). As well-known meta-models are now considered: Wright for static architecture, SOFA and Darvin for dynamic architecture and SOFA 2.0 for mobile architecture, see (Rych, Weis, 2008).The CBD approach verbally defines the basic terms as component (primitive / composite), interface, component system, configuration, reconfiguration, logical (structural) view, process view (behavioral), static component architecture, dynamic architecture, mobile architecture (fully dynamic architecture), see (IEEE Report, 2000) and (Crnk, Chaud, 2006).The CBD approach also presents several ADL languages (Architecture Description Languages) which are able to describe software architecture. The known languages are integration ACME and UML (Unified Modeling Language), see (Garl, Mon, Wil, 2000) and (UNIFEM, 2005).The second approach to SWC / SWA systems is formed on SOA, but this article does not deal with it consistently.SOA is a philosophy of architecture. SOA is not a methodology for the comprehensive development of the target software. Nevertheless, SOA successfully filled the role of software design philosophy and on the other hand, also gave an important concept linking software components and their architectural units – business services. SOA understands any software as a Component System of a business service and solved life components in it. The physical implementation of components is given by a Web services platform. A certain lack of SOA is its weak link to the business processes that are a universally recognized platform for business activities and the source for the creation of enterprise services.This paper deals with a specific activity in the CBD, i.e. the integration of the concept of component-based system into an advanced procedural, object-oriented methodology (Arlo, Neust, 2007), (Kan, Müller, 2005), (Krutch, 2003) for problem domains with double-layer process logic. There is indicated an integration method, based on a certain meta-model (Applying of the Component system Development in object Methodology) and leading to the component system formation. The mentioned meta-model is divided into partial workflows that are located in different stages of a classic object process-based methodology. Into account there are taken the consistency of the input and output artifacts in working practices of the meta-model and mentioned object methodology. This paper focuses on static component systems that are starting to explore dynamic and mobile component systems.In addition, in the contribution the component system is understood as a specific system, for its system properties and basic terms notation being used a set and graph and system algebra.

29

Al-bayati, Zaid, Youcheng Sun, Haibo Zeng, Marco Di Natale, Qi Zhu, and Brett H. Meyer. "Partitioning and Selection of Data Consistency Mechanisms for Multicore Real-Time Systems." ACM Transactions on Embedded Computing Systems 18, no. 4 (August 12, 2019): 1–28. http://dx.doi.org/10.1145/3320271.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

30

Natarajan, Ragavendra, and Antonia Zhai. "Leveraging Transactional Execution for Memory Consistency Model Emulation." ACM Transactions on Architecture and Code Optimization 12, no. 3 (October 6, 2015): 1–24. http://dx.doi.org/10.1145/2786980.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

31

Chen, L. G., J. Y. Lee, J. F. Wang, and K. T. Chen. "Fast execution for circuit consistency verification." Integration 4, no. 3 (September 1986): 239–62. http://dx.doi.org/10.1016/0167-9260(86)90003-9.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

32

Liu, Kai, Victor C. S. Lee, Joseph K. Y. Ng, Sang H. Son, and Edwin H. M. Sha. "Scheduling Temporal Data with Dynamic Snapshot Consistency Requirement in Vehicular Cyber-Physical Systems." ACM Transactions on Embedded Computing Systems 13, no. 5s (December 15, 2014): 1–21. http://dx.doi.org/10.1145/2629546.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

33

Zhan, Jinyu, Yiming Zhang, Wei Jiang, Junhuan Yang, Lin Li, and Yixin Li. "Energy-aware page replacement and consistency guarantee for hybrid NVM–DRAM memory systems." Journal of Systems Architecture 89 (September 2018): 60–72. http://dx.doi.org/10.1016/j.sysarc.2018.07.004.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

34

Song, Cheeyang, and Eunsook Cho. "An Integrated Design Method for SOA-Based Business Modeling and Software Modeling." International Journal of Software Engineering and Knowledge Engineering 26, no. 02 (March 2016): 347–77. http://dx.doi.org/10.1142/s0218194016500157.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Service-oriented architecture (SOA)-based system development requires a systematic integration technique for software modeling and business modeling methods that approach the implementation component from the perspective of a business service. We proposes the integrated design method (architecture, metamodel, framework, process) for the integration of component software modeling in business process modeling notation (BPMN) business modeling to service-oriented modeling based on model-driven architecture (MDA) and model view controller (MVC) patterns according to SOA. The integrated architecture is composed of a metamodel and a process framework. The integrated metamodel is mapped to the core modeling elements of the SOA-based extended layered (XL)-BPMN/business process execution language (BPEL)/web service description language (WSDL)/component models, and the conversion profile is defined. For the establishment of the integrated process between business and software modeling, the framework is first defined; using this framework, we apply MDA (CIM: Conceptual Independent Modeling, PIM: Platform Independent Modeling, PSM: Platform Specific Modeling) and MVC patterns to define the integrated modeling process for the three development phases. The proposed modeling process was applied to the design of an online shopping mall system (OSMS). The design models were described on the basis of MDA/MVC according to the layered modeling elements defined in the individual/integrated metamodel and the three modeling phases of the integrated modeling process. The case study demonstrated that the conversion modeling task maintains the consistency and practicality between the SOA-based business and software modeling. The use of this method will make the consistent conversion modeling work between businesses and software convenient with a service orientation, will make it easy to change a business process, and will maximize the number of established reuse models.

35

Budiman, Kholiq, Toni Prahasto, and Amie Kusumawardhani. "Enterprise Architecture Planning in developing A planning Information System: a Case Study of Semarang State University." E3S Web of Conferences 31 (2018): 11002. http://dx.doi.org/10.1051/e3sconf/20183111002.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

This research has applied an integrated design and development of planning information system, which is been designed using Enterprise Architecture Planning. Frequent discrepancy between planning and realization of the budget that has been made, resulted in ineffective planning, is one of the reason for doing this research. The design using EAP aims to keep development aligned and in line with the strategic direction of the organization. In the practice, EAP is carried out in several stages of the planning initiation, identification and definition of business functions, proceeded with architectural design and EA implementation plan that has been built. In addition to the design of the Enterprise Architecture, this research carried out the implementation, and was tested by several methods of black box and white box. Black box testing method is used to test the fundamental aspects of the software, tested by two kinds of testing, first is using User Acceptance Testing and the second is using software functionality testing. White box testing method is used to test the effectiveness of the code in the software, tested using unit testing. Tests conducted using white box and black box on the integrated planning information system, is declared successful. Success in the software testing can not be ascertained if the software built has not shown any distinction from prior circumstance to the development of this integrated planning information system. For ensuring the success of this system implementation, the authors test consistency between the planning of data and the realization of prior-use of the information system, until after-use information system. This consistency test is done by reducing the time data of the planning and realization time. From the tabulated data, the planning information system that has been built reduces the difference between the planning time and the realization time, in which indicates that the planning information system can motivate the planner unit in realizing the budget that has been designed. It also proves that the value chain of the information planning system has brought implications for budget realization.

36

Safonov, V. M., D. A. Pavlov, and A. N. Pavlov. "Justification of information interaction architecture of remote sensing data processing system." Informatization and communication 5 (December 2020): 141–50. http://dx.doi.org/10.34219/2078-8320-2020-11-5-141-150.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Purpose: To fi nd an approach to substantiation of the rational architecture of information interaction of the Earth Remote Sensing Data Processing System. Materials and methods: When conducting research in the fi eld of distributed remote sensing data processing as part of the design of a remote sensing data processing system, it seems necessary to create some digital prototype of it. At the fi rst stage of creating such a “digital double”, the architecture of the information interaction of upper-level elements (services, modules, etc.) should be justifi ed in order to ensure effective and consistent application of the system software components. Results: The article proposes an approach to justifying and choosing the architecture of a software system, which is based on production models of decision maker preferences for describing simple and complex reference situations of the survey, processing of knowledge data using methods of the theory of fuzzy measures and theory of experimental design and checking statements Decision maker for consistency. Conclusions: The proposed approach will signifi cantly increase the degree of formalization and validity of the selection process, which as a result provides the opportunity to increase its automation level.

37

Torre, Damiano, Yvan Labiche, Marcela Genero, and Maged Elaasar. "A systematic identification of consistency rules for UML diagrams." Journal of Systems and Software 144 (October 2018): 121–42. http://dx.doi.org/10.1016/j.jss.2018.06.029.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

38

Abilio, Ramon, Cristiano Mesquita Garcia, Flavio Lopes de Morais, and Antônio Elizeu da Rocha Neto. "A Case study on a service-based information systems integration in academic environment." Revista Brasileira de Computação Aplicada 11, no. 1 (April 15, 2019): 2–13. http://dx.doi.org/10.5335/rbca.v11i1.8051.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

In corporate environments, we can find various information systems (IS), which need to communicate to each other to share and maintain data consistency. Academic environments (AE) are even more complex than corporate environments because they have several IS to help manage different aspects, such as restaurant and library, which need to have consistent data to work properly. Therefore, it is necessary to encounter a form to develop an integration among them and share common, trustworthy data. We present a case study on SOA-based architecture for IS integration within AE to keep data consistent through the systems, to monitor the communication, and to make the integration safe and manageable. We applied the proposal, and the results show that we can integrate, monitor, and manage different software systems and network services and permissions. The main contribution is a useful integration architecture for AE that must share trustworthy data among several, heterogeneous IS and network systems. In addition, a small team can implement and maintain this proposed architecture.

39

Dimokas, N., D. Katsaros, and Y. Manolopoulos. "Cache consistency in Wireless Multimedia Sensor Networks." Ad Hoc Networks 8, no. 2 (March 2010): 214–40. http://dx.doi.org/10.1016/j.adhoc.2009.08.001.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

40

OKANO, Kozo, Satoshi HARAUCHI, Toshifusa SEKIZAWA, Shinpei OGATA, and Shin NAKAJIMA. "Consistency Checking between Java Equals and hashCode Methods Using Software Analysis Workbench." IEICE Transactions on Information and Systems E102.D, no. 8 (August 1, 2019): 1498–505. http://dx.doi.org/10.1587/transinf.2018edp7254.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

41

Klare, Heiko, Max E. Kramer, Michael Langhammer, Dominik Werle, Erik Burger, and Ralf Reussner. "Enabling consistency in view-based system development — The Vitruvius approach." Journal of Systems and Software 171 (January 2021): 110815. http://dx.doi.org/10.1016/j.jss.2020.110815.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

42

Horng, Jorng-Tzong, and Chi-Wei Chen. "A mechanism for view consistency in a data warehousing system." Journal of Systems and Software 56, no. 1 (February 2001): 23–37. http://dx.doi.org/10.1016/s0164-1212(00)00083-2.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

43

Minet, Pascale, and Simone Sedillot. "Integration of real-time and consistency constraints in distributed databases: The sigma approach." Computer Standards & Interfaces 6, no. 1 (January 1987): 97–105. http://dx.doi.org/10.1016/0920-5489(87)90050-x.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

44

Fotouhi, Mehran, Hamid Hekmatian, Mohammad Amin Kashani-Nezhad, and Shohreh Kasaei. "SC-RANSAC: Spatial consistency on RANSAC." Multimedia Tools and Applications 78, no. 7 (August 23, 2018): 9429–61. http://dx.doi.org/10.1007/s11042-018-6475-6.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

45

An, Yuan, Xiaohua Hu, and Il-Yeol Song. "Maintaining Mappings between Conceptual Models and Relational Schemas." Journal of Database Management 21, no. 3 (July 2010): 36–68. http://dx.doi.org/10.4018/jdm.2010070102.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

This paper describes a round-trip engineering approach for incrementally maintaining mappings between conceptual models and relational schemas. When either schema or conceptual model evolves to accommodate new information needs, the existing mapping must be maintained accordingly to continuously provide valid services. In this paper, the authors examine the mappings specifying “consistent” relationships between models. First, they define the consistency of a conceptual-relational mapping through “semantically compatible” instances. Next, the authors analyze the knowledge encoded in the standard database design process and develop round-trip algorithms for incrementally maintaining the consistency of conceptual-relational mappings under evolution. Finally, they conduct a set of comprehensive experiments. The results show that the proposed solution is efficient and provides significant benefits in comparison to the mapping reconstructing approach.

46

Lu, Yan. "An Algorithm for Checking Absolute Consistency of DTDs." Journal of Computer Research and Development 42, no. 11 (2005): 1977. http://dx.doi.org/10.1360/crad20051122.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

47

Lee, Byoung-Hoon, Sung-Hwa Lim, Jai-Hoon Kim, and Geoffrey C. Fox. "Lease-based consistency schemes in the web environment." Future Generation Computer Systems 25, no. 1 (January 2009): 8–19. http://dx.doi.org/10.1016/j.future.2008.06.001.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

48

Gutierrez-Nolasco, Sebastian, Nalini Venkatasubramanian, Mark-Oliver Stehr, and Carolyn Talcott. "Tailoring consistency in group membership for mobile networks." Future Generation Computer Systems 31 (February 2014): 134–46. http://dx.doi.org/10.1016/j.future.2013.06.014.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

49

Farkas, Keith, Zvonko Vranesic, and Michael Stumm. "Scalable cache consistency for hierarchically structured multiprocessors." Journal of Supercomputing 8, no. 4 (December 1995): 345–69. http://dx.doi.org/10.1007/bf01901614.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

50

Hossein Sheikh Attar, M., and M. Tamer Özsu. "Alternative Architectures and Protocols for Providing Strong Consistency in Dynamic Web Applications." World Wide Web 9, no. 3 (June 8, 2006): 215–51. http://dx.doi.org/10.1007/s11280-006-8563-1.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.