The techniques listed

The following are the core techniques you need to have in your toolkit. A good understanding and some experience in putting them to use (together with "soft" business analysis techniques such as relationship building and influencing) will make you an excellent contributer to projects as a business analyst:

• Requirements Definition (RD)
  Understanding quantifying and recording the users' needs of the system and the associated non-functional requirements.
• Dataflow Modelling (DFM)
  Expressing the totality of the users' in-scope business processes as a set of diagrams with their detail documented in prose and list form.
• Logical Data Modelling (LDM)
  Expressing the users' data needs of the system as a diagram with supporting prose and lists describing their detail.
• Function Definition (FD)
  Defining, from the users' perspectives, the discrete functions that together cover all processing of the required system, taking into account the practicalities of the day-to-day running of each business area.
• Event / Entity Analysis
  Identifying the triggers that cause a process to do its thing and recording the way that this changes each affected entity's attributes. It is also where you identify the business rules.
• Business System Options (BSO)
  Defining (with the users' guidance) a range of options for taking the fulfilment of the requirements forward. Each has an associated cost / benefit analysis and (often) its own supporting dataflow model and logical data model. The project /board or governance group then chooses which way to go.
• Dialogue Identification
  Identifying at a practical level the critical dialogues (two way interaction) with the system. What logically has to be on screen, what is keyed in, what comes back, what then gets done using the screen before that dialogue is complete.