ESolutions SK
  • DISCUSS SOLUTIONS

    Based on past experience we see that before plan any solution for problem is necessary discuss with client and have good understanding of client working processes, to understand client current system if any and spend time work in client environment. That can help us find solutions that fits to client needs.

    We try to make focus to discuss solutions and over simulation, mockups and other techniques evaluate them in practise.

  • WORK ON SOLUTIONS

    We offer applications build based on common sense. Customer feedback during implementation phase is very importent too. Each type of application and solutions needs separate approach. We are able to build application based on last technology or reuse already build solutions and adapt per client requirements. Anytime we will follow follow the best practices and standards.

    Software delivery contains list of unit tests, code analyses , code metrics and coverage results.

  • SUPPORT SYSTEM

    We take support deployed application very serious. There are a number of steps that are necessary to achieve before delivery. Performance and stress tests results are part of delivery that helps client final decision about go to production.

    There are a number of post deployment steps that help at first stage and at the future monitor, troubleshoot and fix production issue. Per application type and test results we define list of application output that helps identify bottlenecks or system issue soon.

 

ALM ( Application Lifecycly Management)

We believe good software has to follow certain steps. The process how to build software can change based on complexity but the main steps has to be still part of software development life cycle. There is necessary spent some amount of time with base requirements, make sure we understand client non-functional requirements so at the end final product meets SLA. ALM introduces us a number of options how to accomplies that process. Define development methodology, define tools to help us follow development processes and deliver workable software with the best possible quality.

Manifesto for software Agile Development

We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:

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

  • That is, while there is value in the items on the right, we value the items on the left more.

    Development

    The professional goal of every software developer and every development team is to deliver the highest possible value to employers and customers. Yet our projects fail, or fail to deliver value, at a dismaying rate. The upward spiral of process inflation, though well intentioned, is culpable for at least some of this failure. The principles and values of agile software development were formed as a way to help teams break the cycle of process inflation and to focus on simple techniques for reaching their goals. At the time of this writing, there are many agile processes to choose from: SCRUM, Crystal, feature-driven development (FDD), adaptive software development (ADP), and Extreme Programming (XP). However, the vast majority of successful agile teams have drawn from all these processes to tune their own particular flavor of agility.
    from Agile Principles, Patterns, and Practices in C#