while preparing Business requirements documents you mention why you need to bulit a system, i.e. problem statement. What you need to do while creating functional requirements is you have to specify is, solution of the problem. Specify thorugly business problem and explain solution for the same.
Business requirement documents does not necessarrily contains solution part, functional requirement may contain it how end user wants the system to perform. Dont forget to add non-functional requirements same doc.
Following is the instance of Business Requirement, Functional Requirement and Non-Functional Requirement.
Business Requirements :- sales order is made against customers purchase order. Sales order is given for approval to upper authority
Functional requirement:- Sales order shall be made with reference from Purchase order and it should be approved from upper authority.
Non-Functional Requirement:- Sales order should be in proper format (Specify format) and six copy of sales order should be printed from printer in 1 minute.
RE: How would you transform business requirements to f...
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.
RE: How would you transform business requirements to f...
while preparing Business requirements documents you mention why you need to bulit a system i.e. problem statement. What you need to do while creating functional requirements is you have to specify is solution of the problem. Specify thorugly business problem and explain solution for the same.
Business requirement documents does not necessarrily contains solution part functional requirement may contain it how end user wants the system to perform. Dont forget to add non-functional requirements same doc.
Following is the instance of Business Requirement Functional Requirement and Non-Functional Requirement.
Business Requirements :- sales order is made against customers purchase order. Sales order is given for approval to upper authority
Functional requirement:- Sales order shall be made with reference from Purchase order and it should be approved from upper authority.
Non-Functional Requirement:- Sales order should be in proper format (Specify format) and six copy of sales order should be printed from printer in 1 minute.
RE: How would you transform business requirements to functional requirements?
Business Requirements depict the features or needs the business is looking for. They represent what they are expecting from the system.
Functional Requirements depict how the system should represent the functionality desired by the system.
This transition from business requirements to functional requirements can be indicated textually and also via UML modeling using Use cases Activity Diagrams Mockups.
1 
1