Right behind "thing" as the most ambiguous word in the English language, "system" can mean just about anything for software. This ambiguity has historically been a root cause of problems in understanding software requirements. So, we will define it here for our purposes.
From business systems theory, a general definition is useful.
Kerzner says that a system is a group of elements organized and arranged so that the elements can act as a whole toward achieving a common goal; is a collection of interacting subsystems; and has boundaries that define it as an open system (which interacts with the
surrounding environment) or a closed system (which is isolated from the surrounding environment).J—1
IEEE defines a system as a collection of components organized to accomplish a specific function or set of functions.
This means that any collection of organized elements oriented towards a goal can be a system. In software project management, we can have many systems: change management system, cost management system, configuration management system, project management information system, and performance measurement system.
We think of the software products of our projects as systems, often composed of hardware, software, and processes.
A key point about systems is that they have boundaries and may or may not interact with their surrounding environments. If they can stand alone and function independently they are closed systems. If they must interact with their environment to be effective they ar®pen systems.
Regardless of whether the products produced by a software project are closed or open systems, programs and projects are almost always open systems, as much of the project manager's job involves interacting with other people and systems in a business environment.
Our definition of the term will be: A system is an organized group of elements with a boundary defining openness or closeness that acts as a whole toward achieving a common goal.
It is important for software project managers to understand the basic nature of systems as they run programs and projects made up of many interacting systems in organizations composed of many interacting systems. This is why their jobs are so complex.
Now we have a consistent language that includes a basic set of PM terms. Next, we will turn to brief descriptions of the SWPM essential software project management competencies, and how they will be addressed in this book. Each SLC phase requires the use of more than one competency, and each competency is used in more than one phase. The chapters are arranged to follow an SLC sequence, each chapter addressing applicable PM skills. As described earlier in this chapter, our focus is quality, software, project, and management. Quality underlies all; software (product), project, and management (people) each have a number of skills that should be possessed or acquired by a project manager. So, we will begin with a brief description of software, or product, competencies.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.