The notation "SSIS-109" could refer to:
A compact federal agency in a mid-sized U.S. city. The server room is a cluttered, half-basement space; SSIS-109 runs on an old rack of machines, its interfaces primitive, its documentation outdated.
A simulated breach exercise forces teams to identify the malicious payload injected via a compromised npm package, isolate affected containers, and produce an incident report. SSIS-109
Assessment is multifaceted to capture the diverse competencies outlined earlier:
| Assessment | Weight | Rationale | |------------|--------|-----------| | Conceptual Mapping Paper (2,000 words) | 15% | Tests theoretical integration. | | Quantitative Lab Report | 20% | Evaluates statistical reasoning and coding skills. | | Qualitative Coding Portfolio | 15% | Assesses depth of interpretive analysis. | | Mixed‑Methods Project Proposal | 20% | Gauges ability to design coherent interdisciplinary studies. | | Policy Brief & Oral Defense | 20% | Measures translation of research into actionable recommendations. | | Participation & Peer Review | 10% | Encourages engagement and critical feedback. | The notation "SSIS-109" could refer to: A compact
The rubric emphasizes process (e.g., documentation, ethical considerations) as much as product, reinforcing the course’s holistic learning philosophy.
The capstone project is the heart of SSIS‑109. Teams of 3‑5 students are given a scenario—for instance, “build a secure, multi‑tenant marketplace that integrates payment processing, shipping APIs, and third‑party recommendation engines.” The project lifecycle follows: A simulated breach exercise forces teams to identify
Evaluation emphasizes process (risk assessment, secure design decisions) as much as output (functional code).
Students design a reference architecture for a multi‑tenant SaaS product, documenting how each layer mitigates identified threats.