Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Main Documents and Diagrams for business system analysis
Previous Previous
 
Next Next
New Post 10/7/2015 11:53 PM
User is offline Isra
2 posts
No Ranking


Main Documents and Diagrams for business system analysis 

Hi all,

as I'm a junior business system analyst, I'm confused about the following:

1- Main Documents should be prepared for Client, and type of diagrams shall be included in document.

2-Main Documents should be prepared for developers,and type of diagrams shall be included in document.

where I used to  design a prototype of my project (or new feature of existing system) and prepare document describes the prototype.
As well i used to prepare ERD Diagram for developers
please tell me, Am I in the correct way???

 
New Post 10/12/2015 12:25 PM
User is offline Adrian M.
764 posts
3rd Level Poster




Re: Main Documents and Diagrams for business system analysis 

Dear Isra,

I'm going to let others chime in on your question so I will just address the diagrams portion.

As a business systems analyst you are not unlike a builder who has many tools at their disposal with a few caveats:

  • The more tools you know how to use the better you will be able to serve your customers, you would be able to provide better quality, and do the job quicker.
  • You need to know what each tool is for and when to use it and when it is not appropriate to use.  The more you use a tool the more you'll discover its best uses.  For example: you would not want to use a table saw when all you need is to break a stick in half for your campfire.

As with any other craftsman, you there a two types of tools:

  • Tools which you have and know how to use.  If these can do the job use them first.
  • Tools which you have but don't have much experience with.  Don't be afraid to use (apply in practice) some of the modeling techniques you learned in the classroom.  The more you use them the better you will get.
  • Tools which you don't have.  In the case of the analyst, these are techniques and modeling standards which you have not learned about nor used.

So - make sure you keep adding to your toolbox and get your new tools dirty (used).

On to your specific question...

Stakeholder/Customer Centric diagrams allow you to model the business need, problem domain, and requirements in order to ensure you have a  good understanding of what you are trying to solve.  Note: while these are 'customer' centric, the technical team and developers can learn a lot about the customer's need from these artifacts:

  • Business Objective Model which help you identify the key drivers of the project and the key customer objectives.
  • Feature Tree & Functional Decomposition allow you to dive into the next level of detail in order to identify the logical groupings of features and functions needed to be addressed by the project.
  • Process Flow Diagram allows you to understand the problem domain in the context of the existing business process (AS IS) or the proposed/re-designed business process (TO BE).
  • Business Entity Model allows capture and validate the key "things of the business' aka business entities which are involved in the problem domain.  This would generally be a class diagram showing business entities (not system classes). 
  • Decision Model allows you to model the business decisions down to the most low level business rules in order to clearly understand how the business decisions are made.

System/Developer Centric Diagram are created once the problem domain is understood at the desired level or breath (scope).  These diagrams help to document system design decisions and solution direction.  Note:, don't discount these diagrams as not being understood by the customer.

  • Context Diagram & TAM Block Diagram (aka Ecosystem Map) show the key systems and/or system components participating in the solution.
  • Data Flow Diagram (DFD) shows how the information flows among the various systems components giving an understanding of how data is transformed.
  • State Transition Diagram can be used when the system and/or system objects have complex states which need to be tracked.
  • Sequence Diagram would be used to show sequence of interactions, over time, which will take place in order to accomplish a specific scenario or flow.

These just a few tools which you can use, there are many more.

Happy Learning!

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 10/19/2015 7:11 AM
User is offline Isra
2 posts
No Ranking


Re: Main Documents and Diagrams for business system analysis 

Many Thanks Adrin, This will help me in rearrange and review my workflow and Documents Style 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Main Documents and Diagrams for business system analysis

Community Blog - Latest Posts

Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...
I recently had the pleasure of chatting with Wolfgang Goebl, a visionary in the field of business architecture and enterprise design. His unique approach, which he refers to as "architectural thinking," and his work with the EDGY framework, offer valuable insights into the future of organizational structure and design. This tool covers th...
Our next speaker in our Blueprints for Success series is none other than Roger Burlton, a prominent leader in business architecture. As founder of Process Renewal Group, Roger has spent over three decades helping businesses worldwide translate strategy into execution. “Intention is everything.” – Roger Burlton Known for his ...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC