CSE3SMT Assessment 2 Help: La Trobe Specification-Based Testing Guide
Quick answer: CSE3SMT Software Measurement and Testing is an undergraduate subject at La Trobe University, also offered online through Open Universities Australia. A specification-based testing assessment asks you to read a requirements specification, find issues in it, derive test cases with black-box techniques such as equivalence partitioning, boundary value analysis and decision tables, and present them in a traceable test case table. Most marks go to systematic derivation and coverage, not to the number of test cases.
CSE3SMT at a glance
| Item | Detail |
|---|---|
| Subject | CSE3SMT Software Measurement and Testing |
| Institution | La Trobe University (also via Open Universities Australia as LTU-CSE3SMT) |
| Level | Undergraduate; study load 0.125 EFTSL |
| Prerequisite | CSE2ALG Algorithms and Data Structures (via OUA listing) |
| Learning outcomes (summary) | Analyse requirements for issues, risks and test inputs; design and run manual and automated tests with structured techniques; apply quality metrics; relate testing roles and processes to the software life cycle |
| Assessment 2 focus | Specification-based (black-box) test design. Check your brief for weighting, word count and submission format |
Step-by-step approach
Step 1: Analyse the specification
Read the specification line by line and number each requirement (R1, R2 and so on). Note anything ambiguous, missing or contradictory, such as an input range with no stated behaviour at the limit, or two rules that apply to the same input. Learning outcome one rewards this analysis, so record the issues in a table with a suggested clarification.
| ID | Requirement (paraphrased) | Issue found | Question for the client |
|---|---|---|---|
| R3 | Discount applies to orders over 100 items | Is exactly 100 included? | Confirm whether the boundary is inclusive |
| R5 | Invalid codes are rejected | No error message defined | What message should the user see? |
Step 2: Identify inputs and equivalence classes
For each input, list the valid and invalid partitions. Each partition is a set of values the system should treat the same way. Give every class an ID so you can trace it.
Step 3: Apply boundary value analysis
For each ordered range, test at and on either side of each boundary. State which convention you used (two-value or three-value boundary analysis) and keep it consistent.
Worked method example (not an answer): an invented rule says a student age field accepts whole numbers from 16 to 65 inclusive. Equivalence classes are: EC1 valid 16 to 65; EC2 invalid below 16; EC3 invalid above 65; EC4 invalid non-integer; EC5 invalid empty. Two-value boundary analysis gives test inputs 15, 16, 65 and 66. Each test case then records its input, the class or boundary it covers, the expected result from the specification and the requirement ID.
| TC | Input | Covers | Expected result (from spec) | Req |
|---|---|---|---|---|
| TC1 | 15 | EC2, lower boundary | Rejected with error | R2 |
| TC2 | 16 | EC1, lower boundary | Accepted | R2 |
| TC3 | 65 | EC1, upper boundary | Accepted | R2 |
| TC4 | 66 | EC3, upper boundary | Rejected with error | R2 |
| TC5 | 20.5 | EC4 | Rejected with error | R2 |
Step 4: Use decision tables for combined conditions
Where the output depends on several conditions together (for example membership type and order size), build a decision table with every combination of conditions as a column, then collapse impossible or identical columns and explain why. Each remaining column becomes at least one test case.
Optional step: automate the tests
Learning outcome two covers automated as well as manual test execution. If your brief asks you to automate, turn each row of your test case table into one automated test so the IDs match (for example a test method named after TC1 to TC5). Use the framework your labs used, keep one assertion focus per test, and include the run output or a screenshot of the results in an appendix. Explain any test that fails: is it a defect in the program or an ambiguity in the specification?
Step 5: Show coverage and traceability
Finish with a traceability matrix linking requirements to test cases, and a coverage summary: percentage of equivalence classes, boundaries and decision rules covered. If the task includes running tests, record actual results, pass or fail, and defects with steps to reproduce.
Step 6: Metrics and reflection
If your brief asks for measurement, report simple, well-defined metrics such as test cases per requirement, pass rate, defects found per requirement or cyclomatic complexity for a given function, and interpret them. A number without interpretation earns few marks.
Common mistake: Listing many random test inputs with no link to a partition, boundary or requirement. Markers look for systematic derivation: every test case should say which class or boundary it covers and where its expected result comes from in the specification. Also avoid writing expected results from what the code does; expected results come from the specification.
Stuck on CSE3SMT Assessment 2 Help: La Trobe Specification-Based Testing Guide?
Send us your brief. A Australian tutor will explain what the marking criteria are asking for and help you plan your answer. Your first consultation is free.
How assessors judge CSE3SMT specification-based testing
| Criterion | What strong work shows |
|---|---|
| Requirement analysis | Numbered requirements, real ambiguities found, clear clarification questions |
| Equivalence partitioning | Valid and invalid classes for every input, uniquely labelled |
| Boundary value analysis | Consistent convention, all boundaries tested |
| Decision tables | Complete combinations, justified collapsing, rules mapped to tests |
| Test case quality | Input, expected result from spec, coverage and requirement ID for each |
| Traceability and coverage | Matrix and coverage figures that match the tables |
| Presentation | Consistent IDs, readable tables, assumptions stated |
Pre-submission checklist
- Every requirement numbered and every issue recorded
- Every input has valid and invalid equivalence classes
- Boundary convention stated and applied to every range
- Decision table complete before collapsing
- Expected results taken from the specification, not the code
- Traceability matrix covers every requirement
- Assumptions listed where the specification is silent
- Any generative AI use follows the subject's stated rules and is acknowledged if required
Want a tutor to check your draft first?
Get clear written feedback on your own work before the deadline: structure, criteria coverage and referencing. Your first 15-minute consultation is free.
Stuck on CSE3SMT? Get tutor feedback
Share your draft or your plan and a tutor will explain where the marks are, check your structure against the criteria and suggest improvements. We tutor, give feedback and proofread; you write your own work.
CSE3SMT Assessment 2 answer hints and sample structure
Searches for CSE3SMT assessment answers usually come from students unsure how to set out their tables. Specifications change each teaching period, so copied test cases would not match your brief. This report structure works for most specification-based testing tasks:
| Section | Suggested share of marks or effort | Content |
|---|---|---|
| Requirement analysis and issues | 15% | Numbered requirements, issue table |
| Equivalence classes | 20% | Class table per input |
| Boundary values | 15% | Boundary table and convention |
| Decision table | 20% | Full and collapsed tables, rules |
| Test cases and traceability | 25% | Test case table, traceability matrix, coverage |
| Summary and assumptions | 5% | Key risks, assumptions, metrics if required |
Deadline coming up?
Book a 1-to-1 online session today. Tutors are available 7 days a week, 8am–11pm, and usually reply within 2 hours.
Frequently asked questions
What is CSE3SMT at La Trobe?
CSE3SMT Software Measurement and Testing is a La Trobe University undergraduate subject, also offered through Open Universities Australia, covering test design techniques, test automation, quality metrics and testing processes.
What is specification-based testing?
It is black-box testing where test cases are derived from the requirements specification, not from the code, using techniques such as equivalence partitioning, boundary value analysis and decision tables.
How many test cases do I need?
Enough to cover every equivalence class, boundary and decision rule you identified. Markers value coverage and traceability over a large number of tests.
Should boundary values include both sides of a limit?
Yes. Test at the boundary and just outside it, and state whether you use two-value or three-value boundary analysis.
Where do expected results come from?
From the specification. If the specification does not define the behaviour, record it as an issue and state your assumption.
What is the prerequisite for CSE3SMT?
The Open Universities Australia listing names CSE2ALG Algorithms and Data Structures. Check the La Trobe handbook for your enrolment.
Can you give me the CSE3SMT test cases?
No. We tutor you through the techniques, review your tables and give feedback so the test design is your own work.
Related help
- Computer and IT assignment help
- Programming assignment help
- TECH1200 Fundamentals of Programming guide
- University assignment help Australia
Academic integrity: This guide explains how to approach the task. It is not an answer to submit. Your provider may check your work with similarity and authorship tools, and in Australia the TEQSA Act makes it an offence to provide or advertise academic cheating services. Use this guide, your provider's brief and marking guide, and tutor feedback to produce your own work, and follow your provider's rules on generative AI.