Can we make an analysis and design a systemic solution without requirements? Is Business Analysis a coaching/communication discipline or an engineering discipline? Where do customers get requirements from? Should requirements not be the result of an investigation and analysis activity .. professionally conducted? What if the customer did a wrong diagnosis? (labelling a consequence of a deeper problem as problem or misunderstood the problem or misunderstood what will solve the problem or ignore the consequences, risks and implications? Do you believe that a system is "good enough" if it meets the expectations of a customer? I see the BA as an ENGINEER operating at a certain higher level of detail or area, in and/or outside a project, and specialised in organisation, systems (+structure, process, flows, etc..: = systemology), information (information science), information systems and software engineering performing 1) investigation, 2) goal clarification and/or diagnosis (needs, issues, opportunities), 3) analysis, 4) conception and 5) evaluation
@TechcanvassAcademy3 жыл бұрын
Hi Axel, Business Analysis is really a broad practice encompassing not only communication, collaboration, Analysis and modelling but many more aspects. You have made really valid point about requirements coming out as a result of investigation and discover. Interestingly, requirements elicitation is also called as "Requirements discovery", echoing your point. It does involve engineering aspects because of analysis and modelling involved, which also act as validating the understanding of "right" requirements. Thanks for your insights.
@jalakvyas39093 жыл бұрын
I really appreciate you for this wonderful video...!!
@TechcanvassAcademy3 жыл бұрын
Thanks Jalak
@TechcanvassAcademy5 жыл бұрын
If you would like to know more about the 🔥ECBA Training (DISCOUNT CODE: YTTECH15) bit.ly/3GNdQRw To know more about us - Contact us at +91 93255 66777 or visit us at techcanvass.com Other Business analysis certification courses: bit.ly/3GQUxXv