Introduction to Software Engineering - Software Engineering: A Hands-On Approach - page 5

Table 1.1 Positions and associated rolls commonly held amongst stakeholders of a software
engineering project
Position Roll

Client Individual or organization that has commissioned a software project, and for

whom the final product is being made. Also referred to as the customer

Project manager Responsible for overseeing the entire software engineering project. Ensures

that the project remains on task, on time and within budget. Manages
team leaders

Team leader Works under project manager and manages teams that are established to

handle portions of the software engineering project. Functions as a project
manager for smaller 'sub-projects'

System architect Designs the software system and determines the way in which various parts

of the system interact with each other

Programmer/
developer

Responsible for writing the code called for by the system architect.
Transforms system model into actual code. Also responsible for creating
and maintaining up to date documentation of the code

Tester Tests software system by using it in the manner prescribed and desired by the

client's requirements and specifications

End user Consumers of the final software product, as intended by the client

team. For this reason, it is not possible to compile an accurate list of all possible
stakeholders. However, Table 1.1 details some common positions and associated
rolls.

1.3 Software Engineering Activities

Software Engineering is made up of many activities. This section describes some
of the general activities that occur throughout all phases of the software engi-
neering project.

1.3.1 Planning

A software engineering project can be a very large and complicated undertaking,
composed of many different tasks to accomplish and roles to designate. In order to
efficiently and effectively direct this conglomeration of goals and resources, it is
crucial to establish comprehensive plans of action.
In the next chapter, we will discuss the phases of the software development
process. Planning will not be one of them. It is far too important to be confined to
just one phase of the process. Instead, the creation and use of plans is an activity
which occurs throughout the entire development process (Schach 2008 ). In addi-
tion, plans are continuously analyzed, evaluated and updated to meet changes
encountered, such as updated requirements or specifications from the client or an