Monday, November 26, 2007

Our Services for Small and Medium Enterprises.

1. Company Information

RIA LB COM SDN BHD (RIA) – A Brief Overview

Ria Lb Com Sdn Bhd ( 643348-P) is a MSC Malaysia status company focus more on productivity issues for Small and Medium Enterprises. We have developed customized Enterprise Software Solutions for our clients for more than 5 years in Malaysia.

Business Strategy and Focus

We never provide generic Enterprise Software Solutions instead we develop customized solution for each SME, Which has helped us to provide more cost effective as well highly customized Enterprise Software Solutions. This has helped SME to double their productivity which has resulted in doubling their profit.

We provide free IT consulting to increase your productivity and profitability.

We are the only company which gives guarantee to double your productivity and profit using our software solutions or refund 50% the money you spend on developing the software solution.

Quality @ RIA

We have robust development methodologies; systems & processes that we believe are world class and allow us to effectively compete globally. We are guided by global standards.

We are committed to delivering to you leading edge, innovative and high quality business solutions which ensures customer delight. We do this by establishing a culture of continuous improvement and focusing on each project we have, as it is our last.

Product Offerings

We offer products in the following domains:

Ø Enterprise products (e.g., ERP, CRM, Knowledge Management and Human Resource Management System)

Ø E Learning & Content Development

Ø Enterprise solutions integration with SAP, Oracle, and Microsoft Dynamics

Ø 2D and 3D Graphics and Animations

Organization Structure for a typical software delivery.

Provided below is a generic organization and communication structure that we successfully used with our other clients. This model is flexible and would be developed for every project. We would optimize this model based on the project, size of team, Ria and Client needs to successfully accomplish your project .The client team would be fully aware of the project every step of the way.

Ria – Client: Communication Flow

1) Regular communication of project plan, status reports, issue lists and action plans via emails & weekly conference calls

2) Technical reviews, discussions, clarifications along with offshore Architect, Analyst/Designer

3) Key milestone review along with Project Leader

4) Issue resolution of exceptional cases along with Project Manager and Project Leader

We use Base Camp for project management and tracking. The project plan is jointly developed resulting in a realistic project plan that will allow us to better manage risk and changes. The result is that your project is executed on time and within budget. . Our experience has shown that frequent communication with you is critical. Consequently, we would propose using the following communication plan to monitor the project’s performance.



Weekly project review

* Identify and resolve project issues, risk management

* New topics; change management reviews

* Project logistics

Monthly quality review

* Quality review – metrics and share them with THE CLIENT

Board Review meeting

* Between RIA and THE CLIENT management to monitor the performance of the project

2. Our Services – Expertise/Practices

Our company’s strategy aims at providing complete service options for current and potential Information Technology needs across industries. We also focus at providing these quality services in a variety of flexible models that are tailored to a specific industry or customer. Through this we are able to create a win-win business model that is mutually beneficial engagement.

Current service offerings:

* Consulting Services

Ø Technology Consulting

Ø Domain Consulting

Ø Infrastructure Consulting

* Research and Development

Ø Research, Architecture and Design

Ø System analysis and Specification Creation

Ø Development and Testing

Ø Re-engineering and Migration

Ø System Integration

Ø Enterprise Application Integrations

* Support and Maintenance

Ø 24 Hours Response on Bugs

Ø Automatic Notification of Update

Ø Automated Installation of Images

Ø Automated Patch Management

Ø Helpline and Call Center

* Additionally, we have four focus domains listed below along with our experience:

1. Enterprise – over 5 years

2. E Learning & Content Development – over 7 years

3. Enterprise solutions integration with SAP, Oracle, and Microsoft Dynamics – Over 5 years

4. 2D and 3D Graphics and Animations over 5 years

We are constantly looking to expand our expertise beyond these domains. In every case we understand that it is about providing high quality services along with the technical component. In cases where we do not have the complete domain expertise, we are willing to make the appropriate business investment to ensure that our customer receives value and high quality products and/or services.

Technical Expertise

We have a dedicated Research and Architecture team, with expertise in the latest software architecture trends such as SOA, LAMP, etc. This Team ensures that the software developed in-house is well structured; assuring the availability of reusable components and hence quick deployment. Also ensuring future maintenance and enhancements could be achieved with ease.

We have executed a number of projects and have core competency in .net, JAVA, Data migration (ETL) etc. Our other expertises are presented below.



Web Technologies



ASP (Active Server Page)

A core competence; very experienced



A core competence; very experienced


J2EE (EJB, JSP, Servlets) & Macro Media Flash

A core competence; very experienced


CGI-Perl (common gateway interface- Perl)

A core competence; very experienced


ISAPI (Internet Server Application Program Interface)

A core competence; very experienced


IIOP (Internet Inter-orb Protocol)

A competence; experienced


