---SAD1 Assignment # 1---

Based on our learning’s in Chapter 1 report, we are to identify and discuss some of the characteristics we have as a good system analyst.

I never thought how tricky to be a system analyst, until the class discuss about how and what does “System Analyst” means. Yes, its ponder me of aiming all the qualities and requirements of a system analyst, but the question is Am I that capable to become one? This question knocks my mind when dreaming to achieve these necessities of system analyst. Glad that we are given the chance to listen and share some of the aspects of a good system analyst. As they said, a good system analyst is a solution provider and can cope up every little problem running inside and outside of the scope of the system.

As a student facing this futuristic generation, computers is hard to imagine without them. As a result of new technologies, our modern society has been almost deluged by a continual introduction of new products, both in computer hardware systems and software. And these things are created through also the idea and help of professional analyst. System analyst plays a very important role in producing a good, quality product either a plan, software or even hardware. An analyst can be called as a “Computer Scientist” because all of the remarkable and continuing advances in computer technology are credited to the highly trained and skilled system analyst.


“I can be a system analyst someday” a line which repeatedly comes to mind every time I think of inspiring to become one. As what I understand in the report systems analysts are in great demand, get paid well, and work in a thrilling field while enjoying many work place freedoms. The name it self is not very commonly known and the tasks are complicated but intriguing at the same time. The highlights for this job are total freedom, and a respectable salary. Many corporations would not be able to function without the assistance of systems analysts, and yet in many cases employers can't explain what it is they do, or how they do it. When new programs are not needed, a systems analyst may be required to maintain the software they have already created. It can be frustrating, not to mention financially devastating, to have computer or network crash, and no one on hand to fix it! A common cause for system crashes is pilot error, which is also easily avoided with instruction, however; glitches in programs do pop up from time to time. Such a crisis reinforces how important it is to have someone on hand to prevent, and cure problems. This area of problem solving grants him or her freedom, by having the most knowledge in crisis situations.

To be able to meet these requirements I have to set my priorities and identify some of my characteristics as a good analyst.

A system analyst should gather all information’s and a good listener.

I can make designs and implements the information gathered about the system, the first thing to do is to interview the company or any respondents which can help to our system development, this is to find out what kind of information’s do we need and improved. I should find whether the report is feasible or not. Actually, group 1 reported various tools in gathering information’s, but concisely interview is the most common and effective source of gathering information, this is to find and proved all the facts and questions left behind.


A system analyst knows how to analyze both negative and positive side of the possible outputs for the system.


As a student, I believe that I have the ability to analyze the possible different approach of the system, off course in analyzing the system I must find out where are they going to get the information, how, when is the project going to be done, the tools I need, the expense, and other related facts which talks about our project. Since system analyst has a big job to do, I know that am responsible enough to formulate design, the development, and implementation of the report, what purpose will it serve presentation, and many more. I can follow the first analysis of when the project will be finished. Basically a Systems Analyst is responsible for systems projects and from beginning to the end of a project; I can implement the system to good use. The Systems Analyst creates and helps finish the final product, making all the specifications and charts for what is to be done.

A system analyst knows how to formulate diagrams and can provide detailed documents.

They do flowcharting, specifications for the programmers of the report, and development control. They write specifications, of what is to be in the final report. The Systems Analyst then must follow up to make sure the program is running smoothly. A critical flowchart also helps the programmers along. The Systems Analyst helps to makes sure the work is done until the final report is achieved. After the development is finished and a prototype of the report is finished, the Systems Analyst helps the programmers in testing the program for bugs. The critical path also calculates how many man hours it will take to finish, enough time to prepare and many more. A critical path is like a due date, if the report is to be done in thirty days, the Systems Analyst makes sure the report is done in thirty days. Once the final report is finished and free of bugs, it is sent to the user.

These characters should attained every person specially student who aims to be a part of the group of “Professional System Analyst”.