rajasri_profile1

7/27/2019 Rajasri_Profile1

1/7

The Company

We are Rajasri Systems, based in Chennai, the well-known IT hub of India. We are

the preferred Offshore Software Services Provider for many clients in USA.

Incorporated in 2000, managed by leaders with thirty years of innovative industry

experience, employing some of the smartest minds, Rajasri helps corporates and

people conduct business easily and efficiently.

Over the years, we have expanded our horizons to serve various sectors such as

Aviation & Aerospace, Design & Decor, Manufacturing, E-commerce, Advertisement &

Publicity, Media & Publishing , Energy and beyond. Widely, Rajasri is committed to

providing its customers with qualitative long lasting solutions. It is this dedication

and passion towards perfection that has made Rajasri repeatedly win projects and

clients. Once our client, always our client.

The People

We are very proud of our team of developers who constitute a very rich talent pool.

They are our asset and the primary reason for our success.

Our team members combine the right mix of technical and business skills. Add to

this their strong interpersonal and excellent communication skills and you have the

dynamic team that Rajasri is.

The History

Rajasri was incorporated in Chennai, India in the year 2000 to provide offshore

software services. It functions as Software Technology Park Unit and engages in

100% Software Export.

In its previous incarnation it functioned in the name RAD InfoTech India providing

same Offshore Software Services. This functioned from 1997 to mid 2000.

Thus altogether Rajasri has an experience of 8 years as a successful offshore

provider of high-quality software services to US clients.


2/7

The Technology

Internet/intranet applications - n-tier/thin client Client/Server& Legacy systems

Registered Member, Microsoft Partner ProgramSun Developer Connection[sm]Partner

Sun iForce[sm] Partner

Microsoft .NET Java PHP

Visual Studio 6.0 J2EE Perl

SQL Server Oracle MySQL

The Work

We invite you to our website www.rajasri.com to view the various projects we have

done.Here are of some of our recent accomplishments in the Internet Applications

area:

ebonza www.ebonza.com

BargainTix www.bargaintix.com

Bid4Spots www.bid4spots.com

Pacific Design Center www.pacificdesigncenter.com

Country Floors www.countryfloors.com

Front Row USA www.frontrowUSA.com

Cambridge Art gallery www.cambridgeartgallery.com

Netreo www.netreo.net

Lone Madrone www.lonemadrone.com

Monographx www.monographx.com

NeoGov www.neogov.com

The Software Development Principles

We firmly believe in and strive to adhere to the following Software Development

Principles:

We make it our highest priority to satisfy the customer through early and

continuous delivery of valuable software.

We anticipate and welcome changes in user requirements. We understand such
http://www.ebonza.com/http://www.bargaintix.com/http://www.bid4spots.com/http://www.pacificdesigncenter.com/http://www.countryfloors.com/http://www.frontrowusa.com/http://www.cambridgeartgallery.com/http://www.netreo.net/http://www.lonemadrone.com/http://www.monographx.com/http://www.neogov.com/http://www.ebonza.com/http://www.bargaintix.com/http://www.bid4spots.com/http://www.pacificdesigncenter.com/http://www.countryfloors.com/http://www.frontrowusa.com/http://www.cambridgeartgallery.com/http://www.netreo.net/http://www.lonemadrone.com/http://www.monographx.com/http://www.neogov.com/


3/7

changes provide a competitive advantage to the customer.

We strive to deliver functioning software at frequent intervals. This ensures us

that we are on the right track and helps us quickly correct errors. The Customer

sees that the software is growing day by day - just the way they ordered it.

We stress that business/knowledge experts and developers work together

regularly throughout the project.

We build projects around motivated individuals. We give them the environment

and support they need, and trust them to get the job done.

We recognize that the most efficient and effective method of conveying

information within a development team is face-to-face conversation and have

action-item-oriented brief stand-up meetings every day.

We believe that a functioning software is the most important measure of progress

and so strive to deliver such software to customers frequently.

We pay continuous attention to technical excellence and good design. We

constantly look for innovative and sensible ideas.

We firmly believe in the "Keep It Simple" principle.

Our development teams are self-organizing.

At regular intervals and, specifically after completion of a milestone or a project,

we meet to reflect on the areas we could have done better and how we can

become more effective. We then follow-up on this and adjust our internal

procedures accordingly.

The methods of communication with clients

We use telephones, Private Forums, regularly scheduled Net Meetings, and email to

stay in touch with clients.

Project Specific email IDs are given to Clients.

If Client wants to chat, he can look for this Project ID logged into MSN Chat (forexample) and begin chat, knowing someone from the ProjectTeam will be behind

that ID.

EMailIDs - Emails sent to project-based emailids are distributeds to all team

members.


4/7

SMS/Alert: Client can send SMS to a fixed ID via MSN chat or email. This will

