Q. Examples?
Courses required?
Options?
Courses required?
Options?
A. Installs, configures and upgrades operating systems and software, using standard business and administrative packages; may modify specific applications for use in operational departments.
Installs, assembles and configures computers, monitors, network infrastructure and peripherals such as printers, scanners and related hardware; pulls cables and rewires or directs the rewiring of cables as required for new installations and office reconfiguration.
Troubleshoots problems with computer systems, including troubleshooting hardware and software, e-mail, network and peripheral equipment problems; makes repairs and corrections where required.
Acts as a technical resource in assisting users to resolve problems with equipment and data; staffs a centralized help desk to facilitate exchange of information and advice; implements solutions or notifies outsource providers as required.
Makes hardware and software acquisition recommendations including helping users assess needs and providing justification for equipment and services.
Assists in instructing City staff in the use of standard business and administrative software, including word processing, spreadsheets and database management; provides instruction or written documentation where required.
Assists with the planning, design, research and acquisition of new or upgraded hardware and software systems; maintains current knowledge of hardware, software and network technology and recommends modifications as necessary; and,
Performs other duties of a similar nature or level.
Installs, assembles and configures computers, monitors, network infrastructure and peripherals such as printers, scanners and related hardware; pulls cables and rewires or directs the rewiring of cables as required for new installations and office reconfiguration.
Troubleshoots problems with computer systems, including troubleshooting hardware and software, e-mail, network and peripheral equipment problems; makes repairs and corrections where required.
Acts as a technical resource in assisting users to resolve problems with equipment and data; staffs a centralized help desk to facilitate exchange of information and advice; implements solutions or notifies outsource providers as required.
Makes hardware and software acquisition recommendations including helping users assess needs and providing justification for equipment and services.
Assists in instructing City staff in the use of standard business and administrative software, including word processing, spreadsheets and database management; provides instruction or written documentation where required.
Assists with the planning, design, research and acquisition of new or upgraded hardware and software systems; maintains current knowledge of hardware, software and network technology and recommends modifications as necessary; and,
Performs other duties of a similar nature or level.
Software project assumption?
Q. We are developing a proposal for IT project about Help desk tracking system. can anyone help me to address the project assumption
A. The assumption section just talks about the environment and conditions of your project. Assumptions help to explain the project for your stakeholders by defining conditions that may change or may not be known yet. You'll mention these assumptions because if these conditions change, or if it is discovered your assumptions are not true, then you would have to submit a new proposal or re-plan the project.
For the assumptions you'll want to
effectively describe the requirements of the project,
state your time, staff and resource needs
discuss the technology you will use to develop your project
ensure effective documentation and work breakdown structure (WBS)
identify scope
talk about steps in place to ensure quality
talk about time - meaning not only development time, but also date for deliverables (be sure to include time for review and approval processes)
Costs and risks
Communication modes for handling the project
Legal assumptions
You will probably want to talk with people who have developed similar projects to get a better idea of some of these items.
Just a simplistic example, let's say in your case, you need to build a tracking system because there are no third party tracking systems available that would work for our specific needs. And then suppose later you learn of a tracking system that works perfectly for your needs that has already been built for help desk tracking. You no longer have to build all the code, but only have to implement the software. Then you would revisit the proposal and make changes as your assumptions were not correct.
Providing all these details is like giving yourself loopholes in case the project will need to change. Since you have described your requirements and given an outline of the resources you'll need to meet your aims, if any of these assumptions of the project change, such as the scope becomes larger than originally described in your assumptions, you can ask for more resources or time.
For the assumptions you'll want to
effectively describe the requirements of the project,
state your time, staff and resource needs
discuss the technology you will use to develop your project
ensure effective documentation and work breakdown structure (WBS)
identify scope
talk about steps in place to ensure quality
talk about time - meaning not only development time, but also date for deliverables (be sure to include time for review and approval processes)
Costs and risks
Communication modes for handling the project
Legal assumptions
You will probably want to talk with people who have developed similar projects to get a better idea of some of these items.
Just a simplistic example, let's say in your case, you need to build a tracking system because there are no third party tracking systems available that would work for our specific needs. And then suppose later you learn of a tracking system that works perfectly for your needs that has already been built for help desk tracking. You no longer have to build all the code, but only have to implement the software. Then you would revisit the proposal and make changes as your assumptions were not correct.
Providing all these details is like giving yourself loopholes in case the project will need to change. Since you have described your requirements and given an outline of the resources you'll need to meet your aims, if any of these assumptions of the project change, such as the scope becomes larger than originally described in your assumptions, you can ask for more resources or time.
what is a system analyst?
Q. i took a career quiz and i got matched up to this. i tried googling it and reading about it but i dont really understand it (im only 14). the parts i did understand sound really interesting, but could someone who works with one or is one give me a "dummy" version of what a system analyst would do in a day? where do they work? what does it pay? everything you know. thanks soo much!
A. Generally speaking, a systems analyst is someone who is familiar with a given software program or group of software programs and provides administration and / or advanced "help desk" type support for it.
For example, many health care / insurance companies use the OAO MC400 health care information management system, which is basically an advanced relational database with a Java-based client program to access the data.
A systems analyst would be a person who can follow the technical documentation provided with that program, make sure certain features were working, provide troubleshooting for the program when things aren't working quite right, help management get reports from the system, and provide day-to-day management of the program.
You wouldn't expect a systems analyst to tell people how to log in, resolve login problems users were having, install the software on users' computers, etc. -- that's a help desk technician's area.
You also wouldn't expect a systems analyst to solve advanced issues with the software, such as fixing broken stored procedures, getting malfunctioning servers to work, etc.
In short, a systems analyst is the middle step between a help desk tech and a programmer / database administrator.
For example, many health care / insurance companies use the OAO MC400 health care information management system, which is basically an advanced relational database with a Java-based client program to access the data.
A systems analyst would be a person who can follow the technical documentation provided with that program, make sure certain features were working, provide troubleshooting for the program when things aren't working quite right, help management get reports from the system, and provide day-to-day management of the program.
You wouldn't expect a systems analyst to tell people how to log in, resolve login problems users were having, install the software on users' computers, etc. -- that's a help desk technician's area.
You also wouldn't expect a systems analyst to solve advanced issues with the software, such as fixing broken stored procedures, getting malfunctioning servers to work, etc.
In short, a systems analyst is the middle step between a help desk tech and a programmer / database administrator.
Powered by Yahoo! Answers
No comments:
Post a Comment