Traditional Development Methodologies Research Articles

Performance Assessment of Traditional Software Development Methodologies and DevOps Automation Culture

Successful implementations of Software Development Methodologies significantly improve software efficiency, collaboration and security. Most companies are moving away from traditional development methodologies towards DevOps for faster and better software delivery. DevOps, which is a primary need of the IT industry, brings development and operation teams together to overcome communication gaps responsible for software failures. It relies on different sets of automation tools to robotize the tasks of software development from continuous integration, to testing, delivery, and deployment. The existence of several automation tools in each development phase raises the need for an integrated set of tools to reduce development time. For this purpose, we used the DevOps-based hybrid model Integrated Tool Chain (ITC), along with three sample java-based projects or code repositories to quantify the results. This paper evaluates and compares measurement metrics of java projects using traditional development methodologies and DevOps, and the results are shown in tabular and graphical format. The latest Google and Stack Overflow Trends have also been included to retrieve the best performer development methodology. This comparative and evaluative performance analysis will be beneficial to young researchers that study the metrics of software development, while also they will be introduced to the automotive environment of DevOps, the latest emerging buzzword in software development.

Analysis of Low Code-No Code Development Platforms in comparison with Traditional Development Methodologies

Abstract: This paper examines the overview of low-code/no-code development platforms in comparison with traditional development methodologies and examines the benefits and limitations of the same. For several decades, businesses have had multiple options when they demanded new information systems. They could develop a new system using in-house developers, or they could order a system from an external merchant. This offers a close fit to business obligations. However, nowadays, there is a new alternative that is becoming increasingly prevalent. Low code/no code (LC/NC) applications can cater to business requirements efficiently, can be implemented instantly, and the cost is much less than systems developed in-house. Few, if any, programming skills are required. Keywords: Traditional development, No code development, low code development, Low code No code development, Software development life cycle (SDLC)

Una revisión comparativa de la literatura acerca de metodologías tradicionales y modernas de desarrollo de software

Existen una gran variedad de metodologías de desarrollo de software, con diferencias significativas en cuanto al tipo de proceso empleado y productos obtenidos, cantidad de recursos involucrados, tiempos de desarrollo y estructura organizacional requerida. Considerando la diversidad de información disponible, este trabajo presenta una revisión enfocada a identificar las tendencias reportadas en la literatura sobre metodologías de desarrollo de software, incluyendo tanto las modernas como las tradicionales. Se aplicaron filtros de búsqueda para seleccionar estudios primarios y secundarios, encontrando que las metodologías de desarrollo tradicionales más reportadas son los de tipo cascada y modelos en espiral, mientras que entre las metodologías modernas las ágiles son las más reportadas, incluyendo programación extrema, scrum, desarrollo orientado a funcionalidades y las basadas en componentes. Se identificaron y compararon las principales ventajas y desventajas de las metodologías, buscando que este trabajo sirva como un punto de partida para los desarrolladores de software a nivel empresarial, educativo e investigativo.

Distributed, Connected Everything: It’s Already Happening

Abstract The Materials Genome Initiative aims to enable discovery, manufacture, and deployment of advanced materials twice as fast as using traditional development methodologies, at a fraction of the cost. This article explores how semantic technologies address three of the key challenges outlined in the MGI Strategic Plan.

Agile Practices: The Impact on Trust in Software Project Teams

Agile software development involves self-managing teams that are empowered and responsible for meeting project goals in whatever way they deem suitable. Managers must place more trust in such teams than they do in teams following more traditional development methodologies. The authors highlight how the use of agile practices can enhance trust amongst agile team members. They also present challenges that agile teams can face as a result of using agile practices. Their results are based on the findings from three case studies of agile software development teams.

Transition from Classic/Traditional to Agile: Critical Steps for Smooth Transition

The Internet economy has altered the rules of software engineering. Traditional development methodologies are too cumbersome to meet the rapidly changing requirements and short product cycles demanded by business. This paper introduces critical steps required for smooth transition from classic software development model to agile methodology as per my experience in service organization such as HCL Technologies that needed to learn agile methodology to support the transition. It also lists the popular methodologies, metrics that matter and agile estimation and planning techniques. Finally, it summarizes the whole paper. KEYWORDS: Classical Model, Agile Model, Transformation, Agile Methodologies, Metrics, Estimation And Planning.

