RESPOND TO BOTH OF THE PEER POSTS BELOW IN ONE PARAGRAPH EACH

Description

Prompt: write a paragraph response to each peer post based on their initial discussion post.

PEER POST # 1

Reflecting on Modules One through Ten, the project presented a range of challenges that required continuous adaptation and problem-solving, typical of complex system implementations. The most significant challenges over the course of the project included:

• Requirements Gathering and Stakeholder Alignment: In the early stages, gathering clear and accurate requirements posed a challenge, especially considering the multiple stakeholders involved, including auditors, the Finance Department, and the Office of the Comptroller. The challenge was ensuring all needs were understood and prioritized effectively. This was mitigated through continuous stakeholder engagement, focus groups, and iterative feedback loops .
• Managing Change and User Adaptation: As highlighted in the project plan, resistance to change, particularly from the audit team accustomed to manual processes, was a concern. Implementing a structured change management process with training, communication, and user-centered design helped address this issue.

Most Difficult and Helpful Diagrams:

• The Data Flow Diagrams (DFDs) were the most challenging to comprehend and create. DFDs required a precise understanding of how data moves between different components of the system, involving complex interactions between entities like the ERP, contract management systems, and users .
• The Use Case Diagrams and Entity-Relationship Diagrams (ERD) were among the most helpful. They provided clarity on user interactions and data relationships, ensuring that the system’s functionality aligned with the business processes (Cockburn & Cockburn, 2008; Tilley & Rosenblatt, 2016) .

My understanding of the role of a systems analyst has deepened since Module One. Initially, I viewed the systems analyst primarily as a bridge between business requirements and technical solutions, focusing on solving existing system inefficiencies. Now, I appreciate that the role is much broader, encompassing not just problem-solving but continuous improvement, stakeholder management, risk mitigation, and ensuring that the system evolves to meet changing needs (Armel, 1997; Osemeike Gloria Eyieyien, et al., 2024). Throughout the course, I realized that the systems analyst must also play a proactive role in shaping business strategy through technology, as demonstrated in the iterative process of requirements modeling and system design .

Would I Want to Be a Systems Analyst?
Yes, as a data analyst, I already perform many of the tasks involved in system analysis, such as requirements gathering, data modeling, and process improvement (Chowdhury, 2023; Tilley & Rosenblatt, 2016). This course has reinforced that systems analysis aligns well with my current role and career trajectory. The combination of technical problem-solving, business process alignment, and continuous learning makes this a field I’m eager to continue exploring in my professional development

PEER POST # 2

The biggest challenge for me was the data flow diagram; the connectors did not initially do what I needed them to. I needed help figuring out how to connect two connectors simultaneously to another object without starting from scratch. There were many do-overs. Another challenge was that the Visio program would not load or time out if I switched to a new window. The UML diagrams were confusing as well, but by the third milestone, I understood where to go and what to use in order to visualize what was needed. Use case diagrams were the easiest to navigate; they showed the key players and their roles without adding confusion for those who are not tech-savvy. Overall, this course taught me that being a systems analyst is not in my future, and I am ok with that knowledge.