Journal articles: 'Software patterns'

1

Schmidt, Douglas C., Mohamed Fayad, and Ralph E. Johnson. "Software patterns." Communications of the ACM 39, no. 10 (October 1996): 37–39. http://dx.doi.org/10.1145/236156.236164.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Stevens, P. "Software design patterns." Computing & Control Engineering Journal 11, no. 4 (August 1, 2000): 160–62. http://dx.doi.org/10.1049/cce:20000403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Helm, Richard. "Patterns, architecture and software." ACM SIGPLAN Notices 31, no. 1 (January 1996): 2–3. http://dx.doi.org/10.1145/249094.249099.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Coplien, J. O. "Software patterns: Design utilities." Computer 29, no. 10 (October 1996): 48. http://dx.doi.org/10.1109/mc.1996.539721.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Vogt, Peter. "Patterns in software design." Landscape Ecology 34, no. 9 (March 28, 2019): 2083–89. http://dx.doi.org/10.1007/s10980-019-00797-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Kallja, Aurela. "Software development using design patterns." Ingenious 1, no. 2 (2021): 7–20. http://dx.doi.org/10.58944/uqak8608.

Full text

Abstract:

Information systems have become an integral part of our lives. The demands for software that helps us accomplish our daily tasks are ever-increasing, considering the great technological momentum around the globe. Software engineering is the process of analyzing user requirements and designing and developing software applications. Each user request is a problem that an individual or a business has encountered in the daily work processes. The goal of software engineering is to provide an optimal and efficient solution to these problems to increase the overall productivity of employees in the respective industries and at the end of the day, to increase profits. Providing these solutions is no easy feat, as the problems are often complex and in addition to requiring careful analysis, they also need smart solutions. Fortunately, we have the ability to learn from experience and apply our knowledge in different contexts to achieve our goals. As in any field of life, problems have a recursive nature and it often happens that the same problem is encountered in different contexts. Naturally, we can think that similar problems have similar solutions. The set of solutions to general software design problems in a specific context constitutes what are called design patterns. Design patterns are structures of how some objects dialogue with each other to provide a specific solution to a problem. They are ready-made solutions to known problems, and the real challenge with them is not in their construction, but in the intuitive ability to associate a design problem with the corresponding pattern that offers the most optimal solution. This paper will deal with the development of an information system for an ATM Exchange system, which carries the functionalities of an ATM cash machine and exchange rate chart. The development of this software will be totally based on design patterns, more specifically the “Observer” pattern and “Chain of Responsibility” pattern. This paper aims to emphasize the advantages of using design patterns and highlight their potential to solve general problems in a specific context. It also focuses on software engineers, information systems developers, and software engineering students. This paper will serve as a manual of best software development practices, and emphasize the principles of flexibility and reusability of information systems development components.

APA, Harvard, Vancouver, ISO, and other styles

7

Su, Jian Xia. "The Software Methods for Digital Textile Pattern." Applied Mechanics and Materials 738-739 (March 2015): 1328–31. http://dx.doi.org/10.4028/www.scientific.net/amm.738-739.1328.

Full text

Abstract:

Based on the analyzing of digital textile picture, pattern, and feature, Digital textile computer simulation is proposed in this paper. A series of softwares are used to make the digital patterns. and some examples are showed done by software. They are created by experiments of classic patterns and parameters or combination of several softwares.The results shows that the methods of making digital textile pattern are useful and available.

APA, Harvard, Vancouver, ISO, and other styles

8

Alshudukhi, Jalawi Sulaiman. "Pattern-based solution for architecting cloud-enabled software." International Journal of ADVANCED AND APPLIED SCIENCES 8, no. 8 (August 2021): 9–19. http://dx.doi.org/10.21833/ijaas.2021.08.002.

Full text

Abstract:

