Thursday 3 April 2008

This Day - That Year in 2005! :)

The day was Sunday - The Time 10 AM. An unusual Sunday considering I had got up well before my usual Sunday wake up time of 9:30 – 10 AM. The purpose was clear. We had a family coming down to visit us and assess if we could strike our relations for the long term.

I was my usual self – hair nicely shampooed and neatly left open, my favorite Fast Track watch on the left palm, a single bangle in the right, a simple gold chain bearing the unique ‘S’ pendant, a crisply ironed cotton dress – only I was carrying the dupatta this time in spite of it being a conservatively measured neck with a Stand collar and absolutely no trace of makeup other than a lip balm.

Dad was busy organizing the logistics – the Boy's Dad would sit here. The Boy would sit on this chair and you sit exactly opposite to him. Mom would be in this corner and I would sit beside his Dad with his Mother sitting beside you. :)

And all this seemed so very funny – I even remember asking if he is going to command them to sit where their seats were planned and he said of course not but I would definitely guide them. And I thought in my mind what a waste this exercise was!

My brother Anant, assuming that this is going to be just another family which my Sis isn’t gonna approve of had already left to meet his friends for the supposed project work that they had taken up! [I had disapproved of two other proposals that my parents short listed].

The clock struck 10, when seconds later the door bell rang - the family is here – SHARP at 10!! While we @home were prepared with all that was to be served and in place, our extended family was still to come. The Boy’s Family was welcomed home – I don’t know who came in 1st cause I was in the kitchen and wasn’t supposed to come out till commanded :) They were 5 of them – The Boy, his Parents and his Aunt and Uncle and we shortly after were 3 families from our side – Mom n Dad, Aunt and Uncle [both Maternal and Paternal] and me.

So it was 5 People to see the girl and 7 to see the Boy! Maan the place was crowded and amongst this crowd I was suppose to figure out if this Boy was indeed my dream match! I however had it easier since I was rehearsing this for the 3rd time. For him though it was his 1st time [and he hoped post meeting that it was his last as well! :) ]

Shortly after when the Poha, was finally to be served amongst several other things I picked up the tray and told Mom I am Going to serve this! Mom was shocked – its too early for you to make an appearance – I said I don’t care!! I am going! And in my usually fast pace Out I GO! My Mom by then had probably almost collapsed :).

Well the Boy dint have the guts to look up but his Dad introduced me to him [I was wondering that like my Dad, he too had his actions well pre planned :) ] I said “Hi!” and he was astonished “Is this the Girl, or is there someone still waiting in there” ***

And so now that I was there, seated right in front of him as planned, I was being variedly questioned. The talkative and extrovert soul that I am, I spilled it all in one go :) and
slowly, so did the Boy – not once did he look at me! When the Father figures asked us had I anything more to ask I said: "No he summarized things very well". My Dad however, was uncomfortable with that and so was the Boy. He said he would like to have a moment in person and I was quite speechless – my heart skipped a beat!

So when we were given privacy, he was casually discussing a lot of other things only to find me not responding as vivaciously. So he said “its fine if you are short of things to say or are not in a mood to talk – maybe you could call me up or email me and we could talk at ease when you wished to – and he handed me his Business Card” I thought wow how considerate – I should be humble enough and play a good host!

That kind of eased me out and then I got talking. I do not know how, but he had managed to get the 3 most important things out of my mind and they were - that I dint have the intentions of retiring doing technology, that I wanted to pursue a Masters Degree but what I would specialize in was something I needed help in figuring out and that if I was faced with an impending situation where I would have to choose a career and family I’d always choose the later.

And while he agreed that the moment he saw me in the snap he found himself looking at a girl who had a warm and loving look, that he would love to come back to, after a hard day of work, his decision to marry me was reaffirmed only after he had learnt the above things. The only thing not clear to him was whether I was going to approve of him.

What I had learnt from him was, he always wanted his wife to keep herself occupied - that dint necessarily mean that she is compelled to work. To put her skills and education to good use. And it was perfectly fine if she dint know how to cook.

Before we parted, there was no handshake, no “nice meeting you nothing”! We just exchanged smiles. It was close to Noon when both the families exchanged pleasantries and were guided downstairs accompanied by my Parents and Uncle. The ball was in our court and we were asked to communicate my decision.

