Package Relationships Sample Clauses

Package Relationships. The Infrastructure::CoreConstructs::Relationships subpackage of EAST-ADL2 defines general- purpose relationship constructs that may be used to model dependencies between structural constructs. The purpose of the metaclasses in the Infrastructure::CoreConstructs::Relationships domain metamodel package is to specify rigorously ("formally") the various relationships that may exist between ADL basic constructs. 6.2.3.1 EAST-ADL2 – Construct for Relationships, «ADLRelationship« The EAST-ADL2 construct for relationships makes it possible for various relationships in the language to be owned by a specific context. A specialization of a relationship is for example the EAST-ADL2 satisfy requirement relationship. 6.2.3.2 EAST-ADL2 – Derive Requirements Relationship, «ADLDeriveReq« The derive requirement relationship in EAST-ADL2 is an automotive specialization of the SysML derive requirement relationship [4]. The EAST-ADL2 derive requirement relationship signifies a dependency relationship in-between two sets of EAST-ADL2|SysML requirement constructs, showing the relationship when a set of derived client EAST-ADL2|SysML requirements are derived from a set of supplier EAST-ADL2|SysML requirements. As with other UML dependencies [4] the dependency arrow direction points from the derived (client) EAST-ADL2|SysML requirement, to the (supplier) EAST-ADL2|SysML requirement. The following constraints apply to the EAST-ADL2 derive requirement relationship: [1] The first and second constraint in the SysML specification related to derive requirement relationship [4] is not applicable. [2] The supplier must be an element stereotyped by EAST-ADL2|SysML requirement or one of EAST-ADL2|SysML requirement subtypes. [3] The client must be an element stereotyped by EAST-ADL2|SysML requirement or one of EAST-ADL2|SysML requirement subtypes. 6.2.3.3 EAST-ADL2 – Refine Requirements Relationship, «ADLRefine« The refine requirement relationship in EAST-ADL2 signifies a dependency relationship in-between an EAST-ADL2|SysML requirement and an EAST-ADL2 entity, showing the relationship when a client EAST-ADL2 entity construct refines the supplier EAST-ADL2|SysML requirement. As with other UML dependencies [4] the arrow direction points from the EAST-ADL2 entity that refines the EAST-ADL2|SysML requirement to the refined (supplier) EAST-ADL2|SysML requirement. The following constraints apply to the EAST-ADL2 refine requirement relationship: [1] The supplier must be an element stereotyped by E...
View Source

Related to Package Relationships

  • Customer Relationships The Executive understands and acknowledges that the Company has expended significant resources over many years to identify, develop, and maintain its clients. The Executive additionally acknowledges that the Company’s clients have had continuous and long-standing relationships with the Company and that, as a result of these close, long-term relationships, the Company possesses significant knowledge of and confidential information about its clients and their needs. Finally, the Executive acknowledges the Executive’s association and contact with these clients is derived solely from Executive’s employment with the Company. The Executive further acknowledges that the Company does business throughout the United States and that the Executive personally has significant contact with the Company’s clients and customers solely as a result of Executive’s relationship with the Company.

  • EMPLOYMENT RELATIONSHIPS The ORGANIZATION, its employees, volunteers or agents performing under this Agreement are not deemed to be employees of the COUNTY, nor volunteers or agents of the COUNTY in any manner whatsoever. No officer, employee, volunteer or agent of the ORGANIZATION will hold themselves out as, or claim to be, an officer, employee, volunteer or agent of the COUNTY by reason hereof, nor will they make any claim, demand or application to or for any right or privilege applicable to an officer, employee volunteer or agent of the COUNTY. The parties agree that the COUNTY will not be responsible for the payment of any industrial insurance premiums or related claims or other benefits that may arise during the performance of services under this Agreement for any ORGANIZATION employee or volunteer, or for any consultant’s, contractor’s or subcontractor’s employee(s) or agent(s) that has been retained by the ORGANIZATION.

  • Certain Relationships No relationship, direct or indirect, exists between or among either of the Transaction Entities, on the one hand, and the directors, officers, stockholders, partners, customers or suppliers of the Transaction Entities, on the other hand, which is required to be described in the Registration Statement, the General Disclosure Package or the Prospectus which is not so described.

  • Lending Relationships Except as disclosed in the Pricing Disclosure Package, Registration Statement and the Prospectus, the Company (i) does not have any material lending or other relationship with any bank or lending affiliate of the Underwriters and (ii) does not intend to use any of the proceeds from the sale of the Securities hereunder to repay any outstanding debt owed to any affiliate of the Underwriters.

  • Relationships Nothing contained in this Agreement shall be deemed to constitute either party a partner, joint venturer or employee of the other party for any purpose.