Cloud computing exploits the software as a service model with distributed and interoperable services for the composition of software systems. Cloud-enabled systems that demand elasticity, scalability, and composition of services, etc., there is a need to capitalize on reusable solutions exploiting patterns and styles to architect cloud-based software. The objective of this research is to build and exploit a catalog of patterns that support reusable design knowledge to develop cloud-based architectures. We propose a three-step process with (i) pattern discovery, (ii) pattern documentation (building the catalog), and finally, (iii) pattern application (exploiting the catalog) to enable pattern-based architecting of cloud systems. We discovered seven patterns as generic and reusable solutions and demonstrate the pattern-driven architecture of the ECMC case study. Results suggest that pattern-based architecting enables the reuse of generic design decisions but lacks fine-grained architectural design. The solution is the first attempt towards establishing the catalog as a repository of patterns for architecture-based development of cloud systems.

APA, Harvard, Vancouver, ISO, and other styles

9

D Kulkarni, Nilesh, and Saurav Bansal. "Strategy Design Pattern Applied on a Mobile App Building." Journal of Mathematical & Computer Applications 1, no. 1 (March 31, 2022): 1–6. http://dx.doi.org/10.47363/jmca/2022(1)121.

Full text

Abstract:

This paper provides the importance and application of design patterns in software engineering, particularly focusing on the Strategy Design Pattern. It outlines how design patterns offer efficient, flexible, and reusable solutions to common problems in object-oriented software development. The paper presents a case study of Strategy Design Pattern’s application in a mobile app builder, emphasizing its role in creating adaptable and maintainable software architecture. Additionally incorporates commentary on the SOLID Open and Close principle, explaining how it allows software entities to be extendable without modifying existing code, thus enhancing the scalability and robustness of the application. The OC principle integration with the Strategy Design Pattern demonstrates its practicality in promoting flexible and stable software development.

APA, Harvard, Vancouver, ISO, and other styles

10

Harrison, Neil B., and James O. Coplien. "Patterns of productive software organizations." Bell Labs Technical Journal 1, no. 1 (1996): 138–45. http://dx.doi.org/10.15325/bltj.1996.6780050.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Gay, David, Philip Levis, and David Culler. "Software design patterns for TinyOS." ACM Transactions on Embedded Computing Systems 6, no. 4 (September 2007): 22. http://dx.doi.org/10.1145/1274858.1274860.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Kircher, Michael, and Markus Volter. "Guest Editors' Introduction: Software Patterns." IEEE Software 24, no. 4 (July 2007): 28–30. http://dx.doi.org/10.1109/ms.2007.109.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Gay, David, Phil Levis, and David Culler. "Software design patterns for TinyOS." ACM SIGPLAN Notices 40, no. 7 (July 12, 2005): 40–49. http://dx.doi.org/10.1145/1070891.1065917.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Stoenoiu, Carmen Elena. "Patterns in enterprise management software." Balkan Region Conference on Engineering and Business Education 2, no. 1 (December 20, 2017): 292–300. http://dx.doi.org/10.1515/cplbu-2017-0038.

Full text

Abstract:

Abstract In this paper a study was conducted on the complex integrated software that exists on the Romanian market. This consisted in identifying and analysing the size of the enterprise, the number of users, the technical characteristics determined by the type and number of modules included in the software and other information related to the implementation, according to the supplier's specifications. The primary analysis made it possible to obtain results regarding the integrated software market in Romania in terms of customer size, field of activity, software products that include the biggest number of modules. By statistical analysis using the multivariate cluster grouping exploration technique, the degree of similarity between the software and the modules was determined, calculating the distance by means of three measurement methods: the Euclidean distance, the percentage of disagreement, and the correlation coefficient 1- Pearson-r.

APA, Harvard, Vancouver, ISO, and other styles

15

