final year mca presentation

Kiosk Printing Dashboard

Developed By : Bharat Lakhiyani (11MCA032)Developed At : Vrindi India Pvt. Ltd.

Submitted to : Smt. Chandaben Mohanbhai Patel Institute of Computer Application

Internal GuideMr. Arpit Trivedi

External Guide Mr. Kapil Akhia

Miss. Manaswi Darjee

INDEX

1. Company Profile2. Project Profile3. Definition4. Scope5. Modules Description6. Diagrams

1. Module Hierarchy Diagram2. Use case Diagram3. Activity Diagram4. Sequence Diagram5. Class Diagram

7. Data Dictionary8. Screen Layouts9. Reports10. Test Cases11. Future Enhancements12. Bibliography13. Plan & Actual(Weekly)

Company Profile

Hosted in New Jersey but also with offices in Delhi (India), Vrindi India Pvt. Ltd. has the ability to service your needs wherever you may be.

Vrindi provide an extensive range of optional components and extra functionality such as image galleries, newsletter management etc.

Our goal is dedicated to a cost effective and customer friendly restaurant online ordering software & solutions for the Restaurants worldwide.

Project Profile

Title : Kiosk Printing and Dashboard

Front-end : Microsoft Visual Studio 2010

Back-end : Microsoft SQL Server 2008

Add. Tools : Telerik WPF Toolkit, WPF, WCF

Team Size : 2

Definition

“To make such an application which deals with WCF/WEB Services to retrieve data from database

about orders placed, to classify orders according to different branches and also to provide auto print functionality with fully customizable GUI using

WPF(Windows Presentation Foundation).”

Scope

Location Filterization All orders from all locations were displayed and

actually there is requirement that at each location, only orders specific to location must be displayed and only the main branch must get all order details.

Also orders at main branch must be in proper format and categorized.

Auto Print There should be functionality that user can configure

for prints to be taken directly. Print Status Acknowledgement

There should be functionality of tracking each print.

To be Continued…

..Scope

Get Solution to Platform Problem The application must be capable to run in all OS

platforms. Work On Extension(R&D)

To develop an extension for printing and order status updation.

Reduce PDF to Image Conversion To directly convert contents to a printable format

without performing PDF to Image conversion. Work on Remote printing device

Allowing user to print orders in remote printing device(e.g. Small Printers or Receipt Printer) .

Module Description

Login To support login functionality This module Authenticates to the server.

Registration It will support URL registration to the system

Filterization To support location wise filters for the admin

Customization Customization of the user’s interface and app settings

are set from this module. Printing

To Support printing functionality in the system. It is also helper to report print status.

To be Continued…

..Module Description

Notification When new order comes this module helps to notify the

system Updation

This module provides functionality of automatic system updation.

Print Status To report print status to the centralized monitoring

system, this module provides functionality for that. App Status

To report app’s alive status to the centralized monitoring system.

Logs To maintain each event logs in the system.

Diagrams

Module Hierarchy

Printing Kiosk And Dashboard

Login Registration

Filterization

Customization

Printing

Automatic Manual

Updation

Print Status

Automatic Manual

Notification

App Status

Logs

Invoice Receipt Invoice Receipt

Cloud Cloud

Use Case Diagram

Use case Diagram for Kiosk Printing and Dashboard

Activity Diagram

Activity diagram to register for using “KIOSK”

To be Continued…

..Activity Diagram

Activity diagram to Login to “KIOSK”

To be Continued…

..Activity Diagram

Activity diagram to Use “KIOSK”

Sequence Diagram for Login

Sequence diagram for login to “KIOSK”

Admin System

Supply Credentials

Display appropriate data

Load appropriate

filters

Sequence Diagram for customization

Sequence diagram for customization in “KIOSK”

Admin Settings

Customize Settings

Save Changes

Apply Changes

Sequence Diagram for Printing

Sequence diagram for printing in “KIOSK”

User Home

Give print Command

Print Module

Forward request

Printing Helper

Generate printable document

Printer

Invoke print with required

details

Print

Sequence Diagram for filterization

Sequence diagram for filterization in “KIOSK”

Admin Home

Filter Command

Orders

GetAllOrders(GUID)

Return and bindrecords.

Display filtered orders

Class Diagram

Class diagram from “WebTelStore” Schema To be Continued…

..Class Diagram

Class diagram from “WebTelRum” Schema

Data Dictionary

WT_ORDERS

Table Name WT_ORDERTable Description Used for storing master order details.Constraints Primary Key, Foreign Key

Field Name Type Allow Nulls. Description

