Requirements — SMART (Specific, Measurable, Achievable, Relevant, Testable)

3.6.27 · Physics › Spacecraft Structures & Systems Engineering

SMART Kya Hai?

YEH framework kyun? Engineering collaborative hoti hai — dozens of teams parallel mein kaam karte hain. SMART ke bina, Team A woh banata hai jo unhe lagta hai tumne matlab kiya, Team B kuch alag banata hai, aur integration fail ho jaata hai. SMART interpretation ko eliminate karta hai.

Har Criterion Ko Samjhein

Specific

KYA: Requirement exactly batati hai ki kaunsa component/parameter/function constrain ho raha hai, bina kisi multiple interpretation ki gunjaaish ke.

KYUN matter karta hai: Vague requirements design branches banate hain jo diverge ho jaate hain, resources waste hote hain.

Measurable

KYA: Requirement mein quantitative metrics hote hain units, tolerances, aur measurement methods ke saath.

KYUN matter karta hai: "Jo measure nahi ho sakta, woh manage nahi ho sakta." Agar tum usse number nahi de sakte, tum verify ya track nahi kar sakte.

Achievable

KYA: Requirement current ya near-term technology se meet ho sakti hai, budget aur schedule ke andar, bina physics violate kiye.

KYUN matter karta hai: Unrealistic requirements design loops mein time waste karti hain ya jab reality aati hai toh costly redesigns force karti hain.

Achievability verify kaise karein:

Technology Readiness Level (TRL) check: Kya tech kam se kam TRL 6 par hai (system demo in relevant environment)?
Physics limits: Kya yeh thermodynamics, structural load limits, Δv budgets violate karta hai?
Cost/schedule: Kya tum program timeline mein afford kar sakte ho?

Worked example Achievable vs. Impossible

❌ Impossible: "The propulsion system shall provide Δv = 50 km/s using chemical propulsion with dry mass ≤ 100 kg." Kyun impossible? Tsiolkovsky rocket equation: $Δ v = I_{s p} g_{0} ln (\frac{m _{0}}{m _{f}})$ Best chemical $I_{s p} \approx 450$ s, toh $v_{e} = 450 \times 9.81 = 4414$ m/s. $Δ v = 50$ km/s $= 50000$ m/s paane ke liye: $50000 = 4414 ln (\frac{m _{0}}{m _{f}}) ⟹ \frac{m _{0}}{m _{f}} = e^{11.33} \approx 83000$ Agar dry mass 100 kg hai, tumhe 80 lakh kg se zyada propellant chahiye. Physically possible hai lekin ek chhote satellite ke liye bilkul bakwaas.

✅ Achievable: "The propulsion system shall provide Δv ≥ 500 m/s using chemical propulsion (monoprop hydrazine), with propellant mass ≤ 50 kg and dry mass ≤ 10 kg."

Check: $I_{s p} \approx 230$ s (hydrazine), toh $v_{e} = 230 \times 9.81 = 2255$ m/s. Mass ratio = (50+10)/10 = 6. $Δ v = 2255 ln (6) = 2255 \times 1.79 = 4037 m/s$ 500 m/s requirement exceed karta hai. ✅ Existing thrusters se feasible hai.

Relevant

KYA: Requirement upar ki taraf ek mission objective ya parent requirement se trace hoti hai — woh kisi kaam ke liye exist karti hai, sirf bureaucracy ke liye nahi.

KYUN matter karta hai: Irrelevant requirements bina kisi benefit ke cost aur complexity badhate hain. Har requirement ko yeh question answer karna chahiye: "Mission ko yeh kyun chahiye?"

Testable

KYA: Tum verify kar sakte ho ki requirement meet hui hai inn chaar methods mein se kisi ek se:

Test: Physical hardware/software test
Analysis: Mathematical model ya simulation
Inspection: Visual check, measurement
Demonstration: Operational scenario run

KYUN matter karta hai: Untestable requirements unverifiable hoti hain — tum hardware ship karte ho bina yeh jaane ki woh needs meet karta hai ya nahi. Isi se missions fail hote hain.

Formula Domain ke Hisaab se Verification Methods

Requirement Type	Preferred Verification
Structural load capacity	Analysis (FEA) + Test (load test to qualification level)
Power generation	Test (measure actual output under simulated sun)
Software function	Test (unit/integration tests) + Demo (end-to-end scenario)
Dimensional tolerance	Inspection (CM measurement)
Thermal limits	Analysis (thermal model) + Test (thermal-vacuum chamber)
Derivation: Yeh requirement ke physical domain se aate hain. Tum woh test karte ho jo directly measure ho sake (power output), woh analyze karte ho jo full scale par test karna impractical ho (reentry heating), geometry inspect karte ho, aur complex behaviors demonstrate karte ho.

Common Requirements Pitfalls

Common mistake Galti 1: "Shall be designed to..."

❌ Bura: "The structure shall be designed to withstand launch loads." Kyun sahi lagta hai: Lagta hai tum robust design maang rahe ho.

Kyun galat hai: "Designed to" ek process requirement hai (engineers ko kya karna chahiye yeh bataata hai), performance requirement nahi (end product ko kya achieve karna chahiye). Yeh verifiable nahi hai — tum test nahi kar sakte ki kisi ne kuch "designed to" kiya ya nahi.

✅ Fix: "The structure shall survive launch loads of ≥ 8g axial and ≥ 4g lateral quasi-static, verified by analysis and qualification testing to 1.25× design limit loads."

Steel-man: Bura version try karta hai ensure karna ki engineers launch loads consider karein. Lekin requirements outcomes constrain karti hain, design process nahi. Engineers ko decide karne do ki performance target kaise meet karein.

