00:03
If finding a system boundary and creating an appropriate context model are crucial steps in the project management, especially in the complex system.
00:13
So these decisions can impact the scope complexity and the cost of a project.
00:19
So here are two example illustrating how these considerations are applicable.
00:25
So first is software development software development.
00:35
So consider a project to develop an enterprise level software system for a large organization defining the system.
00:45
Boundary involves determining which processes departments and functionality will be included within the software system.
00:55
So defining the system boundary involves determining which processes determining which processes departments and functionalities will be included within the software system will be included within the software system.
01:53
So if the boundary set to wide in come passing too many processes, the complexity of the project will increase significantly.
02:02
So if the boundaries to white the complexity will increase significant more integration points, dependencies and interaction will have to be considered leading to longer development time and higher cost.
02:29
So on the other hand, if boundary is set to narrow critical functionalities might be left out requiring additional integration or modification post -launch second is our work infrastructure project are one infrastructure project.
02:52
So imagine a city planning to construct a new subway system...