order_id uniqueidentifier No Unique ID for each order placedorder_code nvarchar(30) Yes Unique Code for each order placedstore_id uniqueidentifier No Id of the store for which the order is placed

consumer_id uniqueidentifier Yes Unique ID for the consumerconsumer_name nvarchar(50) Yes Name of the consumerconsumer_phone nvarchar(30) Yes Phone number of the consumerconsumer_address1 nvarchar(256) Yes Address 1 of the consumerconsumer_address2 nvarchar(256) Yes Address 2 of the consumerconsumer_city nvarchar(20) Yes City of the consumerconsumer_state nvarchar(20) Yes State of the consumerconsumer_zipcode nvarchar(10) Yes Zipcode of the stateconsumer_email nvarchar(80) Yes Email of the consumer order_type nvarchar(20) Yes Type of order:

- ASAP- Future Order

placed_datetime datetime Yes Date and Time when the order is placed

schedule_delivery_datetime datetime Yes Date and Time when the order is scheduled to be delivered.

ready_datetime datetime Yes Date and Time when the order is ready.

amt decimal(18, 2) Yes Total amount of the items ordered.tax decimal(18, 2) Yes Tax incurred on the ordergratuity decimal(18, 2) Yes Gratuity amount amt_paid decimal(18, 2) Yes Total amount paid by the consumerperson_taking_order uniqueidentifier Yes ID of the person who takes the order

To be Continued…

..WT_ORDERS

To be Continued…

Fieldname Type Allow Nulls. Descriptionperson_delivering_order uniqueidentifier Yes ID of the person who will deliver

the order

order_status nvarchar(20) Yes Staus of the order:- Served- BeingPrepared- new- NewButRead- Read- Delivered- DeliveryInProgress- Confirmed- Rejected- Cancelled- Assigned- Ready

promo_id uniqueidentifier Yes ID of the couponpayment_status nvarchar(20) Yes Status of payment:

-Paid-Pending-Failed-Refunded-Approved

..WT_ORDERS

To be Continued…

Fieldname Type Allow Nulls. Descriptionpayment_method nvarchar(50) Yes Method of payment:

-PayByPhone-GoogleCheckOutAcceleratedPayHostedCheckout-DirectConnectCreditCard-CardSmithPayment-AuthorizeCreditCard-CreditCard-CCAvenue-NoPayment-MercuryPayHostedCheckout-MercuryPayCreditCard-PayPal-CardSmith

comment nvarchar(MAX) Yes Order level commentins_upd_user nvarchar(40) No User Nameins_upd_application nvarchar(50) No Store Nameins_upd_datetime datetime No Date and Time when the

order entry is inserted into the table.

shipping_amt decimal(18, 2) Yes Amount of shippingScheduleASAP bit Yes Whether ASAP is true or not:

1 : True0 : False

..WT_ORDERS

To be Continued…

Fieldname Type Allow Nulls. DescriptionNotificationSentSuccess bit Yes Whether notification is sent or

not.

package_handling_charges decimal(18, 2) Yes Charge for handling the package

order_tip decimal(18, 2) Yes Tip given on the orderis_order_ack_by_restauranteur bit Yes Whether the order is

acknowledged by the restauranteur

- 0- 1

order_ack_by_restauranteur_user_name

nvarchar(512) Yes Name of the user by whom the order is acknowledged

is_order_ack_by_tech_support bit Yes Whether the order is acknowledged by the technical support team

- 0- 1

order_ack_by_tech_support_user_name

nvarchar(255) Yes User name of the technical support person by whom the order is acknowledged

order_ack_by_restauranteur_date_time

datetime Yes Date and Time when the order is acknowledged by the restauranteur

..WT_ORDERS

To be Continued…

Fieldname Type Allow Nulls. Description

order_ack_by_tech_support_date_time

datetime Yes Date and Time when the order is acknowledged by the technical support person

consumer_apt_suite_no nvarchar(50) Yes Consumer apartment suit number

consumer_floor nvarchar(50) Yes Consumer apartment floor number

consumer_cross_street nvarchar(100) Yes Consumer Street Name

consumer_buzzer nvarchar(50) Yes

coupon_code nvarchar(128) Yes Code of the coupon applied

coupon_discount_amt decimal(18, 2) Yes Discount amount given on the order

extra_charges decimal(18, 2) No Extra charges applied on the order amount

adjust_amount decimal(18, 2) Yes

WT_ORDER_OFFLINE

To be Continued…

Table Name WT_ORDER_OFFLINETable Description Used for storing master order details.Constraints Primary Key

Fieldname Type Allow Nulls. Descriptionorder_id uniqueidentifier No Unique ID of the order

which is placed offline