Browser Client Side Scripting Technologies



HTML (Hypertext Markup Language)

A core competence; very experienced


DHTML (Dynamic HTML)

A core competence; very experienced



A core competence; very experienced



A core competence; very experienced


Cascading style sheets (CSS)

A core competence; very experienced


MS JScript

A core competence; very experienced


Distributed and Enterprise Technologies


J2EE (Java 2 Enterprise Edition)

A core competence; very experienced


. NET framework

A core competence; very experienced


MS transaction services (MTS)

A core competence; very experienced


Distributed COM (DCOM)

A core competence; very experienced


Remote method invocation (RMI)

A core competence; very experienced


Sun JINI & Common object request broker architecture (CORBA)

Little experience


Wireless Technologies


WAP (Wireless Access Protocol)

A competence; experienced


WML (Wireless Markup Language)

A competence; experienced


J2ME (Java 2 Platform, Micro Edition)

Some experience


Microsoft Mobile (Smart Phone)

A competence; experienced


Component Technologies


COM (Component Object Model)

A core competence; very experienced


ATL (Active Template Library)

A core competence; very experienced


Macro Media Flash

A core competence; very experienced



A core competence; very experienced


Java Server Faces

A competence; experienced


Microsoft .NET Framework

A core competence; very experienced


3D Max, Director Shockwave Studio, along with the Adobe standards: Photoshop, Illustrator, In Design, and AfterEffects.

A core competence; very experienced


DPS Velocity, Final Cut Pro, Shake, Combustion

A core competence; very experienced

3. Methodology and Practices

Our Software Development Methodology - Rational Unified Process

Our development process follows the Rational Unified Process (RUP). RIA suggests the use of RUP for this project due to the following reasons:

q It would be the best methodology to address the managerial & technical risks of the project

q It would allow for effective management of requirements

q It would enable high quality output of all project deliverables

q It would allow good management of changes

RUP segments the development lifecycle into four phases:

· Inception: The major goal of the inception phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. The inception phase is of significance primarily for new development efforts, in which there is significant business and requirement risks that must be addressed before the project can proceed.

· Elaboration: The goal of the elaboration phase is to baseline the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the construction phase.

· Construction: The goal of the construction phase is on clarifying the remaining requirements and completing the development of the system based upon the baseline architecture.

· Transition: The focus of the Transition Phase is to ensure that software is available for its end users.

Functional Specs

Functional user requirements are formally defined and delineate the requirements in terms of data, system performance, security, and maintainability requirements for the system. All requirements are defined to a level of detail sufficient for systems design to proceed.

Project Goals, Justification, and Success Criteria

* Features

Ø Feature 1 - Explain exactly what the feature is to perform in Use Case format. List any constraints, actors, security implications, etc.

Ø Feature 2, etc.

* Data Conversion Requirements

Ø Identify the requirements in which we must convert data to import into the system. Detail the mapping needed from their system to the new system.

Ø Performance and Response Time Requirements

Ø How many concurrent users will be using the system and expected response time.

Ø Platform Dependent and Installation Requirements

What platforms the client presentation layer must run on (Windows 95, 98, NT 4, 5, etc) and describe the installation process.

* Localization Requirements - Requirements that are specific to localization (date and postal code format, etc.)

* Parallel Testing Requirements

Explain the areas of the system (if any) that must be run parallel to an existing production system and compared for consistency.

* Cross System Interface Requirements

How the system interacts with and details any requirements for testing with that system to ensure integrity.

* Data Archival, Backup and Recovery Requirements

How to manage the purge, archival, backup and recovery requirements of the system.

* Reporting Requirements

Describe the reports (if any) are required for the system. Are they to be online or run in batch and must they be exportable to other formats such as MS Word, MS Excel or HTML.

Project Flexibility Matrix

For a project to succeed, there are 3 variables that affect how quickly a project can be completed: Resources, Schedule and Feature (see diagram below). One of the sides of the triangle must always be flexible to achieve success. For example, if the client has a fixed number of resources (people that work on the project) and their schedule has been set in stone, the feature set must be flexible. This means that they must be flexible to drop some features to make the pre-determined date with that number of resources.

Project Trade-off Matrix



Resources (Cost)

Ship Date


Working together, the team and customer place a check mark in the appropriate column for each of the project variables. The columns are defined as:

q Inflexible. Mark 2 items that is inflexible. For example, if the cost and ship date are set in stone, make Resources (Cost) and Ship Date as Inflexible. Only 2 items can be inflexible, the last item must be flexible.

q Flexible. Mark one item as flexible. For example, if you are flexible with the features that are included in the project, mark Features as Flexible.

A team should use the project trade-off matrix as a reference when making decisions. The matrix is not intended to show absolute priorities; it is merely a tool to facilitate communication and understanding. Most important for the project team is that the matrix shows areas in which the customer is willing to compromise. Make sure that no row or column in the project trade-off matrix has more than one check mark. Any other combination poses serious risk to the project and must be accounted for explicitly in the risk management plan.

