IT204

Visual Basic Project

VISUAL BASIC .Net ( IT 204 )

PROJECT GUIDE LINES & MARKING SCHEME

DIT/IT204/project guidelines/V. Net.1.0

Page 1

IT204

Visual Basic Project

A project is something to enjoy. If you are not enjoying the stimulation of being involved in a major piece of work then see the project co-ordinator. Self-motivation is an important aim of the project and it will be accessed. This project is individual project. This module is 100 percent project based. 1. Presentations and Demonstrations
1.1

Interim Presentation: The interim presentation will: a) provide a fixed point in the academic year at which students must demonstrate the progress made, and outline the future work to be done, b) enable students to practice presentation skills. The presentation should include: 1. an outline of the project. 2. a review of the progress to date in relation to the project plan. 3. Plans for future work; a revision of objectives may be necessary in the light of progress made.

Feedback on the presentation will be provided to all students by their PMPs. 1.2 Final Demonstration: The final project demonstration, organised by the student, will enable the proposer, supervisor and PMP member(s) to assess the quality and completeness of the resultant product together with your presentation ability. 1.3 Final presentation/Viva: The student will formally present his/her project to a panel of at least two members. The presentation/Viva panel will normally consist of the project supervisor, one member of the students PMP (who may be the supervisor), and one or more other members of an academic staff. External examiners are also invited to attend this session, which will normally consist of: a) a 15-minute assessed presentation.
DIT/IT204/project guidelines/V. Net.1.0 Page 2

IT204

Visual Basic Project

b) a viva period of 10 minutes, the student will be expected to answer questions on any aspect of their project.

2. Project Report The project report is a self contained document normally consisting of, an introduction, terms of reference, analysis of requirements, discussion of existing facilities, system design including alternatives, implementation overview, development/quality assurance and acceptance, future developments, summary and analytical appraisal. The report should include detailed reasoning for any changes in the terms of reference, project plan or in the scope of the implementation of the entire project. Supplementary detailed material should be supplied as Appendices, It should be noted that the production of the project is the responsibility of the student. Although there is no absolute format the following guidelines should prove useful. 2.1 Contents The content of a project report will vary and will be dependent upon the type and scope of the project. It would normally be expected that the following main parts would be present in the report: - an introduction - brief description of term of reference - analysis of term of reference - analysis of requirements - discussion of existing facilities (where applicable) - systems design including alternatives considered - implementation overview - development/quality assurance and acceptance - test strategy - future developments - summary and critical appraisal - bibliography You should also include in your report detailed reasoning for any changes in the terms of reference, project plan or in the scope of implementation of the entire project. 2.2 Format The following points give only the specific requirements for the format of the final report. Abstract
DIT/IT204/project guidelines/V. Net.1.0 Page 3

IT204

Visual Basic Project

An abstract should be provided with the report. It must: not be bound with the report be typed not extend beyond one page of A4

The abstract should include: the students name project title supervisors name

Main Report This must be typed using double line spacing. All diagrams should be drawn using black ink. Sample outputs may be included. Appendices Any additional material should be included as appendices to the main report. This should include detailed technical specification, program listings, test data and results, reference material, user guide, technical guides etc. Appendices should be typed on A4 paper. Computer listings may be added but must be paged correctly to allow ease of reading. Number of Copies Two copies of the main report and appendices must be provided for the School. One copy will be retained and will ultimately be stored in the School or Library. The second copy may be colleted by you after the examination board meeting. Where an outside client or another University department or School is involved, the student should send an extra copy to them. Acknowledgements It is usual to insert an acknowledgement of any person who has played a significant part in the project or preparation of the report. Typing Typing should be double spaced on A4 with a 1 inch left margin and 1 inch right margin. Each chapter should start on a new page with the title typed in block letters. Numbered sections within the chapter should be typed in lower case and underlined or highlighted. Binding The main report should be bound separately but appendices can be grouped together. Computer output should be trimmed where possible to A4 size. Ensure each item has a title.
DIT/IT204/project guidelines/V. Net.1.0 Page 4

IT204

Visual Basic Project

Report Structure Title page: Contents: Summary: Project Title, author, course and academic year (all suitably capitalised and centered). Main headings and sub-headings with appropriate page numbers. All appendices should be listed on this page(s). The main text as the abstract.

Acknowledgements: Discretion of the author. Introduction: To make the report intelligible to anyone (especially an examiner) who has no prior knowledge of the project, the background should be set out here. A reasoned discussion of the subject, stating objectives, giving consideration to problem areas encountered, arguments for an against possible solutions and defence of the solution adopted. A discussion of the board achievements of the project compared with the original objectives. It should contain comments on the approach adopted to the project and in retrospect, how this could have been improved. The main learning experiences should be outlined and work should also be discussed. Remember, you should have improved both your knowledge and skills during the project. It may be expected that armed with this you could improve your project if you started again. The evaluation of the project is something the examiners will look for.

Main text:

Conclusions:

