Core Concepts: Methodology Overview & Orientation

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

The Netspective Unified Process (NUP) provides a clear, structured way to build software that meets strict quality, security, and healthcare standards. It breaks engineering down into four simple building blocks: when work happens (Phases), what domain of expertise is needed (Disciplines), what specific tasks are performed (Activities), and what verifiable documents or code are produced (Artifacts). Separating these four ideas allows engineering teams to move quickly and deliver iteratively while staying 100% audit-ready for regulators.

The Four Architectural Pillars

In regulated software engineering (such as medical devices, healthcare data systems, and aerospace controls), quality cannot be added as an afterthought. The Netspective Unified Process (NUP) separates development into four distinct dimensions to ensure agility without losing audit readiness:

Dimension 1

Phases ("When")

Lifecycle stages marking high-level business goals and formal milestone review gates.

Dimension 2

Disciplines ("What Domain")

24 specialized capability domains (e.g., Architecture, Verification, Security) that span across phases.

Dimension 3

Activities ("What Tasks")

Specific, role-performed units of work with clear entry criteria and verification steps.

Dimension 4

Artifacts ("Evidence")

Version-controlled deliverables (code, design history files, test reports) proving compliance.

Interactive Exploration Matrix

Explore the 5 Core Concept Pillars

Click any card for deep-dive specifications & regulatory mappings
7 Enterprise ↔ 6 SDLC

Lifecycle Phases

Enterprise Governance ↔ Engineering SDLC

Bridges business milestone gates (Strategy to Production) with sprint-level software development (Discovery to Maintenance).

Dual-View BridgeStage-Gate CriteriaISO 13485 Cl. 7.3.2
Read Deep-Dive Guide
6 Canonical Domains

24 Disciplines

Continuous Capability Across 6 Domains

Organizes specialized professional capabilities—from Software Architecture and SRE to SecOps and AI Engineering.

Core EngineeringOperations & SREArch & SecurityAI/ML Governance
Read Deep-Dive Guide
Role-Performed Work Units

Role Activities

Repeatable Work Breakdown Structures (ABS)

Step-by-step tasks with explicit entry criteria, procedure steps, role assignments, and dual-sign-off exit gates.

Activity BreakdownsEntry & Exit GatesIndependent ReviewAI Practical Callouts
Read Deep-Dive Guide
DHF & Traceability

Formal Artifacts

Version-Controlled Legal & Engineering Evidence

Immutable work products including code, test reports, architecture records, and Design History Files proving compliance.

Requirements SpecsSBOM & Test EvidenceFDA 21 CFR §820 DHFTraceability Matrix
Read Deep-Dive Guide
Interactive Section 508 SVG

How It Fits Together

The Holistic Method Architecture & Core Principles

Separates "what to do" (Disciplines & Activities) from "when/how" (Phases) and "what evidence is produced" (Artifacts) with four core operating principles.

Standalone Relationship SVGWhat vs When/How4 Core PrinciplesQMS Bidirectional Traceability
Read Deep-Dive Guide

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...