Mood's In Control
In today's modern office, information technology is necessary to conduct business. A systems analyst helps organizations achieve goals by utilizing information technology. Through the use of software and hardware, he may help design new computer systems or figure out ways to fine-tune existing systems. A systems analyst is also known as a computer systems analyst. Computer system analysts are concerned more with the computer system itself - and you'd need experience/training in whatever computer system that particular company is using. This does not mean you could not become a computer systems analyst - as most companies would feel that your managerial experience is more welcome than your computer knowledge. What the company would want is someone who understands the basic workings of their system to be able to fix, create, evolve as the company evolves.
SAMULCO stands for Sta. Ana Multipurpose Cooperative and is the company that we have chosen to have an interview to their systems analyst in regards to this assignment given to us. Samulco is currently run by people of diverse profession in the community, such as doctors, teachers, bankers, businessmen, accountant, policemen, and IT professionals. One of these people is Mr. James Bautista, an IT graduate, and the company’s systems analyst.
We started the interview by asking, “What skills and characteristics must a systems analyst develop in order to be more productive in any design modeling process?” Mr. James Bautista, the Samulco’s Management Information Systems supervisor answered us by defining first what a systems analyst is. According to him, a systems analyst should see the problem alone. Meaning, problem must be seen first before the solution. A systems analyst also needs to analyze and solve problems in an efficient manner so as to achieve results and meet deadlines. He or she should be able to mentally handle having several projects to monitor simultaneously, while possessing the ability to organize, prioritize, and show initiative in attacking the problem at hand. Now, going back to the first question, he gave us four answers. First, is that the systems analyst must be a keen observer. A systems analyst must be keen to detail, must be observant in every single detail. Mr. James added that in any modeling process, if you miss a detail when the development had already started it signifies waste of human resource, time, and money. Second, a systems analyst must have developed basic programming skills. Although an analyst is not a programmer, he/she must have the knowledge about programming even just the basics. I think it is because a systems analyst and the developer/programmer is dependent with each other. The systems analyst looks at the requirements and designs the solution at the systems level. The analyst will often design the external interfaces and functionality of each piece, but will not get down to the implementation or code level since there’s a programmer to do that. The programmer takes the design from the analyst, and implements or codes each component, testing along the way to ensure that the implementation meets the design. This is also a two-way street. Say for example, during the implementation, the programmer may realize there is a need to revise the system design, and will go back to the analyst. The analyst will then integrate the required change/s into the design. Sometimes, these roles overlap. Certainly, if the project is small, the analyst and programmer can be the same person. Next, are the two characteristics that sir James define and differentiate. A systems analyst is a global thinker which means that an analyst should look in the overall of the project and not just the details while a developer is a systematic thinker or a local thinker that all he sees is the piece of codes and solutions to the problem. To further understand the difference between the two, here’s a sample situation: Two men were digging a hole in the ground. Someone stopped and asked what they are doing. First man answered that they are digging a hole in the ground. The second man said that they are building a house. Here, the local thinker is the first man while the global thinker is the second man. Fourth, an analyst should have a good communication skills. Communication skill is important in a systems analyst especially when dealing with clients, said sir James. Communicating with clients and coworkers is a very important step for a systems analysis to success on the job. A systems analyst must be really able to communicate well. Excellent verbal and written communication skills are a must for anyone wishing to pursue a career as a systems analyst. He or she also needs to be able to cooperate and get along with others while thriving in a team-oriented environment. A systems analyst must posses good interpersonal communication skills because they must be able to converse back and forth with the client over what the problem is and how to go about finding the best solution. This is the point where good problem solving skills come into play. In order to find the best possible solution, the systems analyst will have to define the problem and come up with a way to solve it that is most beneficial to everyone.
On that interview, I gained more knowledge about the systems analyst. I learned that an analyst must possess various skills to effectively carry out the job and that systems analysts need to be independent thinkers-people who can “think out of the box” by grasping concepts quickly and seeing the big picture as opposed to the small details. I am lucky having that chance to interview a real systems analyst for the reason that I clarified some queries in my mind regarding about my systems analyst (personal thoughts, own conception) and the real systems analyst. The purpose of this interview is not just to have an answer on this assignment but to help us understand what really a systems analyst is. Thanks to sir James for allowing us to take some of his precious time for us to have an interview with him.
SAMULCO stands for Sta. Ana Multipurpose Cooperative and is the company that we have chosen to have an interview to their systems analyst in regards to this assignment given to us. Samulco is currently run by people of diverse profession in the community, such as doctors, teachers, bankers, businessmen, accountant, policemen, and IT professionals. One of these people is Mr. James Bautista, an IT graduate, and the company’s systems analyst.
We started the interview by asking, “What skills and characteristics must a systems analyst develop in order to be more productive in any design modeling process?” Mr. James Bautista, the Samulco’s Management Information Systems supervisor answered us by defining first what a systems analyst is. According to him, a systems analyst should see the problem alone. Meaning, problem must be seen first before the solution. A systems analyst also needs to analyze and solve problems in an efficient manner so as to achieve results and meet deadlines. He or she should be able to mentally handle having several projects to monitor simultaneously, while possessing the ability to organize, prioritize, and show initiative in attacking the problem at hand. Now, going back to the first question, he gave us four answers. First, is that the systems analyst must be a keen observer. A systems analyst must be keen to detail, must be observant in every single detail. Mr. James added that in any modeling process, if you miss a detail when the development had already started it signifies waste of human resource, time, and money. Second, a systems analyst must have developed basic programming skills. Although an analyst is not a programmer, he/she must have the knowledge about programming even just the basics. I think it is because a systems analyst and the developer/programmer is dependent with each other. The systems analyst looks at the requirements and designs the solution at the systems level. The analyst will often design the external interfaces and functionality of each piece, but will not get down to the implementation or code level since there’s a programmer to do that. The programmer takes the design from the analyst, and implements or codes each component, testing along the way to ensure that the implementation meets the design. This is also a two-way street. Say for example, during the implementation, the programmer may realize there is a need to revise the system design, and will go back to the analyst. The analyst will then integrate the required change/s into the design. Sometimes, these roles overlap. Certainly, if the project is small, the analyst and programmer can be the same person. Next, are the two characteristics that sir James define and differentiate. A systems analyst is a global thinker which means that an analyst should look in the overall of the project and not just the details while a developer is a systematic thinker or a local thinker that all he sees is the piece of codes and solutions to the problem. To further understand the difference between the two, here’s a sample situation: Two men were digging a hole in the ground. Someone stopped and asked what they are doing. First man answered that they are digging a hole in the ground. The second man said that they are building a house. Here, the local thinker is the first man while the global thinker is the second man. Fourth, an analyst should have a good communication skills. Communication skill is important in a systems analyst especially when dealing with clients, said sir James. Communicating with clients and coworkers is a very important step for a systems analysis to success on the job. A systems analyst must be really able to communicate well. Excellent verbal and written communication skills are a must for anyone wishing to pursue a career as a systems analyst. He or she also needs to be able to cooperate and get along with others while thriving in a team-oriented environment. A systems analyst must posses good interpersonal communication skills because they must be able to converse back and forth with the client over what the problem is and how to go about finding the best solution. This is the point where good problem solving skills come into play. In order to find the best possible solution, the systems analyst will have to define the problem and come up with a way to solve it that is most beneficial to everyone.
On that interview, I gained more knowledge about the systems analyst. I learned that an analyst must possess various skills to effectively carry out the job and that systems analysts need to be independent thinkers-people who can “think out of the box” by grasping concepts quickly and seeing the big picture as opposed to the small details. I am lucky having that chance to interview a real systems analyst for the reason that I clarified some queries in my mind regarding about my systems analyst (personal thoughts, own conception) and the real systems analyst. The purpose of this interview is not just to have an answer on this assignment but to help us understand what really a systems analyst is. Thanks to sir James for allowing us to take some of his precious time for us to have an interview with him.
