Log in

Relevant bibliographies by topics / Software development methodology / Journal articles

To see the other types of publications on this topic, follow the link: Software development methodology.

Journal articles on the topic 'Software development methodology'

Author: Grafiati

Published: 4 June 2021

Last updated: 25 January 2023

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

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Software development methodology.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Gidroets, M. O., and L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY." System analysis and logistics 4, no. 26 (December 17, 2020): 45–53. http://dx.doi.org/10.31799/2007-5687-2020-4-45-53.

Full text

Abstract:

This article discusses the main methodologies for developing software products. The most common cascading and flexible methodologies are characterized. Considered the pros and cons of each methodology. The situations of expedient application of cascade and flexible approaches to software product development are determined. Key words: development methodologies, waterfall model, agile model, project management, planning, software product development.

APA, Harvard, Vancouver, ISO, and other styles

2

DESPA, Mihai Liviu. "Formalizing the ISDF Software Development Methodology." Informatica Economica 20, no. 2/2015 (June 30, 2015): 66–80. http://dx.doi.org/10.12948/issn14531305/19.2.2015.07.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Cort, G., J. A. Goldstone, R. O. Nelson, R. V. Poore, L. Miller, and D. M. Barrus. "A Development Methodology for Scientific Software." IEEE Transactions on Nuclear Science 32, no. 4 (1985): 1439–43. http://dx.doi.org/10.1109/tns.1985.4333629.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

HUHNS, MICHAEL N. "INTERACTION-ORIENTED SOFTWARE DEVELOPMENT." International Journal of Software Engineering and Knowledge Engineering 11, no. 03 (June 2001): 259–79. http://dx.doi.org/10.1142/s0218194001000530.

Full text

Abstract:

This paper describes a new approach to the production of robust software. We first motivate the approach by explaining why the two major goals of software engineering — correct software and reusable software — are not being addressed by the current state of software practice. We then describe a methodology based on active, cooperative, and persistent software components, i.e., agents, and show how the methodology produces robust and reusable software. We derive requirements for the structure and behavior of the agents, and report on preliminary experiments on applications based on the methodology. We conclude with a roadmap for development of the methodology and ruminations about uses for the new computational paradigm.

APA, Harvard, Vancouver, ISO, and other styles

5

Xu, Peng, and Yurong Yao. "Methodology Fit in Offshoring Software Development Projects." Information Resources Management Journal 27, no. 4 (October 2014): 66–81. http://dx.doi.org/10.4018/irmj.2014100104.

Full text

Abstract:

Offshoring has become a viable alternative for companies to lower software development costs and leverage labor resources worldwide. To achieve success in offshoring software development projects, a vendor must choose appropriate development methodologies. This study aims to examine how methodology fit affects offshoring project performance. It proposes that methodology fit affects project performance through interfirm knowledge sharing between vendors and clients. In addition, the impact of methodology fit on knowledge sharing is dependent on relational capital between vendors and clients. A survey was conducted among software companies in China that provide offshoring services. 108 completed questionnaires were collected. The results confirm this article's hypotheses.

APA, Harvard, Vancouver, ISO, and other styles

6

Xu, Peng, and Yurong Yao. "Methodology Fit in Offshoring Software Development Projects." Information Resources Management Journal 28, no. 3 (July 2015): 42–58. http://dx.doi.org/10.4018/irmj.2015070104.

Full text

Abstract:

Offshoring has become a viable alternative for companies to lower software development costs and leverage labor resources worldwide. To achieve success in offshoring software development projects, a vendor must choose appropriate development methodologies. This study aims to examine how methodology fit affects offshoring project performance. The authors propose that methodology fit affects project performance through interfirm knowledge sharing between vendors and clients. In addition, the impact of methodology fit on knowledge sharing is dependent on relational capital between vendors and clients. A survey was conducted among software companies in China that provide offshoring services. 108 completed questionnaires were collected. The results confirm the authors' hypotheses.

APA, Harvard, Vancouver, ISO, and other styles

7

