Noypi

 Profile Answers by Noypi 

• Feb 20th, 2007

 

Create project-initiation diagrams including business use cases, activity diagrams, workflow diagrams, flowcharts

Determine project scope and derive context diagrams and project use cases from the business diagrams

Detail the use cases by using activity diagrams or other techniques

Create high level analysis dataflow diagrams, domain class diagrams, and entity-relationship diagrams from the use cases or other high level diagrams

Recognize and understand the various design models, including the other relevant types of UML diagrams, detailed design entity-relationship diagrams, and decomposed dataflow diagrams

Determine when to use which modeling technique, following them through a project life cycle, and understand which diagrams are derived from others

Understand the basic concepts of normalization and decomposition so can converse intelligently on the topic and review diagrams that have been normalized or decomposed

srikanthpullikanti

 Profile Answers by srikanthpullikanti 

• May 16th, 2008

 

When the Business Obectives are set then BA makes a Requirements documentation in which the analysis is done by various techniques like
Stakeholder interview,Goals,JRD sessions ,prototypes,usecases,SRS,Stake holders intrest and issues and Attempted soltions.

MOdelling techniques is the next step after the requirements is done by UML used for functional or logical view, code view,or development or structural view.

dody1108

 Profile Answers by dody1108 

• May 14th, 2010

 

The analysis techniques that I have used:

• Lay out business problems
  
• Depicting business problems by grapical structures using MS visio, rational s/w tool, simple flowcharts
• Well organized JAR sessions with homework
  
• Well asked, documented questions to users and giving them time to answer them
• Use case with diagrams and simple English
• Feasibility study involving technology team
• Capturing & clarifying non-functional requirement along with tehnology team involvement
• Creating CAR (control-action-response) document and getting reviewed from user and technology team

Infact, apart from using some standard documentation and analysis methodologies, well organized procedures according to your organization need, team size and geography, time frame of deliverables is more suitable, I believe.