Academic journal article Informatica Economica

Software Development: Agile vs. Traditional

Academic journal article Informatica Economica

Software Development: Agile vs. Traditional

Article excerpt

Organizations face the need to adapt themselves to a complex business environment, in continuous change and transformation. Under these circumstances, organization agility is a key element in gaining strategic advantages and market success. Achieving and maintaining agility requires agile architectures, techniques, methods and tools, able to react in real time to change requirements. This paper proposes an incursion in the software development, from traditional to agile.

Keywords: Software Development, Traditional Models, Agile Models, Agile Architectures, Agile Techniques, Agile Instruments

Introduction

Increased agility is a magnet to all organizations, especially for those in private sector. It will allow a rapid and efficient adaptation to market changes and gaining a strategic advantage. Moreover, increased agility contributes to decreasing the development time for new processes and increasing flexibility for existing processes, where modification and implementation is required. All that leads to decreased time for solving client demands, more clients gained, lower adaptation costs and finally increased revenue.

In a complex and permanently changing environment, organization agility is no longer a necessity but a condition to access or remain on the market. An agile enterprise adapts fast to client demands and market opportunities, gaining competitive advantages on the market. This can be achieved only if the stakeholders clearly understand the working ways of the organization.

From informational systems point of view, there are several ways to achieve agility, among which: Business Process Management (BPM) for orchestrating independent functionalities, Service Oriented Architecture (SOA) for designing and developing such functionalities and Decision Management (DM) for management of organization decisions.

2 Software Development Life Cycle

Development models are various processes or methodologies, selected to develop the project according to its purpose and objectives. Software developments models help improve the software quality as well as the development process in general.

There are several models for the software development life-cycle, each developed for certain objectives. Software Development Life Cycle (SDLC) is an environment that describes activities performed in each stage of the software development process. SDLC consists of a detailed plan that describes how the development, maintenance and replacement of specific software is conducted. This is also known as software development process. [1]

The international standard for SDLC is ISO/IEC 12207. It aims to define all activities required to develop and maintain software. Figure 1 depicts the various stages of a typical SDLC.

Stage 1: Requirements analysis and planning Analysis of requirements is the most important stage in SDLC. It is performed by senior members of the team, using inputs from the clients, sales department, market research and industry experts. This information is then used for a basic project plan and feasibility study from economic, operational and technical points of view. Also, in this stage the team plans the quality insurance requirements and identifies project risks. The result of technical feasibility study consists of definition of carious technical approaches that can be used to implement the project with minimal risks.

Stage 2: Definition of requirements

After the requirements are analyzed, product requirements are clearly defined and documented. They must be approved by the client or by the market analysts through SRS (Software Requirement Specification). The SRS document lists all product requirements that must be designed and developed throughout the project life-cycle.

Stage 3: Product architecture design

SRS is the basic reference from which the architects set out to create the best architecture for the product. Usually, at least one product architecture approach is proposed, and it is documented in a DDS (Design Document Specification). …

Search by... Author
Show... All Results Primary Sources Peer-reviewed

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.