Systems Design for Projects

Systems Design for Projects 1
SYSTEMS DESIGN FOR PROJECTS
by [Name]
Professor’s Name
Course Title
City/State
Date

Systems Design for Projects 2
Introduction
This paper will discuss the reasons for studying complexity, and the consequences of not
recognizing complexity. In addition, the paper provides comments on the use of systems
techniques to addressing problems such as acquiring a large tract of land for a new facility and
approach on how to deal with student plagiarism. The paper also recommends the choice of
methods to understand the issue of complexity and finally describes how a project managers
exercise governance.
The reason for studying complexity when a reductionist methodology offers a simpler alternative
is because complexity is not a model but a program in the field of science that research the
manner in which features interact in a system to generate general configurations (Kerr, 2014).
Similarly, studying these patterns will enable individuals to understand the manner in which they
result in the relating features to change. Therefore, complexity is concerned with the creation of
structures and how the development of these structures influence the objects that form them.
Allen, Maguire and McKelvey (2011) defines complexity system as many interacting parts that
are controlled by certain forces that correlate in terms of behavior at a given time contingently to
the state of others.
We study complexity because it is an adaptive system that consists of several features. Some of
these features include: several heterogeneous agents. Each heterogeneous agent is tasked with
making decisions regarding how it work. The most significant measurement is that these
decisions will advance with time (Lessard, Sakhrani, and Miller, 2014). Second, these agents
interact with each other and through these interaction it results in another aspect referred to by
scientists as emergence. It is not possible to comprehend the entire system by observing distinct
parts. These representatives makes independent resolutions on how to act and then interact with

Systems Design for Projects 3
each other to result in the emergence that create the general system. A combination of the three
aspects when put together are greater than each distinct parts.
If complexity is not acknowledged it has consequences that can cause accidents for example tight
coupling. In multifaceted systems in which evolving effects are predominant, there is a
propensity in the direction of high risk of calamities. In this essence an accidents is any occasion
that is not intended resulting in the damage of the subsystems or even the entire system. When an
accident occurs it abruptly stops the intended output from taking place. Accidents happen not
because of natural consequences of the complexity but due to the attempts to manage the
complexity (Gupta, and Anish, 2009). Accidents in multifaceted systems happen because of
unexpected interactions failures happening in the system. When a system is more tightly
coupled, the more possibility of experiencing failures that influence each agents leading to
greater risks of accidents.
In general tight coupling is principle that is applicable for all systems of systems. When
components of a system are tightly coupled, it results to their actions as well as interactions
being constrained. Consequently, this results in higher probability of failure occurring. Tight
coupling minimizes the existent chances for evolution and adaptation. Therefore, any
unnecessary coupling will negatively influence the feasible solutions by causing delays,
heightening costs and excessive consumption of resources (Boisot, and McKelvey, 2011). On the
same note, the emergent of unnecessary coupling has been found to easily prevent all feasible
solutions. Certainly, in regard to accidents, tight coupling is challenging because it work to
prevent system of systems from realizing its objectives. It is unfortunate that actions undertaken
to minimize risks in system of systems traditional originate from traditional software as well as
system engineering approaches that does not factor in emergent effects. As a result, these actions