Journal articles: 'Software methodologies and engineering'

1

Masood, Zafar, Xuequn Shang, and Jamal Yousaf. "Usability Evaluation Framework for Software Engineering Methodologies." Lecture Notes on Software Engineering 2, no. 3 (2014): 225–32. http://dx.doi.org/10.7763/lnse.2014.v2.127.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Srinivasan, K. P., and T. Devi. "Software Metrics Validation Methodologies in Software Engineering." International Journal of Software Engineering & Applications 5, no. 6 (2014): 87–102. http://dx.doi.org/10.5121/ijsea.2014.5606.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Shtern, Mark, and Vassilios Tzerpos. "Clustering Methodologies for Software Engineering." Advances in Software Engineering 2012 (May 10, 2012): 1–18. http://dx.doi.org/10.1155/2012/792024.

Full text

Abstract:

The size and complexity of industrial strength software systems are constantly increasing. This means that the task of managing a large software project is becoming even more challenging, especially in light of high turnover of experienced personnel. Software clustering approaches can help with the task of understanding large, complex software systems by automatically decomposing them into smaller, easier-to-manage subsystems. The main objective of this paper is to identify important research directions in the area of software clustering that require further attention in order to develop more effective and efficient clustering methodologies for software engineering. To that end, we first present the state of the art in software clustering research. We discuss the clustering methods that have received the most attention from the research community and outline their strengths and weaknesses. Our paper describes each phase of a clustering algorithm separately. We also present the most important approaches for evaluating the effectiveness of software clustering.

APA, Harvard, Vancouver, ISO, and other styles

4

Gómez-Sanz, Jorge J., and Rubén Fuentes-Fernández. "Understanding Agent-Oriented Software Engineering methodologies." Knowledge Engineering Review 30, no. 4 (2015): 375–93. http://dx.doi.org/10.1017/s0269888915000053.

Full text

Abstract:

AbstractFor many years, the progress in agent-oriented development has focused on tools and methods for particular development phases. This has not been enough for the industry to accept agent technology as we expected. Our hypothesis is that the Agent-Oriented Software Engineering (AOSE) community has not recognized the kind of development methods that industry actually demands. We propose to analyze this hypothesis starting with a more precise definition of what an AOSE methodology should be. This definition is the first step for a review of the current progress of an illustrative selection of methodologies, looking for missing elements and future lines of improvement. The result is an account of how well the AOSE community is meeting the software lifecycle needs. It can be advanced that AOSE methodologies are far from providing all the answers industry requires and that effort has grounded mainly in requirements, design, and implementation phases.

APA, Harvard, Vancouver, ISO, and other styles

5

Wassyng, Alan, and Mark Lawford. "Integrated software methodologies – An engineering approach." Transactions of the Royal Society of South Africa 65, no. 2 (2010): 125–36. http://dx.doi.org/10.1080/0035919x.2010.522449.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Kamepally, Arun Kumar, and Tejaswini Nalamothu. "Agile Methodologies in Software Engineering and Web Engineering." International Journal of Education and Management Engineering 6, no. 5 (2016): 1–14. http://dx.doi.org/10.5815/ijeme.2016.05.01.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Cross, M., A. O. Moscardini, and B. A. Lewis. "Software engineering methodologies for scientific and engineering computation." Applied Mathematical Modelling 10, no. 5 (1986): 376–85. http://dx.doi.org/10.1016/0307-904x(86)90097-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

BERNON, CAROLE, MASSIMO COSSENTINO, and JUAN PAVÓN. "Agent-oriented software engineering." Knowledge Engineering Review 20, no. 2 (2005): 99–116. http://dx.doi.org/10.1017/s0269888905000421.

Full text

Abstract:

Considering the great number of agent-oriented methodologies that can be found in the literature, and the fact that each one defines its own concepts and system structure, one of the main challenges in agent-oriented software engineering (AOSE) research is how to make these methodologies interoperable. By defining concepts used in a specific domain in a non-ambiguous way, meta-modelling may represent a step towards such interoperability. Consequently the main objective of the AOSE TFG (Technical Forum Group) is to establish a strategy for identifying a common meta-model that could be widely adopted by the AOSE community. This paper sums up the approach used by this TFG which consists of (i) studying and comparing the meta-models related to some existing methodologies (ADELFE, Gaia, INGENIAS, PASSI, RICA and Tropos) in order to find commonalities and (ii) giving a clear and basic definition for the core concepts used in multi-agent systems for relating and positioning them in a unified MAS meta-model. The first proposal, set up by the working group, for this unified meta-model then concludes this paper.

APA, Harvard, Vancouver, ISO, and other styles

9