order_code nvarchar(30) Yes Code of the orderstore_id uniqueidentifier No ID of the store for which the

order is placed

consumer_id uniqueidentifier Yes ID of the consumer who placed the order

consumer_name nvarchar(50) Yes Name of the consumer who placed the order

consumer_phone nvarchar(30) No Phone number of the consumer

consumer_email nvarchar(80) Yes Email ID of the consumer

amt_paid numeric(18, 2) No Amount paid by the consumer

consumer_address1 nvarchar(256) Yes Address 1 of the consumer

consumer_address2 nvarchar(256) Yes Address 2 of the consumer

consumer_apt_suite_no nvarchar(50) Yes Appartment suit number of the consumer

consumer_floor nvarchar(50) Yes Floor number of the consumer

..WT_ORDER_OFFLINE

consumer_cross_street nvarchar(100) Yes Street name of the consumer

consumer_buzzer nvarchar(50) Yes

consumer_zipcode nvarchar(10) Yes Zipcode of the state

consumer_city nvarchar(20) Yes City of the consumer

consumer_state nvarchar(20) Yes State of the consumer

order_type nvarchar(20) Yes Type of order:- ASAP- Future Order

placed_datetime datetime Yes Date and Time when the order is placed

ins_upd_user nvarchar(40) No User Name

ins_upd_application nvarchar(50) No Store Name

ins_upd_datetime datetime No Date and Time when the order entry is inserted into the table.

WT_USER_AUTHENTICATIONTable Name WT_USER_AUTHENTICATIONTable Description Used for maintaining sessions for users.Constraints Primary Key

Fieldname Type Constraints Description

token_id uniqueidentifier Yes

user_name nvarchar(255) Yes

store_id uniqueidentifier Yes Store ID

WT_PENDING_CHECKOUTTable Name WT_PENDING_CHECKOUTTable Description Used for storing order checkout master information for the order in

progress.Constraints Primary Key

Fieldname Type Allow Nulls. Descriptionpending_checkout_id Uniqueidentifier No Unique ID of the order which is

currently being placedorderid Uniqueidentifier No ID of the order which is

currently being placedpending_checkout_code nvarchar(30) No Order CodeStoreid Uniqueidentifier No Store ID for which order is

placedpayment_received_id Uniqueidentifier Yesmessage_comments nvarchar(MAX) Yes Comments if anySubject nvarchar(2048) No Subject of the mailemail_html nvarchar(MAX) No Email contentfrom_display_name nvarchar(256) No Email ID of the sender of the

mailto_list nvarchar(2048) No Email ID of the person who

placed the orderpending_amount decimal(18, 2) No Amount which is pendingIspaid Bit No Whether the pending amount is

paid or not- 0- 1

To be Continued…

..WT_PENDING_CHECKOUTpayment_option nvarchar(128) No Method of payment:

-PayByPhone-GoogleCheckOutAcceleratedPayHostedCheckoutDirectConnectCreditCard-CardSmithPayment-AuthorizeCreditCard-CreditCard-CCAvenue-NoPaymentMercuryPayHostedCheckout-MercuryPayCreditCard-PayPal-CardSmith

payment_status nvarchar(50) Yes Status of payment:-Paid-Pending-Failed-Refunded-Approved

Isnewrequest Bit No Whether the request is new or not

- 0- 1

website_url nvarchar(260) No Website URL through which the order is placed

To be Continued…

..WT_PENDING_CHECKOUT

is_order_ack_by_restauranteur Bit Yes Whether the order is acknowledged by restauranteur

order_ack_by_restauranteur_user_name nvarchar(512) Yes Name of the restauranteur by whom the order is acknowledged

is_order_ack_by_tech_support Bit Yes Whether the order is acknowledged by the technical support team

order_ack_by_tech_support_user_name nvarchar(255) Yes Use Name of the technical support person by whom the order is acknowledged

order_ack_by_restauranteur_date_time Datetime Yes Date and Time when the order is acknowledged by restauranteur

order_ack_by_tech_support_date_time Datetime Yes Date and Time when the order is acknowledged by technical support team

invoice_number nvarchar(30) Yes Invoice number of the order

invoice_date Datetime Yes Date when the invoice is generated

payment_received_datetime Datetime Yes Date and Time when the payment is received

ins_upd_user nvarchar(40) Yes User Name

ins_upd_application nvarchar(50) No Store Name

ins_datetime Datetime No Date and Time when the entry is inserted in the table

upd_datetime Datetime No Date and Time when the record is updated

WT_PENDING_CHECKOUT_DETAILS

Table Name WT_PENDING_CHECKOUT_DETAILSTable Description Used for maintaining consumer and billing details for the checkout of

