PARIMI RAJARAM
OBJECTIVE
Looking for opportunities to work in new areas using the cutting edge tools and the latest software development methodologies in an environment that gives me scope to apply my knowledge, assume responsibility and strive for collective growth and development.EMPLOYMENT SUMMARY
Over 3 years of software design & development experience in the areas of Thin Client Architecture (Web based), Change and Product Life Cycle management, Online Transaction Processing based Product & Project solutions.
EMPLOYMENT DETAILS
S
KILL SET| Languages | Java 2 (RMI, JDBC, Networking), C++, & C |
| Internet Tools | DHTML, JavaScript, VbScript, ASP, & XML |
| Web Servers | IIS (with Servlet Extension), JavaWebServer, & Apache |
| Rapid App. Dev.Tools | VC++, & Developer 2000 |
| RDBMS | Oracle 7.3 |
| Baan ERP | Baan ERP Tools 6.0, Baan Object Data Management, & Baan Product Data Management |
| OS/Platforms | Windows 95, Windows NT, UNIX (HP-UX, Solaris) |
| Source Control Systems | ClearCase, Baan SCM |
| Test Environment | WinRunner Suite |
| S/W Dev. Method's & Tech. | OOAD (Booch, Rambaugh Methods), CORBA, COM/DCOM (familiarity) |
P
ROJECT SUMMARYProject Title : Baan WebTop
Role : Design & Development
Duration : October 1999 ~ Till Date
Tools : Java Servlets, JavaScript, DHTML, XML, Middleware (B3)
Summary : Baan WebTop is a Thin Client Architecture based UI framework that can be configured to serve the needs of both power users and occasional users. Baan WebTop runs inside a Web Browser on an Intranet/Internet, and uses a similar UI concept as the Windows based Baan Worktop, with a look and feel that resembles the Microsoft Outlook interface.
My Role in this product is in the design and development of a Shortcut Bar Component for the WebTop framework, similar to the MS-Outlook Bar, to facilitate creation of user-specific Shortcuts to various Baan and non-Baan entities. The Shortcut Bar is built using JavaScript and is plugged onto the WebTop framework. It stores the login-specific shortcuts and shortcut groups along with the other User-Context information on the Web Server. Thus it is primarily a Client-Web Server communication based component.
Project Title : Baan Object Data Management
Role : Design & Development
Duration : July 1998 ~ September 1999
Tools : Baan 3GL and 4 GL Programming Tools, Java, and C++
Summary : Baan ODM is a generic and customizable (Complete/Quick) Change control, execution and implementation framework. It helps in defining, approving, and executing organization-wide change requirements including Product Life Cycle Management.
My Role in this product was in the design and development of the ODM Infrastructure management module. It was designed with an Object driven Architecture that provides a highly configurable framework to manage changes. This module manages the registration of Entities (that need to undergo changes) as Object-Type (with a pre-defined state). The state & behavior of an Object-Type can be modified as per the user requirements using Rules & Attributes. This module also provides a composite User Authorization Module where the existing Baan users can be assigned different Roles that help then in managing and completing the desired changes. It also has an Object based Querying facility with stored result-set option.
Project Title : Baan Product Data Management
Role : Development & API Testing
Duration : March 1998 ~ June 1998
Tools : Baan PDM API’s, VC++, and Oracle.
Summary : Baan PDM is a fully featured stand-alone PDM application including document & file management, configuration management, revision control, engineering change management and engineering workflow management capabilities.
My Role in this product was in the development of the Vaulting API’s. The Vaulting API’s are built over the lower layer System API’s. They help in providing a secured Electronic-Vault for the documents attached to the entities undergoing the engineering change. This class of API’s did the check-out, check-in of the main and associated entities along with their documents by moving the documents between Work/Temp/Release areas. These areas are user-defined directories on the local machine that serve as the storage for document vaulting. These were developed using the C programming language.
Project Title : Object Oriented front-end
Role : Design & Development
Duration April 1997 ~ November 1997
Tools : VC++
Summary : The Object Oriented front-end supplements Object Modeling and Object Querying facilities to an existing GIS system. It facilitates organizing the GIS data in an Object Oriented manner and clubs their behavior with the underlying GIS systems functions. It allows each user to define his/her own Model of Object Classes and Associations (single level Inheritance) and behavior. Each user’s object model is stored in a different Schema. The Object Manager manages the creation and updation of object instances and the User Manager controls the creation and updation of user and user schema’s. The front-end also has a Query Manager that helps the user with an interactive Query Builder Interface for the querying the Objects within a single Schema. The users can store the queries for repeated or later use. It implements OO-SQL SELECT statement.
Project Title : Status Reporting Tool on Job Scheduling
Role : Design & Development
Duration July 1996 ~ August 1996
Tools : Oracle 7.1 and Pro*C on Solaris
Summary : The job scheduling utility is used to query the work-in-progress status of a specified pattern. It generates a GANTT chart for the specified pattern, listing the various work orders in the shop floor, work order quantity, the operation which the work order is presently undergoing (along with the quantity). This utility helps in planning the date & time by which the work order will get completed so that both the work center utilization and order delivery and quantity can be planned. This helps in rescheduling the work orders and releasing fresh work orders to the shop floor.
EDUCATION
ACADEMIC HONOURS
PERSONAL DETAILS