instantly inform the right person.

Forums - We have found these to be one of the best tools to make surecommunication flows both ways and maximum colloboration is achieved.

Telephones - Nothing beats a phone call. We speak to clients periodically - monthly,

weekly, as needed. Even if there are no issues/problems.

The Development Methodology

Reusability is a major consideration in design. We have several libraries of in-house

reusable libraries and objects. We have also built several tools and webservices that

perform common-purpose tasks.

On the DB front, we follow practical normalization. User requirements, such as

reporting, decides the DB design. The team has worked with SQLServer, Oracle,

MySQL, MS Access and other flavors.

Strict version control is followed, as a matter of routine. We use VSS.

For projects that we begin working from scratch, we begin with requirements

analysis, then a look-alike prototype. When client OKs the prototype, we begin to

work on a detailed Test Plan, Validation rules, Process Specifications. Then follow

object and component designs. Then we begin coding.

For utility functions we have numerous reusable in-house libraries available, we

make use of these for the most part.

All changes are documented in the code and also notes are made in VSS when

checking in.

The level of detail of the changes is confined to explaining very briefly the reason for

the change. This is kept in VSS.


5/7

Our testing process has static/unit testing, integrated testing and then a system test.

Changes to existing functionalities require regression testing. With some clients, we

define Acceptance Testing up front. In such cases, we finish the project with an

acceptance test. Some cases require a predefined Acceptance DB. It may be defined

even before we begin the design of the system!

Our QA consists of code reviews & peer testing. This is strictly enforced.

Our release procedures follow the industry standard - a summary of changes done is

included, followed by a listing of files to be changed and special instructions. Details

of code changes made as part of the release are not included in the release notes.

Release notes are actually meant for the System Administrator, who is usually not

involved in the technical reasons for the changes. He is empowered to make changes

to the system and he follows instructions given in the release notes. He takes

precautions (such as backups) to safeguard the system against any ill-effects of the

release. He just needs to know what changes to make and where.

As a matter of routine, we recommend that the dev group (us) has no access to the

target environment. We know by experience that it is dangerous to mix the dev

group and the system admin group.

We have strict procedures to effect changes to production source files. Paper &

electronic trails are kept on the changes to be made. There is a Librarian for VSS who

is in charge of making changes - all developers cannot change files in VSS. Same

with DB changes - there is a DBA. There is also a system admin who is the only one

who can implement the changes on the production look-alike environments we have

to match client's.

We follow the standard practice of documenting the reasons for code change in the

code itself, under Modification History and in VSS. The level of detail of this

documentation is defined to be 'just enough to explain what and why' and is

expected to be as brief as possible. Those are the guidelines and, in real life, the text

of the detail is determined by the developer who makes the change.

Our experience is that dev team members know the amount of details that have to


6/7

note in the Change History. The description, in conjuction with details that can be

found by inquiring VSS will easily tell any other developer what changes were made

and why.

That, briefly, explains, hopefully, our process here.

The CEO

Since 1980, Rali has worked in the field of Information Technology with various

industries in the US, both on the west and east coast. He has several years of hands-

on software engineering and project management experience in development of web-

enabled applications, including eCommerce, Client/Server systems as well as

development maintenance, and reengineering of legacy software systems, in a

variety of industries. After working for several companies including Citicorp, Star TV,

and Casco Bank in Boston and Portland Maine, as well as Bank of America in Los

Angeles, Rali joined Digital Equipment Corporation in 1988 to provide software

consulting to various customers in Southern California.

After 4 successful years at DEC that included Excellence and Outstanding

Achievement awards in 1989 and 1990, he launched SREE Consulting Services in

Orange County and has been providing software services since 1992. In 1997, he

merged his business with RAD Info Tech, a new software company based in Santa FeSprings, California, and was successful in providing software services to a number of

customers both in California and Alabama. In 2000, Rali joined forces with Steve

Gray and Randy Wang to launch AmbaSoft, Inc to bring high quality software

solutions to the customer as a value proposition.

Rali works with a team pool of talented minds to create cost-effective services for

Rajasri's clients. Born and educated in India, Rali moved to the United States in 1980

and became a citizen in 1990. He holds Masters degrees in both Mathematics and

Computer Science. The prestigious Indian Institute of Technology awarded Rali the

University's top rank in Mathematics during both his Bachelors and Masters

programs.


7/7

The next phase

We are working towards getting the Carnegie Mellon's SEI-CMM certification in the

near future.

www.rajasri.com RAJARI SYSTEMS PRIVATE LIMITED# 26, FIRST MAIN ROADNANGANALLUR, CHENNAI 600061TAMILNADU, INDIAPhone: 91 44 2224-2272 / 2273 / 2274Email: business @rajasri.com
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]

rajasri_profile1

Documents