To begin with, the subject SAD is a very broad topic yet its a great help for everybody, especially to CS and IT students. While having me enrolled in this subject I have realize that creating a system is not just like somewhat you can find everything you want else where. Its like finding a water in a dessert.
As we go along with our discussions in SAD it made us realize that in creating or formulating a system is you need more time and effort to finished it successfully. You must also consider many things especially the purpose of why you are doing it. You should have a goal and objective that will at least satisfy you and satisfy yourself as a CS and IT student.
In chapter 1 which tackles about what is a System Analyst is or the world of a System Analyst. Being an analyst is not necessary to be a very good in hard coding, a system must have a critical mind to analyze one dilemma. He/she must love what he/she is doing and know what he/she is doing. He/she should have a communication with the users or personnel. It was been define also here about what is a system and a subsystem. An anlyst should possess some skills and qualities before proudly scream that you are an Analyst.
In chapter 2, to summarize it, it discusses more on the Approaches that an Analyst or certain person to encounter while developing a system. Therefore, in developing a system you just don't do what you like or what the company wants. An analyst should consider some approaches and follow it. So that in the end, the system that he/she is developing would meet the expectations of the organization. Creating a system is not easy, its like also creating a theses.
While in Chapter 3, it talks about an Analyst being a project manager. Here, as a group there would be someone to stand as a leader and would lead the group probably. But being a project manager does n't mean that you have all the power to manipulate the group but you have the given the chance to be the model of the group. Your power also has limitations. Project Management is breaking down the task equally and creating rules to be followed.
In chapter 4 which we have just discussed last Thursday afternoon, talks about the Analysis Phase, fact-finding, or investigating the business you will worked with. Here we have tackled about the activities of the Analysis Phase. It only mean that in Analysis phase, system Analyst should be knowledgeable with the business problem, he/she should be involved his/her self with it. Because to become an expert in the area you are planning to solve, surely would bring you to stardom. Analyzing a system processes is not easy, you need a lot of time executing it. In the end, analyst should meet the business expectations and the needs of the system as well.
Lastly, in chapter 5, we have discussed the second key skills of an Analyst should have. which is modelling or producing a model for the project. Modelling the project is very important, because modelling is a learning process. It will also help you to fully understand, rather easily understand it.
To generalized it, Analyzing and designing a system is not easy, it would take enough time to create one. Time is precious. You need to have at least more and more time to finished it. Validate the reason of doing it and your pupose. Would it be enough for you?.
No comments:
Post a Comment