Stamelos, Ioannis. "Software project management anti-patterns." Journal of Systems and Software 83, no. 1 (January 2010): 52–59. http://dx.doi.org/10.1016/j.jss.2009.09.016.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Bola�os Castro, Sandro Javier, Rub�n Gonz�lez Crespo, and Victor Hugo Medina Garc�a. "Patterns of Software Development Process." International Journal of Interactive Multimedia and Artificial Intelligence 1, no. 4 (2011): 33. http://dx.doi.org/10.9781/ijimai.2011.146.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Solinas, Miguel, and Leandro Antonelli. "Software evolution and design patterns." IEEE Latin America Transactions 11, no. 1 (February 2013): 347–52. http://dx.doi.org/10.1109/tla.2013.6502828.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Mateosian, Richard. "Software Development Patterns [Micro Review]." IEEE Micro 28, no. 5 (September 2008): 72. http://dx.doi.org/10.1109/mm.2008.78.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Harrison, Neil B., and James O. Coplien. "Patterns of productive software organizations." Bell Labs Technical Journal 1, no. 1 (1996): 138–45. http://dx.doi.org/10.1002/1538-7035(199622)1:1<138::aid-bltj2010>3.0.co;2-g.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Harrison, Neil B., and James O. Coplien. "Patterns of productive software organizations." Bell Labs Technical Journal 1, no. 1 (1996): 138–45. http://dx.doi.org/10.1002/1538-7305(199621)1:1<138::aid-bltj2010>3.0.co;2-p.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Harrison, Neil B., and James O. Coplien. "Patterns of productive software organizations." Bell Labs Technical Journal 1, no. 1 (1996): 138–45. http://dx.doi.org/10.1002/1538-7305(199622)1:1<138::aid-bltj2010>3.0.co;2-m.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Uzakova, Umida, and Sevara Murodova. "Weaving construction software system." E3S Web of Conferences 497 (2024): 02038. http://dx.doi.org/10.1051/e3sconf/202449702038.

Full text

Abstract:

The construction methods within the Desint system are organized into three distinct groups, each catering to specific aspects of the weaving process. These groups delineate the procedures involved in creating woven patterns and are selected based on the type of the initial element required to achieve the final desired weave. This group encompasses construction methods that initiate the weaving process from fundamental elements. These elements can range from a single thread to a collection of threads. The focus is on building the foundational structure of the weave, starting from basic components. The second group of construction methods deals with the assembly of specific parts of pattern rapports using the initial elements established in Group 1. It involves combining and arranging these elements to form intricate patterns within the weave. This stage contributes to the development of more complex and detailed designs. The third group is dedicated to specialized methods for constructing pattern rapports with a specific arrangement, often guided by a pre-determined drawing or design. This group involves intricate techniques that go beyond basic weaving, allowing for the creation of intricate and customized patterns based on artistic or functional requirements. The choice of the group is contingent upon the type of initial element essential for constructing the final desired weave. This systematic categorization enables weavers to select the most appropriate set of methods based on the intended design complexity and intricacy.

APA, Harvard, Vancouver, ISO, and other styles

23

Macasaet, RJ, Manuel Noguera, María Luisa Rodríguez, José Luis Garrido, Sam Supakkul, and Lawrence Chung. "Representing Micro-Business Requirements Patterns with Associated Software Components." International Journal of Information System Modeling and Design 5, no. 4 (October 2014): 71–90. http://dx.doi.org/10.4018/ijismd.2014100104.

Full text

Abstract:

This paper proposes representations for micro-business requirements patterns with associated software components. The patterns must be comprehensible enough for micro-business owners without technical backgrounds but at the same time be technical enough for the software developers who use them during the design and development of software. Both objectives are somewhat conflicting and trade-offs have to be made regarding their representations. The pattern representations use a combination of tables, business process models, goal graphs, labels, and UML component diagrams. First, the paper provides an example of a micro-business requirements pattern in the form of an inventory pattern and applies it in a real-world micro-business case, a clothes retail store. Through the example, it shows how the pattern is instantiated and associated with software components. Then, it shows how the patterns are applied in industrial practice, including the software development companies currently adapting and applying them, accompanied by observable strengths and weaknesses.

APA, Harvard, Vancouver, ISO, and other styles

