To create successful custom software systems, our experts have
developed a hybrid software development methodology from these
existing methodologies:
Rapid Application Development (RAD) - rapid prototyping to
prove in the concepts
Agile Software Development - rapid delivery of simple and
functional software, close cooperation between developers and
customer, technical excellence, solid design, adaptable
Extreme Programming - reduce the cost of change, deliver
frequent working software
We have never failed(!) to produce the system that our
customer wants.
Languages & Platforms
Here are some of the languages in which we are fluent:
ActionScript, C#, C++, Cold Fusion, Delphi, Java, JavaScript,
PHP, Perl, Python, Ruby, SQL, Visual Basic. We are also fluent
in various software technologies including DHTML, DCOM, WSDL,
XML, Web Services, mobile apps, etc.
User interface
Simplicity is important in user interface design. select the
right interface controls for the situation. Different
situations can be handled in different ways, and certain
controls are better at their intended task than others.
We Disable pressed buttons.
Emphasis on buttons: “Create” and “Cancel.” The “Create” link
is more important.
When we are designing a Web application, it’s important not
only create it to look good with sample data, but we ensure
that it looks good and is helpful when there is nothing there
yet.
We design the empty states.
We design useful feedback messages,
great flat navigation that's clear, breadcrumbs.
We darken the background or use Shadows around modal windows
under modal window. |
|
Code Compatibility & vetting
There are variety of tools are available today to help us
cross check and validate our code. We use a variety of Project
Analyzer tools. W3C, XHTML, Browsers, etc.
Quality Assurance
The primary purpose for testing is to detect errors in coding
so that defects may be uncovered and corrected.
Testing cannot establish that a product functions properly
under all conditions but can only establish that it does not
function properly under specific conditions. The scope of
software testing often includes examination of code as well as
execution of that code in various environments and conditions.
It also verifies the requirements of the code: does it do what
it is supposed to do and what it needs to do?
Staging server environment
A server used to temporarily show certain users new and
revised Internet and/or intranet pages before they are put
into production. The staging environment lets us move Web site assets within
and across different environments. For example, we can move a
new Web page or a marketing campaign from a test environment
to a production environment. In an enterprise deployment, we
can define staging projects to move content from the
development environment to the integration/test environment,
from there to the staging environment, and from there to the
production environment.
A typical timeline may include:
3-4 user interface design studies (usually the home page)
Sitemap (& possibly workflow diagram)
Use cases (for apps)
Storyboards (if any)
Approval of each of the above
Production management
Module and code base development
Staging
Quality assurance
|