Molesini, Ambra, Andrea Omicini, and Mirko Viroli. "Environment in agent-oriented software engineering methodologies." Multiagent and Grid Systems 5, no. 1 (2009): 37–57. http://dx.doi.org/10.3233/mgs-2009-0118.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Fox, John. "Methodologies for knowledge engineering." Knowledge Engineering Review 7, no. 2 (1992): 95–96. http://dx.doi.org/10.1017/s0269888900006214.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Fonseca, Victor M. Flores, and Jesica Gomez. "Applying Active Methodologies for Teaching Software Engineering in Computer Engineering." IEEE Revista Iberoamericana de Tecnologias del Aprendizaje 12, no. 3 (2017): 147–55. http://dx.doi.org/10.1109/rita.2017.2738178.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Flores Fonseca, Victor M., and Jesica Gomez. "Applying Active Methodologies for Teaching Software Engineering in Computer Engineering." IEEE Revista Iberoamericana de Tecnologias del Aprendizaje 12, no. 4 (2017): 182–90. http://dx.doi.org/10.1109/rita.2017.2778358.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

PALMER, KENT D. "SOFTWARE ENGINEERING DESIGN METHODOLOGIES AND GENERAL SYSTEMS THEORY." International Journal of General Systems 24, no. 1-2 (1996): 43–94. http://dx.doi.org/10.1080/03081079608945107.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Abdalla, Reem, and Alok Mishra. "Agent-Oriented Software Engineering Methodologies: Analysis and Future Directions." Complexity 2021 (December 29, 2021): 1–21. http://dx.doi.org/10.1155/2021/1629419.

Full text

Abstract:

The Internet of Things (IoT) facilitates in building cyber-physical systems, which are significant for Industry 4.0. Agent-based computing represents effective modeling, programming, and simulation paradigm to develop IoT systems. Agent concepts, techniques, methods, and tools are being used in evolving IoT systems. Over the last years, in particular, there has been an increasing number of agent approaches proposed along with an ever-growing interest in their various implementations. Yet a comprehensive and full-fledged agent approach for developing related projects is still lacking despite the presence of agent-oriented software engineering (AOSE) methodologies. One of the moves towards compensating for this issue is to compile various available methodologies, ones that are comparable to the evolution of the unified modeling language (UML) in the domain of object-oriented analysis and design. These have become de facto standards in software development. In line with this objective, the present research attempts to comprehend the relationship among seven main AOSE methodologies. More specifically, we intend to assess and compare these seven approaches by conducting a feature analysis through examining the advantages and limitations of each competing process, structural analysis, and a case study evaluation method. This effort is made to address the significant characteristics of AOSE approaches. The main objective of this study is to conduct a comprehensive analysis of selected AOSE methodologies and provide a proposal of a draft unified approach that drives strengths (best) of these methodologies towards advancement in this area.

APA, Harvard, Vancouver, ISO, and other styles

15

del Águila, Isabel M., José Palma, and Samuel Túnez. "Milestones in Software Engineering and Knowledge Engineering History: A Comparative Review." Scientific World Journal 2014 (2014): 1–10. http://dx.doi.org/10.1155/2014/692510.

Full text

Abstract:

We present a review of the historical evolution of software engineering, intertwining it with the history of knowledge engineering because “those who cannot remember the past are condemned to repeat it.” This retrospective represents a further step forward to understanding the current state of both types of engineerings; history has also positive experiences; some of them we would like to remember and to repeat. Two types of engineerings had parallel and divergent evolutions but following a similar pattern. We also define a set of milestones that represent a convergence or divergence of the software development methodologies. These milestones do not appear at the same time in software engineering and knowledge engineering, so lessons learned in one discipline can help in the evolution of the other one.

APA, Harvard, Vancouver, ISO, and other styles

16

Gu, Qing, and Patricia Lago. "Guiding the selection of service-oriented software engineering methodologies." Service Oriented Computing and Applications 5, no. 4 (2011): 203–23. http://dx.doi.org/10.1007/s11761-011-0080-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Gupta, Archit. "Software Engineering in Healthcare." International Journal for Research in Applied Science and Engineering Technology 9, no. 11 (2021): 326–28. http://dx.doi.org/10.22214/ijraset.2021.38845.

Full text

Abstract:

Abstract: As technology is advancing and affecting every phase of human life, health care facilities are also getting improved with the introduction of new advanced, customized, and patient-centric approaches in software engineering. Engineers all around the world are working to create unique and efficient ways for the prevention and early detection of diseases along with improving the patients’ experience while using these technologies. With the gain in computing power and access to a wide range of software, software engineers are working on technologies such as Big Data, AI, Data Science, and Cybersecurity to improve the existing methodologies and pave the way for patient-centric approaches and knowledge translation.

APA, Harvard, Vancouver, ISO, and other styles

18

Kamthan, Pankaj. "On the Nature of Collaborations in Agile Software Engineering Course Projects." International Journal of Quality Assurance in Engineering and Technology Education 5, no. 2 (2016): 42–59. http://dx.doi.org/10.4018/ijqaete.2016040104.

Full text

Abstract:

If there is a constant in software development, then it is that its ecosystem is a variable. The agile methodologies are part of a relatively recent shift from predictive to adaptive approach towards software development. This change has had a notable impact on software engineering education (SEE). In this article, a glimpse into the state-of-the-art of incorporating agile methodologies in software engineering courses is presented. In doing so, the reasons for including a project component in software engineering courses, and for committing to agile methodologies in software engineering projects in those courses, are given. The significance of collaboration in the execution of agile methodologies, in general, is underscored, and the pivotal role of collaboration in agile course projects, in particular, is emphasized. To lend an understanding to the notion of collaboration in agile methodologies, a conceptual model for collaboration is proposed and elaborated. The types of collaborations that can occur in agile course projects are classified and discussed. The use technological means for facilitating collaboration, including the Social Web and especially the Wiki, is highlighted.

APA, Harvard, Vancouver, ISO, and other styles

19

Alsaqqa, Samar, Samer Sawalha, and Heba Abdel-Nabi. "Agile Software Development: Methodologies and Trends." International Journal of Interactive Mobile Technologies (iJIM) 14, no. 11 (2020): 246. http://dx.doi.org/10.3991/ijim.v14i11.13269.

Full text

Abstract:

<p>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.</p><p>In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</p>

APA, Harvard, Vancouver, ISO, and other styles

20

Javier, Sandro Bolanos Castro, Ruben Gonzalez Crespo, and Victor Hugo Medina. "Software Processes and Methodologies Modeling Language SPMML, A Holistic Solution for Software Engineering." IEEE Latin America Transactions 12, no. 4 (2014): 818–24. http://dx.doi.org/10.1109/tla.2014.6868888.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Hammo, Asmaa, and Maher Alasaady. "Evaluate and comparission between Software Engineering Methodologies of Agent Systems." AL-Rafidain Journal of Computer Sciences and Mathematics 9, no. 2 (2012): 43–61. http://dx.doi.org/10.33899/csmj.2012.163718.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Ansari, Mohammed Afzal, and Kiran Bhimrao Ingle. "Software Testing." International Journal for Research in Applied Science and Engineering Technology 10, no. 6 (2022): 979–84. http://dx.doi.org/10.22214/ijraset.2022.43914.

Full text

Abstract:

Abstract— With the developing complexity of today’s software program applications injunction with the increasing competitive pressure has driven the excellent assurance of developed software towards new heights. software program trying out is an inevitable part of the software program development Lifecycle and retaining in keeping with its criticality in the pre and submit development process makes it something that have to be catered with stronger and green methodologies and strategies. This paper objectives to speak about the prevailing in addition to advanced trying out techniques for the betterquality warranty functions. Keywords— Testing Methodologies, Software Testing Life Cycle, Testing Frameworks, Automation Testing, Test Driven Development, Test optimization, Quality Metrics

APA, Harvard, Vancouver, ISO, and other styles

23

Hefley, William E., Elizabeth A. Buie, Gene F. Lynch, et al. "Integrating Human Factors with Software Engineering Practices." Proceedings of the Human Factors and Ergonomics Society Annual Meeting 38, no. 4 (1994): 315–19. http://dx.doi.org/10.1177/154193129403800427.

Full text

Abstract:

Engineering processes and methodologies used in building tomorrow's systems must place a greater emphasis on designing usable systems that meet the needs of the systems' users and their tasks. This paper identifies the need for defining human factors and human-computer interaction (HCI) engineering activities that contribute to the design, development, and evaluation of usable and useful interactive systems, and presents a rationale for integrating these activities with software engineering and incorporating them into the system life cycle.

APA, Harvard, Vancouver, ISO, and other styles

24

Rodriguez-Martinez, Laura, Hector Duran-Limon, Manuel Mora, and Francisco Rodriguez. "SOCA-DSEM: A well-structured SOCA development systems engineering methodology." Computer Science and Information Systems 16, no. 1 (2019): 19–44. http://dx.doi.org/10.2298/csis170703035r.

Full text

Abstract:

Service-oriented Software Engineering (SOSE) is a software engineering paradigm focused on Service-oriented Computing Applications (SOCAs), for what SOCA development methodologies are required. Recent studies on SOCA development methodologies revealed theoretical and practical deficiencies. Thus, academicians and practitioners must adapt development methodologies from other paradigms or use the available partial SOCA development methodologies. Also, since the high acceptance of agile approaches, we claim new well-structured and balanced agility-rigor methodologies are required. Then, this paper proposes a new SOCA Development Systems Engineering Methodology, including its description, the explanation of its theoretical foundations and the illustration of its use with a prototype of a running example. Two pilot empirical evaluations on usability metrics are also reported. Findings support both theoretical adequacy and positive perceptions from the evaluators. While further empirical tests are required for gaining more conclusive evidences our preliminary results are encouraging.