24

Ghaleb, Taher Ahmed, Khalid Aljasser, and Musab A. Alturki. "An Extensible Compiler for Implementing Software Design Patterns as Concise Language Constructs." International Journal of Software Engineering and Knowledge Engineering 31, no. 07 (July 2021): 1043–67. http://dx.doi.org/10.1142/s0218194021500327.

Full text

Abstract:

Design patterns are generic solutions to common programming problems. Design patterns represent a typical example of design reuse. However, implementing design patterns can lead to several problems, such as programming overhead and traceability. Existing research introduced several approaches to alleviate the implementation issues of design patterns. Nevertheless, existing approaches pose different implementation restrictions and require programmers to be aware of how design patterns should be implemented. Such approaches make the source code more prone to faults and defects. In addition, existing design pattern implementation approaches limit programmers to apply specific scenarios of design patterns (e.g. class-level), while other approaches require scattering implementation code snippets throughout the program. Such restrictions negatively impact understanding, tracing, or reusing design patterns. In this paper, we propose a novel approach to support the implementation of software design patterns as an extensible Java compiler. Our approach allows developers to use concise, easy-to-use language constructs to apply design patterns in their code. In addition, our approach allows the application of design patterns in different scenarios. We illustrate our approach using three commonly used design patterns, namely Singleton, Observer and Decorator. We show, through illustrative examples, how our design pattern constructs can significantly simplify implementing design patterns in a flexible, reusable and traceable manner. Moreover, our design pattern constructs allow class-level and instance-level implementations of design patterns.

APA, Harvard, Vancouver, ISO, and other styles

25

CONRADI, REIDAR, MINH NGOC NGUYEN, ALF INGE WANG, and CHUNNIAN LIU. "PLANNING SUPPORT TO SOFTWARE PROCESS EVOLUTION." International Journal of Software Engineering and Knowledge Engineering 10, no. 01 (February 2000): 31–47. http://dx.doi.org/10.1142/s0218194000000043.

Full text

Abstract:

The ability to handle changes is a characteristic feature of successful software projects. The problem addressed in this paper is what should be done in project planning and iterative replanning so that the project can react effectively to changes. Thus the work presents research results in software engineering, as well as transfer of methods in knowledge engineering to software engineering, applying the AI planning technique to software process modeling and software project management. Our method is based on inter-project experience and evolution patterns. We propose a new classification of software projects, identifying and characterizing ten software process evolution patterns and link them to different project profile. Based on the evolution patterns, we discuss the planning support for process evolution and propose several methods that are new or significantly extend existing work, e.g. cost estimation of process changes, evolution pattern analysis, and a coarse process model for the initial planning and the iterative replanning process. The preliminary results have shown that the study of evolution patterns, based on inter-project experience, can provide valuable guidance in software process understanding and improvement.

APA, Harvard, Vancouver, ISO, and other styles

26

Yu, Liguo, Yingmei Li, and Srini Ramaswamy. "Design Patterns and Design Quality." International Journal of Secure Software Engineering 8, no. 2 (April 2017): 53–81. http://dx.doi.org/10.4018/ijsse.2017040103.

Full text

Abstract:

Design patterns are reusable software design solutions to object-oriented programs. Since the initial introduction of the 23 well-known design patterns in 1995, more and more patterns have been identified and utilized in the software industry. The benefits of applying design patterns include reducing development cost, improving code quality, and standardizing the integration and maintenance processes. Therefore, using design patterns is becoming a common practice to build both commercial software and open-source products. Although most design patterns are considered creative solutions to some difficult design problems, not all of them are necessarily the best with respect to all different software quality measures, such as program complexity. This paper studies 13 commonly employed design patterns in software industry. First, these 13 patterns are analyzed theoretically about their design complexity in comparison to the conventional solutions. Second, empirical studies are performed on five open-source Java projects to investigate the correlations between design patterns and class structural quality. Finally, these 13 design patterns are evaluated by software programmers who have experience of using all of them. Overall, this study finds that although some design patterns are considered useful, creative, and significant compared to conventional solutions based on user experience, pattern-involved classes are more complex than pattern-free classes, both theoretically and empirically. The authors accordingly recommend a balanced approach to using design patterns: design quality, cost, development time, and product quality should all be considered, when design patterns are utilized.

