A brand new website
When we incorprated Swat.engineering early 2017, we quickly registered the domain swat.engineering and put there some temporary information. Little did we know that “temporary” would mean 3 years.
We needed all our time to run a start up.
A few month ago a colleague in an EU project said: “Hey, Swat.engineering must be doing pretty well, since your website is never updated”. Indeed, we are doing very well as a company working on exciting projects with a range of clients.
So time for a new website. With an increasing team and increasing ambitions we want to clearly communicate our technical expertise and what kind of services we can deliver to our clients.
We asked Kitty Molenaar to create a good looking web site that conveys the professional values we stand for. We think she did a great job. The technical realization of Kitty’s design was done by Bas Vredeling from Code Culture. All content was produced by the Swat.engineering team.
We hope that this website will help you to identify how we can help you to control your software. Or just ask us how we can help you.
We love to hear from you at [email protected].
Recent posts
DSLs for building new software
Most IT systems consist of closely interacting software components (applications/tools) that solve related problems in the same domain. Many components are based on the same domain elements.
In the banking domain this would include account, client, and interest rate. In the forensics domain file format and encryption would be prominent.
Building each software component from scratch will be expensive, error-prone and maintenance-intensive.
Using domain knowledge is the solution to these problems and it forms the centerpiece of the Swat.
DSLs for improving old software
What to do when a legacy system becomes too expensive to maintain or to add new functionality? Rebuilding the leagcy system from scratch will be expensive, error-prone and maintenance-intensive.
Domain knowledge forms the foundation of the Swat.engineering Methodology for legacy systems:
Our first step is to deeply explore all knowledge we can collect about the system, ranging from interviews with developers to automatic analysis of source code and documentation. The result will be a map of all the concepts and their relationships that are implicit in the system.