it:ad:supplemental_specifications:home

IT:AD:Supplemental Specifications

Functional SpecificationsDomain Functional RequirementsSupplemental SpecificationsPrinciplesSystem ConstraintsSystem Functional RequirementsNon-Functional Requirements

Supplemental SpecificationsPrinciplesSystem ConstraintsSystem Functional RequirementsNon-Functional RequirementsPerformance EfficiencyTime behavior-Response time-Recovery time-Start-up time-Shutdown timeResource UtilizationCapacity (Throughput)CompatibilityCo-ExistenceInteroperabilityUsabilityAppropriateness recognizabilityLearnabilityOperabilityUser Error ProtectionUser Interface AestheticsAccessibilityReliabilityReliabilityMaturityAvailabilityFault ToleranceRecoverabilitySecurityConfidentialityIntegrityNon-RepudiationAccountabilityAuthenticity-PrivacyMaintainabilityModularityReusabilityAnalysabilityModifiability-StabilityTestability-Configurability-Installability-Scalability-LocalizabilityPortabilityAdaptabilityInstallabilityReplaceabilityDesignArchitecturalInfrastructuralImplementationCoding standardsLanguageResource limitsInterfaceProtocolFormatScheduleThroughputPhysicalLocationShapeSizeWeight

* Advantages:

* Considerations: * Disadvantages:

  • The term Supplemental in an unfortunate choice: stakeholders do not readily see their value, instead perceiving the supplemental specifications as “afterthoughts” to IT:AD:Domain Functional Requirements.