APA, Harvard, Vancouver, ISO, and other styles

27

Liu, Cong. "A General Framework to Detect Design Patterns by Combining Static and Dynamic Analysis Techniques." International Journal of Software Engineering and Knowledge Engineering 31, no. 01 (January 2021): 21–54. http://dx.doi.org/10.1142/s0218194021400027.

Full text

Abstract:

Design pattern detection can provide useful insights to support software comprehension. Accurate and complete detection of pattern instances are extremely important to enable software usability improvements. However, existing design pattern detection approaches and tools suffer from the following problems: incomplete description of design pattern instances, inaccurate behavioral constraint checking, and inability to support novel design patterns. This paper presents a general framework to detect design patterns while solving these issues by combining static and dynamic analysis techniques. The framework has been instantiated for typical behavioral and creational patterns, such as the observer pattern, state pattern, strategy pattern, and singleton pattern to demonstrate the applicability. Based on the open-source process mining toolkit ProM, we have developed an integrated tool that supports the whole detection process for these patterns. We applied and evaluated the framework using software execution data containing around 1,000,000 method calls generated from eight synthetic software systems and three open-source software systems. The evaluation results show that our approach can guarantee a higher precision and recall than existing approaches and can distinguish state and strategy patterns that are indistinguishable by the state-of-the-art.

APA, Harvard, Vancouver, ISO, and other styles

28

Fowler, M. "Patterns." IEEE Software 20, no. 2 (March 2003): 56–57. http://dx.doi.org/10.1109/ms.2003.1184168.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Wang, Hong. "The Research on Software Reuse Technology." Applied Mechanics and Materials 543-547 (March 2014): 2929–32. http://dx.doi.org/10.4028/www.scientific.net/amm.543-547.2929.

Full text

Abstract:

Software reuse has gained increasing attention by academic organizations and software development agencies. Existing researches on software pattern concentrate on constructing and representing patterns in unstructured way, so it is difficult to maintain and reuse them. This article puts forward pattern-oriented software development process that integrates modeling method based on architecture with software process for software reuse. Through the research on pattern oriented software development process, the reusability of software is enhanced.

APA, Harvard, Vancouver, ISO, and other styles

30

McMeel, Dermott John James, and Robert Amor. "Knitting Patterns." International Journal of Art, Culture and Design Technologies 5, no. 2 (July 2016): 1–16. http://dx.doi.org/10.4018/ijacdt.2016070101.

Full text

Abstract:

Large software conglomerates like Trimble and Autodesk provide consumers with suites of software that perform many functions within the design and construction process. Communicating with software outside of the suite can be highly problematic as file types and communication protocols are proprietary and closed within that software family - the antithesis of interoperability). This is in stark contrast with emerging trends in consumer computing, where we find a rich ecosystem of devices and services facilitating a period of intense innovation. This paper documents original research that aims to implement communication beyond specific software suites and test, to what extent, wider software ecosystems revolving around open standards might be implemented within the design and construction domain. Our first test case—an agent-based dynamic simulation combining natural and built environmental components—is deployed to explore the city as a multitude of interrelated natural and built patterns. We analyze the role this simulation might play in managing the complexities of rebuilding a sustainable urban environment after the devastating earthquake in Christchurch, New Zealand. The second test case deploys an iPad application to communicate with a BIM model - exploring the development of a mobile application and methodology for openly communicating outside of the intended software family. Through these case studies we begin to identify ways to leverage emergent device and data ecosystems and representations for ‘knitting' devices and services together in innovative ways to advance design and construction processes.

APA, Harvard, Vancouver, ISO, and other styles