Everyone came upstairs to ask me what I thought and I said: “He is the best out of the ones I met till date”. My Dad continued to complete “... and he is the BEST we have for you” [after going through a painful search process of a couple of months scanning 50 odd profiles and filtering just 3 that matched my requirements]

It was this day April 3rd 3 years back - the day I met Abhi for the 1st time.

As someone rightly said : “There is someone made for each one” and that one for me was always Abhi… :)

Luv as always
- sayli :)

3 days later [when Abhi had refused to see any other girl till I responded, and on the 3rd day, while he was in the middle of a clean shave, and was thinking of starting afresh on his Bride Hunt, my Dad called up to convey a YES !! :) ] While the rest is history in itself, I am convinced each day, that Life couldn’t be any Better!!

*** Later on I learnt that when the daughters of the Yadav family had guys coming over to see them, they would always be presentably dressed up in a zari bordered saree, jwellery and make up and would make a late appearance – always, only when they were asked to. The exact opposite of what I did and was hence perceived by Aai - Baba as bubbly, original self, open minded and easy to get along with!

Tuesday 1 April 2008

It Ain't Easy Being an HR Professional

I have absolutely no idea what motivates me to write on this topic. Maybe it’s the fact that I have moved across and been astounded by the HR Professionals that I have interacted with.

At times, when I put myself into their shoes I think – its way too taxing to be the bridge between the Higher Management and your Employees. Depending on what you are asked to communicate, you might almost always (if the communication is not pretty much in favor of the employees) run the risk of being criticized to the core!

I’ve had the pleasure of having interacted with at least a quarter dozen HR Professionals who are a part of my social circle. I’ve seen them all go through their own set of ups n downs. So where do the challenges really stem from and in what circumstances. And while attrition is the most obvious of all the varied challenges HR Professionals look to tide over, I think it is worth thinking about the other factors as well.

One: Maybe you have the responsibility of downsizing, right sizing or even ramping up the workforce. These are challenges in themselves. Issuing Pink Slips isn’t easy and neither is it easy to meet recruitment targets when you have people accepting an offer and not joining you.

Two: At times you may not always be empowered to take decisions. There may be situations when the Job you do, may not be truly strategic in the sense of completing the triad of the Business Leaders, the Finance Guys and The HR. You may be desperate to be participating in driving key business decisions, but instead might be asked to focus on other administrative functions.

Three: There will be days you feel not one soul is happy with the work you do. While you do wish to keep the employee interests in mind on one hand, you may be constrained by the company policies on the other.

Four: You might run the risk of carrying the emotional burden of the concerns your employees have. While it’s always wise to be practical, it’s not always possible.

Five: You might be misguided by incorrect feedback. Well when training is being conducted, and you ask in person for a feedback people might be nice to smile and say things are perfect. It may turn out to be the exact opposite when you start going through the feedback forms.

I’ve always heard people say that “HR is the most cursed of all the functions within an organization” – well may be, but it surely is a key driving force in keeping your staff satisfied. And while these 5 paragraphs might lead someone to think against pursuing a career in HR, I’d vouch that there definitely are more motivating factors to truly consider this as a career option – of course only if a passion for communication, people, and teamwork figured bold on your inherent skill set.

Thursday 27 March 2008

A Table of Contents for a Detailed Design

While this is not a Standard Template and should not be treated as one, it is the result of my attempt to come up with A Table of Contents for a Detailed Design Specification using WebSphere Process Server.

1: Purpose of the Document
The need for a detailed design document is authored here.
2: Scope of the Document
List out specifically what the document covers and excludes.
3: Solution Overview
This section will give a brief background of the implementation of the solution.

4: SCA Elements
All elements of Business Transactions are referred to as Service Components. Examples of SCA elements are as follows:
Access to Web Services
Enterprise Information System Service Assets
Business Rules
Workflows
Databases
This section should list out the SCA Elements.

5: Business Objects / SDO (Service Data Objects)
Business objects define the data flowing between SCA components. Business objects provide an abstraction for data access and are based on a data access technology called Service Data Objects (SDO). SDOs provide a universal means of describing disparate data. Business objects provide rich features to map, manage, and transform data to underlying IT and are described through a standards-based XML schema
This section should list out the SDO’s in detail.

