Part 1: Front-end, back-end, APIs and requirements

Module 9 · Sun 13 Sep, morning

PM tech fluency-na engineers kooda nalla work panradhu - feasibility, clarity - coding illa. Flow: user front-end la action pannuvaanga (kannula theriyuradhu) → API request ah edutthu pogum (messenger) → back-end, database rules apply panni state ah store pannum. Endpoint-na front-end call pannura URL.

• HTTP methods: GET = edu, POST = create, PATCH = update, DELETE = remove. Class cart example: menu paakradhu GET; cart la add panradhu POST, back-end mukkiyamana fields ah check pannum.
• Status codes: 200 OK, 201 created, 204 success, content illa, 400 thappana input, 401 login aagala, 403 permission illa, 500 server error. Code back-end oda; adutha user enna paakuraanga nu PM dhaan decide pannanum.
• Clear API contracts front-end/back-end rework ah thadukkum.

Functional requirements = system enna pannum (acceptance criteria vechu testable). Non-functional requirements = evlo nalla: latency (round-trip time), availability, rate limiting (oru time window la requests ku cap - expected usage, risk ah poruthu), scalability.

PM product behaviour, strategy own pannuvaanga; BA usually requirement gathering, docs. PM raw API logs illa, events, analytics vechu behaviour paapaanga. Feature by feature usage forecast pannu. Rule of thumb: measurable targets vei, success um failure um design pannu.