AAPP007-3-2 Visual Basic.

NET Marking Scheme UCD2F0906DIT/ DIT {SE}/DBT

Learning Outcomes:

At the end of the assignment, you should be able to:

1. Critically analyze a scenario and using problem solving techniques to develop a GUI based application based on user
requirements.
2. Construct an application that uses a database for storing data
3. Construct a report using the Crystal report
4. Write codes to handle input errors for an application
5. Write codes for exception handling for an application
6. Use different methods of input and output controls based on the application requirements

Level 2 Asia Pacific Institute of Information Technology 2010

AAPP007-3-2 Visual [Link] Marking Scheme UCD2F0906DIT/ DIT {SE}/DBT

Group Fail Marginal Fail Pass Credit Distinction

0 - 11 12 – 15 16 – 19 20 – 27 28 - 40
 Less than 30% of the  Meets at least 30% of the  Meets at least 40% of the  Meets at least 50% of the  Meets at least 70% of the
basic requirements were basic requirements listed basic requirements listed basic requirements listed basic requirements listed
met  Program does not  Program may not  Program compiles with  Program compiles with
 Program incomplete with compile due to errors compile due to errors or none or little errors and no errors and runs
obvious errors which could not be easily run smoothly when runs smoothly when smoothly when executed
 No program or work not identified executed executed  Incorporate advance
done  Program seems complete  Incorporate basic  Incorporate intermediate [Link] programming
 Database is created but concepts of GUI database programming features
unable to make the programming concepts.  Program incorporates
connection to the  Database is created and  Program incorporates good programming
Coding database connection is successful good programming practices such as
and  Interface design is from the program practices such as comments and
created  Only two of the required comments and indentation
Implementation  Limited usage of functions are working indentation  Incorporates good input
(40%) [Link] built-in  Report produced but  Some exception handling validation practice
functions information not complete was done  Evidence of good
 No reports generated or not formatted  Incorporates some input exception handling
correctly. validation and some practice
usage of [Link] built-  All required reports are
in functions produced and may be
 All the required reports printed.
are produced and may be
printed.

Level 2 Asia Pacific Institute of Information Technology 2010

AAPP007-3-2 Visual [Link] Marking Scheme UCD2F0906DIT/ DIT {SE}/DBT

Group Fail Marginal Fail Pass Credit Distinction

0–6 7 8 – 10 11 -14 15 - 20
 Documentation not done Documentation contains Documentation contains Documentation contains Documentation contains
 Content of  Conceptual design done  Screen capture of the  Screen capture of the  Screen capture of the
documentation does not but does not match with output of the program output of the program output of the program
adhere to any of the the actual screen with minimal with some explanation with appropriate
requirements stipulated  Screen capture of the explanation to describe to describe the program explanation to
in the assignment output of the program the program  Good storyboard design sufficiently describe the
Documentation requirements does not have any  Average storyboard  Description and program
 Not complete storyboard explanation to describe design evidence of at least one  Excellent storyboard
Storyboard And the program  At least 10 test cases additional feature which design
Design  Very simple storyboard done has been incorporated in  Excellent detailed user
 No test cases done  Brief user manual with the solution manual produced
(20%)  No user manual no screen shots  User manual produced  Good critical
provided  Critical assessment done but some instructions assessment, provide
 Some critical  Some referencing done not included or no logical justification for
assessment done but inappropriately done screen shots included future improvement
 Hardly any referencing in terms of style and  Some referencing done  Complete and accurate
done or incorrect relevance accurately in terms of referencing in terms of
referencing format used. style and relevance style and relevance

Individual
0–6 7 8 – 10 11 -14 15 - 20
 Not able to answer any  Not able to answer most  Able to answer some  Able to answer most  Able to answer all
question posed questions indicating questions indicating questions well questions posed
Presentation  Not able to explain the poor understanding of some understanding of indicating some accurately indicating
code the work done the work done understanding of the clear understanding of
(20%)  No understanding or  Not able to explain nor  Able to explain and able work done the work done
idea of programming modify code upon to modify code upon  Able to explain the  Able to explain the
concepts request request. program and modify program and modify
 Has hardly any  Clear indication of some some code upon request code upon request
understanding or idea on understanding of the
the program developed coding concepts

Level 2 Asia Pacific Institute of Information Technology 2010