I
would like to tackle a few questions regarding Systems Analysis, certain
systems, design processes, interviews and answer it with my own opinions. The
first question asks about the technicality of a system analyst or how technical
a system analyst must be. Being technical usually involves one being adept or knowledgeable
at a specific subject, choosing practical methods over idealistic ones and use
of practical tools. For me a system analyst can be both technical and not. It
means that a system analyst should be technical but only to some extent but not
limited to.
A system analyst has a unique blend of technical knowledge and
other skills for it to become effective. Yes, they should be technical and
possess technical knowledge but heavy technical jobs should be handled by
programmers who are required to be technical throughout. The next question is about
how a system analyst is different from the I.T. crowd and how different skills
sets are required and what skills fit in both. The first common ground I can
think of between I.T. roles and a system analyst is their technical knowledge and
understanding of the digital world. Even as the I.T. role has a deeper
knowledge about technical issues a system analyst would not fall far behind. A
big difference between the I.T. role and System Analysis is the fact that I.T.
personnel interact directly to the system analyst while the system analyst
connects to different people; from users, to designers and even the decision
making higher ups. In short system analysts possess interpersonal people
skills, management skills, analytical skills and technical know-how. System analysts
are not only good behind a keyboard for they are the people who connect
different pieces of the organization to from a working system. Now to a
different topic; a topic regarding roles and pyramids. In a large organization
different roles are required and they are filled with people with the right
skill sets.
 |
| The organizational Pyramid |
These people depend on one another to keep things running smooth
and well organized. An organizational pyramid is a guide to help understand the
roles and the people that deal with them. Basically starting from the bottom
going to the top different systems are required for they have specific needs
and tasks to accomplish. A quick example would be the bottom level; they handle
the day-to-day transactions and then record them and send it to someone higher
for them to process. They would require a system that would allow them to
accomplish this while being able to record and send it to the higher ups for
processing. They all belong in different levels each with a different task and
requirements and to fully accomplish their goals they require specific and
goal-oriented system for them to operate at maximum capability. Now we move on
to another question, this time regarding methodologies, documenting and
designing software. First we need to consider 2 methodologies that are widely
used, namely the Waterfall model then the Agile model. First method we are
going to discuss is the Waterfall method, based on the name given to it one can
easily assume it involves a process where it follows a stream going down or
flows from a start point and an end point, the Waterfall method is a sequential
design method. It is a simple and easily understandable.
In the Waterfall
method one must complete the step before moving into the next one for
completion of the step is a prerequisite for the next. It is a well-planned and
rigid process. The Agile model is a flexible and people-oriented process. It is
a process where freeform software design occurs. Developers work on small parts
at a time while customer/client feedback happens simultaneously with development.
As its name suggests it is agile, meaning quick to respond to a change in
requirements or a shift in course. Now that we have the understanding of the
two models we can compare them. The Waterfall model is best used when there is
little chance of change in the customers’ requirements because if the customer
does not require something new the Waterfall model could produce software quite
quickly. Being a rigid model predictions which are fairly accurate is possible.
One can estimate time, costs and other things. Another good thing about the
Waterfall model is the fact that it is very secure since it requires a good
amount of planning. Now the Agile model, since the agile model is very
responsive it could adapt to any changes required by the customer regardless of
step. Agile model is best used when the customer/client has not yet fully
stated its needs and goals. The main
problem with the Agile model is its requirement for constant communication. If the included members are not communicating
properly it could make the task a lot more difficult. Now let us discuss the
cons of the Waterfall model. Being a rigid model one could not easily alter a
stage once it was completed because it would cause problems. Another problem is
that user feedback is withdrawn till the end which will cause a problem if the
customer/client requested something new which would make it difficult to adapt.
Now which model is best? I would say either as long as used for best scenarios,
like if a client has a plan already I would use Waterfall if not then Agile.
Now the last question asks about one of the required skills of a system
analyst. Being a good interviewer is required because you can get specific info
from the client themselves for your design. A great interview happens when both
parties get what they want. If an interviewee properly gets their thoughts and
complains across the table properly and the interviewers getting all the info
to start their task with ease then that would be a great interview. A good interviewer usually addresses the right
questions and follows the basic steps. One can become a good interviewer
through practice.
sources:
No comments:
Post a Comment