Performance specifications
As consultants, we often find that small shortcuts destroy end
results when companies make digital investments. Project
descriptions and contracts are often written to be open, and so
they lose their force as a management tool. Documentation of design
and code is often not supplied or is defective, resulting in huge
hidden costs in the long term. We work to ensure the quality
assurance and usefulness of delivered logic solutions, so that full
business potential is achieved.
Ebita now has the quality assurance tools (QA = Quality
Assurance), which we believe have the greatest influence on the
bottom line in digital investments. Ebita can transfer these tools
and teach their use, act as consultants in your projects, or as a
liaison between management and your project team.
Quality Assurance on Technology
System Tests - uptime and response times
Architecture Tests - security and usability
Database Architecture - Normalization, the optimal architecture of
database
Code Documentation - analysis and description of the
progam/code
Software Screening - selection of standard software.
ASP.Net
Ebita develops and maintains internet, intranet and extranet
solutions with typical project sizes ranging from 300 to more than
2,000 hours. Our starting point is the .Net platform and when
necessary we use CMS systems. Very often our projects involve the
integration of third-party systems via webservices, etc. We work
according to Microsoft's code style and user recommendations
(including MS Enterprise Libraries) to increase the transparency of
our solutions. In daily work, we practice the SCRUM and Lean
methods of development.
Blogs from the Ebita Code
team
Henrik Jensen's blog