Interview a Systems Analyst and ask what skills and characteristics must a systems analyst develop in order to be more effective in any design modeling process.
On Venus Millena's ___th birthday --- December 16,2009 --- some of my classmates and I went to SAMULCO and heard the SAMULCO's MIS Supervisor --Sir James Bautista -- point of view regarding the skills and characteristics a Systems Analyst should develop in order to be more effective in any design modeling process. He first had his sort of a review regarding the question "What skills and characteristics must a systems analyst develop in order to be more effective in any design modeling process?".
After 5 minutes of review, the beautiful and knowledge filled discussion had started. He first defined that Systems Analysis is a plan for future purposes, scalability purposes and that a Systems Analyst is the one who solves problems or certain issues that an organization has.
Sir James Bautista had then enumerated the skills and characteristics that a systems analyst should develop in order to be more effective in any design modeling process, and these are the following:(These are subjective, it differs from other Systems Analyst)
Flexible - a systems analyst should be flexible to be prepared for the rapid changing technology that we have.
Should have enough knowledge in Systems Integration / Systems Development - if you have the experience of developing system you wil have the idea of how to do it, what to do, what's there, what's not there, what's there to fix, etc. System Analysts should start with something small, he associated the carpenter who starts to build small houses, he said that SA should also start with something small, such as programming small-scales. He also imparted to us his thought that a Systems Analyst should have a 'part' or experience of every task such as in documentation team, developing team, quality assurance team, communication team and the likes. Because if he lacks something on those skills there is a possibility that the Systems Analyst won't be effective in doing his job.
Should have both holistic and systematic approach - a holistic approach looks at the whole picture. The totality of something is much greater than the sum of its component parts and they cannot be understood by the isolated examination of their parts. While a systematic approach is more of a philosophy than a technique. It's the way one approaches problems in life, as opposed to the specific solutions that exist. Given a certain problem, one has many choices as to how to solve it. However, approaching the problem haphazardly, may or may not solve the problem. But, approaching the problem with the analytical approach, one is more likely to find the solution to the problem. How one can approach the problem analytically, or systematically, depends on how one views the problem. This is what is often called Analysis, and is really the same thing as breaking the problem down, sometimes referred to as "Divide and Conquer." By breaking down a problem, one can see the various aspects of the problem, and how they inter-relate, and by isolating the causative factors in the problem, one can find the solution to the problem. A Systematic Approach can be used in many areas, such as, systems analysis, software development, (which are part of the software development life cycle), internet site design, web optimization, hosting, business management and consulting, sales, and training. He emphasized that both approaches or views should be a character of a Systems Analyst.
Should have a skill on Calculating Risks - this is very important he said, because the Systems Analyst should be a risk-taker in a smart way. He let us define what is 'risk' for us but he answered his own question he answered that risk is a possibility of a loss. In every move that a Systems Analyst take, there are so many risks involve. HE said that we can never stop a risk from coming but we can prepare on how it will affect us. He emphasized the importance of this characteristic by sharing to us the murphy's law which states that 'If something can go wrong, it will, and it will hit you in the most inappropriate time.' A Systems Analyst knows and understands that murphy's law will exist forever. A good Systems Analyst should be able to identify, analyze and detect the risk that might be involve on his plans. A good Systems Analyst should also be able to take the risk.
** He had also shared 4 ways to deal with risks:
Tolerate - these are risks that won't affect you so much.
Terminate
Treat - prepare or aid the risks.
Transfer
Should be a people person/ Good Communication Skills -A good systems analyst should be able to communicate to other people.
Should have high Adversity Quotient (A.Q.) - Sir James mentioned that Intelligent Quotient and Emotional Quotient will never be used in Systems Planning, because the Adversity Quotient is what matters. Adversity Quotient test the unconscious pattern of how people respond to adversity/problems, and show how to increase it and, thereby, help individuals become valuable at work.
These skills can not be easily learned or acquired in a one sitting, it is built through experience. Therefore, systems analyst are not born they are made.
On Venus Millena's ___th birthday --- December 16,2009 --- some of my classmates and I went to SAMULCO and heard the SAMULCO's MIS Supervisor --Sir James Bautista -- point of view regarding the skills and characteristics a Systems Analyst should develop in order to be more effective in any design modeling process. He first had his sort of a review regarding the question "What skills and characteristics must a systems analyst develop in order to be more effective in any design modeling process?".
After 5 minutes of review, the beautiful and knowledge filled discussion had started. He first defined that Systems Analysis is a plan for future purposes, scalability purposes and that a Systems Analyst is the one who solves problems or certain issues that an organization has.
Sir James Bautista had then enumerated the skills and characteristics that a systems analyst should develop in order to be more effective in any design modeling process, and these are the following:(These are subjective, it differs from other Systems Analyst)
Flexible - a systems analyst should be flexible to be prepared for the rapid changing technology that we have. Should have enough knowledge in Systems Integration / Systems Development - if you have the experience of developing system you wil have the idea of how to do it, what to do, what's there, what's not there, what's there to fix, etc. System Analysts should start with something small, he associated the carpenter who starts to build small houses, he said that SA should also start with something small, such as programming small-scales. He also imparted to us his thought that a Systems Analyst should have a 'part' or experience of every task such as in documentation team, developing team, quality assurance team, communication team and the likes. Because if he lacks something on those skills there is a possibility that the Systems Analyst won't be effective in doing his job. Should have both holistic and systematic approach - a holistic approach looks at the whole picture. The totality of something is much greater than the sum of its component parts and they cannot be understood by the isolated examination of their parts. While a systematic approach is more of a philosophy than a technique. It's the way one approaches problems in life, as opposed to the specific solutions that exist. Given a certain problem, one has many choices as to how to solve it. However, approaching the problem haphazardly, may or may not solve the problem. But, approaching the problem with the analytical approach, one is more likely to find the solution to the problem. How one can approach the problem analytically, or systematically, depends on how one views the problem. This is what is often called Analysis, and is really the same thing as breaking the problem down, sometimes referred to as "Divide and Conquer." By breaking down a problem, one can see the various aspects of the problem, and how they inter-relate, and by isolating the causative factors in the problem, one can find the solution to the problem. A Systematic Approach can be used in many areas, such as, systems analysis, software development, (which are part of the software development life cycle), internet site design, web optimization, hosting, business management and consulting, sales, and training. He emphasized that both approaches or views should be a character of a Systems Analyst. Should have a skill on Calculating Risks - this is very important he said, because the Systems Analyst should be a risk-taker in a smart way. He let us define what is 'risk' for us but he answered his own question he answered that risk is a possibility of a loss. In every move that a Systems Analyst take, there are so many risks involve. HE said that we can never stop a risk from coming but we can prepare on how it will affect us. He emphasized the importance of this characteristic by sharing to us the murphy's law which states that 'If something can go wrong, it will, and it will hit you in the most inappropriate time.' A Systems Analyst knows and understands that murphy's law will exist forever. A good Systems Analyst should be able to identify, analyze and detect the risk that might be involve on his plans. A good Systems Analyst should also be able to take the risk.** He had also shared 4 ways to deal with risks:
Tolerate - these are risks that won't affect you so much. Terminate Treat - prepare or aid the risks. Transfer Should be a people person/ Good Communication Skills -A good systems analyst should be able to communicate to other people. Should have high Adversity Quotient (A.Q.) - Sir James mentioned that Intelligent Quotient and Emotional Quotient will never be used in Systems Planning, because the Adversity Quotient is what matters. Adversity Quotient test the unconscious pattern of how people respond to adversity/problems, and show how to increase it and, thereby, help individuals become valuable at work.These skills can not be easily learned or acquired in a one sitting, it is built through experience. Therefore, systems analyst are not born they are made.
No comments:
Post a Comment