Hwang, Mansoo, Kwanwoo Lee, and Seonghye Yoon. "Software Development Methodology for SaaS Cloud Service." Journal of the Institute of Webcasting, Internet and Telecommunication 14, no. 1 (February 28, 2014): 61–67. http://dx.doi.org/10.7236/jiibc.2014.14.1.61.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Kim, tai-dal. "Software development project management using Agile methodology." Journal of the Institute of Internet Broadcasting and Communication 16, no. 1 (February 29, 2016): 155–62. http://dx.doi.org/10.7236/jiibc.2016.16.1.155.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Koizumi, Hisao, Akira Sugimoto, and Tetsyuki Tobiyama. "III. Software Development Methodology and New Technologies." IEEJ Transactions on Electronics, Information and Systems 114, no. 6 (1994): 627–35. http://dx.doi.org/10.1541/ieejeiss1987.114.6_627.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Roberts, Keith A. "Generic methodology for open source software development." ACM SIGSOFT Software Engineering Notes 30, no. 2 (March 2005): 1–5. http://dx.doi.org/10.1145/1050849.1050863.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Bresciani, Paolo, Anna Perini, Paolo Giorgini, Fausto Giunchiglia, and John Mylopoulos. "Tropos: An Agent-Oriented Software Development Methodology." Autonomous Agents and Multi-Agent Systems 8, no. 3 (May 2004): 203–36. http://dx.doi.org/10.1023/b:agnt.0000018806.20944.ef.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Pullan, Wayne. "A pragmatic Ada software design/development methodology." ACM SIGAda Ada Letters XV, no. 2 (March 1995): 31–39. http://dx.doi.org/10.1145/224126.224128.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Mathur, R. N. "Methodology for Business System Development." IEEE Transactions on Software Engineering SE-13, no. 5 (May 1987): 593–601. http://dx.doi.org/10.1109/tse.1987.233464.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

al-Tarawneh, Mejhem Yousef, Mohd Syazwan Abdullah, and Abdul Bashah Mat Ali. "A proposed methodology for establishing software process development improvement for small software development firms." Procedia Computer Science 3 (2011): 893–97. http://dx.doi.org/10.1016/j.procs.2010.12.146.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Sherry, Marion M. "Methodology for Software Documentation Reuse." Proceedings of the Human Factors Society Annual Meeting 36, no. 3 (October 1992): 198–201. http://dx.doi.org/10.1518/107118192786751772.

Full text

Abstract:

This paper describes a documentation writing methodology developed and used by the author to address some of the issues of consistency in documentation and product function, redundancy of research and solution, and product usability (including timeliness of delivery and quality of support) for a software product engineered, developed and deployed in a multi-organizational or corporate environment. The methodology is compatible with technical systems engineering, development and testing documentation requirements, and is applicable to software products for which there are existing or anticipated “user guides”. The method used to accomplish these goals is the incorporation of existing user guide formats, wherever possible, in the documentation of technical specifications for detailed engineering, development and testing requirements. This paper describes the “cycle of documentation” methodology employed, identifies opportunities to use this methodology, and describes some of the benefits derived from using the methodology (both initially intended and later discovered).

APA, Harvard, Vancouver, ISO, and other styles

16