a current order.Constraints Primary Key

Fieldname Type Allow Nulls.pending_checkout_details_id uniqueidentifier Nopending_checkout_id uniqueidentifier Noconsumer_id uniqueidentifier Yesconsumer_name nvarchar(50) Yesconsumer_phone nvarchar(30) Yesconsumer_address1 nvarchar(256) Yesconsumer_address2 nvarchar(256) Yesconsumer_city nvarchar(20) Yesconsumer_state nvarchar(20) Yesconsumer_zipcode nvarchar(10) Yesconsumer_email nvarchar(80) Yesbilling_name nvarchar(50) Yesbilling_address1 nvarchar(256) Yesbilling_address2 nvarchar(256) Yesbilling_city nvarchar(20) Yesbilling_state nvarchar(20) Yesbilling_zipcode nvarchar(50) Yesconsumer_comments nvarchar(MAX) Yesins_upd_user nvarchar(50) Yesins_upd_application nvarchar(50) Yesins_upd_datetime datetime Yes

WT_STORETable Name WT_STORETable Description Used for maintaining store details.Constraints Primary Key

Fieldname Type Allow Nulls. Descriptionstore_id uniqueidentifier No Unique ID of the storestore_code nvarchar(20) No Unique Code of the storeeffective_date datetime Yes Dateactive_status nchar(1) Yescust_provided_store_code nvarchar(40) Yesname nvarchar(100) Yes Store Namedescription nvarchar(255) Yes Description of the storeplaza_id uniqueidentifier Yeswebsite_url nvarchar(100) Yes URL of the websitefast_search_text nvarchar(MAX) Yesparent_store_id uniqueidentifier Yes ID of the parent storeins_upd_user nvarchar(40) No User Nameins_upd_application nvarchar(50) No Store Nameins_upd_datetime datetime No Date and Time when the

order entry is inserted into the table

WT_STORE_USER_MAPTable Name WT_STORE_USER_MAPTable Description Used for maintaining registration information to KIOSK.Constraints Primary Key, Foreign key

Fieldname Type Allow Nulls. Descriptionstore_id uniqueidentifier No Unique ID of the storeuser_id uniqueidentifier No Unique ID of the userins_upd_user nvarchar(40) No User Nameins_upd_application nvarchar(50) No Store Nameins_upd_datetime datetime No Date and Time when the

order entry is inserted into the table

WT_ORDER_STATUS_HISTORY

Table Name WT_ORDER_STATUS_HISTORYTable Description Used for maintaining order’s History and Status.Constraints Primary Key, Foreign key

Fieldname Type Allow Nulls. Descriptionid uniqueidentifier No Unique ID for database.order_id uniqueidentifier No Unique ID of the userorder_status nvarchar(20) No Staus of the order:

- Served- BeingPrepared- new- NewButRead- Read- Delivered- DeliveryInProgress- Confirmed- Rejected- Cancelled- Assigned- Ready

estimated_timing_window nvarchar(255) Yescomments Ntext Yesins_user nvarchar(255) No User Nameins_application nvarchar(255) No Store Nameins_datetime datetime No Date and Time when the order entry is inserted in

table

WT_APP_STATUSTable Name WT_APP_STATUSTable Description Used to store reporting information with full details from KIOSK

Application.Constraints Primary key

Fieldname Type Allow Nulls. Descriptionid uniqueidentifier Nouser_name nvarchar(50) No User Namehost_name nvarchar(255) No URL of the restaurant whose orders are

displayed in the dashboard

mac_address nvarchar(20) No MAC address of the computer through which the client has logged in

ins_datetime datetime No User Nameins_upd_application nvarchar(255) No Store Nameextra_details nvarchar(MAX) Yes Logged in user name, IP address of the

computer through which the user has logged in, system name

WT_PRINT_STATUSTable Name WT_PRINT_STATUSTable Description To store Printing Status Information for an each order.Constraints Primary key, Foreign key

Fieldname Type Allow Nulls. Descriptionid uniqueidentifier Norequest_id uniqueidentifier No Order ID of the usercommunication_id uniqueidentifier No Unique ID given to those

records whose receipts are printed or given for printing or failed after giving for printing

last_updated_status nvarchar(255) Yes Status of the print:- New- Spooling- Printing- Success- Failed

extra_details ntext Yes Print Status, Printer Name, System Name

ins_datetime datetime No User Name who logged into the application

upd_datetime datetime Yes Date and Time when the record is inserted in the table

ins_upd_user nvarchar(127) No User Nameins_upd_application nvarchar(255) No Application Name: Restaurant

Wave Dashboard

