Champion Power Equipment 92221 Manuale Utente

POLITECNICO DI MILANO Facoltà di Ingegneria dell’Informazione Corso di Laurea Magistrale in Ingegneria Informatica Managing futsal competitions

3 2 Background 2.1 Entity Framework 2.1.1 Introduction Entity Framework (EF) is an object-relational mapper that enables .NET developers to work

4 2.1.3 Data Annotations or Fluent API Data annotations or fluent API are used to define the mappings between the classes defined in DbContext an

5 2.1.4 Migrations Migrations are database updates and can be done automatically by data context on its loading. It is sometimes dangerous to e

6 2.1.5 Eager, Lazy and Explicit loading Eager loading is the process whereby a query for one type of entity also loads related entities as part of

7 Even with lazy loading disabled it is still possible to lazily load related entities, but it must be done with an explicit call (Explicit loading)

8 2.2 Web API 2.2.1 Introduction Restful services have become very popular. Their main popularity is the accessibility from different platforms. I

9 How the implementation of products controller looks in code, we will show you in the following example. Take into consideration that repository ob

10 2.2.3 Defining routes In order to have the proper binding of URIs to controllers, you need to define the routes in WebApiConfig static class whi

11 2.3 Windows Store applications 2.3.1 Introduction Microsoft’s answer for increase in popularity of Application stores is Windows store. Apple j

12 2.3.4 Windows Store Windows Store is marketplace for Windows 8.0 and Windows 8.1 applications for desktop and tablet devices. Currently it offer

To my family

13 3 Sports Manager application The Sports Manager application’s greater goal is to be a robust application for managing competitions and compe

14 The competitions through which the author participated are:  4th European Universities Futsal Championship, Izola (Slovenia), July 23-29, 2007

15 3.1 Functional requirements In the system four roles will exist in order to distribute work equally and to allow greater separation of concerns.

16 3.1.1 Competition administrator role Figure 2. Competition administrator role use case

17 3.1.2 Match commissioner role Figure 3. Match commissioner role use case

18 3.1.3 Match statistician role Figure 4. Match statistician role use case

19 3.1.4 Match reporter role Figure 5. Match reporter role use case

20 3.2 Non-functional requirements 3.2.1 Ability to work offline The application will be used in the environment where more than few thousand peo

21 4 User experience and interaction design While designing the interaction in our application we tried to put main effort to the following featur

22 4.2 Switch competition view 4.3 Competition view Figure 8. Switch competition view Figure 9. Competition view

i Contents 1 Introduction ...

23 4.4 Switch event view 4.5 Event view Figure 10. Switch event view Figure 11. Event view

24 5 Architecture Figure 12. Application's overall architecture

25 5.1 Database layer The database is implemented in MS SQL Server 2012 system. The initial architecture was created in SQL Server Management Stud

26 statistics, etc. MatchReferees Referees and their roles and grades for a specific match MatchTeams Teams involved in a match MatchWorkers Workers

27 5.1.1 Competition core tables Figure 13. Competition core tables

28 5.1.2 Competition schedule tables Figure 14. Competition schedule tables

29 5.1.3 Match core tables Figure 15. Match core tables

30 5.1.4 Competition and sport rules tables Figure 16. Competition and sport rules tables

31 5.1.5 Competition users and mailing lists tables Figure 17. Competition users and mailing list tables

32 5.2 Model layer (Entity Framework) The code first workflow was used in the Entity Framework. From the existing database with reverse engineering

ii 3.1.4 Match reporter role... 19 3.2 Non-functiona

33 Code Example 13. Query for retrieving competition event and all related data Code Example 14. Query for retrieving all matches of a comp

34 5.3 Controller layer (Web API) Web API is the controller layer of our application. For each important entity or a relation we have the accordin

35 5.4 View layer (Windows 8.1 application) The client application was made as a Windows 8.1 application. The technologies used were c# language an

36 <Page x:Class="SportsManager.MasterPage" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

37 6 User manual 6.1 Choose and manage competition View Actions 1. Click on the most left button in the menu bar on top 2. Then the window in

38 6.2 Choose and manage competition event View Actions 1. Click on the second from the left button in the menu bar on top 2. Then the window i

39 7 Conclusion We have briefly showed the technologies we’ve used in the project. They are all latest state of the art technologies on Microsoft’s

40 8 Appendices 8.1 Appendix A: Versioning system details Detail Value Type Team Foundation Server Uri webko.visualstudio.com Owner marko.brcic@o

41 8.3 Appendix C: Visual Studio solution projects Project name Project description SportsManager Windows store 8.1 application project SportsMana

42 8.4 Appendix D: List of figures Figure 1. Sports Manager application logo ...

iii 8.4 Appendix D: List of figures ... 42 8.5 Appendix

43 8.6 Appendix F: List of code examples Code Example 1. Code first Entity Framework workflow ...

44 9 Bibliography [1] Brown, Pete. Windows Store App Development (2013), C# and XAML. [2] Moemeka, Elizabeth and Edward. Real World Windows 8 App

45 [24] Sowell, Eric. Mobile ASP.NET MVC 5 (2013) [25] Freeman,Adam. Pro ASP.NET MVC 5 (2013) [26] Bewis, Tony. C# Design Pattern Essentials (2012)

46 10 Internet resources [35] App features from start to finish (XAML). Retrieved from http://msdn.microsoft.com/en-us/library/windows/apps/xaml/d

47 [47] ASP.NET MVC 5 Full tutorial about new Authentication mechanism. Retrieved from http://forums.asp.net/t/1944903.aspx?ASP+NET+MVC+5+Full+tutor

48 http://stefanoricciardi.com/2011/02/04/ninject-mini-tutorial-part-2/ [61] Introduction to Microsoft DreamSpark. Retrieved from https://www.drea

iv Abstract Tablet devices are becoming more and more popular each day. It’s because they are thinner and lighter than laptops whil

v Sommario Dispositivi tablet stanno diventando sempre più popolare ogni giorno. E' perché sono più sottili e leggeri di computer portati

1 1 Introduction 1.1 Motivation With an increase of popularity in using tablets among common people there is a great need for developi

2 1.2 Outline This work is structured as follows. In section 2, Background, we will start by introducing the technologies used in developing the a