31

Zhang, Dengpan, and Hongli Zhu. "Software Reconfiguration Patterns for Instrumentation Architectures." Open Automation and Control Systems Journal 7, no. 1 (July 10, 2015): 646–54. http://dx.doi.org/10.2174/1874444301507010646.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Edwin, Njeru Mwendi. "Software Frameworks, Architectural and Design Patterns." Journal of Software Engineering and Applications 07, no. 08 (2014): 670–78. http://dx.doi.org/10.4236/jsea.2014.78061.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Ghazal, Ghadeer, Amjad Hudaib, and Waffa Maitah. "Software Architectural Patterns for Service Composition." International Journal of Computer Science and Information Technology 6, no. 4 (August 31, 2014): 31–45. http://dx.doi.org/10.5121/ijcsit.2014.6403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Heer, Jeffrey, and Maneesh Agrawala. "Software Design Patterns for Information Visualization." IEEE Transactions on Visualization and Computer Graphics 12, no. 5 (September 2006): 853–60. http://dx.doi.org/10.1109/tvcg.2006.178.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Janert, P. K. "Software Configuration Management Patterns [Book Review]." IEEE Software 21, no. 1 (January 2004): 104–5. http://dx.doi.org/10.1109/ms.2004.1259254.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Prikladnicki, R., J. L. N. Audy, and F. Shull. "Patterns in Effective Distributed Software Development." IEEE Software 27, no. 2 (March 2010): 12–15. http://dx.doi.org/10.1109/ms.2010.48.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Holmberg, L., and L. Mathiassen. "Survival patterns in fast-moving software." IEEE Software 18, no. 6 (2001): 51–55. http://dx.doi.org/10.1109/52.965802.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

MacGregor, Eve, Yvonne Hsieh, and Philippe Kruchten. "Cultural patterns in software process mishaps." ACM SIGSOFT Software Engineering Notes 30, no. 4 (July 2005): 1–5. http://dx.doi.org/10.1145/1082983.1083116.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Itoh, Kiyohito, and Hiromi Kobayashi. "A Safety Mechanism Using Software Patterns." Electronic Notes in Theoretical Computer Science 82, no. 6 (September 2003): 110–20. http://dx.doi.org/10.1016/s1571-0661(04)81030-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Rajesh, Sudha, and A. Chandrasekar. "Esteemed software patterns for banking system." Cluster Computing 22, S5 (November 24, 2017): 11087–99. http://dx.doi.org/10.1007/s10586-017-1304-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Hepner, M., R. Gamble, M. Kelkar, L. Davis, and D. Flagg. "Patterns of conflict among software components." Journal of Systems and Software 79, no. 4 (April 2006): 537–51. http://dx.doi.org/10.1016/j.jss.2005.11.211.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Jin, Jiangang, Shibao Sun, and Xiaoan Bao. "Research of Adaptive Software Design’s Patterns." International Journal of Control and Automation 9, no. 5 (May 31, 2016): 289–96. http://dx.doi.org/10.14257/ijca.2016.9.5.28.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Mary, S. Roselin, Paul Rodrigues, and E. R. Naganathan. "Patterns of software architecture in vastu." ACM SIGSOFT Software Engineering Notes 38, no. 6 (November 11, 2013): 1–6. http://dx.doi.org/10.1145/2532780.2532815.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Harrison, Neil B., Uwe van Heesch, Stefan Sobernig, Peter Sommerlad, Martin Filipczyk, Alexander Fülleborn, Angelika Musil, and Juergen Musil. "Software Architecture Patterns: Reflection and Advances." ACM SIGSOFT Software Engineering Notes 40, no. 1 (February 6, 2015): 30–34. http://dx.doi.org/10.1145/2693208.2693218.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Blilie, C. "Patterns in scientific software: an introduction." Computing in Science & Engineering 4, no. 3 (2002): 48–53. http://dx.doi.org/10.1109/5992.998640.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Egyed, Alexander, and Barry Boehm. "Comparing software system requirements negotiation patterns." Systems Engineering 2, no. 1 (1999): 1–14. http://dx.doi.org/10.1002/(sici)1520-6858(1999)2:1<1::aid-sys1>3.0.co;2-f.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Fan, G. Y., and J. M. Cowley. "Software pattern recognition applied to nanodiffraction patterns from a STEM instrument." Proceedings, annual meeting, Electron Microscopy Society of America 44 (August 1986): 694–95. http://dx.doi.org/10.1017/s042482010014484x.

