Working with UWP

Summary

In this assignment, students begin to create UWP applications and explore UI design techniques & class relationships. Students use GIT and BitBucket and use best development practices such as iterative development, creating professional comments using XML comments and outline solutions using comments.

Submission checklist

• Visual Studio solution containing all the source files as a ZIP file that contains all files required to load the project into Visual Studio and the GIT repository (.git folder)

Detailed Requirements

Part I (45%): User Interface Layer. The application is used by a dealership that deals in 0-10 year old vehicles. The dealers capture the parameters that impact price of the vehicles using the interface shown in Appendix 1. The captured parameters are then used to compute the depreciated cost using the following logic:

1. Depending upon how old the vehicle model is, there is a depreciation of 10% each year.

2. An additional depreciation of 2.5% is computed for each 10000 Km of run.

3. In case of an accident history, an additional insurance related depreciation %age is provided by the user.

   Using Visual Studio, design a Universal App solution with following features:

   
   

   1. Generate the layout as depicted in the Appendix 1

   2. On pressing of “Submit Information” that page shall use the dealership object to submit the information of a vehicle and its depreciation parameters.

   3. All the information fields are required, so make sure that all the values have been entered by user.

   4. Clicking on “Show Report” should

      1. Show the total value of all the vehicles on current date.

      2. Show the details of the vehicles which have the highest depreciation percentage.

      3. Show the details of the vehicles which have the lowest depreciation percentage.

Part II (50%): Business Logic. Implement the core functionality of the application in the business logic classes: Dealership, Vehicle and Depreciation. The business logic classes to be developed are (you are free to add additional classes / attributes ad required):

1. Dealership:

   1. The “RecordVehicleInformation” method should create and initialize a vehicle object with the required attributes and save the same in the field vehicleList.

   2. The “CalculateTotalValue” method should calculate and return the total depreciated value of all the vehicles on current date.

2. Vehicle:

   1. Define the field variables and properties for maintaining ID, Make, PurchasePrice.

3. Depreciation

   1. Define the field variables and properties for maintaining Model, Mileage, InsuranceDepreciation.

   2. Also, define const for maintaining % deprecation per year, % depreciation per 10,000 Km as described in Part I.

   3. Define a read-only property “DepreciationValue” that calculates the depreciation of the vehicle on current date.

Version Control (5%).

Milestone 1. (1%) Project Creation. Create the initial C# project and add the project to version control using GIT and publish in to BitBucket.

Milestone 2. (2%) Creation of UI components. Commit all the changes done so far with the message “Presentation Tier Complete”

Milestone 3. (2%) Define the classes Dealership, Vehicle and Depreciation. Commit all the changes done so far with the message “Business Logic Layer Complete”

Notes:

1. The professionalism of your submission, clarity of written communication is extremely important. The ability to communicate your knowledge is as important as the knowledge itself.

   
   

   1. Up to 20% of the mark for any written work can be deducted due to poor presentation / communication: title page (5%), document organization (5%), layout (5%) and grammar and spelling (5%).

      
      

   2. Up to 20% of the mark for a program can be deducted due to poor presentation / communication: quality of names according to our naming and coding conventions (10%) and comments (10%).

      
      

2. All assignment shall be submitted by the deadline. Late submissions will be penalized with 10% per day for up to 3 calendar days after which the assignment cannot be submitted anymore. An

   email must be sent should you choose to submit a late assignment. Assignments are not accepted after the solutions have been posted.

   
   

3. This assignment shall be completed individually. Remember that completing the assignment by yourself will ensure your success on the midterm and final exam. See the Academic Honesty at Sheridan.

   
   

4. Submission is done in electronic format using the SLATE DropBox. DO NOT email your submission.

Appendix 1: UI Design