6: CEI
Common Event Infrastructure and the use of a Common Utility Framework for the purpose of:
Logging
Auditing / Archiving / Re Processing
Error / Exception Handling
Notifications
Security
With the Common Event Infrastructure (CEI), service components can emit events that can be captured by business monitors such as WebSphere Business Monitor for real-time monitoring of business processes.
This section should List the specific Events that will be handled by the CUF/CEI.

7: Supporting Services
Supporting services are components that are needed in any integration solution, including data transformation and synchronization services. This Section will list the details of the Supporting Services.

Mediation Flows
WebSphere Enterprise Service Bus provides the ESB functionality, with mediation flows that can operate on messages to perform
• XML-based data transformation
• protocol transformation between various transports
• custom Java operations
• routing
This section will detail out all the mediation flows

Interface Maps
Using interface maps, you can invoke components by translating calls to them. It is possible for interfaces of existing components to match semantically but not syntactically. This is especially true for components that already exist and services that need to be accessed.
This section will detail out the Interface Maps

Business Object Maps
Business object maps, you can translate one type of business object Into another type of business object. You can use these maps in a variety of ways, for example, in an interface map to convert one type of parameter data into another.
This section will detail out the BO Maps

Relationships
You can use relationships to establish relationship instances between object representations of the same logical entity in disparate back-end systems. For example, the same customer’s address might need to be updated in various back-end systems, such as an enterprise resource planning (ERP) system and a customer relationship management (CRM) system. These relationships can be established and managed automatically using the relationships service component. These relationships are typically accessed from a business object map when translating one business object format into another.
This section will list the relationships to be accessed from a BO.

Selectors (Dynamic Service Selections)
You can use selectors for dynamic selection and invocation of different services, which all share the same interface. WebSphere Process Server offers a Web-based interface to enable dynamic updates to the selection criteria and target services, which means that a module that has been deployed at a later time can still be called by this selector component, enabling dynamic changes to the integration solution
This section lists out the Dynamic Service Selections.

8: SCA Element Implementations:
There are Multiple ways of implementing a SC Element
Business Processes
A business process component implements a Business Process Execution Language (BPEL)-compliant process. You can develop and deploy business processes that support long- and short-running business processes and a compensation model within a scalable infrastructure. You can create BPEL models in WebSphere Integration Developer or import from a business model that you have created in WebSphere Business Modeler or any other modeling tool that supports the BPEL standard.

Human Tasks
Human tasks are stand-alone components that you can use to assign work to employees. Additionally, the human task manager supports the ad hoc creation and tracking of tasks. WebSphere Process Server also supports multi-level escalation for human tasks, including e-mail notification and priority aging.

Business State Machines
Business state machines provide another way of modeling a business process. Some processes are easily described as a sequential flow of activities, and they can be modeled as business processes. However some processes are driven by events rather than a sequence, and in this case, the business state machine is a better fit for modeling the process. One example is an ordering process where you can modify or cancel the order at any time during the order process until the order is fulfilled.

Business Rules
Business rules are a means of implementing and enforcing business policy through externalization of business function. As a result, dynamic changes of a business process are enabled for a more responsive business environment.

9: SCA Elements Interface (How to call this component)
By definition, an interface is the place at which independent and often unrelated systems meet and communicate with each other. An interface can be defined by any programming or interface definition language. WebSphere Process Server currently supports a Java interface definition and an XML definition (Web Services Description Language (WSDL) port type). The arguments described in an XML schema are exposed to programmers as SDOs. The WebSphere Integration Developer tooling primarily generates interfaces using the WSDL representation.

10: SCA Elements Reference (What this component calls)
An SCA reference specifies other SCA services that a component uses. These can be soft links that do not have to specify which specific component will be used.

12: Project Build & Design
Libraries
List of Project Libraries referenced / used.
Modules
How the Business Integration Module is developed and the artifacts (services choreography into Business Processes) that are built. Any Import, Export and Service Components that are used should be listed here.

13: Assembly & Deployment
How the Module is packaged, deployed and tested in the development/testing/staging/ production environments.

14: Conclusion

15: Signoff