WT_GENERIC_FORMTable Name WT_GENERIC_FORMTable Description Used to store information other than order.Constraints Primary Key, Foreign key

Fieldname Type Allow Nulls. Descriptionid uniqueidentifier No Unique IDstoreid uniqueidentifier No ID of the storename nvarchar(128) Yes Name of the storeemail nvarchar(320) Yes Email ID of the userphone nvarchar(32) Yes Phone number of the userform_type nvarchar(50) Noxml_data xml Yes Content of the xml fileins_upd_user nvarchar(50) No User Nameins_upd_application nvarchar(50) No Store Nameins_upd_datetime datetime No Date and Time when the record is inserted in the tableorder_ack_by_tech_support_date_time datetime Yes Date and Time when the order is acknowledged by the

technical support person

is_order_ack_by_restauranteur bit Yes Whether the order is acknowledged by the restauranteur

order_ack_by_restauranteur_user_name nvarchar(512) Yes User name of the restauranteur by whom the order is acknowledged

is_order_ack_by_tech_support bit Yes Whether the order is acknowledged by the technical support team

order_ack_by_tech_support_user_name nvarchar(255) Yes User name of the technical support person by whom the order is acknowledged

order_ack_by_restauranteur_date_time datetime Yes Date and Time when the order is acknowledged by the restauranteur

request_id varchar(50) Yes Order IDupd_datetime datetime No Date and Time when the order is inserted in table

WT_MEDIA_COMM_LOGTable Name WT_MEDIA_COMM_LOG

Table Description Used to store all latest information of each communication with a printer and fax server.

Constraints Primary Key, Foreign key

Fieldname Type Allow Nulls. Descriptionid uniqueidentifier No Unique IDrequest_id uniqueidentifier No Order IDcommunication_id nvarchar(255) Yes Unique ID for each communicationmedia_type nvarchar(50) No Type of media:

- Fax- Print- IVR

last_updated_status nvarchar(255) Yes Status of print:- New- Spooling- Printing- Success- Failed

extra_details ntext Yes If media type is fax: Status of fax, fax server name, alternative way of fax if failed with mail ID, subject and country code.If media type is print: Status of print and printer name.If media type is IVR: Status of IVR

ins_datetime datetime No Date and Time when the record is inserted in the tableupd_datetime datetime Yes Date and Time when the record is last updatedins_upd_user nvarchar(127) No User Nameins_upd_application nvarchar(255) No Application Namelast_updated_status2 nvarchar(255) Yes

WT_MEDIA_COMM_LOG_HISTORYTable Name WT_MEDIA_COMM_LOG_HISTORY

Table Description Used to store all information of each communication with a printer including History.



id uniqueidentifier No Unique ID

request_id uniqueidentifier No Order ID

communication_id nvarchar(255) Yes Unique ID for each communication

media_type nvarchar(50) No Type of media:- Fax- Print- IVR

Last_updated_status nvarchar(255) Yes Status of media

extra_details ntext Yes If media type is fax: Status of fax, fax server name, alternative way of fax if failed with mail ID, subject and country code.If media type is print: Status of print and printer name.

Ins_datetime datetime No Date and Time when the record is inserted in the table

upd_datetime datetime Yes Date and Time when the record is last updatedIns_upd_user nvarchar(127) No User Name Ins_upd_application nvarchar(255) No Store Name

last_updated_status2 nvarchar(255) Yes

Table Name BUGS

Table Description Used to store all leads data.



bg_id int No Unique ID for each new lead

bg_short_desc nvarchar(200) No Short description of the lead

bg_reported_user int No Generator of the lead

bg_reported_date datetime No Date at which the lead is generated

bg_status int No Status of lead:- Lead- Qualified Lead- Opportunity- Account- Not Interested

bg_priority int No Priority of lead:- Low- Medium- High

bg_org int No Organization Name

BUGS

To be Continued…

bg_category int No Type of lead

bg_project int No Project Name

bg_assigned_to_user int Yes User name to whom the lead is assigned

bg_last_updated_user int Yes Username by whom the lead is last changed

bg_last_updated_date datetime Yes Date at which the last changes are made

bg_user_defined_attribute int Yes User defined attributes

bg_project_custom_

dropdown_value1

nvarchar(120) Yes Customized dropdownlist 1

bg_project_custom_

dropdown_value2


bg_project_custom_

dropdown_value3


…BUGS

To be Continued…

…BUGS

bg_tags nvarchar(200) Yes Tag name

[Closing Date] datetime Yes Date at which the lead was closed

[Business Owner Name] nvarchar(50) Yes Name of business owner

[Business Owner Telephone] nvarchar(50) Yes Business Owner Telephone