Referenced Material: Wherever you cite reference material from the Bibliography in the report this must be clearly indicated and the author acknowledged. Then in the reference section of the bibliography list the reference material in alphabetic order: e.g. An interactive course for Visual Basic .Net John Socha ,Dan Rahmel ,Visual Basic .Net Text Layout Section and paragraph identification will follow the chapter numbers. Chapters labelled 1, 2, 3,. And are subdivided into sections labelled 1.1, 1.2, 1.3, and so on indefinitely, adding a decimal point for each subdivision.

DIT/IT204/project guidelines/V. Net.1.0

Page 5

IT204

Visual Basic Project

All abbreviations used by the author should on their first occurrence be given in full with the abbreviation given in brackets. Table and diagrams should be placed as near as possible to the appropriate text and should be labelled as Table 1.1, Figure 4.5, etc. Sample Project Topics Students can create a Database and can do the data processing connected to the database e.g. Library system -Can create a database to enter the details of all the books -Display all the books details -Search for one particular book -Can create a database showing the customer name, IC, date of borrow, date of return, calculation of any overdue etc. Video rental system -Can create a database to enter the details of all the video CDs -Display -Updating -Searching Patient monitoring system -Can create a database to enter the details of the patient -Updating -Calculation of medical fee, etc 3. Assessments 3.1 Assessment Mark Scheme The project will be assessed in the following categories: A student is expected to be satisfactory in both of the assessed categories. a) Product quality b) Students performance throughout the project 3.2 Product quality The project report will be accessed by the two readers on a basis of the quality of the product defined in terms of its analysis and design, technical content, implementation, completeness, and quality assurance. The two Project readers will normally be the project supervisor (first reader) and the second reader. These assessments will take into account the complexity and scope of the project, the demonstrated performance (where applicable) and the quality, relevance and completeness of the detailed documentation contained within the project report and its appendices. It is expected that both readers will have seen the product demonstrated, if applicable.

DIT/IT204/project guidelines/V. Net.1.0

Page 6

IT204

Visual Basic Project

The following table provides a guideline for marking the project report. Once the percentage mark is obtained it must be weighted to produce a weighted mark out of 100 for the report.

DIT/IT204/project guidelines/V. Net.1.0

Page 7

IT204

Visual Basic Project

>75%

Outstanding good performance, showing insight, creative thinking or flair in excess of the normal expectations for good sound works. Well organised, clear and accurate documentation. Does not have to be perfect but flaws and omissions should be minor in relation to the quality of work taken as a whole. Very good performance, showing some insight, creative thinking or flair in excess of the normal expectations for a sound performance. Close to a A performance but falling short in some significant respect. When the work is considered as a whole some shortcomings cannot be overlooked. A sound performance. Competent and appropriate response to the task. Significant shortcomings and not serious enough to gravely weaken the whole work. A fair attempt. Some acceptable elements achieved, but the work may lack organisation and lack coherence as a whole, or have other important weaknesses.

65% to 75%

55% to 65%

40% to 55%

<40%

Fail

3.3 Project Management and Presentation The management of the product and presentation of the project is assessed under the following sections: 3.3.1 Student Performance

The students performance throughout the project will be assessed by the PMP members on the students motivation, enthusiasm, organisation, presentation of material showing the progress of the project will include the supervisors assessment. 3.3.2 Final Presentation

The final presentation is assessed by the presentation panel on the students ability to select and organise relevant material to form a structured presentation and their ability to communicate both in a formal way and in a less formal.

Marking Instructions
DIT/IT204/project guidelines/V. Net.1.0 Page 8

IT204

Visual Basic Project

Structure chart/Pseudocode Structure chart/Pseudocode/drafted design/JSP clearly shows all stages in the program. All conditions and selections are properly described and the hierarchy is correctly shown

Modularity Each module in the program is correctly represented and in the correct place on the diagram. Ensure all controls statement within the correct control and the correct component add-ins. Modularity is extracted because Visual Basic is dealing with objects rather than modules. Therefore code is embedded in individual object.

Correct notation & methods The diagram is properly drawn with boxes appropriately labeled for iteration for iteration, decisions and selections. With additional designed tools like DFD, Design View or VisData which allow implementation of coding.

Correct usage of user-defined methods and standard Program is fully modular and each module is well structured. The program is designed so that one main subroutine calls other subroutines and these may in turn call further subroutines and smooth control. It should be worked efficiently. To test whether the students can identify and apply appropriate events. Also, to test whether or not the students can use user-defined methods to extend the capability of standard events.

Meaningful Object names All identifiers /objects have meaningful names, a clear list is provided of all global variables and these are easily distinguished from local variables. To test the students the ability of using meaningful object names to enhance readability. Meaning identifier Eg. Mail which is the matter regarding email or mailing services. Readers can appreciate and tell it nature of job handling.

Standard naming convention A good attempt has been made to use meaningful name but no table is
Page 9

DIT/IT204/project guidelines/V. Net.1.0

IT204

Visual Basic Project

provided to identify them. Some attempt has been made to distinguish between local and global variables. To test students the ability to use standardized prefix to conform Visual Basic naming standard, eg. chkMail, chkInput, chkOutpu are all options Buttons and txtPrice as TextBox handling. lbl for LabelBox prefix.