APA, Harvard, Vancouver, ISO, and other styles

25

Fotariya, Mr Anuj, and Mr Omprakash Mandge. "Systematic Review of Agile Methodologies for Software Development." International Journal for Research in Applied Science and Engineering Technology 10, no. 6 (2022): 1771–74. http://dx.doi.org/10.22214/ijraset.2022.44143.

Full text

Abstract:

Abstract: With the increase in complexity and innovation in IT products and services, developing them, that to by the shared efforts of team members brings in the need of some standardized development model or approach. Due to several advantages of agile methodologies over the traditional waterfall based models, it is the preferred choice. Many a times, a single agile method is also not enough to meet the current scenario of product development. We therefore propose a Competitor Driven Development (CDD) model, a hybrid agile process model for IT product development by abstracting practices from Extreme Programming (XP) and Feature Driven Reuse Development (FDRD) agile methods. This model is based on self-realizing requirements generation for Product development by keeping an eye watch on competitor’s upcoming launch of the product and market response to it rather than customer explicitly specifying the requirements. This development model can be generally used by the organizations who intend to develop IT product for mass targeted customers rather than an individual or an organization.

APA, Harvard, Vancouver, ISO, and other styles

26

Bandyopadhyay, Biswadeb. "A Large Software System Test Engineering Practices." American Journal of Advanced Computing 1, no. 3 (2020): 1–10. http://dx.doi.org/10.15864/ajac.1301.

Full text

Abstract:

The following Paper describes the experiences of a test engineering team, which had worked with a large software product development and support activity. This team has studied the existing software product, available test tools, test environment, with an objective of analyzing existing testing processes and methodologies for this large software product. The Paper discusses a number of initiatives and recommendations made by this test engineering group aimed at increasing the testing efficiency, optimizing the test suites, measuring and improving effectiveness of test cases and the quantifiable benefits and process improvements, that can derived from such initiatives. This activity was undertaken as part of a test engineering initiative to bring in place a set of innovative test engineering practices as potential business value drivers.

APA, Harvard, Vancouver, ISO, and other styles

27

Ramsin, R., and R. F. Paige. "Iterative criteria-based approach to engineering the requirements of software development methodologies." IET Software 4, no. 2 (2010): 91. http://dx.doi.org/10.1049/iet-sen.2009.0032.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Simperl, Elena, and Markus Luczak-Rösch. "Collaborative ontology engineering: a survey." Knowledge Engineering Review 29, no. 1 (2013): 101–31. http://dx.doi.org/10.1017/s0269888913000192.

Full text

Abstract:

AbstractBuilding ontologies in a collaborative and increasingly community-driven fashion has become a central paradigm of modern ontology engineering. This understanding of ontologies and ontology engineering processes is the result of intensive theoretical and empirical research within the Semantic Web community, supported by technology developments such as Web 2.0. Over 6 years after the publication of the first methodology for collaborative ontology engineering, it is generally acknowledged that, in order to be useful, but also economically feasible, ontologies should be developed and maintained in a community-driven manner, with the help of fully-fledged environments providing dedicated support for collaboration and user participation. Wikis, and similar communication and collaboration platforms enabling ontology stakeholders to exchange ideas and discuss modeling decisions are probably the most important technological components of such environments. In addition, process-driven methodologies assist the ontology engineering team throughout the ontology life cycle, and provide empirically grounded best practices and guidelines for optimizing ontology development results in real-world projects. The goal of this article is to analyze the state of the art in the field of collaborative ontology engineering. We will survey several of the most outstanding methodologies, methods and techniques that have emerged in the last years, and present the most popular development environments, which can be utilized to carry out, or facilitate specific activities within the methodologies. A discussion of the open issues identified concludes the survey and provides a roadmap for future research and development in this lively and promising field.

APA, Harvard, Vancouver, ISO, and other styles

29

Yanzer Cabral, Anderson R., Marcelo Blois Ribeiro, and Rodrigo Perozzo Noll. "Knowledge Management in Agile Software Projects: A Systematic Review." Journal of Information & Knowledge Management 13, no. 01 (2014): 1450010. http://dx.doi.org/10.1142/s0219649214500105.

Full text

Abstract:

