Student
MahasiswaSit a timed multiple-choice exam and read the remaining time above every question.
Red code · Student actions
ExamBro is an Android mobile application for online exam management, built for two distinct user roles: Student and Proctor (Pengawas). The product intent is to give students a calm, dependable path through a timed multiple-choice exam — log in, see upcoming exams, take the exam against a countdown timer, submit answers, and view results — while giving proctors a live operational view of the exam room: a real-time list of active students, each student's online/offline status, and the ability to review student submissions.
The audience is Indonesian secondary and higher-education exam settings, where a student needs fast, unambiguous reading of time and question state, and a proctor needs instant reading of who is present, who has dropped offline, and what has been submitted. The interface must be clean, professional, and easy to navigate for both roles.
This document is the System Requirements Document for ExamBro. It specifies the application architecture, the database schema, and the UI structure for both Student and Proctor screens, expressed as requirements, page coverage, and user flows.
ExamBro is delivered as an Android mobile application with a shared backend. Two roles exist and are strictly distinct: a Student and a Proctor (Pengawas). Each role authenticates through the same Login surface and then reaches only its own working area.
Actors
Current delivery and ownership
Accepted behavior summary
Narrow exclusions
ExamBro is a first-party Android application. Both roles enter through a public Landing surface that explains the two roles, then authenticate at Login. Identity is application-owned: a Student's exam session, answers, submission, and results must remain bound to that student across app restarts and reconnects, and a Proctor's live roster view must remain bound to that proctor. Because a student's in-progress exam and a proctor's live monitoring both depend on durable, actor-specific state, the application establishes and verifies identity at first use and on return.
Access is role-restricted after login: the Student working area (Upcoming Exams, Take Exam, Exam Results) is reachable only by an authenticated Student, and the Proctor working area (Active Students, Submissions) is reachable only by an authenticated Proctor. The Landing and Login surfaces are reachable anonymously; protected state remains unavailable until identity is established.
Real-time behavior is a delivery responsibility of the backend plus Redis: the proctor's roster and status changes are pushed as they happen, not polled on a manual refresh. The exam countdown is a client-visible timer driven by the exam session's authoritative end time held by the backend, so a reconnect restores the correct remaining time.
Everything described in this document is current scope. No future-horizon features are committed.
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
FR-1 — Android application delivery (explicit) As a user, I should use ExamBro as an Android mobile application, so that I can manage online exams from my phone.
FR-2 — Two distinct roles (explicit) As the product, I should enforce exactly two distinct user roles — Student and Proctor (Pengawas) — so that each role sees only its own working area.
FR-3 — Student login (explicit) As a Student, I should log in, so that I can reach my exams.
FR-4 — Student self-service enrollment and returning verification (required_inference) As a Student, I should establish my account on first use and verify it on return, so that my exam session, answers, submission, and results stay bound to me.
FR-5 — View upcoming exams (explicit) As a Student, I should view upcoming exams, so that I know what is scheduled.
FR-6 — Select an upcoming exam (required_inference) As a Student, I should select an upcoming exam, so that the correct exam opens for me.
FR-7 — Take a multiple-choice exam with a countdown timer (explicit) As a Student, I should take a multiple-choice exam with a countdown timer, so that I can answer within the allotted time.
FR-8 — Submit answers (explicit) As a Student, I should submit my answers, so that my exam is recorded.
FR-9 — View exam results (explicit) As a Student, I should view my exam results, so that I know how I did.
FR-10 — Proctor login (explicit) As a Proctor (Pengawas), I should log in, so that I can reach my monitoring area.
FR-11 — Proctor self-service enrollment and returning verification (required_inference) As a Proctor (Pengawas), I should establish my account on first use and verify it on return, so that my live monitoring view stays bound to me.
FR-12 — View active students in real time (explicit) As a Proctor (Pengawas), I should view a list of active students taking the exam in real time, so that I know who is present.
FR-13 — Monitor student status (online/offline) (explicit) As a Proctor (Pengawas), I should monitor each student's online/offline status, so that I can see who has dropped off.
FR-14 — Review student submissions (explicit) As a Proctor (Pengawas), I should review student submissions, so that I can examine what each student submitted.
FR-15 — Clean, professional, easy-to-navigate UI (explicit) As a Student or Proctor, I should experience a clean, professional, and easy-to-navigate interface, so that I can read status and time quickly.
Product context. A Student is taking a scheduled online exam on an Android phone. The student arrives at ExamBro already knowing which exam is due and needs to reach it quickly, answer multiple-choice questions against a countdown, submit, and then see the result.
Primary goal. Complete the scheduled multiple-choice exam within the countdown and see the result.
Distinct accepted responsibilities.
Relevant inputs and decisions. Which exam to open; which option to select for each question; when to confirm submission.
Interactions with other participants. The Student's presence, status, and submission are what the Proctor observes on Active Students and reviews on Submissions. The Student does not interact with the Proctor directly.
Observable success. The student lands on Upcoming Exams after login, completes the exam with the timer visible throughout, submits, and sees a score and answer review on Exam Results.
What makes this role different. The Student's work is time-bound and answer-producing; the interface must keep the countdown legible above the question and preserve answers across reconnects.
Product context. A Proctor (Pengawas) supervises an exam session on an Android phone. The proctor needs a live operational picture of who is taking the exam, who has dropped offline, and what has been submitted.
Primary goal. Maintain a live view of active students and their online/offline status, and review submissions.
Distinct accepted responsibilities.
Relevant inputs and decisions. Which student to inspect; whether a student's offline status needs attention; which submission to open.
Interactions with other participants. The Proctor observes the Student's presence, status, and submission; the Proctor does not alter the Student's exam.
Observable success. The proctor lands on Active Students after login, sees the roster update in real time with green/grey status squares, and can open any submission to review the submitted answers.
What makes this role different. The Proctor's work is observational and live; the interface must present a ruled table that updates in place, not a static list.
Muse and headline. Massimo Vignelli — systematic clarity. Headline: "Two roles. One clear exam system."
Mode. Light mode.
Colour tokens (exact hex by role)
#F2EFE6#FFFFFF#141414#D2261E#E8B400#6B6B66#D2261E (red)#007A3D (green)#007A3D (green)#6B6B66 (grey)#141414 (thin black rules)Typography
Shape language
Layout
Imagery
Motion
Accessibility of text and controls
font-size: clamp(...) with its mobile size) to fit.Avoid
The public entry (Landing) is built as a printed manual page. A full-width ruled header bar in black carries the ExamBro wordmark flush left in white caps. Below it, on the warm paper ground (#F2EFE6), a 56px black Archivo Heavy headline — "Two roles. One clear exam system." — sits flush left across eight columns, with the subline beneath it. A single horizontal rule runs edge to edge under the headline block. Below the rule, two solid colour blocks sit side by side: red (#D2261E) labelled Student and green (#007A3D) labelled Proctor, each with a 16px label. The Log in control is a black rectangle at the left margin. A schematic diagram of the two role paths — pictograms and rules only — sits beneath the role blocks, showing the Student path and the Proctor path as numbered sections. Section numbers are set small in the margin beside each heading. The composition recomposes only accepted content: the two roles, their paths, and the login control.
Interaction Model: Static Motion Tempo: still Hero Dimensionality: flat
Landing Hero Motion Brief
NFR-1 — Android mobile delivery (explicit) The application is delivered as an Android mobile application. Rationale: explicit hard constraint.
NFR-2 — Two distinct roles (explicit) The application enforces exactly two distinct roles, Student and Proctor (Pengawas), with role-restricted access to each working area. Rationale: explicit hard constraint.
NFR-3 — Multiple-choice exam with countdown (explicit) The exam is multiple-choice and has a countdown timer. The timer is driven by the exam session's authoritative end time held by the backend so that reconnects restore the correct remaining time. Rationale: explicit hard constraint; durable state required.
NFR-4 — Real-time proctor roster (explicit) The proctor's active-student list is real-time. The backend pushes roster and status changes through Redis-backed coordination; the client updates in place without manual refresh. Rationale: explicit hard constraint; Redis required.
NFR-5 — Clean, professional, easy-to-navigate UI (explicit) The UI is clean, professional, and easy to navigate for both roles, following the Vignelli-derived design system in Sections 6–8. Rationale: explicit hard constraint.
NFR-6 — Durable state (required_inference) Exam sessions, answers, submissions, results, and presence state persist in MariaDB and Redis so that a student's work and a proctor's roster survive reconnects and app restarts. Rationale: indispensable for the accepted lifecycles.
NFR-7 — Application-owned identity (required_inference) Identity is application-owned; a student's exam state and a proctor's monitoring state remain bound to the correct participant. Rationale: indispensable for actor continuity.
NFR-8 — Readable text and controls at every viewport (explicit) Headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px. Rationale: explicit design constraint.

ExamBro gives students a timed exam and proctors a live view of every candidate.
Sit a timed multiple-choice exam and read the remaining time above every question.
Red code · Student actions
Watch the live roster, read each candidate’s online or offline status, and review submissions.
Green code · Proctor actions
Exams at your pace
Pengawas — live room view

ExamBro gives students a timed exam and proctors a live view of every candidate.
Sit a timed multiple-choice exam and read the remaining time above every question.
Red code · Student actions
Watch the live roster, read each candidate’s online or offline status, and review submissions.
Green code · Proctor actions
Exams at your pace
Pengawas — live room view
No comments yet. Be the first!