Software Engineering

98
CHAPTER 6 
Impediments to Software Design
Software should be viewed as a set of data processing transactions that facilitate 
a business or operational process. Data processing transactions describe the stimulus-
response nature of software execution. Almost all software modules are initiated by 
some stimulus, perform some computational action or function to produce some 
result, and transfer data processing control to another transaction. A large software 
program involves a number of possible transactions that are accomplished by the 
execution of a series of modules or routines. The sequence of module execution is 
dependent on the outcome of the computational action, and some form of decision 
or control logic determines how the transaction should proceed.
Because of its lack of physical characteristics, software represents a form of 
artificial language used to:
●
  Perform mathematical computations or process symbols into meaningful data.
●
  Construct logical arguments that guide the flow of data processing transactions.
●
  Preserve data in digital format for future access.
●
  Interact with elements of the computing environment.
●
  Interact with elements of the business or operational system.
Therefore, software is a combination of linguistics, semantics (the study of mean-
ing), mathematical notation, logic, knowledge representation, and systems engi-
neering (problem solving in the presence of complexity).
As software products have grown in size and complexity, the application of 
systems engineering practices to software development became more apropos due 
to its emphasis on analyzing design challenges and reducing design complexity. 
However, there has been no authoritative dictate to motivate or encourage the soft-
ware industry to adopt systems engineering precepts. Software pundits emerged 
proposing numerous methodologies targeted at providing better software develop-
ment stratagems. However, most of these software methodologies were driven by 
rapidly advancing computer technologies or program language–driven refinements, 
such as object-oriented programming. As a result, most software practitioners lack 
the fundamental skills necessary to cope with the convoluted dilemma associated 
with the design of a software product.