Many methodologies, practices, techniques and tools have been suggested for process improvement, among them knowledge management and agile methodologies, which are the focus of this study. Systematic reviews published on knowledge management and agile methodologies have significantly contributed to detailed and deep discussions surrounding these issues. Nevertheless, we realised that there was a gap between these two areas that needed further clarification. Therefore, the objective of this study was to raise the main topics that emerge from knowledge management in agile methodologies. The research method used in this paper is based on a systematic review. We reviewed studies of knowledge management and agile methodologies, published in major software engineering journals and conference proceedings. The search strategy identified 2879 studies, of which 25 were selected as primary studies. The main topics were taken from these 25 works and, in order for them to be discussed; meta-analysis techniques were used to group these topics. The main discussion generated around these analyses was the preferential use of tacit knowledge, instead of explicit knowledge, and its influence on agile projects. This situation has implications for communication, human and social factors, software development cycle and artifacts, tools for knowledge management and knowledge representation forms.

APA, Harvard, Vancouver, ISO, and other styles

30

Faroom, Saeed. "A Review of Requirement Engineering Process Models, Tools & Methodologies." International Journal of Energetica 4, no. 1 (2019): 44. http://dx.doi.org/10.47238/ijeca.v4i1.86.

Full text

Abstract:

As we are living in the Era of Computer Science and almost all individuals and the organizations are completely relying on software systems. The requirement engineering is the most vital and important aspect in the success of any software engineering project. Requirement Engineering is a set of different process that works at different levels, which are incorporated at individual and organizational level Projects We need to consult different sources to find requirements. We need to involve personals from the different fields to find a set of quality requirements. The security issues undergoes as soon as early in the 1st phase of requirements. It is shown from the studies that if we consider Quality Process of Requirement Engineering at the phase it results in saving of million dollars. This paper contains the details study and comparison of different RE Process Models and Requirement Elicitation techniques. This paper elaborates the vital aspects of different Requirement Engineering Process models that help in the selection of appropriate model for the Requirement Engineers and practitioners working in the industry. This Paper also Focus on the giving a detailed view of Elicitation techniques and comparative study including the characteristics and their strengths and weakness. Some strengths and weakness found during detailed study are also structured and listed that is also the helpful for the Appropriate selection of RE Process model.

APA, Harvard, Vancouver, ISO, and other styles

31

Olson, Andrew M. "Transforming an HCI Model to a Software Design Model." International Journal of Software Engineering and Knowledge Engineering 07, no. 01 (1997): 145–67. http://dx.doi.org/10.1142/s0218194097000072.

Full text

Abstract:

The software engineering and human factors communities are seeking ways to integrate their methodologies. This paper outlines an amplified, software engineering methodology that extends beyond requirements gathering to encompass human factors analyses. The methodology employs an object model that is uniform throughout the software project. It involves a procedure that seamlessly transforms a task action grammar model, from HCI theory, directly into a specification model based on user/machine dialog and, thence, into a software design model. The model's object-oriented structure makes it feasible to trace the effects of the user's needs throughout the amplified project life cycle to the final code. A case study documents evidence concerning how effectively the procedure supports the software engineering process. An examination of the extent of metamorphosis the model undergoes in the case study indicates that the transition through the amplified life history is well controlled; in particular, the transition from the software specification to the design model is more controlled than that under traditional methodologies.

APA, Harvard, Vancouver, ISO, and other styles

32

Mišovič, Milan, and Ivana Rábová. "Enterprise services and object-oriented methodologies." Acta Universitatis Agriculturae et Silviculturae Mendelianae Brunensis 60, no. 7 (2012): 179–88. http://dx.doi.org/10.11118/actaun201260070179.

Full text

Abstract:

In this paper we study the possibility of modifying the conventional, advanced object-oriented methodology for software development of enterprise information systems on an enterprise services platform. The presented solution is preceded with the draft of the formal description of the business process logic and its service solutions. In the design for the introduction of business services there is used the so-called native solution that is very close to the thinking of corporate management. Adjustment of the classic, advanced object-oriented methodology is oriented on its cardinal development phases INSEPTION and ELABORATION. In these two phases important descriptions of relevant information modeling results are formed for the following CONSTRUCTION phase and TRANSITION phase. Editing, however, is methodological, and meta-documented with an example of a transparent graphical description of business services and a logical architecture of the target software.In other words, it means that this contribution provides small software companies with valuable knowledge for the creation of their own development methodologies on a platform of enterprise services. The purpose of this paper is to contribute to the formation of implementing development methodologies, which absorb current knowledge disciplines of Software and Information Engineering.

APA, Harvard, Vancouver, ISO, and other styles

33

Belady, L. A. "The special section on the convergence of software and hardware engineering development methodologies." Proceedings of the IEEE 74, no. 6 (1986): 772. http://dx.doi.org/10.1109/proc.1986.13555.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Smith, C. U., and R. R. Gross. "Technology transfer between VLSI design and software engineering: CAD tools and design methodologies." Proceedings of the IEEE 74, no. 6 (1986): 875–85. http://dx.doi.org/10.1109/proc.1986.13560.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Germain, Éric, and Pierre N. Robillard. "Engineering-based processes and agile methodologies for software development: a comparative case study." Journal of Systems and Software 75, no. 1-2 (2005): 17–27. http://dx.doi.org/10.1016/j.jss.2004.02.022.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Kunwar, Sundar. "Scenario Based Requirement Engineering (SBRE) in eXtreme Programming (XP) through Agile Modelling (AM)." SCITECH Nepal 13, no. 1 (2018): 9–15. http://dx.doi.org/10.3126/scitech.v13i1.23496.

