Meaning of Strength

Business is based on two major part Name and Strength

Name means your company reputation in the market, and Strength is your work capability it is nothing but your personnel. If you are HR then what will be point of view from your side absolutely it should be Strength, then how much you are worry about Strength?, what are you looking for it?.

Strength is built up with your personnel property with your company. Dose you know how you evaluate your personnel strength? In simple term we can described as below

1. your company/organization work for
2. company/organization production capability
3. how much skilled work you need
4. how much support you need
5. where is dependance of your work
6. and what you have with your personal

is that simple to understand, let me explain with an example, if you are a manufacturing company which produce a scooter then as per above

1. company work for Scooter
2. company will have machinery which produces 100 scooter in month with available raw material
3. company need 5 technical engineer, 10 helper, 1 manager for done this job
4. company need 2 sweeper, 2 cleaner, and 4 watchman as support
5. company is depend upon constant supply of work
6. then actual personnel in hand

with the expectation and exact situation in hand will be able to calculate the Strength of your personnel.

My discussion point is that does even if we have little strength in hand does our work will not successes or in simple work do we not received target if don't have sufficient Strength?

Yes we do, if you don't have over confidence but have confidence then you can do anything.

Even you have lot of automated machinery along with your plant, you will failure due to lac of good personnel management, because even this situation you will need list a person who can take care of you atomization and if this person is not get well treated then your lost is lot than normal system.

My discussion point is that how important is human being for success of any business and tackle to him is skill of Personnel Management.


I will continue with this discussion how ever I need some best suggestion from your side to make accurate this article.

I does schedule to complete this article before end of May I will post new thoughts I as I wrote in my blog so please keep reading...

HR tactics

The word of recession create afraid in personnel mind, though we consider that any of your staff is strong and have faith and trust on the organization and will feel always comfortable with his job then we are wrong when we says there is recession in these days.

The main reason is that personnel is human being and live with society, if he/she saw or even hear that his colleague or any relative goes through financial problem and have no job just because of recession, might be he loose his temptation in his day to day job, personnel work with the scare “what could be possibility?”.

More and more reason are observed by me that "employee" are looking at management, observe the progress of company and watching the face of management,

if you are working somewhere and some time if you are saying “we are stable in recession period” was just enough, however if you are repeatedly speak such sentence what will be in background? this cycle of thinking get started automatically in human being.

Why our management give a trust about stability? Does every thing is fine or not? Or really we are secured or not?

My article is based on why don’t we behave normal if or even there is nothing to be worried about.

The human resource tactics is not tact; it is an act for tackle situation, I want to explain that we have situation [recession] and we have personnel to manage then where to we look first. As per the personnel management prospect we should look in to personnel first.

I does schedule to complete this article before end of May I will post new thoughts I as I wrote in my blog so please keep reading...

Profiles

Hi Every one this is exciting news that IBM given place for developer where we can share ideas and learn technology with experts and from IBM here is my public profile for IBM Developer Center : - Profiles

Posted using IBM Developer Profile

This is my new comment

Comment

Fund.com sold for $10 Million

This summary is not available. Please click here to view the post.

Debugging tips

Answering questions on the newsgroups, I've noticed that several developers seem to find debugging very difficult - not the mechanics of it, so much as knowing the right place to start. This is not to say that they are lazy or stupid - just that debugging is an art unto itself (arguably more so than writing code in the first place - it certainly involves more intuition in my view), and that a few pointers could be useful.


Making use of the techniques discussed on this page won't make you an ace bug-finder in itself - a mixture of patience, experience, intuition and good practice is needed - but my hope is that it can get you started along the right path. Note that although the page title is "Debugging", a lot of the time you may well not need to step through your code in a debugger in order to fix your code. If I'm trying to find a problem in my own code, without external dependencies such as other whole systems being involved, I usually regard it as a failure on my part if I need to use the debugger. It indicates that my code isn't clear enough and my unit tests aren't robust enough.

Test Case Design

Test Case ID: It is unique number given to test case in order to be identified.Test description: The description if test case you are going to test.Revision history: Each test case has to have its revision history in order to know when and by whom it is created or modified.Function to be tested: The name of function to be tested.Environment: It tells in which environment you are testing. Test Setup: Anything you need to set up outside of your application for example printers, network and so on.Test Execution: It is detailed description of every step of execution.Expected Results: The description of what you expect the function to do. Actual Results: pass / failed If pass - What actually happen when you run the test. If failed - put in description of what you've observed.
Test Case Design Techniques:
Black box techniques: Boundary value analysis, Equivalence partitioning. White box testing techniques are Branch Testing, Condition Testing.

Equivalence Partitioning:
Is the process of taking all of the possible test values and planning them into classes (groups). Test cases should be designed to test one value from each group. So that it uses fewest test cases to cover maximum input requirements.

Boundary Value Analysis:This is a selection technique where the test data lie along the boundaries of the input domain.

Branch Testing:
In branch testing, test cases are designed to exercise control flow braches or decision points in a unit.


Characteristics of a Good Test: They are: likely to catch bugs, no redundant , not too simple or too complex. Test case is going to be complex if you have more than one expected results.