Hapon, Andrii Oleksandrovich, Volodymyr Mykolayovych Fedorchenko, Andrii Oleksandrovich Polyakov, Valeriy Yuriyovich Volovshchykov, and Viktor Alexeevich Guzhva. "ANALYSIS OF DEVSECOPS METHODOLOGY IN SOFTWARE DEVELOPMENT PROCESSES." Bulletin of National Technical University "KhPI". Series: System Analysis, Control and Information Technologies, no. 1 (3) (July 9, 2020): 68–73. http://dx.doi.org/10.20998/2079-0023.2020.01.12.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Kharade, Jyoti, Sneha Prajapati, Dakshata Narkar, and Dhanaji S. Kharade. "Role of agile methodology for software product development." International Journal of Computer Sciences and Engineering 6, no. 5 (May 31, 2018): 424–27. http://dx.doi.org/10.26438/ijcse/v6i5.424427.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Lee, Junho, Jungwoong Woo, Cheongan Lee, and Kyungsoo Joo. "A Software Development Methodology for Secure Web Application." International Journal on Advanced Science, Engineering and Information Technology 9, no. 1 (February 28, 2019): 336. http://dx.doi.org/10.18517/ijaseit.9.1.5987.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Seidewitz, Ed, and Mike Stark. "Toward a general object-oriented software development methodology." ACM SIGAda Ada Letters VII, no. 4 (July 1987): 54–67. http://dx.doi.org/10.1145/25314.25315.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Araújo, Ricardo de A., Sergio Soares, and Adriano L. I. Oliveira. "Hybrid morphological methodology for software development cost estimation." Expert Systems with Applications 39, no. 6 (May 2012): 6129–39. http://dx.doi.org/10.1016/j.eswa.2011.11.077.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Eberlein, Armin, and Li Jiang. "Description of a process development methodology." Software Process: Improvement and Practice 12, no. 1 (January 2007): 101–18. http://dx.doi.org/10.1002/spip.303.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Dudhat, Amitkumar, and Muhammad Ali Abbasi. "Discussion of Agile Software Development Methodology and its Relevance to Software Engineering." ADI Journal on Recent Innovation (AJRI) 3, no. 1 (September 30, 2021): 105–14. http://dx.doi.org/10.34306/ajri.v3i1.536.

Full text

Abstract:

Agile Software Development Methodology is a lesser-known and infrequently utilized methodology in academia. In reality, though, content developer software practitioners frequently employ this technique. This journal was created to give readers an overview of agile techniques and their use at various stages of software development in general.

APA, Harvard, Vancouver, ISO, and other styles

23

Nicolaysen, Torstein, Richard Sassoon, Maria B. Line, and Martin Gilje Jaatun. "Agile Software Development." International Journal of Secure Software Engineering 1, no. 3 (July 2010): 71–85. http://dx.doi.org/10.4018/jsse.2010070105.

Full text

Abstract:

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

APA, Harvard, Vancouver, ISO, and other styles

24

Bastani, F. B. "Experiences with a Feedback Version Development Methodology." IEEE Transactions on Software Engineering SE-11, no. 8 (August 1985): 718–23. http://dx.doi.org/10.1109/tse.1985.232521.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Et.al, Rosnani Shuib. "Towards Adopting Software Quality Assurance in Agile Development Methodology." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 10, 2021): 2152–57. http://dx.doi.org/10.17762/turcomat.v12i3.1158.

Full text

Abstract:

In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product. However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology. Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.

APA, Harvard, Vancouver, ISO, and other styles

26

Sivakumar, P., B. Vinod, R. S. Sandhya Devi, and R. Divya. "Deployment of Effective Testing Methodology in Automotive Software Development." Circuits and Systems 07, no. 09 (2016): 2568–77. http://dx.doi.org/10.4236/cs.2016.79222.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Iglesias, Adriana, Augusto De Arco Chiquillo, and Paul Sanmartin Mendoza. "SCOWP: agile methodology for secure web-based software development." International Journal of Agile Systems and Management 15, no. 1 (2022): 1. http://dx.doi.org/10.1504/ijasm.2022.10048980.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Chiquillo, Augusto De Arco, Paul Sanmartin Mendoza, and Adriana Iglesias. "SCOWP: agile methodology for secure web-based software development." International Journal of Agile Systems and Management 15, no. 1 (2022): 1. http://dx.doi.org/10.1504/ijasm.2022.124161.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Mohd Zin, Abdullah, Mustafa Almatary, Marini Abu Bakar, Rodziah Latih, and Norleyza Jailani. "Blocks Correctness Evaluation Methodology for Block-Based Software Development." International Journal on Advanced Science, Engineering and Information Technology 8, no. 6 (December 30, 2018): 2663. http://dx.doi.org/10.18517/ijaseit.8.6.6664.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Hayashi, Akira, Momoko Ichinokawa, Junji Kinoshita, and Akihiro Manabe. "Optimizing stock assessment workflows by applying software development methodology." Fisheries Research 244 (December 2021): 106108. http://dx.doi.org/10.1016/j.fishres.2021.106108.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Golinko, Ihor, and Pavlo Gikalo. "Methodology of software development for artificial microclimate control systems." MECHANICS OF GYROSCOPIC SYSTEMS, no. 40 (December 10, 2020): 21–31. http://dx.doi.org/10.20535/0203-3771402020248748.