Full text

Abstract:

Software development methodologies have been enhancing significantly all the time and have drawn the attention of software professionals from past few years. The software development methodologies are expanding rigorously with wide range of diverse fields and have become more complex demanding the agility to rapidly changing needs of the customers. As a result, agile software development methodologies have evolved and gaining popularity day by day. Agile software development methodologies have come up with modifications demanded in traditional software development process to make them faster; more flexible, light weighted and productive. Extreme Programming (XP) is one of the well-known agile software development methodologies and is driven by a set of values including simplicity, communication, feedback and courage. Planning game, very short release stories and test first coding are some interesting extreme practices of XP; however, it is criticized for some deficiencies like light weight requirement, onsite customer, pair programming and so on. The study has only focused on only one of the most criticized extreme practice-lightweight requirement and has followed agile modelling approach to make improvement on requirement engineering process in XP. Requirements are the user stories that consist of a few sentences (1-3 sentences) written on an index card which describes the functionality given by single onsite customer in XP. There is lack of analysis of stakeholders and their roles in requirement process. Therefore, it is very difficult to know the specific requirements of the specific stakeholder in XP. This means that the requirement engineering process is incomplete in XP. This may result high chances of providing deficient requirements. Agile Modelling (AM) is the chaordic practice based methodology for effective modelling. The interesting part of AM is that it does not tell how to model, but tells about how to be effective as modellers. A Scenario Based Requirement Engineering (SERE) is proposed using AM as alternative to light weighted requirement which one of the most criticized extreme practice of XP. SERE is the implemented description of techniques that helps to understand the task related activities and also facilitates communication among stakeholders and experts. Stakeholders are analysed for understanding a system by identifying the stakeholders in the system and assessing their respective requirements and influence on the system. This will help to get better requirements for system development, but still needs to be validated.

APA, Harvard, Vancouver, ISO, and other styles

37

Chaar, Jarir K., Daniel Teichroew, and Richard A. Volz. "Real-time software methodologies: Are they suitable for developing Manufacturing control software?" International Journal of Flexible Manufacturing Systems 5, no. 2 (1993): 95–128. http://dx.doi.org/10.1007/bf01358949.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Zhu, Qing. "Data Mining Software Tools and Methodologies for VLSI Design." WSEAS TRANSACTIONS ON ELECTRONICS 13 (March 1, 2022): 1–10. http://dx.doi.org/10.37394/232017.2022.13.1.

Full text

Abstract:

Modern VLSI design process employs numerous EDA tools to produce large-size report files. It is time consuming as well as the possibility to miss some violations from EDA report files. We developed two data mining software tools targeting for the timing, noise and power grid analysis report files in one high-performance SOC design project. The software extracts, sorts and displays the key information from EDA report files into HTML forms, which can be viewed by designers using the web browser. Organization of EDA report files, configure files, program execution flows and output HTML forms are described for the developed data mining software tools.

APA, Harvard, Vancouver, ISO, and other styles

39

Falah, Bouchaib, Sara El Alaoui, and Hajar Abbadi. "Investigating the Effect of Software Complexity Metrics on Software Cost." Applied Mechanics and Materials 548-549 (April 2014): 1319–25. http://dx.doi.org/10.4028/www.scientific.net/amm.548-549.1319.

Full text

Abstract:

Nowadays, software is expected to have an extended lifespan, which makes the evaluation of its complexity at the early stages critical in upcoming maintenance. Indeed, complexity is proportional to the evolution of software. Software metrics were introduced as tools that allow us to obtain an objective measurement of the complexity of software. Hence, enabling software engineering to assess and manage software complexity. Reducing software costs is one of the major concerns of software engineering which creates an increasing need for new methodologies and techniques to control those costs. Software complexity metrics can help us to do so. In this paper, we would investigate how those metrics can be used to reduce software costs. We would first analyze the most popular complexity metrics and distinguish their properties. Then, we will show how each of those metrics fit within the software life cycle. Finally, we will provide a detailed approach to use the complexity metrics to reduce software costs.

APA, Harvard, Vancouver, ISO, and other styles

40

Cowling, James Austin, and Wendy K. Ivins. "Assessing the Potential Improvement an Open Systems Development Perspective Could Offer to the Software Evolution Paradigm." International Journal of Information Technologies and Systems Approach 9, no. 2 (2016): 68–87. http://dx.doi.org/10.4018/ijitsa.2016070105.

