Juan: The way to go about the analysis is to first examine the old system, such as reviewing key documents and observing the workers perform their tasks. Then we can determine which aspects are working well and which should be preserved.
Pedro: We have been through these types of projects before and what always ends up happening is that we do not get the new system we are promised; we get a modified version of the old system.
Juan: Well, I can assure you that will not happen this time. We just want a thorough understanding of what is working well and what isn’t.
Pedro: I would feel much more comfortable if we first started with a list of our requirements. We should spend some time up-front determining exactly what we want the system to do for my department. Then you systems people can come in and determine what portions to salvage if you wish. Just don’t constrain us to the old system.
Required:
a. Obviously these two workers have different views on how the systems analysis phase should be conducted. Comment on whose position you sympathize with the most.
B.What method would you propose they take? Why?
(1000 words)
Most of the time especially when we are in the field of business or even though in our real life, when we are going to carry out such things we should always begin in planning and various arguments pertaining to what we want to achieve. The situation that was stated above was just a mirror to what we usually perform every now and then. Actually, the persons behind this situation John Juan, the professional system analyst and Peter Pedro as a manager of the department was had a conversation or argument of what will be the best method to be used for their new targeted information system. I can say that most successful and unsuccessful projects really rely on the performance, cooperation, ideas, understanding and communication in between the person who is responsible to develop and most especially the user. Moreover, if you're going to bring about real change in an organization you have to have a plan. You need a vision, of course, and you have to engage people and get them excited about the vision. But if you don't have a plan then nothing much will come of it. As the old saying goes, failure to plan is planning to fail.
Fortunately, these two persons above (John Juan and Peter Pedro) have brilliant and good ideas for their new information system. I just remember to what my instructress shared to the class that before making or developing a system it is very important to done with proper communication with your client, you should ask first the client of what would be the features of that system or in other words you should analyze the flow and prepare first of what are those necessary requirements needed in the system. This is very important to remember in order to minimize risk and to maximize your time. Definitely, it was very obvious that the manager of the department had experienced failure so I think he was afraid that it will happen again. Before I will conclude of what will be the feasible method for me, I just want to explain first John Juan (a system analyst) and Peter Pedro’s (as the manager) ideas. John Juan seems to look at first the old system. In relation to this, he will be observing workers performance and examine those pertinent data gathered during their studies and assessment conducted. In this way, we can now identify of which part of that system calls development and what are those things suitable to be preserve for future use. In my point of view, he seems a practical system analyst because he is analyzing first those possible expenditures for their new information system. It is more important for John Juan to look at closely and carefully to the old system of what is the best that could still contributes for improvement. Why should we find for another method if there is an existing system that is possible to be applied and serves as our basis for the new IS? He just wants to make use of the existing resources that is near to them and easy to be studied. Obviously, he is analyzing first the feasible solution for their problem. In the side, Peter Pedro as the manager of the department wants to gather first those important requirements needed for their new information system. Requirements are the crucial things that system professionals must acquire because we all know that most clients are more knowledgeable of what are those possible needs of their system. The manger stands like a Boy Scout for me. Why I say so? Because he is preferably ready and prepare since he is asking for the list of requirements for the new IS. He just wants to assure first those necessary things. Take a look when you are printing documents, it is very important that you will prepare first those things needed for printing such as computer unit, printer, flash disks, ink, papers and others. This is what the manager aims because he believes that most successful projects largely depend on the gathered requirements.
Finally, I came to a conclusion based on my understandings and observation; it is easier for me to maximize my time to make use of the available resources. Therefore, John Juan’s idea that was to look at closely and carefully first the old system because it will serve as the basis for new IS.
Tuesday, June 22, 2010
USEP Life Cycle
In the previous assignment, we are assigned to give at least three systems development process models together with its corresponding stages or phases. Now, we are task to explain or discuss pertaining to the life cycle of our own University, the University of Southeastern Philippines. Life cycle for me is like stages in life. It maybe explained from the time when we are born until we will depart this life. The same with, the organization or University have been established until the time it will last. And for additional information, based on my research, organizational life cycle is the life cycle of an organization from birth level to the termination. There are five level/stages in any organization. (1. Birth, 2. Growth, 3.Maturity, 4. Decline 5. Death). I think that every organization have their own strategies and processes to cope up with those challenges that they may encounter from every now and then. Looking to our own University, like any other things on earth they have different ways to be developed for the sake of their survival. First and for most, before this University established, they have undergo different planning and studies until it will finished and plan again and again for the next arena. The University has undergone different analysis for the betterment of the organization. This may include of how it can be attractive to other people or customer.
Now, the question is how we can know that the developed life cycle meets our needs as a student in the University. Obviously our University has been working well to attain its dreams. They put hand in hand to help and to suffice the needs of students. As we can notice our University has developed different strategies and procedures to address those intellectual, behavioral as well as spiritual needs of students. One we can be proud of are those number of student passers every year from different courses offered by our very own University. And the passers ranking level throughout other schools in the Philippines. It is very obvious that our University has developed and built proper procedures to become a number one and known University globally. We can also observe that our University produced a world class graduates. Many of them are now working on big companies and have their own company. I am very proud because others would ask me, “Where are you studying?, Well, without any hesitation I answer to the in USEP.” And after which they will reply, Oh! Amazing! You are an intelligent student. And so, it is very big evidence that our University offers a helping hand for our success. As a student, the automation processes in our University contribute a very big help and benefits. Let’s take a look on our USEPAT Online registration process. For me, it is a very helpful and it really meets our needs. Students who are interested to register in our University will no longer find difficulties. This can give attraction to students because you can register without any hesitation and is very time consuming. Some students will not just go to school spending almost the whole day for the sake of registration. I think that the University has been working well and implementing different procedures, making pertinent plans in order to address different problems and adapt changes that may happen and most of all to pursue of what was stated in the Vision, Mission, Goals and Objectives of USEP.
Now, the question is how we can know that the developed life cycle meets our needs as a student in the University. Obviously our University has been working well to attain its dreams. They put hand in hand to help and to suffice the needs of students. As we can notice our University has developed different strategies and procedures to address those intellectual, behavioral as well as spiritual needs of students. One we can be proud of are those number of student passers every year from different courses offered by our very own University. And the passers ranking level throughout other schools in the Philippines. It is very obvious that our University has developed and built proper procedures to become a number one and known University globally. We can also observe that our University produced a world class graduates. Many of them are now working on big companies and have their own company. I am very proud because others would ask me, “Where are you studying?, Well, without any hesitation I answer to the in USEP.” And after which they will reply, Oh! Amazing! You are an intelligent student. And so, it is very big evidence that our University offers a helping hand for our success. As a student, the automation processes in our University contribute a very big help and benefits. Let’s take a look on our USEPAT Online registration process. For me, it is a very helpful and it really meets our needs. Students who are interested to register in our University will no longer find difficulties. This can give attraction to students because you can register without any hesitation and is very time consuming. Some students will not just go to school spending almost the whole day for the sake of registration. I think that the University has been working well and implementing different procedures, making pertinent plans in order to address different problems and adapt changes that may happen and most of all to pursue of what was stated in the Vision, Mission, Goals and Objectives of USEP.
System Development Models
On the previous assignments, we have already known on the different characteristics of a good system analyst especially in any design modeling process. In this assignment, we are task to identify and discuss at least three systems development models together with its phases. Since it was already discussed on our system engineering and system analysis and design 1 subject, systems development models for me serves as guiding tools in developing a particular systems. These will be very useful especially in designing process. Through these models, clients were no longer find difficulties in understanding of what is the flow of the system. Similarly, systems development models are very significant especially on the part of system analysts because these will be there tools or instrument on showing and explaining the flow of the system to their clients.
Upon identifying systems development models, I used to choose waterfall, spiral and prototyping model.
Waterfall Model
Waterfall model was the most popular systems development model. As I was remember on my previous software engineering subject, waterfall model done with a sequential manner. It was composed of different phases. As we can see on the picture below, there is an arrow that serves as the flow meaning, it will not go to the next stage or phase unless the first phase was not finish. Actually it was based on the article published in 1970 by Winston W. Royce. Here are the different phases of waterfall model:
1. Requirements specification
Requirements specification is a detailed statement of the accurate results or the customer want to get from a project. Most probable requirements needed to develop in the system will be done in this phase. This phase also can be done on a long study where the developers will be conducting an investigation mainly on the different necessities needed on the system. Moreover, the said studies will also cover the system cost, project schedule and etc. Bluntly speaking, the important purpose of this phase is to find the need and to define the problem that needs to be solved. Finally, this phase will serve as a guideline for the next phase.
2. Design
System design is also known as the overall system architecture. It also serves as a guideline in identifying the hardware and system requirements. Based on our experiences especially in making a system, mostly we should think first what we are going to do and what it should look like before the coding process. Finally, the system design will serve as a guideline for the next phase.
3. Construction (AKA implementation or coding)
Coding can be done after the system designing. This phase mainly covers all the writing, testing, debugging/troubleshooting process and maintaining the source code of computer programs. Finally, this phase will serve as a guideline for the next phase.
4. Integration
After the coding process, integration phase will be the next. This phase mainly focus on the process of linking together the different computing systems and software applications on its physical and its functionality.
5. Testing and debugging (AKA Validation)
Of course, after the coding and integration process, you will now proceed to the testing and debugging of the system. This time, different testing techniques will be done in order to determine the bugs and errors that were committed. Actually this will begin after the coding process.
6. Installation
Once it was already tested, the deployment will be the next phase to be done. This will be the act of putting the program onto a computer system so that it can be executed.
7. Maintenance
We all know that once the system is deployed to the client’s area, definitely this will undergo different changes. It is very necessary to have maintenance in order to address different changes that may happen. Maintenance here are said to be very important because not all the problems come in picture directly but they arise time to time and needs to be solved.
Spiral Model
Spiral Model is said to be the new approach towards software development. As we can observed on the waterfall model it was just only followed on a sequential manner however it does not have equal division on its respective phases. Based on the internet, in order to address on this issue there was a new model called "The Spiral Model" or "Boehm’s Model". Actually, if we take a look on its picture there is an equal division of phases and it contributes risk reduction and also it supports iteration and reflects real-world practices. These are the four phases of spiral model
1. Planning
Planning is very important in every project implementation. In this phase, you will be able to document and fix first the different objectives and specifications in order to prepare and know of what are the necessary techniques and tactics that you are going to do during the project implementation.
2. Risk Analysis
This phase is also important in order to resolve all the possible risks in developing a project. In this phase also all available alternatives that can help in developing a project to become more effective are being studied and those strategies are decided to use.
3. Engineering
In this phase, the actual development of the project is carried out. The output of this phase is passed through all the phases iteratively in order to obtain improvements in the same.
4. Evaluation
As what on the internet said, this phase is similar with the testing stage. After the product development, the developed system will be passed on to the clients in order to get their feedbacks and suggestions. These feedbacks and suggestions are very important in order to identify problems and errors and also to find accurate solutions in resolving potential problems. As what on the internet said, this phase is similar with the testing stage.
Prototyping Model
Last but not the least, prototyping model mainly focus on how to develop a prototype of the system. The client then evaluates the working prototype, and suggests improvements and corrections, which all go into developing the real application. The prototyping model is used when the client is unsure about the exact specification but has a genuine need. Then the software engineers can develop a rough prototype to gain an approval of the customer. If the prototype developed is a working model, the developers may use code fragments of the prototype when developing the final application. When using the Prototyping Model, the developer builds a simplified version of the proposed system and presents it to the customer for consideration as part of the development process. The customer in turn provides feedback to the developer, who goes back to refine the system requirements to incorporate the additional information. Often, the prototype code is thrown away and entirely new programs are developed once requirements are identified. It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems supports this user tendency.
Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.
Reference:
http://www.buzzle.com/editorials/1-5-2005-63768.asp
http://www.mindtools.com/pages/article/newTMC_07.htm
http://en.wikipedia.org/wiki/Waterfall_model
http://searchcio-midmarket.techtarget.com/sDefinition/0,,sid183_gci755441,00.html
Upon identifying systems development models, I used to choose waterfall, spiral and prototyping model.
Waterfall Model
Waterfall model was the most popular systems development model. As I was remember on my previous software engineering subject, waterfall model done with a sequential manner. It was composed of different phases. As we can see on the picture below, there is an arrow that serves as the flow meaning, it will not go to the next stage or phase unless the first phase was not finish. Actually it was based on the article published in 1970 by Winston W. Royce. Here are the different phases of waterfall model:
1. Requirements specification
Requirements specification is a detailed statement of the accurate results or the customer want to get from a project. Most probable requirements needed to develop in the system will be done in this phase. This phase also can be done on a long study where the developers will be conducting an investigation mainly on the different necessities needed on the system. Moreover, the said studies will also cover the system cost, project schedule and etc. Bluntly speaking, the important purpose of this phase is to find the need and to define the problem that needs to be solved. Finally, this phase will serve as a guideline for the next phase.
2. Design
System design is also known as the overall system architecture. It also serves as a guideline in identifying the hardware and system requirements. Based on our experiences especially in making a system, mostly we should think first what we are going to do and what it should look like before the coding process. Finally, the system design will serve as a guideline for the next phase.
3. Construction (AKA implementation or coding)
Coding can be done after the system designing. This phase mainly covers all the writing, testing, debugging/troubleshooting process and maintaining the source code of computer programs. Finally, this phase will serve as a guideline for the next phase.
4. Integration
After the coding process, integration phase will be the next. This phase mainly focus on the process of linking together the different computing systems and software applications on its physical and its functionality.
5. Testing and debugging (AKA Validation)
Of course, after the coding and integration process, you will now proceed to the testing and debugging of the system. This time, different testing techniques will be done in order to determine the bugs and errors that were committed. Actually this will begin after the coding process.
6. Installation
Once it was already tested, the deployment will be the next phase to be done. This will be the act of putting the program onto a computer system so that it can be executed.
7. Maintenance
We all know that once the system is deployed to the client’s area, definitely this will undergo different changes. It is very necessary to have maintenance in order to address different changes that may happen. Maintenance here are said to be very important because not all the problems come in picture directly but they arise time to time and needs to be solved.
Spiral Model
Spiral Model is said to be the new approach towards software development. As we can observed on the waterfall model it was just only followed on a sequential manner however it does not have equal division on its respective phases. Based on the internet, in order to address on this issue there was a new model called "The Spiral Model" or "Boehm’s Model". Actually, if we take a look on its picture there is an equal division of phases and it contributes risk reduction and also it supports iteration and reflects real-world practices. These are the four phases of spiral model
1. Planning
Planning is very important in every project implementation. In this phase, you will be able to document and fix first the different objectives and specifications in order to prepare and know of what are the necessary techniques and tactics that you are going to do during the project implementation.
2. Risk Analysis
This phase is also important in order to resolve all the possible risks in developing a project. In this phase also all available alternatives that can help in developing a project to become more effective are being studied and those strategies are decided to use.
3. Engineering
In this phase, the actual development of the project is carried out. The output of this phase is passed through all the phases iteratively in order to obtain improvements in the same.
4. Evaluation
As what on the internet said, this phase is similar with the testing stage. After the product development, the developed system will be passed on to the clients in order to get their feedbacks and suggestions. These feedbacks and suggestions are very important in order to identify problems and errors and also to find accurate solutions in resolving potential problems. As what on the internet said, this phase is similar with the testing stage.
Prototyping Model
Last but not the least, prototyping model mainly focus on how to develop a prototype of the system. The client then evaluates the working prototype, and suggests improvements and corrections, which all go into developing the real application. The prototyping model is used when the client is unsure about the exact specification but has a genuine need. Then the software engineers can develop a rough prototype to gain an approval of the customer. If the prototype developed is a working model, the developers may use code fragments of the prototype when developing the final application. When using the Prototyping Model, the developer builds a simplified version of the proposed system and presents it to the customer for consideration as part of the development process. The customer in turn provides feedback to the developer, who goes back to refine the system requirements to incorporate the additional information. Often, the prototype code is thrown away and entirely new programs are developed once requirements are identified. It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems supports this user tendency.
Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.
Reference:
http://www.buzzle.com/editorials/1-5-2005-63768.asp
http://www.mindtools.com/pages/article/newTMC_07.htm
http://en.wikipedia.org/wiki/Waterfall_model
http://searchcio-midmarket.techtarget.com/sDefinition/0,,sid183_gci755441,00.html
System Analyst as a Project Manager
As what we did in Assignment 2, we have also interviewed Sir Chris Abella regarding System analyst as a project manager. It was just happened that the question being asked in this assignment was the topic on Chapter 3 which was our report.
System analyst as a project manager is the same with you are a worker at the same time a manager. Your role as a system analyst is to become responsible for the defining, developing, configuring and supporting computer applications. He is also responsible particularly on the flow of the system. He is also a good system designer. A system analyst does not just focus on the interface of the system but the design that makes the clients comfortable in using the system. When time comes, especially during the deployment of the system the client will no longer find difficulties in using with it. System analyst must also a good programmer. It is very necessary that he is oriented with some programming languages. In connection with this, as a system analyst you will be working as a manager in a particular project. His role and function are equally similar to project manager, in which, he will gather systems requirements, make design recommendations, and others. He will also conduct interview, review, research, and collaborate to the various people who will be affected during the project. As a project manager same as a system analyst you are also required to developed some skills. You will develop your communication skills. In this role, he will conduct interview to the managements and end users. He will talk to the developers of how the software should work and operate to match the user experiences.
As a system analyst, you will also undergo some studies like what the project manager did. This time, you will be applying different skills. You will be establishing proper project management. For an instance, in a working place as a system analyst you will also carrying the role of a manager in a project. You will also establish good working relationship towards your employees. You will listen of what your employees’ suggestions comments and reactions. Your company performances will results to the success of your project.
System analyst as a project manager is the same with you are a worker at the same time a manager. Your role as a system analyst is to become responsible for the defining, developing, configuring and supporting computer applications. He is also responsible particularly on the flow of the system. He is also a good system designer. A system analyst does not just focus on the interface of the system but the design that makes the clients comfortable in using the system. When time comes, especially during the deployment of the system the client will no longer find difficulties in using with it. System analyst must also a good programmer. It is very necessary that he is oriented with some programming languages. In connection with this, as a system analyst you will be working as a manager in a particular project. His role and function are equally similar to project manager, in which, he will gather systems requirements, make design recommendations, and others. He will also conduct interview, review, research, and collaborate to the various people who will be affected during the project. As a project manager same as a system analyst you are also required to developed some skills. You will develop your communication skills. In this role, he will conduct interview to the managements and end users. He will talk to the developers of how the software should work and operate to match the user experiences.
As a system analyst, you will also undergo some studies like what the project manager did. This time, you will be applying different skills. You will be establishing proper project management. For an instance, in a working place as a system analyst you will also carrying the role of a manager in a project. You will also establish good working relationship towards your employees. You will listen of what your employees’ suggestions comments and reactions. Your company performances will results to the success of your project.
Effective System Analyst
As for the requirement on our assignment 2 in SAD 1 Summer class, we have visited the Rhine Marketing Corporation. We have interviewed Sir Chris Abella, the MIS head of RMC-CD of the said corporation. During the interview he answered the question clearly and accommodated us well. As for those people who are in doubt, I will give you first the short company profile of Rhine Marketing Corporation. “Rhine Marketing Corporation- Computer Division (RMC-CD) is a leading manufacturer of personal computers, and distributor of a complete line of peripherals and other computer-related services. It was established in February 1992, when Rhine Marketing Corporation's interest has evolved from home appliance business has achieved a good reputation immediately. We not only provide expertise to meet the increasingly sophisticated needs of our clients, but also offer solutions that set new standards for quality performance and value.” Ref. http://www.rhine.com.ph/
In connection with the topic on MIS 2, we asked Sir Abella about what are the skills and characteristics must a system analyst develop in order to be more effective especially in any design modelling process.
To understand better, Sir Abella told us first about what is system analyst. He explained that a system analyst job is responsible for the defining, developing, configuring and supporting computer applications. He is also responsible particularly on the flow of the system. He is also a good system designer. A system analyst does not just focus on the interface of the system but the design that makes the clients comfortable in using the system. When time comes, especially during the deployment of the system the client will no longer find difficulties in using with it. System analyst must also a good programmer. It is very necessary that he is oriented with at least one programming language.
These are the skills and characteristics of a system analyst to become more effective in any design modelling process. A good system analyst must be:
A good system analyst must be responsible. Since he serves as a leader on a particular project, he must be responsible in whatever the clients’ demand. He must be responsible on what are those important things agreed by him and between the client. There are instances that sometimes some system analyst makes a time span on that system which is very crucial especially in the part of the client. So as a system analyst, we should humbly follow of what the client wants.
A good system analyst must be adaptive and observer. It is very important that he is versatile most of the time especially in his working place. He should build good attitude towards his clients and co-workers. We should not deny the fact that every now and then there are a lot of changes that he may encounter either new working place or new co-workers. Furthermore, he must be a keen observer. He will observe of what are those things that he will establish and do especially about hardware on software matter.
A good system analyst must be honest. First and for most, it is very difficult to deal with the system price. As a system analyst, he must be oriented with what are those things that he may consider in dealing with the system cost. He shall not demand excessive price but he should also consider his time and effort. It must be agreed by him as a system analyst and the client.
A good system analyst must also establish good working relationship towards his client and co-workers. It is important that you are good in communication. This will serve as your tool every now and them especially those people behind that project.
A good system analyst must give great effort on his project in order to meet customer’s satisfaction. You should love your job. "Most successful men have not achieved their distinction by having some new talent or opportunity presented to them. They have developed the opportunity that was at hand." –– Bruce Barton
In connection with the topic on MIS 2, we asked Sir Abella about what are the skills and characteristics must a system analyst develop in order to be more effective especially in any design modelling process.
To understand better, Sir Abella told us first about what is system analyst. He explained that a system analyst job is responsible for the defining, developing, configuring and supporting computer applications. He is also responsible particularly on the flow of the system. He is also a good system designer. A system analyst does not just focus on the interface of the system but the design that makes the clients comfortable in using the system. When time comes, especially during the deployment of the system the client will no longer find difficulties in using with it. System analyst must also a good programmer. It is very necessary that he is oriented with at least one programming language.
These are the skills and characteristics of a system analyst to become more effective in any design modelling process. A good system analyst must be:
A good system analyst must be responsible. Since he serves as a leader on a particular project, he must be responsible in whatever the clients’ demand. He must be responsible on what are those important things agreed by him and between the client. There are instances that sometimes some system analyst makes a time span on that system which is very crucial especially in the part of the client. So as a system analyst, we should humbly follow of what the client wants.
A good system analyst must be adaptive and observer. It is very important that he is versatile most of the time especially in his working place. He should build good attitude towards his clients and co-workers. We should not deny the fact that every now and then there are a lot of changes that he may encounter either new working place or new co-workers. Furthermore, he must be a keen observer. He will observe of what are those things that he will establish and do especially about hardware on software matter.
A good system analyst must be honest. First and for most, it is very difficult to deal with the system price. As a system analyst, he must be oriented with what are those things that he may consider in dealing with the system cost. He shall not demand excessive price but he should also consider his time and effort. It must be agreed by him as a system analyst and the client.
A good system analyst must also establish good working relationship towards his client and co-workers. It is important that you are good in communication. This will serve as your tool every now and them especially those people behind that project.
A good system analyst must give great effort on his project in order to meet customer’s satisfaction. You should love your job. "Most successful men have not achieved their distinction by having some new talent or opportunity presented to them. They have developed the opportunity that was at hand." –– Bruce Barton
Characteristics of a Good System Analyst
Wednesday, April 21, 2010 we have discussed about the world of information system analyst. We tackled the whole definition and characteristics of a system analyst. It was discussed first by the group of Dayanan and explained further by the following members and groups. I learned that being an information system analyst is not an easy job. At first, I thought that system analyst job is like a programmer in such way that you will be working with those plenty of codes. System analyst greatly focused on the different programming languages. However as the reporting goes deeper, I used to comprehend that a system analyst was not about programming. It is about on what are the different strategies need to be done or accomplish in order to attain the goals of your company. In connection with this, as a system analyst you will be performing bundles of tasks in order to achieve of what you want in your company in the near future. Based on what I have understood and researched, a good system analyst must posses various skills to effectively carry out the job. Moreover, system analyst is similar with business analyst. As a system analyst you will be doing planning and analyzing critical problems in such a way that you will be planning with an open-minded person, a futuristic one. You will be oriented with what are those processes which involve company’s innovation. You will be upgraded with the new technology. As a system analyst also, you will construct strategic plans on how to adapt the fast approaching changes in technology. Let’s have a short review on the discussion of Amancio (second reporter). During her discussion about the data flow diagram and in connection with this topic, Sir Gamboa told Amancio to draw the data flow diagram of the present Enrollment System in a particular University. As a system analyst we were given a task to do our duty. It was quite obvious that the said Enrollment system of a particular University was done with a long, time-consuming and hassle process. After a moment, we came to a conclusion found a remedy on that issue. We have concluded a short but useful process of Enrollment System. We must always remember that “Time is Gold” so it is more important to maximize our time. My point of view here is that as a system analyst you must be a good problem solver. You can find better solutions in connection with that problem. System analyst is like a scientist. You will be doing relevant step by step process and techniques. You will be using analysis and techniques to address business problems.
A good system analyst must also be knowledgeable in the field of analyzing and designing activity. The output of the project depends on you. A good system analyst is supposed to have in depth knowledge of the system, before taking place to his job assignment. Besides he must also have sound knowledge of technology that will enable him to utilize high technology tools, hardware and software facilities. A good system analyst also must be a good listener and be able to react to what people say. The analyst must be knowledgeable of technology and business. The analyst is not expected to be an expert in business but a decent understanding of the client's world is required. You are not expected to know the details of programming, but a decent general knowledge of concepts and terms is essential. A system analyst can be a perfect doer, perfect system developer, good skills, and better management and there association must be better.
A good system analyst must obtain interpersonal and technical skills in order to deal with deal with those important relationships and the interface with people in an organization. Bear in mind that system analyst must be good in establishing trust, know how to resolve conflict and good in terms of communicating relevant information. You must have an ability to focus on procedures and techniques far operations analysis, systems analysis, and computer science.
System analyst also must be a good project manager. You are not just in an office sitting, looking and letting your members do their assigned area of responsibility but, as a system analyst as the same time a project manager it is your duty to work before your member because you will serve as a project model. If what was the leader did, it was also by the members. Always remember that success of failure of a project depends on skills and performance of a project manager. As a system analyst, you will be building proper project management. It is your responsibility to know how to organize and direct people. It is more important that you will listen to what your members’ opinion. Cooperation and participation of a project leads to success. We all know that a system analyst is said to be a critical job but it is necessary that as a good system analyst you will know how to establish great performance and determination towards your work.
A good system analyst must also be knowledgeable in the field of analyzing and designing activity. The output of the project depends on you. A good system analyst is supposed to have in depth knowledge of the system, before taking place to his job assignment. Besides he must also have sound knowledge of technology that will enable him to utilize high technology tools, hardware and software facilities. A good system analyst also must be a good listener and be able to react to what people say. The analyst must be knowledgeable of technology and business. The analyst is not expected to be an expert in business but a decent understanding of the client's world is required. You are not expected to know the details of programming, but a decent general knowledge of concepts and terms is essential. A system analyst can be a perfect doer, perfect system developer, good skills, and better management and there association must be better.
A good system analyst must obtain interpersonal and technical skills in order to deal with deal with those important relationships and the interface with people in an organization. Bear in mind that system analyst must be good in establishing trust, know how to resolve conflict and good in terms of communicating relevant information. You must have an ability to focus on procedures and techniques far operations analysis, systems analysis, and computer science.
System analyst also must be a good project manager. You are not just in an office sitting, looking and letting your members do their assigned area of responsibility but, as a system analyst as the same time a project manager it is your duty to work before your member because you will serve as a project model. If what was the leader did, it was also by the members. Always remember that success of failure of a project depends on skills and performance of a project manager. As a system analyst, you will be building proper project management. It is your responsibility to know how to organize and direct people. It is more important that you will listen to what your members’ opinion. Cooperation and participation of a project leads to success. We all know that a system analyst is said to be a critical job but it is necessary that as a good system analyst you will know how to establish great performance and determination towards your work.
Subscribe to:
Posts (Atom)