Full text

Abstract:

The specificity of accelerated software development for microcontrollers is considered. The software development technique for a program-logic controller is presented on the example of an algorithm for controlling the industrial premises microclimate. The method of “dew point” for the control system of industrial air conditioning. The analysis of the functioning of the control system of industrial air conditioning according to the “dew point” method has been carried out and a block diagram of the control system of an artificial microclimate has been proposed. Structurally, the mathematical description of an artificial microclimate system is presented, which takes into account the nonlinearity of mass-exchange processes of air preparation. It can be used by specialists to implement computer-integrated technologies and to analyze and adjust the parameters of the control system of industrial air conditioners.

APA, Harvard, Vancouver, ISO, and other styles

32

Sohail, Fizzah, Syed Saood Zia, Rehan Qureshi, Muhammad Naseem, and Hira Haider. "Impact of Agile Methodology on Software Development Life Cycle." Pakistan Journal of Engineering and Technology 4, no. 2 (June 30, 2021): 153–58. http://dx.doi.org/10.51846/vol4iss2pp153-158.

Full text

Abstract:

Software engineering strategies had been hired for decades to create software products. The most challenging task for the development of software is to select appropriate software development methodologies. Software developers use agile techniques to reduce the problems faced by the traditional waterfall process. These days, the motivation behind most programming associations is to give programming in a fast time, inside financial plan and changing situations that propelled the conveyance of Agile. The strategy that utilizes iterative expansion and prototyping is generally utilized in an assortment of industry ventures as a lightweight advancement method that could fulfil the alterations of necessities. Short cycles are utilized which can be required for proficient item delivery. In the paper, we become mindful of the impacts that the coordinated strategy has programming improvement strategies with prominence to decent inside the authoritative, efficient, and social system. Coordinated methods are not in every case great, they have a few restrictions too. In this paper, we likewise clarify the estimations of Agile, its points of interest, and its weaknesses.

APA, Harvard, Vancouver, ISO, and other styles

33

Olagunju, Amos, and Bassey Akpan. "The Benefits of Object-oriented Methodology for Software Development." International Journal of Information and Computer Science 4 (2015): 39. http://dx.doi.org/10.14355/ijics.2015.04.007.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Ceja, Jesús Manuel Olivares, and Emilio Buendía Cervantes. "Software Development Integrating Methodology with Epistemology Promoting Knowledge Production." International Journal of Technology and Educational Marketing 4, no. 1 (January 2014): 106–15. http://dx.doi.org/10.4018/ijtem.2014010109.

Full text

Abstract:

Currently, many specialties should be mastered to produce software, consequently they fall in different levels of knowledge: project, system, program, or routine. This consideration was obtained through an epistemological approach in software development. Therefore, this article develops this consideration for students learning software production. The epistemological approach compliments the methodologies used during software generation. The main focus in this proposal is on applying learning principles, combining both the epistemological approach and methodologies to promote student knowledge production for software development. The implementation of the proposal provides students with a framework that prepares them to face software development problems with different levels of complexity. Evaluation is based on verifying which of the different epistemological categories the student masters.

APA, Harvard, Vancouver, ISO, and other styles

35

Tsubaki, Masaaki. "VII. Data Driven Software Development Methodology of PLAN-DB." IEEJ Transactions on Electronics, Information and Systems 114, no. 6 (1994): 663–71. http://dx.doi.org/10.1541/ieejeiss1987.114.6_663.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Liu, Li-Min. "A New Software Development Methodology for Clinical Trial Systems." Advances in Software Engineering 2013 (March 21, 2013): 1–13. http://dx.doi.org/10.1155/2013/796505.

