Reference no: EM1395948

To demonstrate completing and delivering a prototype RAD system using OOPs capabilities of VB.NET.

Prepare a VVB Boards transaction system that can be installed and run on a Windows system that does not have the Visual Basic programming application on it (but does have .NET Framework installed on it.) You are to define a class that includes the business logic layer required of the purchase area of the system. The Final Project is a more formal presentation of a complete system, and care should be taken to submit a finished product.

1. Plans (interface design, object and properties table, class diagrams, and event procedures/pseudo code) are needed only for newly defined classes and forms needed for the Shirt Transaction Calculations. Be sure to read and work through Chapter 12 before designing this final project. You can use the Class Designer to graphically design the class (not in your text: see Discussion notes.) You may use any Windows controls you wish to enhance the system. For instance, graphics or animations, timers, sound or media players, calendars, MDI, status bar, or toolbar embellishments will enhance your system. (It is highly recommended that you combine ALL plans and printouts of this progressive RAD project into a portfolio for your own future use.)

2. The source code, including the class definitions needed for Shirt orders in your system.

3. The required documentation: description, flowchart, class diagrams.

Provide the finished program (.exe) and the Visual Studio project folder.

STEPS TO COMPLETION OF PROJECT

1. See the System Requirements for guidance in completing the VVB Boards OOPs Windows system.

2. Use previous chapters as a basis for adding other existing forms and controls from earlier versions of the VVB Boards case study requirement. Save them all to a single integrated program. Add as much or as little as needed, as long as you keep in mind that controls for Windows applications are very different from controls on Web pages.

3. Add two unique enhancements of your choice.

4. Add a completed Report done with Crystal Reports or another report system, using the VeryBoards.mdb database (There have been some problems with SSE database reports with Crystal Report Generator, so the Access files may be used for final project database.) [Crystal Reports does not have the same flexible connection strings for database references and report source references.] Be sure to code a menu, button, or toolbar to allow a user to view and print the report from within the VVB Boards transaction system.

5. Debug and then compile the completed project. Turn in the completed project with all folders.

System Requirements

1. Prepare an order for purchase of team shirts, varying in size, pocket and monogram options, and resulting price. I will print the order as a customized invoice (not a screen shot) that includes order total, any items added, the customer's name, and so forth.

2. A summary of the day's sales: total number of orders, total number of shirts, and total sales.

3. Change the shirt collar style needed from the Custom Shirt Center form of the Very Boards System and configure a board and boot rental snowboard order.

4. Have the capability to print out an inventory snowboard product list and/or a manufacturer list via a Crystal report or other report system (you can use a Report.rdlc component, ReportViewer control, and the Report Viewer smart tag).

5. Have the capability to change a manufacturer account (except for the key field, which should be read only) OR add to the VeryBoards Manufacturer table. An update provides that any changes saved are reflected from one run to the next.

6. View single fields of a product item a manufacturer supplies by locating the record through selection of manufacturerID from a combo box on a detail record view of manufacturer table records. This requires manipulating the two related tables joined by a primary and secondary key.