Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Transform Business to Functional Requirements
Previous Previous
 
Next Next
New Post 8/25/2009 8:02 AM
Resolved
User is offline Raj
7 posts
10th Level Poster


Transform Business to Functional Requirements 

Folks,

         Please provide inputs on the following

1. What are the best ways to Transform Business Requirements to Functional Requirements?

I have completed working on BRD with the Business and IT users and stakeholders and have started working on developing the Functional requirements doc. I'm developing the Use cases to represent the system functionality and i believe the use cases will be a major component of the FRD. Please advise if this is the best way to convert the Business Req's into Functional req's or if there are any other methods to capture functional requirements. I work on a state project and they dont follow a standard methodoloy and do not have standard templates that the teams can use. This makes the process a little complex.

Raj

 

 

 
New Post 8/25/2009 2:51 PM
Accepted Answer 
User is offline manoj
1 posts
No Ranking


Re: Transform Business to Functional Requirements 

Raj, here is what you need to do to transform Business requirements into functional requirements.  Also Make use case for each function of system

a)   Create project-initiation diagrams flow that includes business use case activity diagram workflow, diagrams flow charts, etc.

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

c)   Detail the use cases by using activity diagrams or other techniques

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

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

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

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

I hope this helps.........

Manoj

 

 

 

 
New Post 8/25/2009 3:41 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Transform Business to Functional Requirementsck  

check out this discussion

http://tech.groups.yahoo.com/group/Requirements-Engineering/message/1910

nd another point of view; why do it at all?

 
New Post 8/26/2009 1:14 PM
User is offline Raj
7 posts
10th Level Poster


Re: Transform Business to Functional Requirements 

Manoj, Thanks for the quick response. I like your recommendation.How ever, couple of things

1. I have already come up with a high level process flow diagram which explains the complete functionality of the system.

2. So, will the next step be to dis-integrate the high level Process flow into smaller sub categories for each module with in the system?

3. Also, i have come up with Use cases that describe the system and User interaction.This should help too, right?

Raj

 
New Post 8/26/2009 1:15 PM
User is offline Raj
7 posts
10th Level Poster


Re: Transform Business to Functional Requirementsck  

Craig, thanks for the input. Never heard of the Yahoo forums for software development. There's a lot of information in there.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Transform Business to Functional Requirements

Community Blog - Latest Posts

Ekaterina Barabash
Ekaterina Barabash
I address my thoughts to those who are in IT management for whom the terms such as quality of project implementation development and profitability indicators of the company are important.  And it is also addressed to business analysts whose daily routine is the process of communication with Customer. A little about myself first. The last 8...
0 Responses
Dan Tasker
Dan Tasker
I have long been a believer in the saying “Context is everything.” As a business analyst dealing with business users, understanding the context of the topic of discussion is essential. In thinking about what constitutes quality requirements it occurred to me that there are a number of additional contexts that play a role. Examples inclu...
2 Responses
Alexey Kiselev
Alexey Kiselev
We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...
0 Responses




Latest Articles

Featured Digital Library Resources 
Copyright 2006-2019 by Modern Analyst Media LLC