Here we have another reference to modeling a system
by its components and their relationships. This is the way we are constructing the evaluation function in our proposed
heuristic.
p.30"System modeling [section title] During the system requirements
and design activity, systems may be modeled as a set of components and relationships between these components. these are normally
illustrated graphically in a system architecture model that gives the reader an overview of the system organisation."
The implementation phase of software development begins with a detailed system specification.
p.77"The implementation stage of software development is the process of converting a system specification
into an executable system. It always involves processes of software design and programming but, if an evolutionary approach
to development is used, may also involve refinement of the software specification.
A software design is a description of the structure of the software to be implemented
, the data which is part of the system, the interfaces between system components and, sometimes, the algorithms used."
Sometimes we can better understand requirements by spending some time in the environment of the
user, and seeing the operational needs from their point of view. We also might discover hidden system requirements that are
unknown to the user.
p.157"Ethnography is an observational technique that can be used
to understand social and organisational requirements. An analyst immerses him or herself in the working environment where
the system will be used. He or she then observes the day-to-day work and notes made of the actual tasks in which participants
are involved. The value of ethnography is that it helps analysts discover implicit system requirements that reflect the actual
rather than the formal processes in which people are involved."