[Business Owner Mobile] nvarchar(50) Yes Business Owner Mobile

[Business Owner Email] nvarchar(100) Yes Business Owner Email

[Business Email] nvarchar(100) Yes Business Email

[Contact Person Email] nvarchar(100) Yes Contact Person Email

[Business Telephone] nvarchar(50) Yes Business Telephone

To be Continued…

…BUGS

[Contact Person Mobile] nvarchar(50) Yes Contact Person Mobile

[Source Of Lead] nvarchar(40) Yes Source Of Lead

[Contact Person] nvarchar(100) Yes Contact Person

[Lead Generator] nvarchar(25) Yes Lead Generator

[Sales Manager] nvarchar(50) Yes Sales Manager

ZipCode nvarchar(15) Yes ZipCode

[Business Website] varchar(100) Yes Business Website

[Business Address] varchar(200) Yes Business Address

[Business Country] nvarchar(50) Yes Business Country

[Business State] nvarchar(50) Yes Business State

[Contact Person Title] varchar(100) Yes Contact Person Title

[Business Name] nvarchar(100) Yes Business Name

[FollowUp Date] datetime Yes Follow Up Date

To be Continued…

…BUGS

[FollowUp To Person] nvarchar(50) Yes FollowUp To Person

[Appointment Date] datetime Yes Appointment Date

[Customer Type] nvarchar(100) Yes Customer Type

[Email1 Date] datetime Yes Date at which the first email is sent

[Email2 TemplateId] nvarchar(50) Yes Template ID of second email

[Email2 Date] datetime Yes Date at which the second email is sent

[Email3 TemplateId] nvarchar(50) Yes Template ID of the second email

[Email3 Date] datetime Yes Date at which the third email is sent

[Business City] nvarchar(50) Yes City

[High Level Remark] nvarchar(200) Yes High Level Remarks

[DirectEmail1 TemplateId] nvarchar(50) Yes Template ID of the first email

[DirectEmail1 Date] datetime Yes Date of first email

[DirectEmail2 TemplateId] nvarchar(50) Yes Template ID of second email

To be Continued…

…BUGS

[DirectEmail2 Date] datetime Yes Date of second email

[DirectEmail3 TemplateId] nvarchar(50) Yes Template ID of third email

[DirectEmail3 Date] datetime Yes Date of third email

[Email1 TemplateId] nvarchar(50) Yes Template ID of first email

[Data Exchange Id] varchar(100) Yes ID to identify last excel sheet uploaded

[Promotion Code] varchar(50) Yes Offer Code


st_id int No Unique ID of the status

st_name nvarchar(60) No Name of the status

st_sort_seq int No Sort sequence

st_style nvarchar(30) Yes Style of the status

st_default int No Default selected status ID

Statuses

Table Name StatusesTable Description Used to store all leads data.Constraints Primary Key, Foreign key


pr_id int No Unique ID of the project

pr_name nvarchar(60) No Name of the project

pr_sort_seq int No Sort sequence of the project

pr_background_color nvarchar(14) No Background color of the project

pr_style nvarchar(30) Yes Style applied to the project

pr_default int No Default selected project ID

Priorities

Table Name PrioritiesTable Description Used to store all leads data.Constraints Primary Key, Foreign key

Fieldname Type Allow Nulls.

og_id int No

og_name nvarchar(80) No

og_domain nvarchar(80) Yes

og_non_admins_can_use int No

og_external_user int No

og_can_be_assigned_to int No

og_can_only_see_own_reported int No

og_can_edit_sql int No

og_can_delete_bug int No

og_can_edit_and_delete_posts int No

og_can_merge_bugs int No

og_can_mass_edit_bugs int No

og_can_use_reports int No

og_can_edit_reports int No

Orgs

Table Name OrgsTable Description Used to store all leads data.Constraints Primary Key, Foreign key

To be Continued…

og_can_view_tasks int No

og_can_edit_tasks int No

og_can_search int No

og_other_orgs_permission_level int No

og_can_assign_to_internal_users int No

og_category_field_permission_level int No

og_priority_field_permission_level int No

og_assigned_to_field_permission_level int No

og_status_field_permission_level int No

og_project_field_permission_level int No

og_org_field_permission_level int No

og_udf_field_permission_level int No

og_tags_field_permission_level int No

og_active int No

[og_Closing Date_field_permission_level] int Yes

…Orgs

To be Continued…

[og_Business Owner Name_field_permission_level]

int Yes

[og_Business Owner Telephone_field_permission_level]

int Yes

[og_Business Owner Mobile_field_permission_level]

int Yes

[og_Business Owner Email_field_permission_level]

int Yes

[og_Business Email_field_permission_level] int Yes

