The question was based on my learning from chapter 1, identify and discuss some characteristics that a good Systems Analyst must have. So for me to start, I will discuss first all the necessary information that you need to know about chapter 1 which is the world of the information systems analyst. So to start, first I will give you all the definitions and etc. so what is a Systems Analyst? A systems analyst is a business professional who uses analysis and design techniques to solve business problems using information technology. So a systems analyst is just basically person that handles all the necessary analysis and design in an organization. System analysis is the process of understanding and specifying in detail what the information system should accomplish. So as a systems analyst, they are the one who do the analysis so basically they need to understand and specify what the organizations information system should accomplish. And in design, as a systems analyst they should also be able to do systems design. Systems design is the process of specifying in detail how the many components of the information system should be physically implemented. So in short, a system analyst also needs to design the information system of an organization to specify in detail the physical aspect of the desired information system. Now let’s go to the characteristics that a good systems analyst have. I have searched some inputs over the web and this is all the inputs I have gathered. The system analyst must be able to communicate in writing and orally. The analyst must easily get along with people. The analyst must be a good listener and be able to react to what people say. The analyst must be knowledgeable of technology. The analyst is not expected to know the intricacies of programming, but a decent general knowledge of concepts and terms is essential. The analyst must be knowledgeable of business. The analyst is not expected to be an expert in business but a decent understanding of the client's world is required. Other sources are as follows, one should be familiar with designing concepts that is appropriate for the particular development environment. This means one who is good at designing commercial buildings isn't necessarily a good person to design residential housing. Although a lot of concepts overlap, one who is good at designing mainframe system isn't necessarily a good candidate for web projects. One should have the skills to use the tools to facilitate his/her work such as design software tools. If someone is struggling to use a hammer s/he is worrying about putting a nail in straight not about building a good structure. One should have the industry/business knowledge or the capacity to acquire them. System implementation is a lot like a bunch of blind people trying to figure out what an elephant looks like. Each person has his/her own field expertise. However, the more knowledge one person has would make the process easier and create better results. Good communication skills without saying are very important. So these are basically all the characteristics that a good system analyst have. So let’s go deeper to that.
A business problem solver – systems analysis and design is, first and foremost, a practical field grounded in time-tested and rapidly evolving knowledge and techniques. Analysts must certainly know about computers and computer programs. They should possess the special skills and develop expertise in programming. But they must also bring to the job a fundamental curiosity to explore how things are done and the determination to make them work better. Developing information systems is not just about writing programs. Information systems are developed to solve problems for organization, and a systems analyst is often thought of as a problem solver rather than a programmer. How does an analyst solve problems? System analysis and design focuses on understanding the business problem and outlining the approach to be taken to solve it. Now I will discuss to you or show you the systems analyst approach in problem solving. Obviously, part of the solution is a new information system, but that is just part of the story.
· First is research and understand the problem
· Then, verify that the benefits of solving the problem outweigh the costs
· After, define the requirements for solving the problem
· Next, develop a set of possible solutions (alternatives)
· Then, decide which solutions is best and make a recommendation
· Next, define the details of the chosen solutions
· After, implement the solution
· And lastly, monitor to make sure that you obtain the desired results
The analyst must first understand the problem and learn everything possible about it – who is involved, what business processes come into play, and what other systems would be affected by solving the problem. Then the analyst needs to confirm for the management that the benefits of solving the problem outweigh the costs. If solving the problem is feasible, the analyst defines in detail what is required to solve it – what specific objectives must be satisfied, what data need to be stored and used, what processing must be done to the data, and what outputs must be produced. What needs to be done must be defined first. After detailed requirements are defined, the analyst develops a set of possible solutions. Each possible solution (an alternative) needs to be thought through carefully. Usually, an information system alternative is defined as a set of choices about physical components that make up an information system. Many different alternatives must be considered, and the challenge is to select the best – that is, the solution with the fewest risks and more benefits. Alternatives for solving the problem must be cost-effective, but they also must be consistent with the corporate strategic plan. Does the alternative contribute to the basic goals and objectives of the organization? Will it integrate seamlessly with other planned systems? Does it use technology that fits the strategic direction that the management defined? Will end users be receptive to it? Analyst must consider many factors and make tough decisions. After the systems analyst has determined, in consultation with the management, which alternative is to recommend and the management has approved the recommendation, the design details must be worked out. Here the analyst is concerned with creating a blueprint (design specifications) for how the new system will work. Systems design specifications cover databases, user interfaces, networks, operating procedures, conversion plans, and of course, program modules. After the design specifications are complete, the actual construction of the system can begin, including the programming and testing. An information system can cost a lot of money to build and install so detailed plans must be drawn up. It is not unusual for dozens of programmers to work on programs to get a system up and running and those programmers need to know exactly what the system is to accomplish. So this is a characteristic that a good systems analyst must have.
Systems that solve business problems – so let me define first what is a system, a system is a collection of interrelated components that function together to achieve some outcome. An information system is a collection of interrelated components that collect, process, store, and provide as output the information needed to accomplish a business task. What are the interrelated components of an information system? A subsystem is a system that is part of another system, so subsystems might be one way to think about the components of a system. Every system, in turn, is part of a larger system, called a supersystem. Another way is to list the parts that interact. Examples of this include hardware, software, inputs, outputs, data, people, and procedures. This view is also very useful to the analyst. Every system has a boundary between it and its environment. Any inputs or outputs must cross the system boundary. Defining these inputs and outputs are important part of systems analysis and design. In an information system, people are also key components, and these people do some of the system’s work. Another boundary that is important to a systems analyst is the automated boundary which is a part of the system, where work is done by computers. And now I will discuss the types of information systems that a systems analyst must know which the following is:
· Transaction processing system (TPS)
· Management information systems (MIS)
· Decision support and knowledge-based systems (DSS/KBS)
· Enterprise applications
· Communication support systems
· And office support systems
Required skills of the systems analyst - first is the analytical skills, so what is an analytical skill? Analytical skill is the ability to see things as systems, identify, analyze, and solve problems in an optimal way for a specific organization. So from what is stated above, the ability to see things as a system, the ability to identify, the ability to analyze, and the ability to solve problems are the main concerns of a system analyst in the analytical aspect of a systems analyst. So a system analyst must develop these types of skills. As we all know that we can have all these skills but a system analyst must really develop in order to be more effective in designing any modeling process. So, enough for the analytical skill and lets go to the next one which is the technical skills.
The second one is the technical skills, so what is a technical skill? Technical skill is the ability to understand how computers, data networks, databases, operating systems, etc. work together, as well as their potentials and limitations. So from what is stated above, the ability to understand how computers, data networks, databases, operating systems, and etc. work together is the main concerns of a system analyst in the technical aspect of a system analyst. So a system analyst must develop these types of skills in order to be more effective in designing any modeling process. I think for me this very important that a system analyst must really develop in order to be more effective.
Technical skills needed by systems analysts include but are not limited to:
1. Computers (PCs, mini, mainframes, etc.)
2. Computer networks (LAN, WAN, VPNs, administration, security, etc.)
3. Operating systems (UNIX, Mac/OS, Windows).
4. Data Exchange Protocols (ftp, http, etc.)
5. Programming languages (C++, Java, XML, etc.)
6. Software applications (Office, project managements, etc.)
7. Information systems (databases, MISs, decision support systems)
8. System development tools and environments (such as report generators, office automation tools, etc.)
The third one is the management skills, so let me define what a management skill is all about. So what is a management skill? Management skill includes organization’s recourse management, project management (people and money), risk management, and change management. So to elaborate more it is just management skills help systems analysts manage projects, resources, risk, and change. So a system analyst must develop these types of skills in order to be more effective in designing any modeling process. They should be able to manage all the things that are needed to be manage in an organization such as resources, be able to properly disseminate all workforce in a project and properly manage it, be able to know the risk that are involve, and be able to anticipate changes in the environment.
Managerial skills needed by systems analysts include but are not limited to:
1. Resource management - effectively managing the project’s resources, including time, equipment, hardware, software, people, money, etc.,
2. Project management - determining the tasks and resources needed for a project and how they are related to each other,
3. Risk management - identifying and minimizing risks,
4. Change management - managing the system’s (organization's) transition from one state to another
The last skill that a system analyst must develop is the communication skill. So let me define what communication skill is all about. So what is communication skill? Communication skill includes effective interpersonal communication (written, verbal, visual, electronic, face-to-face conversations, presentations in front of groups), listening, and group facilitation skills. To elaborate, communication skills are very important to develop in order for the system analyst and clients understand each other. Having good communication with client’s makes things go smoothly and properly. Poor communication leads to mismanagement and even resulting to project failures, and etc.
Communication skills needed by systems analysts include:
1. Clear and effective interpersonal communication, whether written, verbal, or visual, from writing reports to face–to–face conversations, to presentations in front of groups;
2. Listening (accepting opinions and ideas from other project team members),
3. Group facilitation or formal technical reviews (FTR) skills:
· setting an agenda,
· leading discussions,
· involving all parties in the discussion,
· summarizing ideas,
· keeping discussions on the agenda, etc.
The analyst’s role in strategic planning – we have described a systems analyst as someone who solves specific business problems by developing or maintaining information systems. The analyst might also be involved with senior managers on strategic management problems – that is, problems involving the future of the organization and plans and processes to ensure its survival and growth. Therefore, the analyst might be asked to participate in a study that carefully examines existing business processes and procedures and then to propose information system solutions that can have a radical impact. Many tools and techniques of analysis and design are used to analyze business processes, redesign them, and the provide computer support to make them work. So basically, the role of a systems analyst in creating a strategic plan is very crucial, so systems analyst must really have the skills in creating a strategic plan.
The analyst as a system developer – we have discussed many roles that a systems analyst can play in an organization, however the main job of an analyst is working on a specific information systems development project. As a preview of what system development involves the systems analyst, systems analysis tasks, systems design tasks, and implementation and support. So these are the requirements that a system development involves.
So to summarize basically to be called a good systems analyst, one must be a problem solver, business problems using information systems technology. Problem solving means looking into the problem in great details, understanding everything and generating several alternatives for solving problem, and then picking up the best solution. And also to be a good systems analyst, you must have the skills needed to be more effective in solving problems such as technical, analytical, managerial, and interpersonal skills. Integrity and ethics behavior are crucial to the success of the analyst. And lastly, become involved in strategic planning.
References:
http://books.google.com.ph
http://answers.yahoo.com/question/index?qid=20080725042042AA2MqMh
http://answers.yahoo.com/question/index?qid=20070731092009AAjzWqQ
Tuesday, December 15, 2009
Subscribe to:
Posts (Atom)