Crafting a software engineering capston project course

When properly constructed, a project-based capstone software engineering course can provide the challenging, but essential bridge from academic computing to the world of professional software development while fostering critical teamwork, leadership, and communications skills. In this work, we discuss experiences with five distinct student projects that involved heterogeneous teams, both systems and software engineering disciplines, industrial partnerships, component-based in addition to traditional development methodologies, and interactions with real customers. The heterogeneous teams included computer science, systems engineering, and systems engineering management majors and ranged in size from five to nine students. The projects included a protocol for file transfers between ground stations and on-orbit satellites, a satellite telemetry archiving and visualization tool, porting and extending an evolutionary algorithm for runway damage optimization, an unmanned aerial vehicle situational awareness capability, and a pedagogical interactive game for learning the concepts and applications of public key infrastructures. Partnership with an aerospace industry corporation exposed our students to Capability Maturity Model (CMM) Level 3 processes and facilitated enriching professional mentorships while stimulating student motivation and ownership of their efforts. The structure of the course afforded students significant autonomy to develop and explore both their interpersonal communication skills as well as the tenets of effective project management including scheduling, project tracking, and risk management. In addition, each project was specifically selected to offer the teams the opportunity to develop a useful deliverable with potential for use beyond this pedagogical setting. The result was a high-energy, dynamic, and demanding learning experience with plenty of lessons and opportunities for improvement by the instructor as well as the student.

Special Theme of Research in Information Systems Analysis and Design -II. Data Modeling or Functional Modeling - Which Comes First? An Experimental Comparison

The software analysis process consists of two main activities: data modeling and functional modeling. While traditional development methodologies usually emphasize functional modeling via dataflow diagrams (DFDs), object-oriented (OO) methodologies emphasize data modeling via class diagrams. UML includes techniques for both data and functional modeling which are used in different methodologies in different ways and orders. This article is concerned with the ordering of modeling activities in the analysis stage. The main issue we address is whether it is better to create a functional model first and then a data model, or vice versa. We conduct a comparative experiment in which the two opposing orders are examined. We use the FOOM methodology as a platform for the experiment as it enables the creation of both a data model (a class diagram) and a functional model (hierarchical OO-DFDs), which are synchronized. The results of the experiment show that an analysis process that begins with data modeling provides better specifications than one that begins with functional modeling.

An investigation of client/server application development methodologies

Client/server application development is becoming increasingly popular in commercial organizations. However, previous research has found that current application development methodologies provide little or no support for client/server computing possibly due to the relative newness of the technology in commercial environments. This research is the first step in demonstrating the applicability of the client/server methodology enhancements proposed in a commercial Management Information System (MIS) environment. It examines the application of traditional development methodologies to the client/server environment, the problems associated in using these methodologies and the respondent's rating of the importance of the various client/server application development issues included in the proposed methodology.

An Investigation of Client/Server Application Development Methodologies

Client/server application development is becoming increasingly popular in commercial organizations. However, previous research has found that current application development methodologies provide little or no support for client/server computing possibly due to the relative newness of the technology in commercial environments. This research is the first step in demonstrating the applicability of the client/server methodology enhancements proposed in a commercial Management Information System (MIS) environment. It examines the application of traditional development methodologies to the client/server environment, the problems associated in using these methodologies and the respondent's rating of the importance of the various client/server application development issues included in the proposed methodology.

A Tripartite Approach to Information Systems Development*

Management information systems (MIS) development is a process in which a user's vague, ambiguous, informal thoughts are translated into precise, nonambiguous, formal systems specifications required for implementation on a computer. A variety of MIS development methodologies have been developed, many designed to model a business‐oriented MIS in which either function modeling or data modeling predominates. Yet many of these techniques are inadequate for modeling time‐dependent behavior of the MIS, particularly when the MIS involves asynchronous, concurrent execution of cooperating processes. This paper proposes a tripartite approach to MIS development in which descriptions of “what” the MIS is to do, and “how” it is to do it are more closely related to the actual system implementation than with traditional development methodologies. The technique is based on three independent modeling tools used in conjunction: data flow diagrams, Petri nets, and production rules. The methodology in the context of computer integrated manufacturing systems is illustrated.