staafl

MVC exam evaluation

Oct 8th, 2013
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.29 KB | None | 0 0
  1. Problem 1. Ticketing System Data Layer
  2. Entity Framework as ORM engine and MS SQL Server Local DB as database storage engine is used
  3. Yes (2)
  4. Partially (1)
  5. No (0)
  6. The data layer is implemented with repository pattern and unit of work.
  7. Yes (7)
  8. Yes, but has some problems (5)
  9. Partially (3)
  10. No (0)
  11. Each user has username, password and points.
  12. The password is stored in the DB encrypted (not as clear text). This is done by default if the ASP.NET Identity is used.
  13. Yes (1)
  14. No (0)
  15. The user’s points are by default 10
  16. E.g. when user is registered it has 10 points in the database. It may be done with [DefaultValue], in constructor or in AccountController
  17. Yes (1)
  18. No (0)
  19. ASP.NET Identity system is used to keep the users in the database
  20. Yes (1)
  21. No (0)
  22. Categories table is implemented correctly
  23. The table has name (mandatory) and hold a set of tickets. Relation one-to-many from tickets to categories
  24. Yes (1)
  25. Partially (0.5)
  26. No (0)
  27. Tickets table is implemented correctly
  28. Mandatory category (relation), title (string), priority (enum, or another table) and screenshot URL (string) fields and optionally author (user or null) and description (nullable string)
  29. Yes (3)
  30. Almost (2)
  31. Significant differences (1)
  32. No (0)
  33. Comments table is implemented correctly
  34. Each comment has user (relation), ticket (relation) and content (string).
  35. Yes (1)
  36. Partially (0.5)
  37. No (0)
  38. Sample data is filled in the database.
  39. E.g. seed method is implemented for code-first approach, or the database file has some initial data in it. There is no need for the users and roles to be seeded.
  40. Yes (2)
  41. Yes, but not enough data (1.5)
  42. No (0)
  43. The project runs without problems with F5 in Visual Studio.
  44. There is no need to change connections strings, settings, deploy databases, etc.
  45. Yes (1)
  46. No (0)
  47. Problem 2. Common Features
  48. Layout page is used properly.
  49. The layout page is designed to reuse the common page elements like headers and footers and navigation in all other pages in the project
  50. Yes (2)
  51. No (0)
  52. For non-registered users there is a link only to home page, register and login actions.
  53. Yes (1)
  54. No (0)
  55. For registered users there is a link for adding a new ticket and to the list of all tickets.
  56. Yes (1)
  57. No (0)
  58. For administrators there is a sub-menu to all available administrations.
  59. Yes (1)
  60. No (0)
  61. Kendo UI menu is used for the navigation.
  62. Yes (2)
  63. No (0)
  64. ASP.NET Identity is working properly
  65. Registration, login and logout are working properly
  66. Yes (2)
  67. Partially (1)
  68. No (0)
  69. Username is validated to be between 6 and 16 characters long
  70. In RegisterViewModel there should be [StringLength] attribute on UserName property.
  71. Yes (2)
  72. Partially (1)
  73. No (0)
  74. Error handling
  75. In case of error an appropriate error message is displayed. No yellow screens are shown.
  76. Yes, everywhere (2)
  77. In some places (1)
  78. No (0)
  79. User interface (UI)
  80. The user interface is the same as in the given images. Bootstrap is used properly. (The UI of the administration pages is not important). The colors of the items on the page are not important (you can use whatever Kendo UI theme you want)
  81. Yes, exactly like in the given images (3)
  82. Almost the same (2)
  83. Has a lot of differences (1)
  84. No (0)
  85. Problem 3. Public Area - Home Page
  86. Home page is displayed properly
  87. At the application start page there should be the top 6 most commented tickets. For each ticket there should be the title of the ticket, the name of the category, the name of the author, the number of comments and a link to the tickets details page.
  88. Yes (6)
  89. Almost properly (4)
  90. Partially (2)
  91. No (0)
  92. The 6 most commented tickets are cached for an hour
  93. Yes (2)
  94. No (0)
  95. Problem 3. Public Area - Ticket Detail Page
  96. Ticket details page is displayed properly
  97. Yes (3)
  98. Almost properly (2)
  99. Partially (1)
  100. No (0)
  101. In ticket details page the optional fields are not displayed when null
  102. E.g. if the description is null then no 'Description:' text is shown, same for author. If the screenshot url is null then nothing is displayed in the middle column.
  103. Yes (2)
  104. Partially (1)
  105. No (0)
  106. In ticket details page the comments are displayed properly
  107. Yes (2)
  108. Partially (1)
  109. No (0)
  110. Problem 4. User Area - Create Ticket Page
  111. The create tickets page is working properly and both client-side and server-side validations are working properly.
  112. Yes (4)
  113. Partially (2)
  114. No (0)
  115. The value of the author is set to the currently logged-in user and after adding the ticket, the user receives 1 point.
  116. Yes (1)
  117. Partially (0.5)
  118. No (0)
  119. The category is a drop down list
  120. Yes (1)
  121. No (0)
  122. The priority is a drop down list
  123. Yes (1)
  124. No (0)
  125. Custom validation attribute for the ticket's title is correctly written and applied
  126. Ticket’s title should not contain the word “bug” in it. It should be validated with custom validation attribute.
  127. Yes (3)
  128. Partially (1.5)
  129. No (0)
  130. Problem 4. User Area - List Page
  131. Listing tickets is working properly.
  132. Yes (5)
  133. Partially (2)
  134. No (0)
  135. Listing tickets is done using Kendo UI ListView.
  136. Yes (2)
  137. No (0)
  138. Server side paging is implemented and is working properly.
  139. Yes (3)
  140. Partially (1.5)
  141. No (0)
  142. Problem 4. User Area - Commenting Tickets
  143. Commenting tickets is working properly.
  144. Registered users should be able to comment the tickets in their details page
  145. Yes (4)
  146. Partially (2)
  147. No (0)
  148. Commenting is done with AJAX
  149. Commenting is done with AJAX updating the information without refreshing the page
  150. Yes (3)
  151. Partially (1.5)
  152. No (0)
  153. Problem 4. User Area - Searching Tickets
  154. Filtering tickets by category is working properly.
  155. Yes (3)
  156. Partially (1.5)
  157. No (0)
  158. An empty option is available in the drop down list and when selected the filtering is disabled.
  159. Yes (1)
  160. No (0)
  161. Category filter is done with Kendo UI Drop Down list
  162. Yes (3)
  163. Partially (1.5)
  164. No (0)
  165. Problem 5. Administration Area - Categories
  166. Only administrators can see the categories administration.
  167. If there is a commented [Authorize] attribute also answer to this question with 'Yes'
  168. Yes (0.5)
  169. No (0)
  170. Displaying categories is working properly
  171. Yes (0.5)
  172. No (0)
  173. Creating category is working properly
  174. Yes (1)
  175. No (0)
  176. Editing category is working properly
  177. Yes (1)
  178. No (0)
  179. Deleting category is working properly
  180. When a category is deleted all its tickets and their comments should be deleted as well
  181. Yes (2)
  182. Partially (1)
  183. No (0)
  184. Kendo UI Grid is used for this administration and paging, sorting and filtering are working properly.
  185. Yes (5)
  186. Almost everything is working properly (4)
  187. Somethings are working (2)
  188. No (0)
  189. Problem 5. Administration Area - Comments
  190. Only administrators can see the comments administration
  191. If there is a commented [Authorize] attribute also answer to this question with 'Yes'
  192. Yes (0.5)
  193. No (0)
  194. Administrators are not able to add comments
  195. Yes (1)
  196. No (0)
  197. Editing comments is working properly
  198. Yes (1)
  199. No (0)
  200. Administrators are only able to edit comment content
  201. Administrators are not able to edit comment author and comment ticket
  202. Yes (1)
  203. No (0)
  204. Deleting comments is working properly
  205. Yes (1.5)
  206. No (0)
  207. Oписание и коментар на оценката (какви са силните/слабите неща в изпита)
Advertisement
Add Comment
Please, Sign In to add comment