This page holds a finished CSC-FPX4900 Assessment 2 requirements document with functional and non-functional requirements written as observable behaviors, numbered, prioritized and traced to the proposal. Searches like "csc fpx 4900 assessment 2 assignment example", "cscfpx4900 assessment 2 sample" and "csc-fpx4900 assessment 2 example" land here.
What a finished CSC-FPX4900 Assessment 2 requirements document looks like
The finished document looks administrative on purpose. Requirements arrive numbered, one behavior per statement, grouped by the feature they serve, and phrased so an outside tester with the running system could mark each pass or fail without consulting the author. Functional statements describe what the system does in response to what: the input accepted, the action taken, the output produced, the error raised. Non-functional statements get the same discipline, a response threshold, a data volume, a recovery behavior, each with the number that makes it checkable. Every requirement carries a priority and a pointer to the proposal need it serves, and orphans in either direction have been hunted out. Ambiguous verbs are absent, and where a value had to be chosen, a short note says why that value.
How a CSC-FPX4900 Assessment 2 example is structured
The document is organized for lookup rather than reading order. An introduction restates the project in one paragraph and defines the terms the requirements will lean on, so words like session, record and report mean one thing throughout. The functional requirements follow, grouped by feature area, each numbered for traceability, stated as a single observable behavior, and tagged with priority. Edge behaviors are specified alongside the happy path: what the system does with bad input, duplicates, and empty states is written down rather than left to the implementer's mood. The non-functional section covers performance, usability, reliability and security expectations at capstone scale, every one carrying a measurable threshold. A traceability table maps requirements to proposal needs in both directions. The closing section lists the assumptions the requirements depend on and flags the ones most likely to move, which tells the design stage where to stay flexible.
One observable behavior per statement
Each numbered requirement describes a single response the running system either exhibits or does not, which is what makes pass and fail decidable.
Terms defined before they are used
A short glossary pins down the document's nouns, since a requirement about sessions cannot be verified while session means three things.
Edge behavior specified, not implied
Bad input, duplicates and empty states get their own numbered requirements, because unwritten expectations become the defects of Capstone 2.
Non-functional statements with real thresholds
Performance and reliability expectations carry numbers scaled to a capstone system, each with a note on how the check would be run.
Traceability in both directions
Every requirement points to a proposal need and every need is covered, so nothing promised is unspecified and nothing specified is unasked-for.
Where marks go in CSC-FPX4900 Assessment 2
Requirements documents lose marks one untestable sentence at a time. Statements built on comfort words, intuitive, efficient, seamless, robust, cannot fail a test, and criteria written around verifiability treat each as a placeholder where a requirement should be. The second loss is the hidden design decision, requirements that dictate a database or a framework instead of a behavior, which pre-spends choices the next document is supposed to argue. Third is the coverage gap between stages: a proposal feature with no requirements under it, or requirements for capabilities the proposal never promised, both surface in a five-minute consistency check that graders in this sequence routinely perform. Happy-path-only documents leave the system's behavior under error officially unknown. Distinguished work reads almost like a test plan, and that resemblance is the achievement.
Get a CSC-FPX4900 Assessment 2 example written to your instructions
Send us the Assessment 2 instructions and scoring guide from your CSC-FPX4900 courseroom, together with your proposal so the requirements can trace to it. A custom document written to those criteria, testable line by line, comes back within 24 to 48 hours. The first one is free, and the numbering scheme is yours to keep.
CSC-FPX4900 Assessment 2 questions, answered
How many requirements should a capstone project specify?
Enough to cover every proposal feature's behavior, including errors and edges, and no more; padding is visible and priced. Most term-sized projects land in the dozens, not the hundreds, and if yours is heading past that, the problem is usually scope rather than thoroughness. Depth per requirement, the input, the response, the check, matters more than the count.
What is the difference between a functional and a non-functional requirement here?
Functional statements say what the system does: accept this, produce that, reject the other. Non-functional statements say how well it must do it: within what time, at what volume, surviving what failure. The second kind fails faster in grading, because writing it verifiably requires a number, and inventing a defensible number for a capstone system takes actual thought about realistic use.
My proposal changed a little since Assessment 1. What do the requirements follow?
Follow the project as it now stands, and document the change: a short revision note naming what moved and why keeps the sequence coherent and shows the drift was managed rather than accidental. Graders check stage consistency, so an unexplained mismatch costs both documents. If the change is large, ask your instructor before specifying a project the proposal never described.