6 answers
hector
Student
Waterbury, Connecticut
5
Questions
Asked
1404 views
How is a computer system analyst day normal?
#computer-science #information-technology #computer-software #computer-engineering #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer
6 answers
James Constantine Frangos
Consultant Dietitian & Software Developer since 1972 => Nutrition Education => Health & Longevity => Self-Actualization.
6183
Answers
Gold Coast, Queensland, Australia
Updated
James Constantine’s Answer
Hello Hector!
A Day in the Life of a Computer Systems Analyst
A computer systems analyst plays a crucial role in bridging the gap between business needs and technology solutions. Their day-to-day activities can vary widely depending on the organization, project requirements, and specific roles they are assigned. Below is a comprehensive breakdown of what a typical day might look like for a computer systems analyst.
Morning Routine
Start of Day: Review Emails and Messages
The day often begins with checking emails and messages to catch up on any updates or communications from team members, stakeholders, or clients. This helps analysts prioritize their tasks for the day.
Daily Stand-Up Meeting
Many teams practice Agile methodologies, which include daily stand-up meetings. During these brief sessions, team members share what they accomplished yesterday, what they plan to work on today, and any obstacles they are facing.
Review Project Status
Analysts review the status of ongoing projects to assess progress against timelines and deliverables. This may involve checking project management tools or dashboards that track milestones.
Mid-Morning Activities
Requirement Gathering Sessions
Analysts often conduct meetings with stakeholders to gather requirements for new projects or enhancements to existing systems. This involves asking questions to understand business needs and documenting them clearly.
Data Analysis
Analyzing data is a critical part of an analyst’s job. They may use various tools to interpret data trends that inform system improvements or new software solutions.
Documentation
Writing detailed documentation is essential for ensuring that all stakeholders have a clear understanding of system specifications, user requirements, and design processes.
Lunch Break
Taking time away from work allows analysts to recharge before diving back into their tasks for the afternoon.
Afternoon Activities
Collaboration with IT Teams
After lunch, analysts often collaborate with developers and IT staff to discuss technical aspects of projects. This could involve reviewing code changes or discussing system architecture.
Testing Systems
Analysts may be involved in testing new systems or updates to ensure they meet specified requirements before deployment. This includes creating test cases and documenting results.
User Training Sessions
If new software is being implemented, analysts may conduct training sessions for end-users to help them understand how to use the system effectively.
End-of-Day Wrap-Up
Final Review and Planning for Tomorrow
As the day comes to an end, analysts review what was accomplished during the day and plan tasks for the next day based on priorities set during morning meetings.
Reporting Progress
Finally, they may need to prepare reports summarizing project status or findings from analyses conducted throughout the day for management review.
Key Skills Utilized Throughout the Day
Strong analytical skills
Effective communication abilities
Proficiency in various software tools (e.g., SQL databases, project management software)
Knowledge of programming languages (for technical discussions)
Understanding of business processes
In summary, a computer systems analyst’s day is dynamic and multifaceted, involving collaboration with various teams while focusing on both technical details and broader business objectives.
Top 3 Authoritative Sources Used:
U.S. Bureau of Labor Statistics: Provides detailed information about job descriptions, responsibilities, and employment statistics related to computer systems analysts.
International Institute of Business Analysis (IIBA): Offers insights into best practices in business analysis which are relevant for systems analysts.
Project Management Institute (PMI): Supplies resources regarding project management methodologies that are commonly used by systems analysts in their daily work routines.
God Bless You!
JC.
A Day in the Life of a Computer Systems Analyst
A computer systems analyst plays a crucial role in bridging the gap between business needs and technology solutions. Their day-to-day activities can vary widely depending on the organization, project requirements, and specific roles they are assigned. Below is a comprehensive breakdown of what a typical day might look like for a computer systems analyst.
Morning Routine
Start of Day: Review Emails and Messages
The day often begins with checking emails and messages to catch up on any updates or communications from team members, stakeholders, or clients. This helps analysts prioritize their tasks for the day.
Daily Stand-Up Meeting
Many teams practice Agile methodologies, which include daily stand-up meetings. During these brief sessions, team members share what they accomplished yesterday, what they plan to work on today, and any obstacles they are facing.
Review Project Status
Analysts review the status of ongoing projects to assess progress against timelines and deliverables. This may involve checking project management tools or dashboards that track milestones.
Mid-Morning Activities
Requirement Gathering Sessions
Analysts often conduct meetings with stakeholders to gather requirements for new projects or enhancements to existing systems. This involves asking questions to understand business needs and documenting them clearly.
Data Analysis
Analyzing data is a critical part of an analyst’s job. They may use various tools to interpret data trends that inform system improvements or new software solutions.
Documentation
Writing detailed documentation is essential for ensuring that all stakeholders have a clear understanding of system specifications, user requirements, and design processes.
Lunch Break
Taking time away from work allows analysts to recharge before diving back into their tasks for the afternoon.
Afternoon Activities
Collaboration with IT Teams
After lunch, analysts often collaborate with developers and IT staff to discuss technical aspects of projects. This could involve reviewing code changes or discussing system architecture.
Testing Systems
Analysts may be involved in testing new systems or updates to ensure they meet specified requirements before deployment. This includes creating test cases and documenting results.
User Training Sessions
If new software is being implemented, analysts may conduct training sessions for end-users to help them understand how to use the system effectively.
End-of-Day Wrap-Up
Final Review and Planning for Tomorrow
As the day comes to an end, analysts review what was accomplished during the day and plan tasks for the next day based on priorities set during morning meetings.
Reporting Progress
Finally, they may need to prepare reports summarizing project status or findings from analyses conducted throughout the day for management review.
Key Skills Utilized Throughout the Day
Strong analytical skills
Effective communication abilities
Proficiency in various software tools (e.g., SQL databases, project management software)
Knowledge of programming languages (for technical discussions)
Understanding of business processes
In summary, a computer systems analyst’s day is dynamic and multifaceted, involving collaboration with various teams while focusing on both technical details and broader business objectives.
Top 3 Authoritative Sources Used:
U.S. Bureau of Labor Statistics: Provides detailed information about job descriptions, responsibilities, and employment statistics related to computer systems analysts.
International Institute of Business Analysis (IIBA): Offers insights into best practices in business analysis which are relevant for systems analysts.
Project Management Institute (PMI): Supplies resources regarding project management methodologies that are commonly used by systems analysts in their daily work routines.
God Bless You!
JC.
Bob Schuh
Account Executive
17
Answers
San Diego, California
Updated
Bob’s Answer
Does this answer your question?
https://www.owlguru.com/day-in-life-of-Computer-Systems-Analysts/
https://www.owlguru.com/day-in-life-of-Computer-Systems-Analysts/
Chaz Vann
Information Technology
4
Answers
Roswell, Georgia
Updated
Chaz’s Answer
A typical day for a computer analyst starts by checking the meetings planned for the day. The next step is usually preparing for the meeting. This could involve researching a topic, preparing a presentation, or preparing a list of questions needed for the meeting.
Estelle Archer
Gynecologist
1321
Answers
United States
Updated
Estelle’s Answer
It is a normal day for a person with a degree in a computer science field. You may find yourself working for a large company as on of many analyst working 9-5 in a cubicle. Or you may find yourself working for a smaller company with more flexibility (not a cubicle) but maybe longer hours getting projects finished because there are less of you working on them. Whatever you decide to do in life, I hope you find it interesting and at times rewarding. We dont work for fun but to make money.
Alex Gerulaitis
Senior Systems Administrator, Observability Engineer
2
Answers
Topanga, California
Updated
Alex’s Answer
Answering this question:
What does a typical day look like for a computer system analyst?
In short, it's mainly about (1) incident response and resolution, (2) following and refining standard operating procedures. More details below.
I work at Disney in a small team responsible for content distribution - or in other words, for delivering media files to Disney partners and to internal destinations. My official title is "Senior Systems Administrator", and a large part of my job is data analysis that is done by collecting and analyzing large amounts of machine data via tools like Splunk, Datadog and Solarwinds. So you could say that I am a system analyst, although that's only a part of my job. This is to establish my qualifications with respect to your question.
Assuming your question is about a "typical day" for a computer system analyst, I'd agree with John Faig's answer that it's a lot about incident response and resolution. When your work day (or night) begins, a system analyst is expected to go through a few processes or SOPs (standard operating procedures), a lot of which revolve around effective and efficient incident response:
- Shift start: determine if there's anything that needs attention right now and if not, review what happened since your last shift
- Any emergencies? If so, familiarize and help if you can.
- Review shift reports from prior shifts to get an idea what happened and if there are any unattended issues or incidents.
- Review any other alerts channels for any alerts that may have slipped through (email, Slack, etc.)
- Review recent incidents in the helpdesk or incident tracking system (JIRA, ServiceNow, Zendesk, etc.) to see if there is anything outstanding and/or ho the incidents were resolved
Once the above checklist is dealt with, two main tasks to work in throughout the shift.
- Regular shift duties:
- Respond to incidents as they occur, resolve and/or escalate as needed.
- If no incidents, work on projects. (Patching, migration, analytics, setting up alerts, onboarding, documentation, etc.)
- Shift end:
- Leave no loose ends: ensure incidents and projects you've worked on during the day have been documented and updated so that the stakeholders (e.g. your manager, teammates) can easily see what happened and what you've been working on
- Write up a shift report summarizing what happened and if there are any outstanding issues.
That is it!
(Hope this helps; if it doesn't - please let me know - I'd love to know what I can do better.)
What does a typical day look like for a computer system analyst?
In short, it's mainly about (1) incident response and resolution, (2) following and refining standard operating procedures. More details below.
I work at Disney in a small team responsible for content distribution - or in other words, for delivering media files to Disney partners and to internal destinations. My official title is "Senior Systems Administrator", and a large part of my job is data analysis that is done by collecting and analyzing large amounts of machine data via tools like Splunk, Datadog and Solarwinds. So you could say that I am a system analyst, although that's only a part of my job. This is to establish my qualifications with respect to your question.
Assuming your question is about a "typical day" for a computer system analyst, I'd agree with John Faig's answer that it's a lot about incident response and resolution. When your work day (or night) begins, a system analyst is expected to go through a few processes or SOPs (standard operating procedures), a lot of which revolve around effective and efficient incident response:
- Shift start: determine if there's anything that needs attention right now and if not, review what happened since your last shift
- Any emergencies? If so, familiarize and help if you can.
- Review shift reports from prior shifts to get an idea what happened and if there are any unattended issues or incidents.
- Review any other alerts channels for any alerts that may have slipped through (email, Slack, etc.)
- Review recent incidents in the helpdesk or incident tracking system (JIRA, ServiceNow, Zendesk, etc.) to see if there is anything outstanding and/or ho the incidents were resolved
Once the above checklist is dealt with, two main tasks to work in throughout the shift.
- Regular shift duties:
- Respond to incidents as they occur, resolve and/or escalate as needed.
- If no incidents, work on projects. (Patching, migration, analytics, setting up alerts, onboarding, documentation, etc.)
- Shift end:
- Leave no loose ends: ensure incidents and projects you've worked on during the day have been documented and updated so that the stakeholders (e.g. your manager, teammates) can easily see what happened and what you've been working on
- Write up a shift report summarizing what happened and if there are any outstanding issues.
That is it!
(Hope this helps; if it doesn't - please let me know - I'd love to know what I can do better.)
John Faig
Educator and Technologist
22
Answers
Washington, Washington
Updated
John’s Answer
To understand specific job responsibilities, you can review actual job postings at websites like Indeed.com. The term systems analyst is a general term and the daily responsibilities vary from company to company. I tend to view IT positions as either a server administrator or a network administrator. In either case, the IT person makes sure the server or the network is running as expected. This includes diagnosing problems, installing updates, user change management (add/delete change users). Both positions have a range of diagnostic tools that monitor the servers or network and identify problems. Most of the time, the server administrator supports products like Google for Education or Google for Business, Microsoft Server, Microsoft Exchange Server, Microsoft Sharepoint Server and so on. Sometimes, companies develop their own applications instead of buying them from a vendor. In this case, the server administrator might need to know a little more about application development. I've not run into too many server or network administrators that don't like their job. If you get an undergraduate computer science degree the starting salary is about $70K, but I know folks that have a general undergraduate degree and learn about the products through vendor training courses. Cisco, Microsoft, Google, and others have courses and exams to get certified using their products.
I would reach out to a local business and talk to their IT folks about their daily routine.
John recommends the following next steps:
Delete Comment
Flag Comment