Album shop - administration software

Required know-how: - .NET 4.5 - C# - WPF, XAML, MVVM - Prism 5 ([login to view URL]) - Entity Framework 6 ([login to view URL]) - Repository pattern Project Description The goal of the software is to track orders of products made by clients and their payment status. The main modules needed in the software are: - Client management - Orders management o Add/Edit client o Client details screen o Client order history screen o Add/Edit orders – one order can have multiple products in different quantities – wizard like view: Step1: select product Step2: select size Step3: select properties ( multiple different for each product ) - at end calculate price per item Step4: select quantity – final price for order item ( price per item x quantity) Final calculate price per order – make payment – can be whole sum or only partial payment Each order item will have a delivery date, a proposed date will be automatically provided (from product settings) but this can be edited by user Clients will have discounts defined in their settings, also promotions can be defined at product level, and formula will be provided how to handle this o After finishing an order 2 print-outs will be generated ( formats will be provided ), these printouts will be available to send via email as pdf’s One for customer One for production – the one for production will have a section/page for each order item in the order - Management module password protected; In this module the product definitions will be o Screen with situation for unpaid orders – from here adding payments will be possible o Screen with situation for orders listed by county done by the following rules: o Each product can have multiple sizes o Each product can have multiple characteristics (e.g. Page materials, cover types etc.) - Reporting section will contain the following reports, each report will be visible on o Each characteristic has a type, each type can be assigned to a product during ordering only once o Each characteristic type can have a multiplicity of one or more during product ordering this is defined in the settings o Each characteristic has a material type o Material types are defined at runtime o Each combination Product – Size – Characteristic will have assigned properties like price, production cost, material quantity consumed screen, printable, exportable as excel spreadsheet ( open-xml format, xlsx ) o Clients by county o Clients by order number o Financial report o Profitability report ( income vs cost for production ) o Orders by county o Orders by date o Orders by date of delivery o Consumption report – how much materials have been consumed in a time period grouped by orders For all entities CRUD operations will be available. Example for product: Protuct 1 Page Size 10 X 10 1 $ 2 $ 10 $ 15 $ Material1 Page Material2 10 X 15 1 $ 2 $ 12 $ 20 $ 15 X 15 2 $ 4 $ 25 $ 35 $ 25 X 25 5 $ 10 $ 50 $ 100 $ Price calculation for an order for Product1 size 25x25 for 10 pages will be: 10 X 5 $ ( Page Material1 ) + 100 $ ( Cover1 ) = 150 $. All prices in software will be represented in LEI, the interface language for the application will be in Romanian translations will be provided, development and communication language will be English, all code comments need to made in English. The Architecture of the product will be discussed and decided with our architect. The coordination and code check-up will be done by the product architect. Your reply must contain the following work: SKY.