SMART Requirements Likhna: Step-by-Step

HOW to transform a vague need into SMART:

Need identify karo (user story): "Humein satellite ko Earth ki taraf pointed rakhna hai."
Specific banao: Kaunsa parameter? Attitude pointing.
Measurable banao: "Pointing error ≤ 0.1° (3σ) nadir-pointing."
Achievable check karo: Star tracker + reaction wheels 0.01° easily kar sakte hain, toh 0.1° conservative hai. ✅
Relevant banao: GSD ke liye imaging payload requirement se trace hota hai. ✅
Testable banao: "Verified by attitude determination accuracy in ground test + on-orbit telemetry analysis."

Final SMART requirement: "The ADCS shall maintain nadir-pointing attitude with error ≤ 0.1° (3σ) in pitch and roll axes during imaging operations, verified by post-processed telemetry analysis using star tracker and GPS data."

Recall SMART ko 12-Saal ke Bacche ko Explain Karo

Socho tumne apne dost se kaha ki mere birthday ke liye cake banao. Agar tum sirf kaho "cake banao," toh kya milega? Shayad chocolate, shayad vanilla, shayad jala hua, shayad tiny, shayad woh try hi nahi karega kyunki use lagta hai yeh bahut mushkil hai!

Lekin agar tum kaho: "Ek round chocolate cake banao, 10 inches across, 2 layers ke saath, jo achcha lage, Saturday tak, aur jab ho jaaye toh photo dikhao" — ab tumhare dost ko exactly pata hai kya karna hai!

SMART requirements us recipe jaisi hain:

Specific: Round, chocolate, 2 layers (sirf "cake" nahi)
Measurable: 10 inches across (ruler se measure kar sakte ho!)
Achievable: Tumhara dost bake karna jaanta hai aur uske paas oven hai
Relevant: Yeh tumhari birthday party ke liye hai, toh matter karta hai
Testable: Tum photo dekh sakte ho aur taste kar sakte ho check karne ke liye Spacecraft ke liye, agar tum engineers ko kaho "space mein kaam karo" (vague), toh kuch aisa mil sakta hai jo toot jaaye. Lekin "-150°C to +120°C temperature survive karo" (SMART) — ab woh build aur test kar sakte hain!

Connections

Systems Engineering V-Model — SMART requirements verification steps ko feed karte hain
Requirements Traceability Matrix — Relevant criterion track karta hai
Verification and Validation — Testable criterion V&V se link hota hai
Technology Readiness Levels (TRL) — Achievable assess karne ke liye use hota hai
Mass Budget — Measurable requirements budget allocations drive karte hain
Failure Modes and Effects Analysis (FMEA) — Missing requirements identify karta hai
Interface Control Document (ICD) — Interface requirements SMART format mein hote hain
Tsiolkovsky Rocket Equation — Achievable propulsion requirements ke liye physics limit

#flashcards/physics

SMART requirements mein S kya stand karta hai aur yeh kyun matter karta hai? :: Specific — unambiguous with clear scope. Matter karta hai kyunki vague requirements alag-alag teams ko incompatible interpretations banane par majboor karti hain, resources waste hote hain aur integration failures aati hain.

SMART requirements mein M kya stand karta hai?

Measurable — quantitative metrics with units, tolerances, aur measurement methods include karta hai. Jo measure nahi ho sakta woh verify nahi ho sakta.

SMART requirements mein A kya stand karta hai?

Achievable — current ya near-term technology ke saath technically aur economically feasible, budget aur schedule ke andar, bina physics violate kiye (TRL, physics limits, cost/schedule analysis se check hota hai).

SMART requirements mein R kya stand karta hai?

Relevant — mission objectives ya parent requirements se upar ki taraf trace hota hai. Har requirement ko yeh answer karna chahiye "Mission ko yeh kyun chahiye?" taaki unnecessary cost aur complexity na bade.

SMART requirements mein T kya stand karta hai?

Testable — Test, Analysis, Inspection, ya Demonstration se verify ho sake. Untestable requirements unverifiable hoti hain, jo potential mission failure lead karti hain.

Testable requirements ke liye chaar verification methods kya hain?

(1) Test - physical hardware/software testing, (2) Analysis - mathematical model ya simulation, (3) Inspection - visual check ya measurement, (4) Demonstration - operational scenario run.

"Shall be designed to..." ek buri requirement phrase kyun hai?

Yeh ek process requirement hai (kaam karne ka tarika bataata hai) na ki performance requirement (kaunsa outcome achieve karna hai). Yeh unverifiable hai — tum test nahi kar sakte ki kisi ne kuch "designed to" kiya ya nahi. Requirements outcomes constrain karti hain, design process nahi.

Requirements mein "as much as possible" problematic kyun hai?

Measurable nahi — koi clear target ya pass/fail criteria nahi. Engineers infinite time optimizing mein laga sakte hain ya kuch nahi karenge aur claim karenge unhone try kiya. Specific numerical targets se replace karo (jaise "≤ 15 W average power").

Kaunsa formula template requirement ko Measurable banata hai?

Parameter {≤, ≥, =} Value ± Tolerance [units] under Conditions. Numerical value, units, comparison operator, aur environmental conditions physical meaning aur bounded applicability ke liye include karta hai.

Rocket equation use karke yeh check kaise karein ki ek propulsion requirement Achievable hai?

Tsiolkovsky equation use karo: Δv = Isp·g₀·ln(m₀/mf). Diye gaye Δv aur propellant Isp ke liye required mass ratio calculate karo, mass budget constraints aur tank/engine technology limits ke against verify karo.