Finding answers to questions in a text document

At a glance

Project structure

Source bundle/
├── FindingAnswers/
│   ├── App/
│   │   └── AppDelegate.swift
│   ├── View/
│   │   ├── DetailViewController.swift
│   │   ├── Document.swift
│   │   └── MainViewController.swift
│   └── Model/
│       ├── BERT.swift
│       ├── BERTInput.swift
│       ├── BERTVocabulary.swift
│       ├── TokenizedString.swift
│       └── BERTOutput.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── FindingAnswers.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 7 project/configuration file(s) and 8 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["DetailViewController"]
    N3["Document"]
    N4["CoreML APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

FindingAnswers/App/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UISplitViewControllerDelegate {
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Core ML.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    DetailViewController o-- UITextField : questionTextField
    DetailViewController o-- UITextView : documentTextView
    DetailViewController o-- NSLayoutConstraint : questionTextFieldBottomLayoutConstraint

Ownership evidence

FindingAnswers/App/AppDelegate.swift:13 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UISplitViewControllerDelegate {
    // ...
    var window: UIWindow?
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

FindingAnswers/App/AppDelegate.swift:11 — representative type boundary

class AppDelegate: UIResponder, UIApplicationDelegate, UISplitViewControllerDelegate {
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

FindingAnswers/Model/BERTInput.swift:25 — representative boundary

    private let documentOffset: Int

    var documentRange: Range<Int> {
        return documentOffset..<documentOffset + document.tokens.count
    }

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Controller: DetailViewController, MainViewController; Delegate: AppDelegate; Document: Document.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, splitViewController, configureView, viewDidLoad, textFieldShouldReturn, textFieldShouldClear, textViewDidEndEditing, viewWillAppear.
• Files: FindingAnswers/App/AppDelegate.swift, FindingAnswers/View/DetailViewController.swift, FindingAnswers/View/Document.swift, FindingAnswers/View/MainViewController.swift, FindingAnswers/Model/BERT.swift, FindingAnswers/Model/BERTInput.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches CoreML, UIKit, NaturalLanguage through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation