<Tr> <Td> Component </Td> <Td> Screw or Bolt </Td> <Td> </Td> </Tr> <P> Other authors sometimes call use cases at Organization level "Business use cases". </P> <P> Cockburn suggests annotating each use case with a symbol to show the "Goal Level"; the preferred level is "User - goal" (or colloquially "sea level"). </P> <Table> <Tr> <Th> Goal Level </Th> <Th> Icon </Th> <Th> Symbol </Th> <Th> </Th> </Tr> <Tr> <Td> Very High Summary </Td> <Td> Cloud </Td> <Td> + + </Td> <Td> </Td> </Tr> <Tr> <Td> Summary </Td> <Td> Flying Kite </Td> <Td> + </Td> <Td> </Td> </Tr> <Tr> <Td> User Goal </Td> <Td> Waves at Sea </Td> <Td>! </Td> <Td> </Td> </Tr> <Tr> <Td> Subfunction </Td> <Td> Fish </Td> <Td> - </Td> <Td> </Td> </Tr> <Tr> <Td> Too Low </Td> <Td> Seabed Clam - Shell </Td> <Td>--</Td> <Td> </Td> </Tr> </Table>

What do you mean by use cases and actors