As a foundational definition; a system is an assembly of procedures, processes, methods, and/or techniques united by regulated interaction conventions to form an organized whole in support of the entity’s objectives. A key term to this definition is “regulated.” Specifically, for anything to be systematic there must be a process conducted according to some orderly method whereby a control exists that gauges the process against a previously established standard. Thus, systems need not necessarily be technology-based, although basing a system on electronically encoded procedures will tend to provide the regulation necessary for processes to be called systematic.
Even if technology is not utilized as a tool for providing control, a system that executes business processes with the same degree of regulation can be constructed, less, the technologies’ time compression capabilities. Nonetheless, within the context of development projects, under most circumstances, systems refer to IT applications. A new application’s life cycle begins when the inadequacy of the old application leads to a decision to develop a new or improved application. The most common methodology applied to the development of large applications is a system development life cycle (SDLC) approach that incorporates various aspects of application development activities. Customarily, application development life cycle approaches are based on the idea that an information system has a finite lifespan that is analytically divisible into stages. Whereupon, the development life cycle generally includes: planning, systems analysis, systems design, implementation, and operating stages.
“View Part I of the Safeguarding Assets is an IT Project Management Issue series here“