If you've purchased a car, shopped in major retail stores, or used a bank, chances are that you've used some of our software.
If you are an insurance company, bank, government agency, or data-entry shop in Japan, chances are our software is a part of your operations, with full Romanji, Hirigana, Katakana, and Kanji support.
Our specialties include sophisticated backend software for your Web presence, high security interfaces for the Web and Internet, automated software migration from one platform to another and from legacy systems to modern environments, and computer-aided reengineering of legacy systems.
Web Backends
We create sophisticated custom backends to interface your Internet Web
presence with your own internal data. Your Web pages can present
specialized information, advertising, and feedback to attract more
visitors and to better service your customers.
We help make your web page a valuable part of your customer
support, promotion, education, and sales efforts.
Standard Web pages written in regular HTML, the basic language of Web
design, cannot do this.
We add Java, Javascript, XML, Perl, server side includes, client side
imagemaps, and other new technologies to fit your needs.
Along with this, we develop high security packages to control access
to the information behind your web page.
It's great to present up to the minute information via the Web but
not at the cost of allowing random and unauthorized access to your
internal database by outside parties.
Our backends guard against this.
Software Migration
Sii produced the
first major commercial project
on a Unix system not from ATT, back in
1981.
We've been migrating software to Unix longer than anyone else.
We use
automated software translation
tools that we develop.
The goal of all of our translators is 100% conversion of the application
sources with no "fixup" or other manual intervention needed.
We rarely fail to meet that goal.
Why is that important?
Most of the conversions we do consist of thousands of programs and millions
of lines of code.
If even 1% of that required editing, that would make many conversions
impractical.
Why convert?
Why not just throw all the old stuff out and use a CASE system to redo
the application the right way?
That's certainly an option, but that takes a long time, and market pressures
might demand a quick migration.
We typically turn around a multi-million line conversion in a matter of a
couple of months, from start to final acceptance.
That's a whole lot faster than any reengineering effort can match.
But all's not lost!
Part of our translation collects
metadata
about all aspects of the application,
and the metadata can be exported to a CASE system to ease the eventual
reengineering effort.
During the conversion, new features can be added to the application, such
as use of a Relational Database, or providing web access to the applications
or data.