We're Sixty!!

Well. we've our share of problems, and we've got population explosion, zero-ethics politicians, corruption and what not (don't expect me to complete this list in near future!). But, with all that, we're 60....and we roar in many fronts! Vande Mataram!



And salute to those who gave their lives to make us free.......let the sacrifices of those live forever in our minds....

English Verbatim

Sarfaroshi ki tamanna ab hamaare dil mein hai
Dekhna hai zor kitna baazu-e-qaatil mein hai

Karta nahin kyun doosra kuch baat-cheet
Dekhta hun main jise woh chup teri mehfil mein hai
Aye shaheed-e-mulk-o-millat main tere oopar nisaar
Ab teri himmat ka charcha ghair ki mehfil mein hai
Sarfaroshi ki tamanna ab hamaare dil mein hai

Waqt aanay dey bata denge tujhe aye aasman
Hum abhi se kya batayen kya hamare dil mein hai
Khainch kar layee hai sab ko qatl hone ki ummeed
Aashiqon ka aaj jumghat koocha-e-qaatil mein hai
Sarfaroshi ki tamanna ab hamaare dil mein hai

Hai liye hathiyaar dushman taak mein baitha udhar
Aur hum taiyyaar hain seena liye apna idhar
Khoon se khelenge holi gar vatan muskhil mein hai
Sarfaroshi ki tamanna ab hamaare dil mein hai

Haath jin mein ho junoon katt te nahi talvaar se
Sar jo uth jaate hain voh jhukte nahi lalkaar se
Aur bhadkega jo shola-sa humaare dil mein hai
Sarfaroshi ki tamanna ab hamaare dil mein hai

Hum to ghar se nikle hi the baandhkar sar pe kafan
Jaan hatheli par liye lo bhar chale hain ye qadam
Zindagi to apni mehmaan maut ki mehfil mein hai
Sarfaroshi ki tamanna ab hamaare dil mein hai

Yuun khadaa maqtal mein qaatil kah rahaa hai baar baar
Kya tamannaa-e-shahaadat bhi kisee ke dil mein hai
Dil mein tuufaanon ki toli aur nason mein inqilaab
Hosh dushman ke udaa denge humein roko na aaj
Duur reh paaye jo humse dam kahaan manzil mein hai

Wo jism bhi kya jism hai jismein na ho khoon-e-junoon
Toofaanon se kya lade jo kashti-e-saahil mein hai

Sarfaroshi ki tamanna ab hamaare dil mein hai.
Dekhna hai zor kitna baazuay qaatil mein hai.

The Poem ( Devnagari version)

सरफ़रोशी की तमन्ना अब हमारे दिल में है
देखना है ज़ोर कितना बाज़ुए कातिल में है

करता नहीं क्यूँ दूसरा कुछ बातचीत,
देखता हूँ मैं जिसे वो चुप तेरी महफ़िल में है
ए शहीद-ए-मुल्क-ओ-मिल्लत मैं तेरे ऊपर निसार,
अब तेरी हिम्मत का चरचा गैर की महफ़िल में है
सरफ़रोशी की तमन्ना अब हमारे दिल में है

वक्त आने दे बता देंगे तुझे ए आसमान,
हम अभी से क्या बतायें क्या हमारे दिल में है
खैंच कर लायी है सब को कत्ल होने की उम्मीद,
आशिकों का आज जमघट कूच-ए-कातिल में है
सरफ़रोशी की तमन्ना अब हमारे दिल में है

है लिये हथियार दुशमन ताक में बैठा उधर,
और हम तैय्यार हैं सीना लिये अपना इधर.
खून से खेलेंगे होली गर वतन मुश्किल में है,
सरफ़रोशी की तमन्ना अब हमारे दिल में है

हाथ जिन में हो जुनून कटते नही तलवार से,
सर जो उठ जाते हैं वो झुकते नहीं ललकार से.
और भड़केगा जो शोला-सा हमारे दिल में है,
सरफ़रोशी की तमन्ना अब हमारे दिल में है

हम तो घर से निकले ही थे बाँधकर सर पे कफ़न,
जान हथेली पर लिये लो बढ चले हैं ये कदम.
जिन्दगी तो अपनी मेहमान मौत की महफ़िल में है,
सरफ़रोशी की तमन्ना अब हमारे दिल में है

यूँ खड़ा मौकतल में कातिल कह रहा है बार-बार,
क्या तमन्ना-ए-शहादत भी किसि के दिल में है.
दिल में तूफ़ानों कि टोली और नसों में इन्कलाब,
होश दुश्मन के उड़ा देंगे हमें रोको ना आज.
दूर रह पाये जो हमसे दम कहाँ मंज़िल में है,

वो जिस्म भी क्या जिस्म है जिसमें ना हो खून-ए-जुनून
तूफ़ानों से क्या लड़े जो कश्ती-ए-साहिल में है,
सरफ़रोशी की तमन्ना अब हमारे दिल में है
देखना है ज़ोर कितना बाज़ुए कातिल में है

The Poem (Urdu Version)

سرفروشی کی تمنا اب ہمارے دل میں ہے

سرفروشی کی تمنا اب ہمارے دل میں ہے
دیکھنا ہے زور کتنا بازوئے قاتل میں ہے

کرتا نہیں کیوں دوسرا کچھ بات چیت
دیکھتا ھوں میں جسے وہ چپ تیری محفل میں ہے
اے شہید ملک و ملت میں تیرے اوپر نثار
اب تیری ہمت کا چرچہ غیر کی محفل میں ہے
سرفروشی کی تمنا اب ہمارے دل میں ہے

وقت آنے دے بتا دیں گے تجہے اے آسمان
ہم ابھی سے کیا بتائیں کیا ہمارے دل میں ہے
کھینج کر لائی ہے سب کو قتل ہونے کی امید
عاشقوں کا آج جمگھٹ کوچئہ قاتل میں ہے
سرفروشی کی تمنا اب ہمارے دل میں ہے

ہے لئے ہتھیار دشمن تاک میں بیٹھا ادھر
اور ہم تیار ھیں سینہ لئے اپنا ادھر
خون سے کھیلیں گے ہولی گر وطن مشکل میں ہے
سرفروشی کی تمنا اب ہمارے دل میں ہے

ہاتھ جن میں ہو جنون کٹتے نہیں تلوار سے
سر جو اٹھ جاتے ہیں وہ جھکتے نہیں للکا ر سے
اور بھڑکے گا جو شعلہ سا ہمارے دل میں ہے
سرفروشی کی تمنا اب ہمارے دل میں ہے

ہم جو گھر سے نکلے ہی تھے باندہ کے سر پہ کفن
جان ہتھیلی پر لئے لو، لے چلے ہیں یہ قدم
زندگی تو اپنی مہمان موت کی محفل میں ہے
سرفروشی کی تمنا اب ہمارے دل میں ہے

یوں کھڑا مقتل میں قاتل کہہ رہا ہے بار بار
کیا تمناِ شہادت بھی کِسی کے دِل میں ہے
دل میں طوفانوں کی تولی اور نسوں میں انقلاب
ھوش دشمن کے اڑا دیں گے ھمیں روکو نہ آج
دور رہ پائے جو ہم سے دم کہاں منزل میں ہے

وہ جِسم بھی کیا جِسم ہے جس میں نہ ہو خونِ جنون
طوفانوں سے کیا لڑے جو کشتیِ ساحل میں ہے

سرفروشی کی تمنا اب ہمارے دل میں ہے
دیکھنا ہے زور کتنا بازوئے قاتل میں ہے

The Urdu Script was used as a base from here and then modified and amended.

English Translation

The desire for struggle is in our hearts
We shall now see what strength there is in the boughs of the enemy

Why do you remain silent thus?
Whoever I see, is gathered quiet so...
O martyr of country, of nation, I submit myself to thee
For yet even the enemy speaks of thy courage
The desire for struggle is in our hearts...

When the time comes, we shall show thee, O heaven
For why should we tell thee now, what lurks in our hearts?
We have been dragged to service, by the hope of blood, of vengeance
Yea, by our love for nation divine, we go to the streets of the enemy
The desire for struggle is in our hearts...

Armed does the enemy sit, ready to open fire
Ready too are we, our bosoms thrust out to him
With blood we shall play Holi , if our nation need us
The desire for struggle is in our hearts...

No sword can sever hands that have the heat of battle within,
No threat can bow heads that have risen so...
Yea, for in our insides has risen a flame,
and the desire for struggle is in our hearts...

Set we out from our homes, our heads shrouded with cloth,
Taking our lives in our hands, do we march so...
In our assembly of death, life is now but a guest
The desire for struggle is in our hearts...

Stands the enemy in the gallows thus, asking,
Does anyone wish to bear testimony?...
With a host of storms in our heart, and with revolution in our breath,
We shall knock the enemy cold, and no one shall stop us...

What is that body that does not have hot blood in it,
How can a person conquer a Typhoon while sitting in a boat near the shore.

The desire for struggle is in our hearts,
We shall now see what strength there is in the boughs of the enemy.

Introduction to service-oriented architecture: What is SOA?

Service-oriented architecture is a technical concept – but non-technical readers can benefit by understanding the basic, underlying concepts. This overview of service-oriented architecture is appropriate for both business and technical staff. The following is an excerpt from SOA for the business developer: Concepts, BPEL, and SCA, by Ben Margolis; copyright 2007. It is reprinted here with permission from MC Press. Still want to learn more? Read the full chapter, "Introduction to service-oriented architecture: What is SOA?"

Service-oriented architecture (SOA) is a way of organizing software so that companies can respond quickly to the changing requirements of the marketplace. The technology is based on services, which are customized units of software that run in a network.

A service:

• handles a business process such as calculating an insurance quote or distributing email, or handles a relatively technical task such as accessing a database, or provides business data and the technical details needed to construct a graphical interface
• can access another service and, with the appropriate runtime technology, can access a traditional program and respond to different kinds of requesters — for example, to Web applications
• is relatively independent of other software so that changes to a requester require few or no changes to the service, while changes to the internal logic of a service require few or no changes to the requester

The relative independence of the service and other software is called loose coupling. The flexibility offered by loose coupling protects your company from excessive costs when business or technical requirements change.

A service can handle interactions within your company, as well as between your company and its suppliers, partners, and customers. The location of service requesters can extend worldwide, depending on security issues and on the runtime software used to access a particular service.

In most cases, the requesting code has no details on the service location. Like the requester, the service can be almost anywhere. The location is set when the network is configured, and changes to the location are sometimes possible at network run time.

SOA implies a style of development, with concern for the business as a whole and with an increased focus on modularity and reuse. SOA isn't only for new code, though. Migration of existing applications is especially appropriate in the following cases:

• The applications are monolithic, combining the logic of user interface, business processing, and data access, with update of one kind of logic requiring your company to test multiple kinds of behavior.
• The applications are hard to understand — first, because the logic is monolithic, but second, because logic was repeatedly patched rather than rewritten as requirements changed. Updates take extra time as developers try to decipher the logic, and as the complexity grows, additional errors accompany updates.
• The application inventory has duplicate logic. Requests for change are unnecessarily disruptive, requiring changes in several places.

From the point of view of a business developer, a change to SOA is a change in emphasis, and many aspects of the job are unaffected. Consider the task of function invocation, for example. When you invoke a function, you aren't concerned with the internal logic of the invoked code or with how the function receives arguments or returns a value. Similarly, when you code a service request, you care only about the syntax for requesting the service. At best, service requests are as easy as function invocations.

Service-oriented architecture and open standards

In many industries, companies adhere to standards that allow for greater prosperity than would be possible if each company followed its own proprietary rules. Standards in housing construction, for example, ensure that manufacturers of pipes can benefit from economies of scale in pursuit of a larger market than would be available in the absence of industry-wide standards.

The primary benefit of SOA standards is that they make services interoperable, which means that services can communicate with one another, even if each implementation is written in a different computer language or is accessed by way of a different transport protocol (software that oversees the runtime transmission of data).

Standards also ensure that an SOA runtime product can support Quality of Service features, as described in Chapter 2.

SOA standards are open in the sense that any software manufacturer has the right to use those standards when developing an SOA-related product. In addition, the process of creating and revising the standards is based on a political process that is more or less democratic. Any interested party has the right to participate in all meetings that lead to decisions about a standard.

Each company that works on an open standard seeks a text that matches the company's marketplace strengths. The competition among those companies is one reason for the long delay in making a standard final.

Several major organizations oversee development of open standards for SOA:

• Open Grid Forum
• Organization for the Advancement of Structured Information Standards (OASIS)
• Web Services Interoperability Organization (WS-I)
• World Wide Web Consortium (W3C)

Later chapters give you practical insight into standards that are in effect or under consideration, and Appendix A describes several others.

Open standards are distinct from open source, which is source code that you can learn from and use in your own projects, with certain legal restrictions. Opensource implementations of Service Component Architecture (SCA) and Service Data Objects (SDO), for example, are being developed in the Tuscany incubator project of the Apache Software Foundation. For details and code, see the following Web sites: http://incubator.apache.org/tuscany and http://www.apache.org.

Structure of a service-oriented application

A service-oriented application is an application composed largely of services. Often, the invoked services are in a hierarchy, as Figure 1.1 illustrates.

The topmost level contains one or more integration services, each of which controls a flow of activities such as processing an applicant's request for insurance coverage. Each integration service invokes one or more business services.

The second level is composed of services that each fulfill a relatively low-level business task. For example, an integration service might invoke such business services to verify the details provided by an insurance-policy applicant. If the business services return values that are judged to mean "issue a policy," the integration service invokes yet another business service, which calculates a quote and returns the quote to the software (for example, a Web application) that invoked the service-oriented application.

The third level consists of data-access services, each of which handles the relatively technical task of reading from and writing to data-storage areas such as databases and message queues. A data-access service is most often invoked from the business layer.

Great complexity is possible. Some integration services, for example, provide different operations to different requesters, and some invoke other integration services and are said to be composed of those services. Many applications, however, fulfill the three-level model described here.

Data as a Service

>

QUESTION POSED ON: 24 July 2007 What is data-as-a-service? What are the benefits of data-as-a-service?

>

EXPERT RESPONSE The concept of data-as-a-service (DaaS) basically advocates the view that -- with the emergence of service-oriented architecture (SOA), which includes standardized processes for accessing data "where it lives" -- the actual platform on which the data resides doesn't matter. With data-as-a-service, any business process can access data wherever it resides. Data-as-a-service began with the notion that data quality could happen in a centralized place, cleansing and enriching data and offering it to different systems, applications or users, irrespective of where they were in the organization or on the network. This has now been replaced with master data management (MDM) and customer data integration (CDI) solutions, accompanying a master data "hub" on which the golden record of the customer (or product, or asset, etc.) resides, and is available as a service (e.g., "Get Customer") to any application that has the services to access it. Many people hear data-as-a-service and think "outsourcing." While outsourced data is possible, we don't recommend it. We think companies should manage and own their own data assets--again, the platform matters less and can thus be outsourced if the business processes and data are solid. We see architecture groups enabling de-facto master data hubs and offering them as a service to ensure the sanctioned "single version of the truth" is available to everyone.

Responsibilities of the information architect

Acknowledgment : http://searchdatamanagement.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid91_gci1267010_tax302190,00.html?track=NL-520&ad=600164&asrc=EM_USC_1978746&uid=5505931

QUESTION POSED ON: 03 August 2007
What are the typical responsibilities of an information architect? The aim is to have the information architect form part of the business intelligence team, and that this person will also have insights to our IT strategy.

>
EXPERT RESPONSE
Historically, information architects were responsible for the design and usability of Web sites and other software applications. More recently, we are beginning to think of information architects as the coordinators of information flow through the enterprise. This view encompasses much more than the user experience of a particular application. This information architect is responsible for modeling all applications across the enterprise and the logical data flows between them. In this sense, the information architect is an integral part of the business intelligence (BI) team, but their focus includes more than the BI and data warehouse components alone. I agree that this person should have insight into the IT strategy. In fact, the information architect should be partly, if not entirely, responsible for it. Information architecture, these days, spans disciplines of data warehousing, business intelligence, master data management, enterprise information integration (EII) and others.

I would list the following as the high level responsibilities for the information architect:

1. Responsible for expressing the enterprise vision for the applications and the data flows between them
2. Responsible for modeling and maintaining the enterprise data models
3. Responsible for extending the data models to the application architecture
4. Responsible for coordinating the integration and service-oriented architecture (SOA) between applications