Discuss the role of a systems analyst as a project manager.
A Systems Analyst is responsible for the operating system and associated subsystems. They provide system-level support of multi-user operating systems, hardware and software tools, including installation, configuration, maintenance, and support of these systems. In addition, they also Identify alternatives for optimizing computer resources.
Below are the list of the primary responsibilities of a Systems Analyst:
-Collect information to analyze and evaluate existing or proposed systems.
-Research, plan, install, configure, troubleshoot, maintain and upgrade operating systems.
-Research, plan, install, configure, troubleshoot, maintain and upgrade hardware and software interfaces with the operating system. Analyze and evaluate present or proposed business procedures or problems to define data processing needs.
-Prepare detailed flow charts and diagrams outlining systems capabilities and processes.
-Research and recommend hardware and software development, purchase, and use.
-Troubleshoot and resolve hardware, software, and connectivity problems, including user access and component configuration.
-Select among authorized procedures and seek assistance when guidelines are inadequate, significant deviations are proposed, or when unanticipated problems arise.
-Record and maintain hardware and software inventories, site and/or server licensing, and user access and security.
-Install, configure, and upgrade desktop hardware and peripherals to include; network cards, printers, modems, mice and add-in boards.
-Work as a team member with other technical staff, such as networking to ensure connectivity and compatibility between systems.
-Write and maintain system documentation.
-Conduct technical research on system upgrades to determine feasibility, cost, time required, and compatibility with current system.
-Maintain confidentiality with regard to the information being processed, stored or accessed by the network.
-Document system problems and resolutions for future reference.
As i was reading the aforesaid primary responsibilities of a systems analyst, I had said to myself that indeed a systems analyst should be a percent or a 'part' or had experienced every task such as in documentation team, developing team, quality assurance team, communication team, as a project manager and the likes. Because if he lacks something on those skills there is a possibility that the Systems Analyst won't be effective in doing his job. Here are additional information about a systems analyst. A systems analyst is the person (or persons) who guides through the development of an information system. In performing these tasks the analyst must always match the information system objectives with the goals of the organization.
Role of System Analyst differs from organization to organization. Most common responsibilities of System Analyst are following:
1) System analysis: It includes system's study in order to get facts about business activity. It is about getting information and determining requirements. Here the responsibility includes only requirement determination, not the design of the system.
2) System analysis and design: Here apart from the analysis work, Analyst is also responsible for the designing of the new system/application.
3) Systems analysis, design, and programming: Here Analyst is also required to perform as a programmer, where he actually writes the code to implement the design of the proposed application.
Due to the various responsibilities that a system analyst requires to handle, he has to be multifaceted person with varied skills required at various stages of the life cycle. The technical know-how of the information system development a system analyst should also have the following knowledge. [Just a review]
Business knowledge: As the analyst might have to develop any kind of a business system, he should be familiar with the general functioning of all kind of businesses.
Interpersonal skills: Such skills are required at various stages of development process for interacting with the users and extracting the requirements out of them
Problem solving skills: A system analyst should have enough problem solving skills for defining the alternate solutions to the system and also for the problems occurring at the various stages of the development process.
I have read an article by HM Winning (The Role of Business Analyst), let me quote what she had written into her article regarding being a Business Systems Analyst who has taken various technical roles.
"On the IT side, if a business got the chance to know me they were happy (I was eventually "stolen" from IT by my the client.) Otherwise, they felt that the BA role was there to add another layer of billing to their project and that there would be minimal value. Now that I'm on the business side IT can't shut me out but I am viewed with suspicion....If I didn't have the IT experience I wouldn't have been able to walk into my current role and be as comfortable as I am so quickly. It was my prior role in business that led me to IT because I thought technology had the answers to just about any business question and problem. I think individuals working in the role of BA on both the IT side and business side have a unique opportunity to define and develop the role. We have the unique ability to "step outside and look in". We are not married to any particular technology, theory or methodology. We bring with us both business and technological experience and are open to learning from one another. We need to look within and to understand, as individuals, where we can provide the most value using our unique backgrounds. We need to approach each situation in a neutral fashion. We're the diplomats and the translators and we are in one of the best positions to actively participate in the creation of new and exciting cutting edge solutions. "
- This is how broad a Systems Analyst knowledge should be. Aside from th knowledge, experience also counts!
The role of a Systems Analyst as a Project Manager is to develop requirements, budgets, and schedules for their firm’s information technology projects. They coordinate such projects from development through implementation, working with the organization’s IT workers, as well as clients, vendors, and consultants. These managers are increasingly involved in projects that upgrade the information security of an organization.
Outputs of our interview with Mr James Bautista of SAMULCO regarding this subject
A Systems ANalyst as a Project MAnager is of course the person responsible for managing the project. And he is responsible for accomplishing the project objectives within the constraints of the project. He is responsible for the outcome(success or failure) of the project.
-A Systems Analyst as a Project Manager is responsible for identifying, monitoring, and responding to risk.
**This is very important he said, because the Systems Analyst should be a risk-taker in a smart way. He let us define what is 'risk' for us but he answered his own question he answered that risk is a possibility of a loss. In every move that a Systems Analyst take, there are so many risks involve. HE said that we can never stop a risk from coming but we can prepare on how it will affect us. He emphasized the importance of this characteristic by sharing to us the murphy's law which states that 'If something can go wrong, it will, and it will hit you in the most inappropriate time.' A Systems Analyst knows and understands that murphy's law will exist forever. A good Systems Analyst should be able to identify, analyze and detect the risk that might be involve on his plans. A good Systems Analyst should also be able to take the risk.
He had also shared 4 ways to deal with risks:
Tolerate - these are risks that won't affect you so much.
Terminate
Treat - prepare or aid the risks.
Transfer
-A Systems Analyst as a Project Manager collects metrics data(such as baseline, actual values for costs, schedule, work in progress, and work completed) & reports on project progress and other project specific information to stakeholders. He is also responsible to the project stakeholders for delivering a project’s objectives within scope, schedule, cost, and quality.
**Sir James Bautista always provide this reports specially during the annual general assembly of SAMULCO.
- A Systems Analyst as a Project Manager is involved with the planning, controlling and monitoring, and also managing and directing the assigned project resources to best meet project objectives. He controls and monitors “triple constraints”—project scope, time and cost(quality also)—in managing competing project requirements. He also examines the organizational culture and determine whether project management is recognized as a valid role with accountability and authority for managing the project.
A Systems Analyst is responsible for the operating system and associated subsystems. They provide system-level support of multi-user operating systems, hardware and software tools, including installation, configuration, maintenance, and support of these systems. In addition, they also Identify alternatives for optimizing computer resources.
Below are the list of the primary responsibilities of a Systems Analyst:
-Collect information to analyze and evaluate existing or proposed systems.
-Research, plan, install, configure, troubleshoot, maintain and upgrade operating systems.
-Research, plan, install, configure, troubleshoot, maintain and upgrade hardware and software interfaces with the operating system. Analyze and evaluate present or proposed business procedures or problems to define data processing needs.
-Prepare detailed flow charts and diagrams outlining systems capabilities and processes.
-Research and recommend hardware and software development, purchase, and use.
-Troubleshoot and resolve hardware, software, and connectivity problems, including user access and component configuration.
-Select among authorized procedures and seek assistance when guidelines are inadequate, significant deviations are proposed, or when unanticipated problems arise.
-Record and maintain hardware and software inventories, site and/or server licensing, and user access and security.
-Install, configure, and upgrade desktop hardware and peripherals to include; network cards, printers, modems, mice and add-in boards.
-Work as a team member with other technical staff, such as networking to ensure connectivity and compatibility between systems.
-Write and maintain system documentation.
-Conduct technical research on system upgrades to determine feasibility, cost, time required, and compatibility with current system.
-Maintain confidentiality with regard to the information being processed, stored or accessed by the network.
-Document system problems and resolutions for future reference.
As i was reading the aforesaid primary responsibilities of a systems analyst, I had said to myself that indeed a systems analyst should be a percent or a 'part' or had experienced every task such as in documentation team, developing team, quality assurance team, communication team, as a project manager and the likes. Because if he lacks something on those skills there is a possibility that the Systems Analyst won't be effective in doing his job. Here are additional information about a systems analyst. A systems analyst is the person (or persons) who guides through the development of an information system. In performing these tasks the analyst must always match the information system objectives with the goals of the organization.
Role of System Analyst differs from organization to organization. Most common responsibilities of System Analyst are following:
1) System analysis: It includes system's study in order to get facts about business activity. It is about getting information and determining requirements. Here the responsibility includes only requirement determination, not the design of the system.
2) System analysis and design: Here apart from the analysis work, Analyst is also responsible for the designing of the new system/application.
3) Systems analysis, design, and programming: Here Analyst is also required to perform as a programmer, where he actually writes the code to implement the design of the proposed application.
Due to the various responsibilities that a system analyst requires to handle, he has to be multifaceted person with varied skills required at various stages of the life cycle. The technical know-how of the information system development a system analyst should also have the following knowledge. [Just a review]
Business knowledge: As the analyst might have to develop any kind of a business system, he should be familiar with the general functioning of all kind of businesses.
Interpersonal skills: Such skills are required at various stages of development process for interacting with the users and extracting the requirements out of them
Problem solving skills: A system analyst should have enough problem solving skills for defining the alternate solutions to the system and also for the problems occurring at the various stages of the development process.
I have read an article by HM Winning (The Role of Business Analyst), let me quote what she had written into her article regarding being a Business Systems Analyst who has taken various technical roles.
"On the IT side, if a business got the chance to know me they were happy (I was eventually "stolen" from IT by my the client.) Otherwise, they felt that the BA role was there to add another layer of billing to their project and that there would be minimal value. Now that I'm on the business side IT can't shut me out but I am viewed with suspicion....If I didn't have the IT experience I wouldn't have been able to walk into my current role and be as comfortable as I am so quickly. It was my prior role in business that led me to IT because I thought technology had the answers to just about any business question and problem. I think individuals working in the role of BA on both the IT side and business side have a unique opportunity to define and develop the role. We have the unique ability to "step outside and look in". We are not married to any particular technology, theory or methodology. We bring with us both business and technological experience and are open to learning from one another. We need to look within and to understand, as individuals, where we can provide the most value using our unique backgrounds. We need to approach each situation in a neutral fashion. We're the diplomats and the translators and we are in one of the best positions to actively participate in the creation of new and exciting cutting edge solutions. "
- This is how broad a Systems Analyst knowledge should be. Aside from th knowledge, experience also counts!
The role of a Systems Analyst as a Project Manager is to develop requirements, budgets, and schedules for their firm’s information technology projects. They coordinate such projects from development through implementation, working with the organization’s IT workers, as well as clients, vendors, and consultants. These managers are increasingly involved in projects that upgrade the information security of an organization.
Outputs of our interview with Mr James Bautista of SAMULCO regarding this subject
A Systems ANalyst as a Project MAnager is of course the person responsible for managing the project. And he is responsible for accomplishing the project objectives within the constraints of the project. He is responsible for the outcome(success or failure) of the project.
-A Systems Analyst as a Project Manager is responsible for identifying, monitoring, and responding to risk.
**This is very important he said, because the Systems Analyst should be a risk-taker in a smart way. He let us define what is 'risk' for us but he answered his own question he answered that risk is a possibility of a loss. In every move that a Systems Analyst take, there are so many risks involve. HE said that we can never stop a risk from coming but we can prepare on how it will affect us. He emphasized the importance of this characteristic by sharing to us the murphy's law which states that 'If something can go wrong, it will, and it will hit you in the most inappropriate time.' A Systems Analyst knows and understands that murphy's law will exist forever. A good Systems Analyst should be able to identify, analyze and detect the risk that might be involve on his plans. A good Systems Analyst should also be able to take the risk.
He had also shared 4 ways to deal with risks:Tolerate - these are risks that won't affect you so much.
Terminate
Treat - prepare or aid the risks.
Transfer
-A Systems Analyst as a Project Manager collects metrics data(such as baseline, actual values for costs, schedule, work in progress, and work completed) & reports on project progress and other project specific information to stakeholders. He is also responsible to the project stakeholders for delivering a project’s objectives within scope, schedule, cost, and quality.
**Sir James Bautista always provide this reports specially during the annual general assembly of SAMULCO.
- A Systems Analyst as a Project Manager is involved with the planning, controlling and monitoring, and also managing and directing the assigned project resources to best meet project objectives. He controls and monitors “triple constraints”—project scope, time and cost(quality also)—in managing competing project requirements. He also examines the organizational culture and determine whether project management is recognized as a valid role with accountability and authority for managing the project.
References:
http://it.toolbox.com/blogs/business-analyst/the-role-of-business-analyst-3357
http://leadershipchamps.wordpress.com/2008/02/29/roles-and-responsibilities-of-a-project-manager/
http://www.freetutes.com/systemanalysis/role-of-system-analyst.html
http://wiki.answers.com/Q/What_is_a_System_Analyst_an_its_responsibilities
Evidences shall follow... I dont have the copy of the pictures yet.
No comments:
Post a Comment