307
Systems Integration Management
“send application,” “go to interview,” and associated activities. The two
tasks will result in the same event for the successful applicant and the hiring
company: countersigned employment contract. Each of the processes involve
stakeholders who receive inputs of EMMI, and transform those inputs into
various outputs by following procedures, common practices, and various
associated activities. Similarly, the function of ‘to hire’ involves the interaction between the applicant and the hiring individual. For example, during
the interview, both the applicant and the hiring individual exchange EMMI
(e.g., acoustic waves, termed talking). The interaction between the applicant
(object A) and the hiring individual (object B) fulfills the function of ‘to interview.’ The function of ‘to interview’ is a joint function involving both the
participants, the outcome of which is the event of INTERVIEW.* One of
the processes that results from this interaction is ‘to send’ the offer letter. The
event of SEND LETTER is the result of the function of ‘to send’ which summarizes many actions that result in placing the letter in a postal drop box.
The interaction between the mailer and the postal drop box is the function of
‘to send.’ The outcome of each of the interactions that has occurred between
the applicant and other objects (e.g., application and the computer; applicant
and the transportation; applicant and the hiring manager; applicant and the
reading of the company’s offer letter) are all events. Each of these events
occurred in some order at certain times, lasting for certain durations. In this
manner, an event is exemplified by the properties or traits of the interacting
objects at a certain time, and at a certain place (Kim 1966; Goldman 1970;
Borghini and Varzi 2006). The precise location of an event can be considered
to be the mereological sum of the locations of the objects (Borghini and Varzi
2006). Events are characterized as having causal effects on other events.
An event occurs because an object transforms EMMI into an output.
Specifically, an event is the result of an interaction (driven by the mechanisms of the two objects). An event is any detectable output from an object.
Events are antecedent or subsequent. The history and future of the project
are summarized by events. The relation(s) between events as objects with
antecedent, subsequent, or concurrent juxtapositions simultaneously in
event-space and the temporal domain define the plan and schedule for the
project. Therefore, events always have an orderliness that is discernable as a
pattern of behavior. Events that do not occur at the time indicated by the plan
are either “early” or “late,” as measured by the temporal reference to the
planned starting time of the event. Events that take shorter or longer than
indicated by the plan are either “ahead of schedule” or “behind schedule,” as
measured by the temporal reference to the planned length of time. Events
that are planned in a certain sequence are either “in order” or “out of order.”
Events that are planned as concurrent are either “in parallel” or “out of
phase.” Figure 6.6 illustrates planning and scheduling for objects as related
by EMMI exchanges through subfunctions.
* Capital letters signify EVENTS.
Précédent

- 328/407

Suivant