Software Engineering

12
CHAPTER 1 
Introduction to Software Engineering
2. 
Appearance:
 The mechanism by which the user or operator can observe, interact, 
and control software operations. Typical user interface elements involve sounds, 
notification lights, windows or forms, dialog boxes, and report formats. The appear-
ance of the software product may be casual for consumer products or may require 
advanced human–machine interface designs aided by human factors specialists.
3. 
Convenience:
 The usability of the software product in terms of simplicity of 
maneuvering between and among features to control processes, data entry, data 
retrieval, data manipulation, and report generation.
4. 
Efficient functioning:
 This addresses the action or use for which the software 
product is designed; its performance or the manner in which it functions, oper-
ates, or behaves; and the utilization of computing resources. The software 
architecture must be designed to make the best use of available computing envi-
ronment resources, such as processing speed, data transfer rates, memory, data 
storage, and communications bandwidth.
Clearly, the definition and design of a software product architecture demands a 
rigorous approach, as well as techniques for capturing and expressing architectural 
design characteristics. Software engineering involves several design challenges that 
involve computing technology, software components, human factors engineering, as 
well as interfaces with other systems or software applications. The software architec-
ture involves:
●
  The set of requirement specifications derived by interactions with the software 
product stakeholders.
●
  Functional representations of the software behaviors and interactions among 
users, operators, and external systems.
●
  The physical or structural arrangement of software “building blocks” and the 
strategy for combining these software elements into a single, integrated product.