[og_Contact Person Email_field_permission_level]

int Yes

[og_Business Telephone_field_permission_level]

int Yes

[og_Contact Person Telephone_field_permission_level]

int Yes

[og_Contact Person Mobile_field_permission_level]

int Yes

[og_Source Of Lead_field_permission_level] int Yes

[og_Contact Person_field_permission_level] int Yes

[og_Lead Generator_field_permission_level] int Yes

[og_Sales Manager_field_permission_level] int Yes

…Orgs

To be Continued…

og_ZipCode_field_permission_level int Yes

[og_Business Website_field_permission_level] int Yes

[og_Business Address_field_permission_level] int Yes

[og_Business Country_field_permission_level] int Yes

[og_Business State_field_permission_level] int Yes

[og_Contact Person Title_field_permission_level]

int Yes

[og_Business Name_field_permission_level] int Yes

[og_FollowUp Date_field_permission_level] int Yes

[og_FollowUp To Person_field_permission_level]

int Yes

[og_Appoitment Date_field_permission_level] int Yes

[og_Customer Type_field_permission_level] int Yes

[og_Email1 Date_field_permission_level] int Yes

[og_Email2 TemplateId_field_permission_level] int Yes

…Orgs

To be Continued…




[og_Business City_field_permission_level] int Yes

[og_High Level Remark_field_permission_level] int Yes

[og_DirectEmail1 TemplateId_field_permission_level]

int Yes

[og_DirectEmail1 Date_field_permission_level] int Yes


int Yes



int Yes



…Orgs

To be Continued…

og_bg_short_desc_field_permission_level int Yes

og_bg_reported_user_field_permission_level int Yes

og_bg_reported_date_field_permission_level int Yes

og_bg_status_field_permission_level int Yes

og_bg_priority_field_permission_level int Yes

og_bg_org_field_permission_level int Yes

og_bg_category_field_permission_level int Yes

og_bg_project_field_permission_level int Yes

og_bg_assigned_to_user_field_permission_level int Yes

og_bg_last_updated_user_field_permission_level int Yes

og_bg_last_updated_date_field_permission_level int Yes

[og_Data Exchange Id_field_permission_level] int Yes

[og_Promotion Code_field_permission_level] int Yes

…Orgs


ct_id int No

ct_name nvarchar(80) No

ct_sort_seq int No

ct_default int No

Categories

Table Name CategoriesTable Description Used to store all leads data.Constraints Primary Key, Foreign key


pj_id int No

pj_name nvarchar(80) No

pj_active int No

pj_default_user int Yes

pj_auto_assign_default_user int Yes

pj_auto_subscribe_default_user int Yes

pj_enable_pop3 int Yes

pj_pop3_username varchar(50) Yes

pj_pop3_password nvarchar(20) Yes

pj_pop3_email_from nvarchar(120) Yes

pj_enable_custom_dropdown1 int No



Projects

Table Name ProjectsTable Description Used to store all leads data.Constraints Primary Key, Foreign key

To be Continued…

pj_custom_dropdown_label1 nvarchar(80) Yes



pj_custom_dropdown_values1 nvarchar(800) Yes



pj_default int No

pj_description nvarchar(200) Yes

…Projects


us_id int No

us_username nvarchar(40) No

us_salt int Yes

us_password nvarchar(64) No

us_firstname nvarchar(60) Yes

us_lastname nvarchar(60) Yes

us_email nvarchar(120) Yes

us_admin int No

us_default_query int No

us_enable_notifications int No

us_auto_subscribe int No

us_auto_subscribe_own_bugs int Yes

us_auto_subscribe_reported_bugs int Yes

Users

Table Name UsersTable Description Used to store all leads data.Constraints Primary Key, Foreign key

To be Continued…

us_send_notifications_to_self int Yes

us_active int No

us_bugs_per_page int Yes

us_forced_project int Yes

us_reported_notifications int No

us_assigned_notifications int No

us_subscribed_notifications int No

us_signature nvarchar(1000) Yes

us_use_fckeditor int No

us_enable_bug_list_popups int No

us_created_user int No

us_org int No

us_most_recent_login_datetime datetime Yes

…Users

SCREEN LAYOUTS

Test Cases

Login Test Cases

Sr. No. Test case Expected Output Actual Output Result

1. When either or all information does not match with database’s data type.

It should give error message.

Got error message:”Invalid information”

Pass

2. Username is blank It should give error message.

Got Error Message: “Username cannot be blank”

Pass

3. Password is blank It should give error message.

Got Error Message: “Password cannot be blank”

Pass

4. Wrong username and/or password

It should give error message.

