BACS2163 Software Engineering - Group Assignment Rubrics (CLO2)

Student Names: (1) Tutorial Group:

(2) Programme: R( ) Report /80
(3) presenatation
(4) /20
(5)

Section Criteria / Area Excellent Good Average Poor Very Poor Score

Very good Generally show

Good elaboration on Little attempt on Very little attempt on
elaboration on attempt on
Organization introducing introducing introducing
introducing (5m) (4m) introducing (3m) (2m) (1m)
background background of the background of the background of the
background of the background of the
chosen organization. chosen organization. chosen organization.
chosen organization. chosen organization.

Generally show Little attempt to Very little attempt to

Very good
Fact-gathering Good elaboration on attempt on providing provide elaboration provide elaboration
elaboration on fact- (5m) (4m) (3m) (2m) (1m)
techniques used fact-gathering used. elaboration on fact- on fact-gathering on fact-gathering
gathering used.
gathering used. used. used.

Generally show Little attempt to Very little attempt to

Very good
Problems of Good elaboration on attempt on providing provide elaboration provide elaboration
elaboration on
existing/legacy (5m) problems of existing/ (4m) elaboration on (3m) on problems of (2m) on problems of (1m)
problems of existing/
system legacy system. problems of existing/ existing/ legacy existing/ legacy
legacy system.
legacy system. system. system.

Very good
explanation and
Software quality justification on
(5m)
attributes suggested software
quality attributes for
the proposed system.
Good explanation
and justification on
suggested software (4m)
quality attributes for
the proposed system.
Generally show
Little attempt to
attempt to provide Very little attempt to
provide explanation
explanation and provide explanation
and justificationon
justification on (3m) (2m) and justification. (1m)
suggested software
suggested software Irrelevant software
quality attributes for
quality attributes for quality attributes.
the proposed system.
the proposed system.

Very good Generally good on Little attempt to Very little attempt to

Good justification and
Suggested justification and providing justification provide justification provide justification
elaboration on
Software Process elaboration on (5m) (4m) and elaboration on (3m) and elaboration on (2m) and elaboration on (1m)
suggested process
Model suggested process suggested process suggested process suggested process
model.
model. model. model. model.

TOTAL (25 marks)

 Comments:

Score
Section Criteria / Area Excellent Good Average Poor Very Poor
(1) (2) (3) (4) (5)

Very good project Good project plan Shows attempt to

Inadequate attempt
plan and schedule for and schedule for the use MS Project in Very little attempt to
to prepare project
Project Plan and the project scenario project scenario & producing project develop project plan
(8-10m) (5-7m) (3-4m) plan. Weak on using (2m) (1m)
Schedule & process model process model plan and schedule and use of MS
MS Project to
chosen. Very good chosen. Good use of but some errors of Project.
produce project plan.
use of MS Project. MS Project use of MS Project

Very good defined, good defined, Good on identifying Inadequate attempt

Very little attempt to
structured and structured and the functional and to identify the
identify the functional
System organised functinal organised functinal non-functional functional and non-
(8-10m) (5-7m) (3-4m) (2m) and non-functional (1m)
Requirements* and non-functional and non-functional requirements for the functional
requirements for the
requirements for the requirements for the new system but requirements for the
new system.
Part 2 new system. new system. some errors. new system.

Very good defined Good defined Inadequate attempt Very little attempt to
viewpoint hierarchy viewpoint hierarchy Average viewpoint to prepare viewpoint prepare viewpoint
with all necessary with almost all hierarchy with partial hierarchy with some hierarchy with some
viewpoint involved necessary viewpoints viewpoints involved inadequate irrelevant viewpoints
Viewpoint
and excellent in (5m) involved and good in (4m) and in justifying the (3m) viewpoints involved (2m) involvedery and weak (1m)
hierarchy
justifying the justifying the roles/importance of and weak in justifying in justifying the
roles/importance of roles/importance of each viewpoint the roles/importance roles/importance of
each viewpoint each viewpoint involved. of each viewpoint each viewpoint
involved. involved. involved. involved.

TOTAL (25 marks)

Comments:

Score
Section Criteria / Area Excellent Good Average Poor Very Poor
(1) (2) (3) (4) (5)
Very good Good justification and Generally good on Little attempt to Very little attempt to
Suggested justification and elaboration on the providing justification provide justification provide justification
System elaboration on the suggested system and elaboration on and elaboration on and elaboration on
suggested system (5m) organisation model. (4m) the suggested (3m) the suggested (2m) the suggested (1m)
Organisation
Model. organisation model. system organisation system organisation system organisation
model. model. model.

Part 3
 Test Plan Very good structured
(Testing process, Good structured and Generally good on Inadequate attempt
and organised test
organised test plan developing test plan to develop test plan
tested items, plan contains all Very little attempt to
(11m-15m) contains all relevant (7m-10m) but lack of some (3m-6m) but lack of some (2m) (1m)
procedures, relevant contents develop test plan.
Part 3 contents with good contents and contents and
requirements, with excellent
elaboration. elaboration. elaboration.
constraints) elaboration.

Very good
Good justification and Generally show Poor justification and Very poor justification
justification and
elaboration of UI attempt on elaboration on UI and elaboration on UI
Screen Design elaboration of UI
design principles suggesting UI design design principles design principles
Principles & design principles (8-10m) (5-7m) (3-4m) (2m) (1m)
used & good match principles but lack of used and lack of used & totally not
Justification used & excellent
with the prototype match with the match with the match with the
match with the
developed. prototype developed. prototype developed. prototype developed.
prototype developed.

TOTAL (30 marks)

Comments:

* Individual Assessment
BACS2163 Software Engineering - Individual Presentation Rubric (CLO3)

Programme: R( ) Student Names: (1) (2) (3) (4) (5)

Group:

Rating: 1-Very Poor, 2-Poor, Rating: 1-Very Poor, 2-Poor, Rating: 1-Very Poor, 2-Poor, Rating: 1-Very Poor, 2-Poor, Rating: 1-Very Poor, 2-Poor,

Section Criteria/Area Very Poor 3-Average, 4-Good, 5-Excellent 3-Average, 4-Good, 5-Excellent 3-Average, 4-Good, 5-Excellent 3-Average, 4-Good, 5-Excellent 3-Average, 4-Good, 5-Excellent Excellent

Ability to deliver ideas 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5

clearly, effectively and
Delivery of ideas is Able to present ideas very
confidently use of
vague, unorganised and clearly, organized,
visual aids and tools
without confidence. attractively and confidently.
for effective
presentation .

1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 Able to answer the all

Ability to answer the Unable to answer the
questions & provides
question and provides question & not
Oral excellent understanding &
justification. understanding
justification.
Presentation
Inaudible,no eye 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 Poised, clear articulation;
contact, speaker proper volume; steady
Presentation skill
seemed uninterested rate; good posture and
and used monotone eye contact; enthusiasm;

1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5
Able to use of visual Not prepare Able to of visual aids or tools
aids and tools for presentation slides and appropriately and
effective presentation no visual aids used attractively.

TOTAL (20 marks) /20 /20 /20 /20 /20

Comments: