Is this UML Use Case too detailed?

Is this use case diagram over compl开发者_运维百科icated? I'm trying to implement a use case for the first time, and I'm trying to get it within the ball park.

---

Jordan, your use case is missing out the system name at the top.

And there is no over-complicated Use Case Diagram, as long as it fits the requirements of the client.

P.S: By the way, the following Use Case Diagram is one of my assignment in school (so it's not for a system to be built, but similar anyway). It's way complex than what you have there, but it's not over-complicated because the system needs all these use-cases. Imagine drawing the use case of Twitter or Facebook.

   Merlion University Student Association System Use Case Diagram

---

Doesn't look overly complicated, but you're missing the part that goes on the right, which is the actions in the box use/affect. For example, Add Account may communicate with a database, in which case you'd put a box on the right (outside of the center box) called Database and have Add Account point to it.