The term stakeholder is often misconstrued to mean the customers of the project. While I have listed several role players that affect the project objectives, you should never lose sight of the customers and the ability they have to change the project's direction.
Users: From this group, you will collect your functional requirements, therefore they heavily influence the stated project objectives. The typical system stakeholders that I would classify as users can be system users, internal customers, external customers, managers, or executives. Essentially, anyone who may rely on the project deliverables becomes a user.
Downstream Systems and Processes: As with user stakeholders, this area should be considered in its broadest sense. Any software, hardware, or process that could be affected by the changes caused by your project becomes a stakeholder in its success. Think about it: if you rely on a system or process to give you information to perform your job, then you are by default a customer of that application and are dependent upon its success.
Image Credit: Renjith Krishnan / FreeDigitalPhotos.net