Full text

Abstract:

Emerging stakeholder needs and a changing environment drive increasing demands for the constant adaption of software through maintenance and new capability development. A more evolutionary software engineering approach is sought to improve engineering responsiveness; Open System Development appears to offer a partial contribution but presents many challenges. This exploratory research proposes a new definition of the evolution of complex engineered systems, building on the essential features of ‘openness' described by Cowling et al (2014) and Lehman's (1980) ideas of evolutionary software. Using Checkland's (1999) Soft System Methodology enabled a structured literature review and analysis of the relative contributions of three divergent methodologies to the success of systems outcomes. These methodologies are: Plan-Driven, Agile, and Open Source Software Development. The analysis reveals several opportunities and highlights the critical issue of determining return on investment which needs to be overcome if an open approach is to contribute to evolutionary software engineering.

APA, Harvard, Vancouver, ISO, and other styles

41

Bohan, Jennifer A., and Daniel F. Wallace. "Team Ergonomics and Human Engineering Methods for the Design of Collaborative Work Environments: A Case Study." Proceedings of the Human Factors and Ergonomics Society Annual Meeting 41, no. 2 (1997): 1066–70. http://dx.doi.org/10.1177/107118139704100275.

Full text

Abstract:

Everyday, in both the workplace and the home, we see evidence of how human engineering has advanced software technologies. The advances in computer software were enabled through the application of standardized methodologies grounded in sound systems engineering. It is increasingly apparent that these methodologies have applications to domains other than Human Computer Interface (HCl) development. Specifically, the design of collaborative work environments benefits greatly from the application of human engineering processes. The Tactical Information GUI Engineering & Requirements Specification (TIGERS) methodology was developed to define, articulate, and integrate user requirements into tactical computer interface design (Wallace, Dawson, & Blaylock, 1995). This proven human engineering methodology has been applied to the redesign of the Naval Space Operations Center (NAVSPOC) at the Naval Space Command, in Dahlgren, Virginia (Wallace, Bohan, & White, 1996). This paper discusses the successful application of this human engineering method to the operations center domain.

APA, Harvard, Vancouver, ISO, and other styles

42

Garcia-Holgado, Alicia, Andrea Vazquez-Ingelmo, Francisco J. Garcia-Penalvo, and MaJose Rodriguez Conde. "Improvement of Learning Outcomes in Software Engineering: Active Methodologies Supported Through the Virtual Campus." IEEE Revista Iberoamericana de Tecnologias del Aprendizaje 16, no. 2 (2021): 143–53. http://dx.doi.org/10.1109/rita.2021.3089926.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Fulbright, Ron. "Incorporating Innovation into Iterative Software Development Using the Inventive Problem Solving Methodology." International Journal of Innovation Science 5, no. 4 (2013): 203–12. http://dx.doi.org/10.1260/1757-2223.5.4.203.

Full text

Abstract:

Iterative software methodologies allow development teams to be agile in their response to changing requirements. However, the software development team is usually at the mercy of requirements changes, rather than being part of the project engineering staff defining the changes to the solution architecture. Therefore, projects tend to implement inferior solutions. Integrating a project-level innovation technique called Inventive Problem Solving into agile software development methodologies such as the spiral model, the Rational Unified Process, and Scrum, allows the development team to affect the overall solution architecture utilizing their expertise in information technology to the maximum benefit. As a result, more creative, innovative, and efficient solutions to the problem are conceived and implemented.

APA, Harvard, Vancouver, ISO, and other styles

44

FERNÁNDEZ-LÓPEZ, MARIANO, and ASUNCIÓN GÓMEZ-PÉREZ. "Overview and analysis of methodologies for building ontologies." Knowledge Engineering Review 17, no. 2 (2002): 129–56. http://dx.doi.org/10.1017/s0269888902000462.

Full text

Abstract:

The use of methodologies in software and knowledge engineering is very extensive due to their important advantages. In the case of the development of ontologies, until now, several methodological proposals have been presented for building ontologies. Some of these methodologies are designed for building ontologies from scratch or reusing other ontologies without modifying them, concretely, the following cases can be mentioned: the Cyc methodology, the approach proposed by Uschold and King, Grüninger and Fox's methodology, the KACTUS methodology, METHONTOLOGY and the SENSUS methodology. There is even a proposal for re-engineering ontologies, and several proposals for collaborative construction of ontologies.In this article, we describe the methodologies and check their degree of maturity, contrasting them with respect to the IEEE standard for software development. Before this, we justify to what extent this standard can be used. A conclusion to this study is that there is no completely mature methodological proposal for building ontologies, since there are some important activities and techniques that are missing in all these methodologies. However, all the methodologies do not have the same degree of maturity. In fact, METHONTOLOGY is a very mature methodology. The other conclusion of this article is that, although work to unify proposals can be interesting, maybe several approaches should coexist.

