Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Entity Relationship Diagram
Previous Previous
 
Next Next
New Post 2/9/2008 9:07 PM
User is offline Adrian M.
764 posts
3rd Level Poster




Re: Entity Relationship Diagram 

Hi Sonavi,

Here are a couple of resources:

UML basics: The class diagram

UML 2 Class Diagrams by Scott Ambler

UML 2 Class Diagram Guidelines by Scott Ambler

Class Diagram Tutorial

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 2/9/2008 9:11 PM
User is offline sonavi
37 posts
9th Level Poster


Re: Entity Relationship Diagram 

Thank you all for helping !!

 
New Post 2/9/2008 9:28 PM
User is offline sonavi
37 posts
9th Level Poster


Re: Entity Relationship Diagram 

Hi,

I have a project where in i have to document the existing process. The organization needs to document the existing process so that they can use the same process to develop another applicaiton of similar kind. I have following information

1. Database information ie ( what are the different tables which are being used)

2. User Interface

What all documents should i create so that it can be easily understandable by the stakeholders. What all diagrams should i include in my document. There is no change in the UI for creating the new application. Basically the new application will use the same UI and i have to figure out what is the data that is being used. So  what procedure should i follow and what diagrams should i include?

Thanks

sonavi

 

 
New Post 2/9/2008 10:08 PM
User is offline Adrian M.
764 posts
3rd Level Poster




Re: Entity Relationship Diagram 
Modified By Adrian M.  on 2/10/2008 1:12:49 AM)

Hi Sonavi,

Do you also have access to the code or can work with a developer who can read the code?  Just understanding the UI and the data structure is not enough - you need to understand the business logic which, for most applications, is hard coded in the actual code.  If you don't have access to the source code then you have a tough job ahead of you since you'll have to guess/infer the business logic based on the application behavior and, perhaps, from talking to users who are familiar with the system.

The activity that you are actually being asked to perform is called "reverse engineering" where rather than trying to gather requirements from the stakeholders you are using an existing system and trying to document what it does.

Here are some things to consider:

  • If you are trying to document the business processes which utilize this application you should document this using a business process notation such as BPMN (Business Process Modeling Notation).  This will help you understand the big picture and how the given application supports (or does not support) the goals of the business.
  • What are the "things" of the business, that is what are the nouns which the application deals with and which are recognizable by the business?  These are also known as "business entities".  You can discover most of the business entities by taking a look at UI and the database tables.   These can be modeled using a Class Diagram which can also show the relationships among these entities. For example: in a banking application some of the business entities might be: bank account, customer, transaction, etc.
  • For each business entity you should try to identify its attributes (data which describes the thing).  For example: a bank account might have: a number, creation date, current balance, etc.
  • What does the application do? What are the key functions that a user can perform on the application?  Please note that most functions deal with one or more of the identified business entities by Creating, Reading, Updating, or Deleting (CRUD) business entities and related data.  You could model these key functions using a Use Case Model.
  • For each key function, you will need to understand the detailed business rules and logic.  For example: It is not enough to know that the user can enter numbers on the screen, press a "Calculate" button, and view/save a result.  You will need to know what logic/formula the system uses to calculate the result.  There are many ways to capture this logic such as: use case specifications, pseudo code or structured English, activity diagram, business rules, etc.

One more note from personal experience:  The fact that the database contains a number of tables and fields, it does not mean that the system actually uses all that data.  Similarly, the fact that the user can enter a piece of data in a screen, it doesn't mean that piece of data is used anywhere.  I once worked on a legacy application which had about 1000 tables but only about 300 of them were actually used by the application.  As the system evolved, the developers and DBAs did not remove old/legacy tables out of fear of breaking something.  That is the drawback of not having up-to-date system documentation.

Hope this helps!

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 2/9/2008 10:43 PM
User is offline sonavi
37 posts
9th Level Poster


Re: Entity Relationship Diagram 

Hi Adrian,

Thank you for your valuable advise.

Yes i do have access to the source code and  i am going through the code to understand the logic behind it. I will first understand the process and let you know the entire process and will work on creating business process. Hope you can help me out if i need any help in creating the Business Process diagram.

Thanks

Sonavi

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Entity Relationship Diagram

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
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...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC