Module and Code Names of members

: :

Visual Basic.NET Praveena Sarathchandra(CB003403) Pulasthi Perera (CB003472) Aritha Hettiaratchi (CB003516)

Intake Title

:

Diploma in Computing and IT

Intake Code Submitted to

: :

DF0931ICT Ms. Nadeera Ahangama

Date Assigned Date Due

: :

11th August 2009 29th September 2009

1|Page

Criteria (Maximum 5 marks awarded for each criteria)

Score Excellent Good Adequate (3) Poor (2) Very poor (1 or 0)

(5) (4) ANALISIS AND DESIGN Screen Report and Database Design Flowchart or Pseudo code (Accuracy and Correctness) CODING Naming Conventions and Meaningful variables Indentation and remarks DOCUMENTATION Content and Completeness Quality of presentation Weekly Reports (On time and quality content) Introduction, Project Description and Conclusion Testing (Testing plan and results) RUNNING PROGRAM Functional Quality and Validations System Interface Reports generation *5= Total *4=

*3=

*2=

*1=

Group Marks (60)

Remarks:

2|Page

Lecture¶s Use Only Individual Student Marks (Total 40 Marks) ± Presentation
Criteria **Presentation abilities **Clarity of Explanation Skills and Knowledge Ability to Answer Questions Total

Name Praveena Pulasthi Aritha

10

10

10

10

40

**Clarity of Explanation

Understanding of the project requirement Description / justification Analyzing the problem (6)

4 3 3 3 3 2 2

[ [ [ [ [ [ [

] ] ] ] ] ] ]

**Presentation abilities

Confidence Pronunciations Eye contacts Language

Total Marks (100) Name: _________/ 60 + _________/ 40 = _________/ 100 Name: _________/ 60 + _________/ 40 = _________/ 100 Name: _________/ 60 + _________/ 40 = _________/ 100 Remarks: 3|Page

Table of Contents
Acknowledgement ......................................................................................................... 5 Introduction ................................................................................................................... 6 Project Description .................................................................................................... 7 1.1 Functionality of the project............................................................................... 7 Hardware Software Specifications ............................................................................. 8 2.0 Data Flow Diagrams ................................................................................................ 9 2.1 Context Diagram .................................................................................................. 9 2.2 Level 0 ............................................................................................................... 10 2.3 Level 1 ............................................................................................................... 11 3.0 Sample Output ....................................................................................................... 12 4.0 Database Design .................................................................................................... 15 4.1 Entity Relationship diagram ............................................................................... 15 4.2 Table design .......................................................................................................... 16 4.21 Customer Table ................................................................................................ 16 4.22 VCD Table ....................................................................................................... 16 4.23 VCD Rental Table ............................................................................................ 17 5.24 VCD Return Table ........................................................................................... 17 5.0 Testing ................................................................................................................... 19 6.0 Limitation .............................................................................................................. 24 7.0 Further Development ............................................................................................. 25 Conclusion .................................................................................................................. 26 Appendix ..................................................................................................................... 27 Gantt Chat ............................................................................................................... 27 Minutes of Mandatory Meetings .............................................................................. 28 Agreed Work Percentage ......................................................................................... 31 4|Page

Acknowledgement

We would like to thank our lecturer Ms. Nadeera Ahangama, without her continuous guidance and assistance we wouldn¶t have been able to get anywhere close to what we have done in this project. She also made it through her very busy schedule just to help us with our problems that we faced while developing this program and for that we are very thankful to her. Also, our gratitude goes to APIIT Lanka (PVT) Ltd for providing the necessary library facilities which we used a lot to complete this project and also the computer laboratories. Finally we would extend our thankfulness to our batch mates of DF0931ICT for their help with even the smallest problems that we encountered while working on this project. Last but not least we are indeed grateful to all our friends stood by us helping in various ways.

5|Page

Introduction
Our assignment topic was to develop software for a VCD rental shop, where the entire system is computerized to allow burrowing, returning modifying, updating and many other new features which accommodate with regard to this kind of system. We developed this project by using the software Visual Basic. NET for the coding and also the designing of the interface, this was aided with the software Microsoft SQL Server where we used this as our database to store and retrieve the data from. The system is designed so that it will appear first with a splash screen, also known as a welcome screen, which then moves on to a login screen where the username and the password has to be entered in order to differentiate between the operator, administrator and the customer. This is done so that these different users have restricted access to the system. A customer has the privileges only to view: y To view his or her details and the VCDs that are available at the rental store

The operator has the access to the following items: y The customer details and also the VCD details in order to operate the transactions taking place in the rental store. In addition to the above items, of both the customer and the operator, the administrator has the privileges to the following: y The administrator has all the writes, when we take a look at all the other two groups. The administrator has the privileges to add, delete and modify customer¶s details and the VCD details.

6|Page

Project Description

1.1 Functionality of the project This is a system that is developed for a VCD rental shop that keeps track of the VCDs that are being rented, the customers that borrow the VCDs and the transactions that take place. This system is handled by the shop keeper, who is the operator in our case. The administrator is the head of this business and has all the privileges that are provided with the software. Like the deletion of customer details, modifications and also addition of new customers, these can only be done by the administrator. The operator has access to all the details of the customers and also the VCD details but doesn¶t have the privilege to change any of the information. The customer also has been given an interface to deal with, where the customer has only the privilege of viewing details such as his or her account details or search for the available VCDs available at the store. These three categories are being differentiated when it comes to the login screen where the administrator has to enter their unique username and password and they will be taken to the administrator form. If the username and password matches that of the operator then the operator form will be displayed, and if the customer enters his or her username and password the customer form will be displayed. The fine and all the dates of when the customer joined and when a VCD was borrowed has been programmed to be auto generated so that the user wouldn¶t make any mistakes and the chance of errors will also reduce, which means that the program will be having a good error handling system. The fine will be added if the user has rented the VCD for more than three days.

7|Page

Hardware Software Specifications
Minimum Requirements Processor Personal computer with a Pentium 2 class processor,450 Megahertz(MHz) Operating System Windows XP Professional Windows Vista Windows Seven

y y y

Memory

y

Windows XP Professional, 160 megabytes (MB) of RAM.

y y y y Hard Disk

Windows 2000 Professional, 96 MB of RAM Windows 2000 Server, 192 MB of RAM Windows NT 4.0 Workstation, 64 MB of RAM Windows NT 4.0 Server, 160 MB of RAM

500 MB on system drive, 2.0 gigabytes (GB) on installation drive.

Drive Display

CD-ROM or DVD-ROM drive. Super VGA (800*600) or higher resolution monitor with 256 colors.

Mouse

Microsoft mouse or compatible pointing device.

8|Page

2.0 Data Flow Diagrams

2.1 Context Diagram

Fine Details

Damages, Late return Return

Customer

Customer Details

Membership Request

Confermation

Customer ID

Rent Items Return Details & Rules

Extreme Video Center

Fine Details

Add new customer & New ID Rent Items Return Details & Return Rules Repoarts Add stock Details Return accept Damage, late return Details

Operator

Administrator

9|Page

2.2 Level 0

10 | P a g e

2.3 Level 1

11 | P a g e

3.0 Sample Output
Login Screen

Welcome Screen

12 | P a g e

Authentication

User Details

13 | P a g e

Borrowed Items

14 | P a g e

4.0 Database Design

4.1 Entity Relationship diagram

15 | P a g e

Users

Field Name Customer-ID Name IC Number Address Gender DOB Age

Data Type Auto Number(Primary Key) Text Text Text Text Date Numeric

4.2 Table design
Field Name Data Type

4.21 Custo

mer Table

4.22 VCD Table
16 | P a g e

Customer-ID Name Field Name IC Number VCD-ID Address Customer-ID Gender Rented Date DOB Status Age

Auto Number(Primary Key) Text Data Type Text Numeric Text Numeric Text Date Date Boolean(IN\OUT) Numeric

Field Name

Data Type

4.23 VCD Rental Table

5.24 VCD Return Table

17 | P a g e

VCD-ID Customer-ID Rented Date Status

Numeric Numeric Date Boolean(IN\OUT)

18 | P a g e

5.0 Testing
User ID/Customer ID: Test: Numbers will be auto generated. Result: Entry of any characters is restricted. Only numbers should be accepted.

Name: Test: Enter names into the textbox. Result: Alphabets should be allowed

IC / Passport No: Test: Enter Alphabets and numbers. Result: Both types should be accepted.

Address: Test: Enter Alphabets and numbers Result: Both should be accepted.

19 | P a g e

Gender: Test: Select the radio buttons. Result: Both selections should be accepted.

Date of birth: Test: Select Alphabets and numbers Result: Date of Birth should be according to the data time picker.

Login: Test: Enter alphabets in the text box. Result: Only numbers should be accepted. And there should be admin rights

Username: Test: Entering Alphabets and numbers Result: Both should be accepted.

Password: Test: Entering Alphabets and numbers Result: Both should be accepted.

20 | P a g e

Item id: Test: Enter numbers in the text box. Result: List the item details

Rented date: Test: Alphabets and numbers are acceptable. System date should be rented date. Auto generates it. Result: Numbers are according to the date time picker. Auto generates it.

Return date: Test: alphabets and numbers are acceptable. Auto generated date. Result: Numbers according to the data time piker. Auto generates using system date.

Fine: Test: Auto generated fine, by calculating late days. Result: Only numbers should be accepted.

Bill: Test: Auto generated bill according to the amount of fine. Result: Alphabets and numbers should be accepted. Print the all details. Ex: customer id, item id and amount of fine. 21 | P a g e

Amount paid: Test: Enter amount. It should be number. Result: Only numbers should be accepted.

VCD id Test: Entering alphabets and numbers in the text box. Result: Entry should be limited. Only Administrator should be accepted.

Title Test: Entering Alphabets and numbers Result: Both should be accepted.

Producer Test: Entering Alphabets and numbers Result: Both should be accepted.

Year Test: Entering Alphabets and numbers Result: Numbers according to the data format should be accepted.

22 | P a g e

Category Test: Select the category in combo box. Result: All selections should be accepted.

Stock Test: Entering Alphabets and numbers Result: Only numbers should be accepted.

Available copies Test: Entering Alphabets and numbers Result: Only numbers should be accepted.

23 | P a g e

6.0 Limitation
y When compiled to an ³.exe´ format the program would not run on Mac machines since they use a different operating system when compared to the normal windows operating system. y The password that is given when the person registers to the system has to be used and cannot be changed.

24 | P a g e

7.0 Further Development
The further developments that we would like to have added were mainly the new features, which are like: y Uploading of images and trailers of a particular movie that has been recently added. y The system should have the option of generating reports as graphs so that it would be easier to understand and also more user friendly rather than having only to look at lists of data. y Allow the user, operator or the administrator to change their password since they are given one and they have to keep on using that. y Provide a help function so that it would be easier to get help at that moment instead of asking the operator help.

25 | P a g e

Conclusion
Visual Basic.NET is user friendly software whose abilities were clearly seen in our project. It gave us a hand on experience about the software, what it is used for and how it can be applied to a day to day situation. The project which was carried out with the purpose of designing a computerized system for a VCD rental shop, developing it and implementing it successfully was the main objective of this whole process. This documentation was a guide to all the readers, the viewers who are interested in using the system for evaluating the project or trying to get an idea how to carry out the similar projects in the future. This documentation is carried out according to the requirements highlighted and discussed in the meetings. The system is successful in terms of interface design and the functionalities. The Learning that was Gain carrying out this project was achieved while developing and coding, implementing. Each member gained the experience about visual basic.net as they are coding, according to the project requirements given in the description. Critically evaluating the system it is user friendly and with providing the basic aspects highlighted in the project description.

26 | P a g e

Appendix
Gantt Chat

27 | P a g e

Minutes of Mandatory Meetings

Meeting No. 01 Date: Start Time: Venue: Purpose: Attendees: Praveena Sarachchandra (group leader) Pulasthi Perera Aritha Hettiarachchi Approaches: The scenario was discussed, taking each action that involves with the lending of a VCD until returning of a VCD, with respect to procedures and transactions. A DFD was sketched summarizing the procedures that take place in the VCD rental shop. 13/ 08/ 09 5.00pm-6.00pm L3-SR Overview of project

Meeting No. 02 Date: Start Time: Venue: Purpose: Attendees: Praveena Sarachchandra (group leader) Pulasthi Perera Aritha Hettiarachchi 25/ 08/ 09 1.00pm-1.45pm Cafeteria Designing structure for database and interface

28 | P a g e

Approaches: DFDs of members were discussed and a finalized DFD was drawn. The ER-Diagram was drawn, taking concern of the DFD and required specifications for table design.

Meeting No. 03 Date: Start Time: Venue: Purpose: Attendees: Praveena Sarachchandra (group leader) Pulasthi Perera Aritha Hettiarachchi Approaches: The ER-Diagram was converted to tables and modifications for several tables were discussed. The tables were divided to each of the group members to be developed. 30/ 08/ 09 3.45pm-5.30pm L2-SR2 Developing database

Meeting No. 04 Date: Start Time: Venue: Purpose: Attendees: Praveena Sarachchandra (group leader) Pulasthi Perera Aritha Hettiarachchi 29 | P a g e 14/ 09/ 09 3.30pm-5.00pm L2-SR2 Starting with the appropriate coding

Approaches: Necessary validation checks were discussed along with the logic briefly. The modules were broken down to group members to start out with the coding.

Meeting No. 05 Date: Start Time: Venue: Purpose: Attendees: Praveena Sarachchandra (group leader) Pulasthi Perera Aritha Hettiarachchi 30/ 09/ 09 2.30pm-6.00pm L3-CR8 Finalizing project

Approaches: It was decided to finalize the interface for the forms and get the sample output screens, altogether with the combining of documentation, on the day of the submission itself.

30 | P a g e

Agreed Work Percentage

Name
Praveena Pulasthi Aritha Victor Hettiaratchi

Percentage Work Done

Signature

In situations where they is a dispute, then each group member should complete the following assessment form as outlined below. In this form each member divides the 100% between himself/herself and the other members of the group and fills in a column (either A, B, C, D, E, F) where A, B, C, D, E, F reflects student names and the table below must be substituted with actual names when used.
PERCENTAGE PERCENTAGE PERCENTAGE PERCENTAGE PERCENTAGE PERCENTAGE

STUDENT NAME

A

B

C

D

E

F

A B C D

31 | P a g e

Signature Total of 100%

A¶s signature

B¶s signature

C¶s signature

D¶s signature

E¶s signature

F¶s signature

I, hereby agree that the above members have undertaken the above tasks and their work is reflective of what I have written above. Name of Group Leader: Group Leader¶s Signature: ____________________

32 | P a g e

Sign up to vote on this title
UsefulNot useful