CSE Roadmap

Core tier · about 2 hours · 9 parts

Part 9 of 9 · 3 min read

Exercises

Easy

Easy 1: Functional or not? (15 minutes)

Sort these into functional and non-functional: (a) a user can delete an account, (b) pages load in under one second, (c) the service stays up 99.9 percent of the time, (d) a user can follow another user, (e) data is encrypted when stored, (f) the app supports 1 million users.

Done when: six lines, each marked functional or non-functional with a four-word reason.

Hint

Ask "does this say what the system does, or how well?".

Easy 2: Five questions (15 minutes)

A friend asks you to design "an app for a food truck". Write five questions you would ask first, one from each group in section 2.

Done when: five questions, one for features, users, size, growth and limits.

Hint

One question per group: features, users, size, growth, limits.

Easy 3: Make it checkable (20 minutes)

Rewrite each as a checkable sentence with a number and a unit: (a) "the site must be fast", (b) "many users are expected", (c) "storage must be big enough", (d) "the app must rarely go down".

Done when: four rewritten sentences, each with a number, a unit and a way to measure it.

Hint

Use the pattern "99 out of 100 requests in under N milliseconds", or "N users each day".

Medium

Medium 1: Scope the product (25 minutes)

The request is "design a video call app for teachers and students". Write the scope: three core features, three later features and three out-of-scope items.

Done when: nine items in three lists, and one sentence saying why the first core feature is first.

Hint

Core features are the ones without which the app has no point.

Medium 2: Numbers from questions (30 minutes)

A town library wants an app. Assume 8,000 members, 25 percent active each day, 4 searches per active member per day, and each member borrows 2 books a month. Work out daily active users, searches per day, and borrows per month.

Done when: three results with the arithmetic shown, and one sentence saying whether one small server is enough.

Hint

8,000 × 0.25 gives daily active users. Multiply by 4 for searches.

Medium 3: Find the hidden requirements (30 minutes)

Pick an online food ordering app. Answer the four hidden-requirement questions from section 5 for it. For each answer, name one design change it causes.

Done when: four answers, four design changes, and one line saying which hidden requirement is the most costly to meet.

Hint

Think of what must never be lost, what happens at dinner-time spikes, and who sees addresses.

Hard

Hard 1: Interview in writing (40 minutes)

The prompt is "design a ride-sharing app". Write the conversation you would have: eight or more questions, made-up but sensible answers, and the final requirements table in the style of section 6.

Done when: eight or more question-answer pairs, a table with scope, numbers, must-not-lose and assumptions, and at least one number that follows from other numbers.

Hint

End each answer with a number or a yes or no, so the table can be filled.

Hard 2: Two sizes, two designs (40 minutes)

Write requirements for a photo-sharing app for 5,000 users and again for 50 million users. Show which requirements change in kind (not only in size).

Done when: two requirement tables, and a list of at least three requirements that are new or different in the large version, each with a reason.

Hint

Think about what a single server cannot do that 50 million users demand.

Hard 3: Catch the contradiction (40 minutes)

A client says: "The app must be cheap, always available, instant for users in every country, and never lose any data." Explain which of these pull against each other, ask the client three questions to resolve it, and propose a ranked top three.

Done when: at least two conflicts named with reasons, three questions, and a ranked list of three with a sentence for each.

Hint

Faster and safer usually cost more. Ask which one the client gives up first.