Show pageOld revisionsBacklinksBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. # IT:AD:Requirements:Diagrams # * [[./|(UP)]] {{indexmenu>.#2|nsort tsort}} <panel title="Summary"> </panel> ## Diagrams ### Requirements Requirements and Supplemental Specifications look as follows: ##### Requirements Diagram <uml> skinparam monochrome true '================================================= object "Functional Specifications" as FS { } object "Domain Functional Requirements" as DFR{ } object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { } object "Non-Functional Requirements" as NFR { } '================================================= FS o-- DFR SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#Requirements Diagram¬itle&nofooter}} </sxh> ### System Functional Requirements ##### System Functional Requirements Diagram <uml> skinparam monochrome true '================================================= object "Functional Specifications" as FS { Completeness Correctness Appropriateness } object "Domain Functional Requirements" as DFR{ } object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { DateTime Diagnostics Caching Host Settings Data Access Authentication Authorisation Auditing Assistance Cryptographic Services Licensing etc. } object "Non-Functional Requirements" as NFR { } '================================================= FS o-- DFR SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#System Functional Requirements Diagram¬itle&nofooter}} </sxh> ##### System Functional Requirements Diagram 2 <uml> skinparam monochrome true '================================================= object "System Functional Requirements" as SFR { DateTime Diagnostics Caching Host Settings Data Access Authentication Authorisation Auditing Assistance Cryptographic Services Licensing etc. } note bottom of SFR Completeness Correctness Appropriateness end note '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#System Functional Requirements Diagram 2¬itle&nofooter}} </sxh> ### Non-Functional Requirements ##### Non-Functional Requirements Diagram <uml> skinparam monochrome true '================================================= object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { } object "Non-Functional Requirements" as NFR { } '================================================= object "Performance Efficiency" as PE { Time behavior - -Response time - -Recovery time - -Start-up time - -Shutdown time Resource Utilization Capacity (Throughput) } object Compatibility { Co-Existence Interoperability } object Usability { Appropriateness recognizability Learnability Operability User Error Protection User Interface Aesthetics Accessibility } object Reliability { Reliability Maturity Availability Fault Tolerance Recoverability } object Security { Confidentiality Integrity Non-Repudiation Accountability Authenticity - -Privacy } object Maintainability { Modularity Reusability Analysability Modifiability - -Stability Testability - -Configurability - -Installability - -Scalability - -Localizability } object Portability { Adaptability Installability Replaceability } '================================================= SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= NFR o-- PE NFR o-- Compatibility NFR o-- Usability NFR o-- Reliability NFR o-- Security NFR o-- Reliability NFR o-- Maintainability NFR o-- Portability '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#Non Functional Requirements Diagram 2¬itle&nofooter}} </sxh> ### System Constraints The [[IT/AD/System Constraints/]] in turn look as follows: ##### System Constraints Diagram <uml> skinparam monochrome true '================================================= object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { } object "Non-Functional Requirements" as NFR { } '================================================= object Design { Architectural Infrastructural } object Implementation { Coding standards Language Resource limits } object Interface { Protocol Format Schedule Throughput } object Physical { Location Shape Size Weight } '================================================= SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= CONS o-- Design CONS o-- Implementation CONS o-- Interface CONS o-- Physical '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#System Constraints Diagram¬itle&nofooter}} </sxh> ### Supplemental Specifications The [[IT/AD/Supplemental Specifications/]] in turn look as follows: ##### Supplemental Specifications Diagram <uml> skinparam monochrome true '================================================= object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { DateTime Diagnostics Caching Host Settings Data Access Authentication Authorisation Auditing Assistance Cryptographic Services Licensing etc. } object "Non-Functional Requirements" as NFR { } '================================================= object "Performance Efficiency" as PE { Time behavior - -Response time - -Recovery time - -Start-up time - -Shutdown time Resource Utilization Capacity (Throughput) } object Compatibility { Co-Existence Interoperability } object Usability { Appropriateness recognizability Learnability Operability User Error Protection User Interface Aesthetics Accessibility } object Reliability { Reliability Maturity Availability Fault Tolerance Recoverability } object Security { Confidentiality Integrity Non-Repudiation Accountability Authenticity - -Privacy } object Maintainability { Modularity Reusability Analysability Modifiability - -Stability Testability - -Configurability - -Installability - -Scalability - -Localizability } object Portability { Adaptability Installability Replaceability } '================================================= object Design { Architectural Infrastructural } object Implementation { Coding standards Language Resource limits } object Interface { Protocol Format Schedule Throughput } object Physical { Location Shape Size Weight } '================================================= SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= NFR o-- PE NFR o-- Compatibility NFR o-- Usability NFR o-- Reliability NFR o-- Security NFR o-- Reliability NFR o-- Maintainability NFR o-- Portability '================================================= CONS o-- Design CONS o-- Implementation CONS o-- Interface CONS o-- Physical '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#Supplemental Specifications Diagram¬itle}} </sxh> ##### Supplemental Specifications Diagram 2 <uml> skinparam monochrome true '================================================= object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { } object "Non-Functional Requirements" as NFR { } '================================================= object "Performance Efficiency" as PE { Time behavior - -Response time - -Recovery time - -Start-up time - -Shutdown time Resource Utilization Capacity (Throughput) } object Compatibility { Co-Existence Interoperability } object Usability { Appropriateness recognizability Learnability Operability User Error Protection User Interface Aesthetics Accessibility } object Reliability { Reliability Maturity Availability Fault Tolerance Recoverability } object Security { Confidentiality Integrity Non-Repudiation Accountability Authenticity - -Privacy } object Maintainability { Modularity Reusability Analysability Modifiability - -Stability Testability - -Configurability - -Installability - -Scalability - -Localizability } object Portability { Adaptability Installability Replaceability } '================================================= object Design { Architectural Infrastructural } object Implementation { Coding standards Language Resource limits } object Interface { Protocol Format Schedule Throughput } object Physical { Location Shape Size Weight } '================================================= SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= NFR o-- PE NFR o-- Compatibility NFR o-- Usability NFR o-- Reliability NFR o-- Security NFR o-- Reliability NFR o-- Maintainability NFR o-- Portability '================================================= CONS o-- Design CONS o-- Implementation CONS o-- Interface CONS o-- Physical '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#Supplemental Specifications Diagram 2¬itle}} </sxh> ### Complete Overview Putting all together looks as follows: ##### Complete Requirements Diagram <uml> skinparam monochrome true '================================================= object "Functional Specifications" as FS { } object "Domain Functional Requirements" as DFR{ } object "Supplemental Specifications" as SS{ } object "Principles" as PRINC{ } object "System Constraints" as CONS { } object "System Functional Requirements" as SFR { DateTime Diagnostics Caching Host Settings Data Access Authentication Authorisation Auditing Assistance Cryptographic Services Licensing etc. } object "Non-Functional Requirements" as NFR { } '================================================= object "Performance Efficiency" as PE { Time behavior - -Response time - -Recovery time - -Start-up time - -Shutdown time Resource Utilization Capacity (Throughput) } object Compatibility { Co-Existence Interoperability } object Usability { Appropriateness recognizability Learnability Operability User Error Protection User Interface Aesthetics Accessibility } object Reliability { Reliability Maturity Availability Fault Tolerance Recoverability } object Security { Confidentiality Integrity Non-Repudiation Accountability Authenticity - -Privacy } object Maintainability { Modularity Reusability Analysability Modifiability - -Stability Testability - -Configurability - -Installability - -Scalability - -Localizability } object Portability { Adaptability Installability Replaceability } '================================================= object Design { Architectural Infrastructural } object Implementation { Coding standards Language Resource limits } object Interface { Protocol Format Schedule Throughput } object Physical { Location Shape Size Weight } '================================================= FS o-- DFR SS o-- PRINC SS o-- CONS SS o-- SFR SS o-- NFR '================================================= NFR o-- PE NFR o-- Compatibility NFR o-- Usability NFR o-- Reliability NFR o-- Security NFR o-- Reliability NFR o-- Maintainability NFR o-- Portability '================================================= CONS o-- Design CONS o-- Implementation CONS o-- Interface CONS o-- Physical '================================================= </uml> ##### Tip Embed as follows: <sxh> {{page>IT:AD:Requirements:Diagrams#Complete Requirements Diagram¬itle}} </sxh> /home/skysigal/public_html/data/pages/it/ad/requirements/diagrams.txt Last modified: 2023/11/04 03:30by 127.0.0.1