Isse pehle ki tum judge karo ki koi requirement "Specific" hai ya "Measurable", tumhe us chhoti si alphabet ke symbols mein fluent hona padega jo parent note quietly use karta hai. Yeh page unhe ek-ek karke zero se build karta hai. Ise upar se neeche padho — har symbol use hone se pehle samjhaya gaya hai.
Picture. Ek number line socho — ek ruler jo left (chhota) se right (bada) tak jaata hai. Ek requirement us ruler par ek region paint karta hai jahan real spacecraft land kar sakta hai.
Topic ko yeh kyun chahiye. Parent note likhta hai "mass ≤150 kg". Yeh koi wish nahi hai — yeh ruler par ek line drawn hai. Koi bhi bana hua satellite jiska mass green region mein aata hai (line ke left) pass karta hai; kuch bhi right mein fail karta hai. Falsifiability poori tarah is picture mein rehti hai: ek requirement tab acchi hoti hai jab woh ek clear line draw kare taaki tum point karke keh sako "hum pass side par hain."
Is chapter mein baaki har unit inhe multiply aur divide karke bani hai — isliye kisi number ko kuch matlab hone ke liye unit chahiye.
Picture. "150" akela 150 grams (ek phone) bhi ho sakta hai ya 150 tonnes (ek truck). Sirf unit hi fix karti hai ki hum ruler par kaun se tick-marks count kar rahe hain.
Symbol
Padha jaata hai
Base-unit composition
Measure karta hai
kg
kilogram
(base)
mass (kitna stuff)
m/s
metres per second
m⋅s−1
speed / velocity change
N
newton
kg⋅m⋅s−2
force (ek push ya pull)
J
joule
kg⋅m2⋅s−2
energy
W
watt
kg⋅m2⋅s−3
power (energy per second)
N⋅m
newton-metre
kg⋅m2⋅s−2
torque (ek twist)
N⋅m⋅s
newton-metre-second
kg⋅m2⋅s−1
angular momentum (stored spin)
(Note: chhote raised numbers jaise s−2 exponents hain — "kitni baar multiply kiya" wali notation jo Section 5 mein define ki gayi hai. s−2 ka matlab hai "seconds se do baar divide kiya".)
Topic ko yeh kyun chahiye. SMART mein M — Measurable — literally yeh hai ki "requirement mein ek unit hai." Units ke bina, "generate ≥2.5" falsifiable nahi hai: 2.5 kya? Watts, kilowatts, horsepower? Dekho Mass Budget aur Interface Control Document (ICD), jahan har line ek number-plus-unit hai exactly isi liye.
Picture. Koi bhi factory kuch bhi exactly nahi banati. Toh ek razor-thin line ki jagah, tolerance ruler par ek band draw karta hai.
2.5kW±5%⟺allowed range [2.375,2.625]kW
Topic ko yeh kyun chahiye. Real hardware degrade aur vary karta hai. Tolerance ke bina ek requirement secretly perfection maangti hai, jo koi test kabhi pass nahi kar sakta. Tolerance hi hai jo ek measurable requirement ko ek hi saath achievable aur testable banati hai.
Gaussian assumption. "68% / 99.7%" rules universal nahi hain — yeh tab hold karte hain jab scatter bell-shaped normal (Gaussian) distribution follow kare, jo measurement noise aksar karta hai. Us specific curve ke under, mean ke ±kσ ke andar aane wale measurements ka fraction ek fixed number hota hai:
±1σ≈68.3%,±2σ≈95.4%,±3σ≈99.7%.
Yeh percentages sirf un limits ke beech bell curve ke neeche ka area hain — picture ise concrete banati hai.
Topic ko yeh kyun chahiye. Parent ki traceability example altitude knowledge "±5 m (3σ)" ki maang karti hai. 3σ attach karna (Gaussian assumption ke under) ek vague "accurate" ko ek statistical promise mein badal deta hai: roughly 1000 mein 3 se zyada baar fail mat karo. Yahi ek accuracy requirement ko genuinely testable banata hai — dekho Verification and Validation.
Pehle woh notation jo rocket equation mein likhi jaati hai — exponentiation.
Parent ka Achievable example Tsiolkovsky Rocket Equation par lean karta hai, jo ek special base ko power par raise karta hai. Ise zero se banao.
Picture.ex ek curve hai jo tezi se upar rocket karti hai. ln(x) wahi curve hai diagonal line ke across reflect ki gayi — pehle tezi se chadhti hai, phir crawl karti hai, aur sirf x=0 ke right mein exist karti hai. Yeh mirror images hain kyunki ek doosre ko undo karta hai.
Yeh tool kyun, simple division kyun nahi? Rocket jo velocity gain karta hai woh fuel add karne ke proportional nahi badhti — fuel ka har extra kilo bhi carry aur accelerate karna padta hai. Woh "diminishing return" exactly wahi hai jo ln capture karta hai. Rocket equation mein,
Δv=Ispg0ln(mfm0)
Δv ko double karne ke liye mass ratio m0/mf ko square karna padta hai, double nahi — woh brutal maths jo "chemistry par Δv=50 km/s" ko absurd banata hai.
Picture. Ek staircase socho "napkin sketch" (bottom) se "flight-proven" (top) tak. Parent ka Achievable test — "kya yeh kam se kam TRL 6 par hai?" — puch raha hai ki technology real mission par trust kiye jaane ke liye kaafi upar chadh chuki hai. Full ladder: Technology Readiness Levels (TRL).
Neeche diya diagram dikhata hai ki har foundation agla kaisa feed karta hai. Ise ek flow ki tarah padho: comparison operators aur base units (top) raw grammar hain; tolerance aur σ (units se bane) ek stated number ko honest banate hain; exponents/ln TRL ke saath milke Achievable check feed karte hain; aur yeh sab ek single SMART requirement par converge karta hai, jo phir verification mein flow karta hai.
Shabdon mein, chain padha jaata hai: operators + units ek number ko kuch matlab dete hain → tolerance aur σ us number ko honest banate hain → exponents, ln aur TRL check karne dete hain ki yeh possible hai → milke yeh requirement ko testable banate hain.