Indentation/Use of comments Loops, if ... then statements, subroutines etc. are all properly indented, each important section is clearly commented

Validation Easy of use with good validation to reject incorrect data entry. With good error messages, prompting or allow user to pick the correct item from the list

Compatibility with design Most aspects of the design have been completed but there are some which are incomplete and are appear to be non-functionality.

Correct Logic The logic of the program is correct and clearly explained Use of standard language features Good use has been made of a full, range of features in the language (e.g. Proper use of loops, selection constructs, etc.) Use database and Input screen layouts Good description of planned design for input screens. Good explanations of how data will be captured and validated and /or verified. Well considered database design and database structure able to cope with planned quantity of data Output screen, print layouts Good layout of output screens, printouts and use Menu Editor. Design linked to requirements listed in design section. Output files and appropriately designed. Using Form1.PrintForm or Printer Dialog screen to change properties and control
DIT/IT204/project guidelines/V. Net.1.0 Page 10

IT204

Visual Basic Project

the printer. Using [Print Screen] key to print and capture screen and paste it on document file. Scope and limitation The documentation clearly shows the range of tasks which the program could be used to complete and makes clear any possible limitations (Will not accept certain data, needs a particular kind of printer etc.) User guide User guide is complete and written in such a way that the target user for the system would have no problem in following it Test plan, test cases & test log shown A test plan, test data including both likely data and a good selection of extreme data. Reasons for choice of test data clearly given together with a clear statement of expected outcome. Data files should contains a sufficient size of records to demonstrate proper working of systems. Clearly set of results presented.

Expected result & actual result shown Expected result matches actual result in most or all cases

Conclusion of tests conducted Sensible conclusion drawn from the testing about what might have gone wrong either in the design 6r the testing process or a statement that all tests worked as expected Documentation layout, completeness of documentation The project seems to have been developed in an ordered and planned way. All parts are present and are largely correct. With good-furnished document

Overall presentation & table of content The project is presented with a good table of contents and each of the major sections clearly identified. There is no irrelevant material included and it is easy to understand. Excellent project. Necessary acknowledgments are included (such as sources
Page 11

DIT/IT204/project guidelines/V. Net.1.0

IT204

Visual Basic Project

for any algorithms which may have been used)

Note that a project should not be bound in book form; a simple card or plastic folder with the pages held in place with treasury tags or similar. Continuous paper, such as might be used in a dot matrix printer should be separated into single sheets and presented in the correct order.

Schedule for Project submission

The students have to submit the necessary documents for the Project according to the following schedule: A. Project Proposal : 1st Submission Date - Lesson 3 B. Analysis & Design: 2nd Submission Date_Lesson6 Description of Current System (Problem and Limitation, Scope and Constraints) Narrative and requirement specification for new system Interface Design, Procedural Design, Input screen and data design C. Development and Testing: 3rd Submission Date _Lesson10 Correct usage of user defined methods and features Meaningful object names and standard naming convention Indentation / use of comments Validation Compatibility with design Correct logic ADO Database usage Form usage (minimum 5 forms) Test plan, Test cases & test log shown Expected result & actual result Conclusion of tests conducted D. Implementation: 4th Submission Date _Lesson 12 Justification for New System User guide Strengths, weaknesses and enhancements E. Documentation Page Numbering, TOC, and Cover page Project Layout (Header, footer, cleanliness) F. Presentation/ Viva (student performance, project effort, presentation skill): Lesson 13Lesson14 G. Scope and Limitation of project meets with modules objective Note: Students have to bind all documents together from previous submission and submit it as a final project document in Lesson 13 or Lesson 14.
DIT/IT204/project guidelines/V. Net.1.0 Page 12

IT204

Visual Basic Project

Sample format project lay out cover page

INFORMATICS COMPUTER SCHOOL DIT PROJECT IT204

<project title>

Full Name:_____________________ Class :<class code > Lecturer Name:_________________ Centre :<Douby Ghaut/Jurong East/TanjongPagar/Tampines>
DIT/IT204/project guidelines/V. Net.1.0 Page 13

IT204

Visual Basic Project

Country: Singapore

Sample format project layout cover page

INFORMATICS COMPUTER SCHOOL DIT PROJECT PROPOSAL IT204

Full Name : ______________________ Class: <Class Code> Lecturer Name: ___________________ Centre :<Douby Ghaut/Jurong East/TanjongPagar/Tampines>
DIT/IT204/project guidelines/V. Net.1.0 Page 14

IT204

Visual Basic Project

Country: Singapore Appendix A (external proposal) INFORMATICS COMPUTER SCHOOL PROJECT PROPOSAL FORM FOR DIT Name of Proposal: Address: Telephone No: Title of proposed Project: Brief Description of the Project:

Main subject area covered by project:

Software requirements:

Hardware Requirements:

Special skills needed by student (if any)

For School Use Only Name of Contact at School: Received by: Passed by:
DIT/IT204/project guidelines/V. Net.1.0

Date: Date:
Page 15

IT204

Visual Basic Project

Expenditure needed:

DIT/IT204/project guidelines/V. Net.1.0

Page 16