The document describes the Module Report Statistics Assistant (MRSA) project. The MRSA project contains two Visual Studio projects that share common source code. The initial implementation focuses on the MRSA::MSS class, which contains raw data from a module spreadsheet. Tests will validate the raw data by checking conditions like having the same number of fields in each row and non-null column names. The list of validation conditions is not final but initially includes checks like each student ID corresponding to one row per assessment.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
63 views1 page
Odule Eport Tatistics Ssistant: M R S A
The document describes the Module Report Statistics Assistant (MRSA) project. The MRSA project contains two Visual Studio projects that share common source code. The initial implementation focuses on the MRSA::MSS class, which contains raw data from a module spreadsheet. Tests will validate the raw data by checking conditions like having the same number of fields in each row and non-null column names. The list of validation conditions is not final but initially includes checks like each student ID corresponding to one row per assessment.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1
SOFT30161 Advanced Software Engineering
Module
Report
Statistics
Assistant
(MRSA)
The
MRSA
project
has
a
familiar
shape
with
2
VS
projects
(main
&
test)
sharing
common
source
in
folders
src
&
headers.
Rev1
of
the
warren
repo
tdd
has
implementation
of
only
(most
of)
class
MRSA::MSS.
The
MSS
class
is
a
container
for
raw
data
from
a
module
spreadsheet;
the
initial
effort
will
be
concentrated
on
generating
a
number
of
validation
checks
on
the
raw
data
(see
below).
The
tests
should
refine
the
design
of
the
class
rather
than
find
bugs
in
the
implementation;
they
should
be
designed
to
identify
data
that
does
not
meet
the
validation
criteria.
The
list
of
validation
conditions
is
not
finalized;
the
initial
list
is
below,
but
the
current
version
will
always
be
in
the
file
conditions
1. All
rows
should
have
the
same
number
of
fields.
2. Every
column
must
have
a
non-null
name
in
the
1st
row.
3. There
are
a
number
of
necessary
field
names
for
a
valid
spreadsheet;
the
details
are
not
yet
available.
4. Each
unique
student
ID
must
have
one
row
per
assessment
element.
5. {(Student
ID,
Student
Name)}
is
a
bijection
6. #{Student
ID}
=
#{Student
Name}