Full text

Abstract:

Clinical trials are crucial to modern healthcare industries, and information technologies have been employed to improve the quality of data collected in trials and reduce the overall cost of data processing. While developing software for clinical trials, one needs to take into account the similar patterns shared by all clinical trial software. Such patterns exist because of the unique properties of clinical trials and the rigorous regulations imposed by the government for the reasons of subject safety. Among the existing software development methodologies, none, unfortunately, was built specifically upon these properties and patterns and therefore works sufficiently well. In this paper, the process of clinical trials is reviewed, and the unique properties of clinical trial system development are explained thoroughly. Based on the properties, a new software development methodology is then proposed specifically for developing electronic clinical trial systems. A case study shows that, by adopting the proposed methodology, high-quality software products can be delivered on schedule within budget. With such high-quality software, data collection, management, and analysis can be more efficient, accurate, and inexpensive, which in turn will improve the overall quality of clinical trials.

APA, Harvard, Vancouver, ISO, and other styles

37

Qureshi, M. Rizwan Jameel. "Agile software development methodology for medium and large projects." IET Software 6, no. 4 (2012): 358. http://dx.doi.org/10.1049/iet-sen.2011.0110.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Wongthongtham, P., E. Chang, T. S. Dillon, and I. Sommerville. "Ontology-based multi-site software development methodology and tools." Journal of Systems Architecture 52, no. 11 (November 2006): 640–53. http://dx.doi.org/10.1016/j.sysarc.2006.06.008.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Gray, J. P. "CASE tool construction for a parallel software development methodology." Information and Software Technology 39, no. 4 (April 1997): 235–52. http://dx.doi.org/10.1016/s0950-5849(96)01145-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Son, Kyung A., and Young-Sun Yun. "Introduction and Analysis of Open Source Software Development Methodology." Journal of Software Assessment and Valuation 16, no. 2 (December 31, 2020): 163–72. http://dx.doi.org/10.29056/jsav.2020.12.18.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Elderkin, David. "Choosing a Software Development Methodology for Document Management Systems." Drug Information Journal 29, no. 2 (April 1995): 687–94. http://dx.doi.org/10.1177/009286159502900248.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

BLOESCH, A., E. KAZMIERCZAK, P. KEARNEY, and OWEN TRAYNOR. "COGITO: A METHODOLOGY AND SYSTEM FOR FORMAL SOFTWARE DEVELOPMENT." International Journal of Software Engineering and Knowledge Engineering 05, no. 04 (December 1995): 599–617. http://dx.doi.org/10.1142/s0218194095000290.

Full text

Abstract:

Cogito 1 is the first iteration of a Z-based integrated methodology and support system for formal software development. This paper gives an overview of the Cogito methodology and associated tools. Particular emphasis is placed on the way in which Cogito integrates the various phases of the formal development process and provides comprehensive tools support for all phases of development addressed by the methodology.

APA, Harvard, Vancouver, ISO, and other styles

43

Rodríguez-Hernández, V., M. C. Espino-Gudiño, J. L. González-Pérez, J. Gudiño-Bazaldúa, and Victor Castano. "Assessing quality in software development: An agile methodology approach." Journal of Advanced Computer Science & Technology 4, no. 2 (June 9, 2015): 225. http://dx.doi.org/10.14419/jacst.v4i2.4173.

Full text

Abstract:

<p>A novel methodology, result of 10 years of in-field testing, which makes possible the convergence of different types of models and quality standards for Engineering and Computer Science Faculties, is presented. Since most software-developing companies are small and medium sized, the projects developed must focuson SCRUM and Extreme Programming (XP), opposed to a RUP, which is quite heavy, as well as on Personal Software Process (PSP) and Team Software Process (TSP), which provide students with competences and a structured framework. ISO 90003:2004 norm is employed to define the processes by means of a quality system without new requirements or changing the existing ones. Also, the model is based on ISO/IEC 25000 (ISO (IEC 9126 – ISO/IEC 14598)) to allow comparing software built by different metrics.</p>