In order for a team to be successful, at least one check mark must be in the “flexible” column. This means that the team owns one side of the triangle (that is, owns at least one variable) so that the team is empowered to manage change and risk, and is therefore positioned to achieve success instead of failure.

Stack Ranking of Features

To ensure that items are worked on in order of importance, stack rank the features with the lowest stack rank being most important and the highest stack rank being least important. This will allow the development team to focus on the important items and to manage risk.


Req #




Display MSL Listings (very important)



Update agent information (not very important)

Technical Specs

System Design Overview

1) Architectural Representation (this section describes what software architecture is for the current system, and how it is represented. Of the Use-Case, Logical, Process, Deployment and Implementation Views, it enumerates the views that are necessary, and for each view, explains what types of model elements it contains.)

2) Key Abstractions

3) Layers and their Dependencies

4) System Requirements

5) Software Requirements (Win 95,Biztalk…. etc.) Hardware Requirements (processor speed, RAM, hard disk space…)

Business Domain Model

q (Global summary level class diagram without attributes and operations)

Use Case Analysis

q Overall Use case diagram, Use Case Realization Interaction Diagrams, VOPCs, Analysis Class-To-Analysis Mechanism Map

Design Elements

q Subsystem Context Design, Analysis Class-To-Design Element Map, Design Element-To-Owning-Package Map

q Packages and their Distribution

Static View: (Class Diagrams for each Use case with methods)

Concurrency Design

i. Process Model (Identification of process and threads to utilize multiple CPUs and/or nodes, increase CPU utilization, provide fast response to external stimuli, service time-related events, prioritize activities, load sharing, improve system availability and support major subsystems.)

ii. Element-to-Process Design (To determine which processes classes and subsystems should execute within.)

Distribution Solution

i. Deployment Model (mapping of module/component/subsystem to runtime entity),

ii. Distribution Mechanism

Subsystem/Component Design

i. Component Architecture (A pictorial representation is presented.)

ii. List of components

iii. Functionality of component

iv. Interface Realizations

a) System

§ Internal

§ External (Interfaces to other systems, products, or networks are described.)

b) Machine (Interfaces to other machines (computers or devices) are described.)

v. Subsystem Dependencies Class Diagrams

vi. Performance Issues

vii. Restrictions/Limitations

Class Design

Operations, States, Attributes, Dependencies and Associations

Data Design

i. Data Structure

a) Internal (Data structures that are passed among components the software are described)

b) Global (Data structured that are available to major portions of the architecture are described)

c) Temporary (Files created for interim use are described)

ii. Database Description Overall data model, Tables: Table name, Column name, Data types. Index: Relationships, Constraints, Keys, Checks. Triggers

Code Organisations: Binaires, Librairies, Files, Directoires, Version matrix (optional)

Operations Détail:

(Optional-if relevant)

i. Data Storage

ii. Audit Trails maintained

iii. Backup/Recovery Plan

iv. Installation

Security Aspects: (Optional-if relevant)

i. User Level authentication

ii. Access rights

iii. Firewall

iv. Encryption

v. 3rd party tool

vi. System level security

Capability Issues:

A description of how the architecture and design contributes to all capabilities (other than functionalities)

Extensibility, Reliability, Portability, Reusability, Performance

Administrative Activities

I. Admin levels with roles

II. Maintenance Task: Daily, Weekly, Monthly

III. Archiving


The mission of RIA is to ensure that software systems and products are delivered to the customer in the best possible working condition, using established standard procedures to measure defects, determine their root causes, and take action to prevent their future insertion. The purpose of this document is to assist RIA projects in establishing a Software Testing function. This Testing process describes seven activities. They are:

1. Plan Test

2. Design Test

3. Implement Test

4. Evaluate Developed Test

5. Execute Test

6. Report and Evaluate Results

7. Quality Measures

Testing Process Overview

RIA – Quality Assurance Program

Our quality program addresses all areas of the development life cycle including design, development, installation, delivery and support.

We have formally documented our software development process along with the related process assets (e.g., software life cycles etc.).

Ria is responsible for coordinating and ensuring that lessons learned are incorporated into our current project development and delivery methodology. Ria leads efforts to define, document, and implement a disciplined process for developing software. By developing a more standardized process, we are able to lower the learning curve when we bring new members to the project.

Change control process

Any changes are managed rigorously so as not to impact the overall product schedule. Change requests are analyzed for its detailed impact on the system. The change control board defined by our organization will decide if that change request will be incorporated based on our analysis of the project impact.


Krista said...

This is great info to know.

Anonymous said...

The information here is great. I will invite my friends here.


Anonymous said...

You are not similar to the expert :)