Got Error Message:“Invalid Username and/or password”

Pass

5. Invalid URL Registered It should give error message and exit.

Got Error Message:“Invalid URL entered or URL not Registered System will exit now”

Pass

6. No Internet connection. It should give error and exit.

Got Error Message:“Unable to contact server. System will exit now”

Pass

Customization Test Cases


1. Theme set. Theme should be set to the selected one.

New theme applied. Pass

2. Refresh interval set. Interval should be set to the new interval.

Applied new refresh interval.

Pass

3. Automatic start on window startup.

The application should start on window start up.

Application starts when user logs in.

Pass

4. Default printer set. Default printer should be set to the selected one.

Default printer is set to the selected one.

Pass

5. Automatic Printing set. Automatic printing should be either enabled or disabled.

Automatic printing is enabled or disabled.

Pass

6. Set type of invoice to be printed by default.

Type of invoice should be set to the selected one for default printing.

Type of invoice is set to the selected one for default printing.

Pass

7. Set number of copies to be printed.

Number of copies of the invoice should be printed.

Number of copies of invoice is printed.

Pass

Application Reporting Test Cases


1. Application reports at every 5 minutes for indicating that the application is running.

Application should reports to RUM.

Application reported to RUM when it was running.

Pass

2. No Internet connection.

Application should not report to RUM.

RUM indicates that application is not running.

Pass

3. Unexpected shutdown of application.



Pass

Home Screen Test Cases


1. Check for admin user.

Application should load multiple branches in dropdown list.

Application loads multiple branches in dropdown list.

Pass

2. Click on print button.

Print dialog box should be opened for printing normal invoice.

Print dialog box opens for normal invoice printing.

Pass

3. Unexpected shutdown of application.



Pass

Future Enhancements

Future Enhancements

User Interface can be improved. Level of performance can be increased. Local database can be used to sync. Can be made portable. Synchronization can be handled in a better way. Can be converted to app.

Bibliography

Bibliography

Reference books used for developing the project Asp .Net 4 by Stephen Walther,Kelvin Hoffman,Nate Dudek Asp .Net Bible ASP.NET Black book

Websites referred www.asp.net official site from Microsoft for ASP.NET

developers www.stackoverflow.com msdn.microsoft.com www.sourceforge.net www.codeproject.com www.telerikcontrols.com www.youtube.com books.google.com

http://www.asp.net/

http://www.stackoverflow.com/

http://msdn.microsoft.com/

http://www.sourceforge.net/

http://www.codeproject.com/

http://www.telerikcontrols.com/

http://www.youtube.com/

http://books.google.com/

Plan & Actual

Plan & Actual (Weekly)

Week Plan Actual

Week 1 (6/12/2013 – 12/12/2013)To learn about project and analyze project and learn tools that will be required for project and its development.

Done

Week 2 (13/12/2013 – 19/12/2013)To start development for project’s prototype and other configuration.

Done

Week 3 (20/12/2013 – 26/12/2013)To Develop and test prototype of the system and implement it for initial purpose.

Done

Week 4 (27/12/2013 – 02/01/2014) To develop and test full prototype of the system. Done

Week 5 (03/01/2014 – 09/01/2014) To start working on live project and its development. Done

Week 6 (10/01/2014 – 16/01/2014) To develop project’s basic modules. DoneWeek 7 (17/01/2014 – 23/01/2014) To develop project’s basic modules. DoneWeek 8 (24/01/2014 – 30/01/2014) To develop project’s main modules DoneWeek 9 (31/01/2014 – 06/02/2014) To develop project’s main modules DoneWeek 10 (07/02/2014 – 13/02/2014) To develop project’s main modules CompletedWeek 11 (14/02/2014 – 20/02/2014) To develop project’s main modules Completed Before Decided Time

Week 12 (21/02/2014 – 27/02/2014)Get Special requirements if any and implement all non functional requirements.

Completed Before Decided Time

Week 13 (28/02/2014 – 06/03/2014) Development of non functional and/or special requirements Completed Before Decided Time

Week 14 (07/03/2014 – 13/03/2014) Unit testing of the system Completed Before Decided TimeWeek 15 (14/03/2014 – 20/03/2014) Make changes in system if any required. Completed Before Decided TimeWeek 16 (21/03/2014 – 27/03/2014) To Successfully develop Application. Completed Before Decided Time

Week 17 (28/03/2014 – 03/04/2014)To test application under all test cases and generate test chart for the system.


Week 18 (04/04/2014 – 10/04/2014)To Verify documentation and provide system to company and help in launching the system


Note : Development of Documentation will be parallel to the development of the system and so, it is not included in above plan.

final year mca presentation

Education