Requirements

Filesystem Library Requirements		status: draft security: YES safety: ASIL_B
tags: requirements, filesystem_library realizes: wp__requirements_comp
doc__filesystem_lib_requirements		Generic Document

Functional Requirements

Standard Filesystem Abstraction		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional satisfies: feat_req__baselibs__consistent_apis, feat_req__baselibs__filesystem_library
The Filesystem library shall provide filesystem API based on the C++ standardization.
comp_req__filesystem__api_abstraction		Component Requirement

Path Manipulation Utilities		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional satisfies: feat_req__baselibs__consistent_apis, feat_req__baselibs__filesystem_library
The Filesystem library shall provide type-safe utilities for path construction and manipulation.
comp_req__filesystem__path_utilities		Component Requirement

Directory Iterators		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional satisfies: feat_req__baselibs__filesystem_library
The Filesystem library shall provide directory iterator types for traversing directory contents.
comp_req__filesystem__directory_iterators		Component Requirement

File I/O Operations		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional satisfies: feat_req__baselibs__filesystem_library
The Filesystem library shall provide functionality for reading from and writing to files, including buffered I/O operations.
comp_req__filesystem__file_io		Component Requirement

Fully testable public API		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Non-Functional satisfies: feat_req__baselibs__filesystem_library
The public API of the library shall support dependency injection with test doubles. Note: This enables full testability of the user code.
comp_req__filesystem__full_testability		Component Requirement

File Utility Functions		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional satisfies: feat_req__baselibs__filesystem_library
The Filesystem library shall provide additional file utility functions, such as temporary file handling and file comparison.
comp_req__filesystem__file_utils		Component Requirement

Mock and Fake Implementations		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Non-Functional satisfies: feat_req__baselibs__filesystem_library
The Filesystem library shall provide mock and fake implementations for unit testing and validation.
comp_req__filesystem__mock_fake		Component Requirement

Assumptions of Use (AoU)

Low-Level Use Only		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional
Users shall use this library only when they need to manipulate files, directories, and paths at the operating system level beyond what higher-level storage abstractions provide, accepting reduced portability to other platforms.
aou_req__filesystem__low_level_use_only		Assumption of Use Requirement

Supported Path Formats		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional
Users shall not use Windows paths with this library.
aou_req__filesystem__supported_path_formats		Assumption of Use Requirement

Error Handling		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Functional
Users shall handle all function return values and take appropriate action on errors.
aou_req__filesystem__error_handling		Assumption of Use Requirement

Thread Safety		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Non-Functional
Users shall implement appropriate synchronization mechanisms when accessing shared filesystem resources concurrently.
aou_req__filesystem__thread_safety		Assumption of Use Requirement

Performance		status: valid security: NO safety: ASIL_B
tags: baselibs reqtype: Non-Functional
Users shall not assume any performance characteristics. Note: Filesystem operations are subject to underlying OS and storage performance.
aou_req__filesystem__performance		Assumption of Use Requirement