APA, Harvard, Vancouver, ISO, and other styles

44

Leitner, A., R. Mader, Ch Kreiner, Ch Steger, and R. Weiß. "A development methodology for variant-rich automotive software architectures." e & i Elektrotechnik und Informationstechnik 128, no. 6 (June 2011): 222–27. http://dx.doi.org/10.1007/s00502-011-0001-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Matsumoto, Shunji. "ES/SDEM Software development engineering methodology for expert systems." Future Generation Computer Systems 5, no. 1 (August 1989): 33–39. http://dx.doi.org/10.1016/0167-739x(89)90018-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Rathore, Manvender, and Deepa Jose. "Software Upgradation Model Based on Agile Methodology." Oriental journal of computer science and technology 10, no. 2 (April 6, 2017): 352–58. http://dx.doi.org/10.13005/ojcst/10.02.14.

Full text

Abstract:

Agile software development work on twelve principle for software development which implies requirements and solutions evolved through the combined teamwork of disciplined and interdisciplinary teams. The objective of this paper is to connect agile methodology with Version Control System for more efficient and effective utilization of resources. In this proposed model based on agile methodology, the Version Control System plays a vital role to make work done faster as compared to SCRUM. This paper compares various existing agile methodologies. The efficiency of the proposed model is proved through comparative analysis with existing agile methods and using ANOVA mathematical model. Bitbucket as Version Control System is used as web based hosting service and the proposed model is compared by maintaining similar sprints in SCRUM and VSprint model. VCS and previous SRS documents are the important components of this proposed model which helps in increasing the work speed at different phases of software development which the existing models does not consider.

APA, Harvard, Vancouver, ISO, and other styles

47

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.

Full text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

48

McLeod, Laurie, Stephen G. MacDonell, and Bill Doolin. "Qualitative research on software development: a longitudinal case study methodology." Empirical Software Engineering 16, no. 4 (January 5, 2011): 430–59. http://dx.doi.org/10.1007/s10664-010-9153-5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Ošlejšek, Radek, and Tomáš Pitner. "Optimization of Cyber Defense Exercises Using Balanced Software Development Methodology." International Journal of Information Technologies and Systems Approach 14, no. 1 (January 2021): 136–55. http://dx.doi.org/10.4018/ijitsa.2021010108.

Full text

Abstract:

Cyber defense exercises (CDXs) represent an effective way to train cybersecurity experts. However, their development is lengthy and expensive. The reason lies in current practice where the CDX life cycle is not sufficiently mapped and formalized, and then exercises are developed ad-hoc. However, the CDX development shares many aspects with software development, especially with ERP systems. This paper presents a generic CDX development method that has been derived from existing CDX life cycles using the SPEM standard meta-model. The analysis of the method revealed bottlenecks in the CDX development process. Observations made from the analysis and discussed in the paper indicate that the organization of CDXs can be significantly optimized by applying a balanced mixed approach with agile preparation and plan-driven disciplined evaluation.

APA, Harvard, Vancouver, ISO, and other styles

50

Núñez-Sánchez, Yeison, and Antonio González-Torres. "Third-party management in software development: proposal of a methodology." Enfoque UTE 11, no. 2 (April 1, 2020): 71–84. http://dx.doi.org/10.29019/enfoque.v11n2.621.

Full text

Abstract:

Outsourcing allows organizations to reduce costs, optimize the use of resources, provide added value in services and goods, and concentrate on achieving the strategic objectives of the business. However, many software projects have failed due to the lack of knowledge of the factors involved in its planning. Some of these elements are poor communication with the supplier, weak monitoring of the status of tasks, lack of active participation of users and stakeholders at all stages of the process, and software quality assurance. Consequently, this research aims to aid the management of the outsourcing process and proposes a methodology for its management during system development. The methodology comprises 7 phases, each one with its inputs, tasks, and outputs, which are used by the following stages. In summary, it synthesizes the best practices for the management of third parties.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!