Following the principle of modularity implies separating software into components according to functionality and responsibility.

Following the principle of abstraction implies separating the behavior of software components from their implementation. It requires learning to look at software and software components from two points of view: what it does, and how it does.

The clients are learning to see the range of possible solutions that software technology can provide and it's effectiveness in meeting the clients needs. They want a reasonable & timely solution soon; perfection can come later.

It is important in designing software that is free from unnatural restrictions and limitations. Good software frequently survives beyond its expected lifetime.

In this process, we build the software in small increments; for example, adding one use case at a time. A carefully planned incremental development process can also ease the handling of changes in requirements.

Consistency serves two purposes in designing graphical user interfaces. First, a consistent look and feel makes it easier for users to learn to use software. Second, a consistent user interface promotes reuse of the interace components.

What is the use of a softare if all above are there, but dead slow? We find an optimum speed for the software along with all the above in place.

We take all basic measures for security of the aplication like never store plain passwords, add security headers to web page, proper file permissions and so on.