Software Development

Although our developers are highly experienced in software development in web technologies, they also differentiate for their following qualities. They have a positive attitude and are really interested in the success of your product. They have superior communication skills that are directly related to development skills. They have amazing self-learning skills. They have worked with a variety of technologies long enough to become experts and are proficient with many others. Another great quality is their ability to help others improve.

Finally, our team of developers does not just complete the tasks assigned to it, but takes into account the wider impact on the system and the user experience as a whole. Whether you are improving outdated code, or creating new, innovative, responsive applications, our team has the knowledge and experience to achieve any project goal.

Agile is a set of principles for software development rather than a methodology. Below are four values ​​as described in the principles appearing in the Agile Manifesto.

• Individuals and interactions over processes and tools;
• Working software over comprehensive documentation;
• Customer collaboration over contract negotiation;
• Responding to change over following a plan.

When we talk about an Agile project management methodology, what we describe is a flexible, iterative design and development process. Agile projects are characterized by a series of tasks that are captured, executed and adapted according to the situation, and not by a planned process. Being agile helps teams respond to the unpredictable through gradual, repetitive work processes.

What characterizes agile projects is the series of tasks that are captured, executed and adapted to the situation, and not the pre-planned process. Agility helps teams respond to the unpredictable through gradual, repetitive work processes.

Agile as a set of principles is Big Daddy. Agile tends to be used as an umbrella term used in Scrum, eXtreme Programming (XP), Kanban and Scrumban. In Agile project management, you can use any of these versions of Agile (Scrum, eXtreme Programming, Kanban, Scrumban).

Scrum is a project management methodology that proposes principles and process for improving delivery. In the context of software development, the Scrum methodology is one of the most popular and simple frameworks for the practical application of Agile principles.

Scrum’s main goal is to optimize communication, teamwork and development speed. When you hear sprints, scrums, backlogs and burndowns, they are probably referring to Scrum or some of its derivatives.

Scrum can not be considered as a project management methodology, but a framework for the continuous development and maintenance of complex products. Scrum defines a simple set of roles, meetings (called Scrum ceremonies), and tools for efficient, repetitive, and gradual delivery of valuable, shippable functionality.

Waterfall methodology often referred to as SDLC (Software Development Lifecycle) is a project management methodology with a simple approach that values ​​design; you just make a good plan and do it.

At the beginning, before any work begins, the requirements are completely defined, “At the top of the waterfall”. Then the work descends from the phases of the project, as water descends from a waterfall. In a Waterfall model, each phase is completed before the next begins. There is no overlap in the phases. Usually, in a waterfall approach, the result of one phase acts as the input for the next phase sequentially.

After program approval, there is minimal room for customizing it, unless the changes are really necessary, and change requests are required.

Due to the approach of a single circle, in a Waterfall project, there is minimal room for reflection and difficulty in reviewing and adapting once something is completed. Once you get to the test phase, it is very difficult to go back and change something that was not well designed at the idea phase.

Waterfall is considered an ineffective and passive traditional project management approach. However, the waterfall can be a useful approach in cases where the requirements are stable, well documented and clear, the technology is understandable and mature, the work is short and there is no added value from “going Agile”. The waterfall is a good approach for a more predictable end result for your budget, schedule and range.

The web applications we develop are mainly based on the “onion architecture”. This architecture does not raise fundamental issues of tight coupling and separation of concerns, like most traditional ones. Onion Architecture provides a better way to build applications for better testing, maintenance and reliability.

Onion Architecture uses the concept of layers, but differs from 3-tier and n-tier architectures as it addresses the challenges, that these architectures face, and provides solutions to common problems. Onion architecture uses Interfaces so that its’ layers can interact to each other.

Ιnversion of control is the principle on which Onion Architecture is based. It consists of multiple concentric layers that interface with each other towards the core that represents the domain. Classic multi-tier architectures depend on the data layer , onion architecture depends on the actual domain models.

Onion Architecture is undoubtedly biased toward object-oriented programming, and it puts objects before all others. At the center is the domain model, which represents the business and behavior objects. Around the domain layer are other layers, with more behaviors.

Onion architecture has four levels:

1. Domain Entities Layer
2. Repository Layer
3. Service Layer
4. UI (Web/Unit Test) Layer

These layers are towards to center. The center part is the Domain entities that represent the business and behavior objects. These layers can vary but the domain entities layer is always part of the center. The other layer defines more behavior of an object.