APA, Harvard, Vancouver, ISO, and other styles

45

Wyatt, T. "Methodologies for manufacturing systems." Integrated Manufacturing Systems 1, no. 1 (1990): 25–27. http://dx.doi.org/10.1108/eum0000000002043.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Croock, Muayad Sadik, Zahraa Abbas Hassan, and Saja Dhyaa Khudhur. "Adaptive key generation algorithm based on software engineering methodology." International Journal of Electrical and Computer Engineering (IJECE) 11, no. 1 (2021): 589. http://dx.doi.org/10.11591/ijece.v11i1.pp589-595.

Full text

Abstract:

Recently, the generation of security keys has been considered for guaranteeing the strongest of them in terms of randomness. In addition, the software engineering methodologies are adopted to ensure the mentioned goal is reached. In this paper, an adaptive key generation algorithm is proposed based on software engineering techniques. The adopted software engineering technique is self-checking process, used for detecting the fault in the underlying systems. This technique checks the generated security keys in terms of validity based on randomness factors. These factors include the results of National Institute of standard Test (NIST) tests. In case the randomness factors are less than the accepted values, the key is regenerated until obtaining the valid one. It is important to note that the security keys are generated using shift register and SIGABA technique. The proposed algorithm is tested over different case studies and the results show the effective performance of it to produce well random generated keys.

APA, Harvard, Vancouver, ISO, and other styles

47

Khan, Rashid Ali, Muhammad Faisal Abrar, Samad Baseer, et al. "Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective." Electronics 10, no. 19 (2021): 2341. http://dx.doi.org/10.3390/electronics10192341.

Full text

Abstract:

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.

APA, Harvard, Vancouver, ISO, and other styles

48

Sharma, Poorti. "Impact of Agile Methodologies in Project Success." International Journal for Research in Applied Science and Engineering Technology 10, no. 5 (2022): 3728–30. http://dx.doi.org/10.22214/ijraset.2022.43204.

Full text

Abstract:

Abstract: The Agile Manisfesto of software development put forth a groundbreaking mindset on delivering value and collaborating with customers when it was created in 2001. Agile methodology that utilizes iterative development and prototyping are vitally used in variety of industry projects as a light weight development method which can satisfy to changes of requirements. Traditional waterfall approach is not much efficient to manage the rapid change in requirements. The purpose of this study is to present the impacts of agile methodology in project success. Most studies have reported that when comparing structured methodologies with agile methodologies, agile does improve software quality, other studies have contradicted and questioned the claimed benefits , while others argued that there is not enough empirical evidence. This study aims at investigating the impact that agile method on project success in an organization. The selected studies were published between 2018 to 2022. Index Terms: Agile methodology, agile practices, impact of agile, project success

APA, Harvard, Vancouver, ISO, and other styles

49

De Almeida, Jonathas Arestides, Helder Jerônimo Leite Rangel, Matheus Augusto Coutinho Costa, Maurício Barbosa De Lira Filho, Francisco Petrônio Alencar De Medeiros, and Heremita Brasileiro Lira. "Guia interativo de boas práticas em Engenharia de Software." Revista Principia - Divulgação Científica e Tecnológica do IFPB 1, no. 44 (2019): 23. http://dx.doi.org/10.18265/1517-03062015v1n44p23-30.

Full text

Abstract:

Analyzing the diversity of best practices in Software Engineering present in industry, the Software Engineering Research Group of the Federal Institute of Paraíba realized the need to organize them together in a web repository so that the access, identification and proper application in various software project scenarios is easier. The objective of work is to present the first functional version of this web environment, in order to enable the best practices in Software Engineering as researched by the group. This project has been developed using agile methodologies and is the result of a trio of complementary and collaborative projects from the research group: Repository of Practices in Management of Software Project, Repository of Practices in the Software Development Process, together with the project Reconfigurable Best Practices Environment in Software Engineering.

APA, Harvard, Vancouver, ISO, and other styles

50

Linkens, D. A. "AI in control Systems engineering." Knowledge Engineering Review 5, no. 3 (1990): 181–214. http://dx.doi.org/10.1017/s0269888900005403.

Full text

Abstract:

AbstractDecision-making is an integral part of any consideration of the discipline of control Systems. This implies feedback of knowledge in some format, whether it is mediated via human or machineoriented methods. The application of AI methodologies to control Systems engineering is described in this review under two broad categories of design and implementation. The design of control strategies is itself divided into phases of modelling and simulation, identification, and algorithm selection and tuning. The aspects of implementation which are covered include real-time considerations such as knowledge-based control and fuzzy logic, multi-sensor data fusion, fault detection and Human–Computer Interaction (HCI).

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Software methodologies and engineering'

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