Full text

Abstract:

In recent developments, the ASU HB5 has been modified so that the timing, positioning, and scanning of the finely focused electron probe can be entirely controlled by a host computer. This made the asynchronized handshake possible between the HB5 STEM and the image processing system which consists of host computer (PDP 11/34), DeAnza image processor (IP 5000) which is interfaced with a low-light level TV camera, array processor (AP 400) and various peripheral devices. This greatly facilitates the pattern recognition technique initiated by Monosmith and Cowley. Software called NANHB5 is under development which, instead of employing a set of photo-diodes to detect strong spots on a TV screen, uses various software techniques including on-line fast Fourier transform (FFT) to recognize patterns of greater complexity, taking advantage of the sophistication of our image processing system and the flexibility of computer software.

APA, Harvard, Vancouver, ISO, and other styles

48

Mastanvali, Shaik. "A Study on Framework for Anti-Pattern Evaluation of System Software." International Journal for Research in Applied Science and Engineering Technology 9, no. 12 (December 31, 2021): 1990–95. http://dx.doi.org/10.22214/ijraset.2021.39672.

Full text

Abstract:

Abstract: Studies with a variety of viewpoints, goals, measurements, and quality characteristics have been conducted in order to determine the effect of design patterns on quality attributes. This has resulted in findings that are contradictory and difficult to compare. They want to explain these findings by taking into account confounding variables, practises, measurements, and implementation problems that have an impact on quality. Furthermore, there is a paucity of research that establishes a link between design pattern assessments and pattern creation studies, which is a significant limitation. For the purpose of detecting and categorising software performance anti-patterns, this article proposes a non-intrusive machine learning method dubbed Non-intrusive Performance Anti-pattern Detector (NiPAD). Keywords: software performance, anti-patterns, classification, machine learning, dynamic software analysis

APA, Harvard, Vancouver, ISO, and other styles

49

Atkinson, Darren C., and William G. Griswold. "Effective pattern matching of source code using abstract syntax patterns." Software: Practice and Experience 36, no. 4 (2006): 413–47. http://dx.doi.org/10.1002/spe.704.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Medina, Oscar Carlos, Manuel Pérez Cota, Brenda Elizabeth Meloni, and Marcelo Martín Marciszack. "Business Patterns Catalogue and Selection Proposal for the Conceptual Model of a Software Product." JUCS - Journal of Universal Computer Science 27, no. 2 (February 28, 2021): 135–51. http://dx.doi.org/10.3897/jucs.65083.

Full text

Abstract:

A pattern is a model that allows reusing a successful solution to the same problem in a different context. A pattern implementation could be the elaboration of an analysis model to incorporate good practices patterns Conceptual Modelling of Electronic Government systems. Defining a new pattern, and selecting a previously existing one from a limited set, called catalogue, are essential activities that every analysis model must solve when using patterns. The present work describes a proposal to manage a Business Patterns catalogue that can be applied to Conceptual Modelling of software products. Business Patterns allow to model and design business processes inside an organization, being it public or private. An application, called “PatCat” (Pattern Catalogue), was developed to test de proposal, using the Business Model of an Information System for a public education institution as a pilot. The introduction of patterns at the beginning of the Modelling Process allows to simplify and clarify the requirements elicitation, amongst other benefits. Thus, a specific management application for a pattern catalogue is useful to standardize and speed up this software design task.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Software patterns'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles