Header Image
Requirements : Public Package PackageDependencies, DomainModel
A requirement expresses a condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed properties.<br/><br/>Requirements can be introduced in different phases of the development process for different reasons. They could be introduced by marketing people, control engineers, system engineers, software engineers, Driver/OS developers, basic software developers or hardware engineers. This leads to the fact that requirements have many sources, and requirements are of many types (at different levels of detail) and have several relations between them. Under these conditions the number of requirements can become quickly unmanageable if appropriate management does not exist. Note that, requirements can change during the project development and the changes should be taken into account. Requirements are organized hierarchically through several kinds of refinement relations.<br/><br/>EAST-ADL has constructs that deal with these problems. Some of these constructs deals with general issues in software development and have been already addressed in the past by general processes. As done for the structure part of EAST-ADL, the requirements part will be compliant with UML2. The EAST-ADL adapts existing concepts whenever possible and develops new ones otherwise.<br/><br/>Elements inspired by SysML are Requirement, Satisfy, Refine, DeriveRequirement, and Verify.<br/><br/><br/><br/><br/>
  • Other Links
Object Type Connection Direction Notes
VerificationValidation Package Nesting From  
Structure Package Dependency To PrecedenceConstraint -> ADLFunctionPrototype UserAttributes
Behavior Package Dependency To  
UseCases Package Nesting From  
Dependability Package Dependency From ADLRequirement
EAST-ADL Package Nesting To  
VerificationValidation Package Dependency From ADLVerify -> ADLRequirement