How It Fits Together: Methodology Foundation & Core Principles

Last Audited: 2026-08-14
Tier-2 Authoritative
In Plain Language

Deterministic NUP connects its four core concepts into a cohesive, repeatable operating system for regulated engineering. By separating "what to do" (Disciplines and Activities) from "when to do it" (Phases) and "what evidence is produced" (Artifacts), the methodology enables teams to practice agile, incremental development without ever sacrificing regulatory rigor or role accountability.

Separation of "What", "When", and "Evidence"

The power of the Netspective Unified Process lies in its method architecture. Traditional methodologies often blend process steps, job titles, and documents into rigid waterfall stages that break down during agile iterations. NUP solves this by establishing clean boundaries between four core concepts:

WHEN

Lifecycle Phases

Provide the temporal structure and milestone gates for the project.

WHAT DOMAIN

Disciplines

Provide the specialized skills and knowledge domains.

WHAT TASKS

Activities

Define the specific, repeatable units of work executed by roles.

EVIDENCE

Artifacts

Capture the tangible, version-controlled deliverables and audit proof.

Concept Relationship Diagram

The standalone SVG diagram below illustrates how Phases, Disciplines, Activities, and Artifacts interact dynamically:

Phase, Discipline, Activity, and Artifact RelationshipConceptual diagram showing how Lifecycle Phases contain Disciplines, which define Activities performed by Roles, producing and consuming version-controlled Artifacts.Deterministic NUP Foundational OntologySeparating "When" (Phase), "What" (Discipline & Activity), and "Evidence" (Artifact)1. PHASE"When" in LifecycleTime & Milestone Gate• Strategy• Inception / Elaboration• Construction• Transition / ProductionISO 13485 Cl. 7.3.2scopes2. DISCIPLINE"Domain" of Practice24 Specialized Disciplines• Core Engineering• Architecture & Strategy• Compliance & Security• Operations & AI6 Canonical Domainsdefines3. ACTIVITY"What" to PerformUnit of Role-Based Work• Define Requirements• Conduct Peer Review• Run Automated Tests• Audit Verification GateRole Responsibilitiesyields4. ARTIFACT"Evidence" ProducedVersion-Controlled Output• Design History File• Test Protocols & Runs• Architecture ADRs• Traceability MatrixISO 13485 Cl. 7.3.3Artifacts feed into milestone review gates across subsequent Lifecycle Phases
Figure 1: Core Concepts Relationship — Phase (when), Discipline (domain), Activity (action), and Artifact (verifiable output).

Key Methodology Principles

1. Iterative and Incremental Delivery

Regulated software is not built in a single massive phase. Early iterations eliminate architectural risk (Elaboration), while later iterations build production features (Construction) with continuous automated compliance checks.

2. Role-Based Responsibility & Independence

Every activity assigns explicit responsibility to defined roles. To satisfy FDA and ISO standards, verification and review roles maintain independence from authoring roles.

3. Artifact-Centric Audit Tracking

Compliance is proven through version-controlled artifacts, not spoken claims. Traceability matrices dynamically link user needs to code commits, test logs, and risk mitigations.

4. Evidence or Silence (Tier-2 Grounding)

All regulatory claims in NUP are anchored to explicit clauses from ISO 13485, ISO 27001, FDA 21 CFR §820, or IEC 62304, ensuring engineers and auditors share verifiable common ground.

Community Discussion & Feedback

Attributed peer feedback and official Netspective architecture notes.

Was this documentation helpful?(100% found this helpful • 0 ratings)

Leave Feedback or Question

○ Loading user info...
0/2000 chars

Discussion (0)

Loading discussion thread...