Powerpoint Presentation of 4 phase Library Project.

3. Custom exception classes

4. Custom attribute classes

5. Generic Collections

6. Custom Serializations

7. Abstract Classes and Interfaces

8. Enumerations Types

9. Implementation of Iserializable, IComparer, Incomparable

10. Custom EventArgsDavid S Pitcher dpitcher75@hotmail.com 2

11. Phase #1 - .NET Framework In this phase we focus on setting up the .NET Framework. This diagrams the interfaces and base classes' that will be used through out the application. David S Pitcher dpitcher75@hotmail.com 3

12. Phase #1 .NET FrameworkBase Classes David S Pitcher dpitcher75@hotmail.com 4

13. Code snippets from the interface classes - Phase#1. David S Pitcher dpitcher75@hotmail.com 5

16. The ability to both check in/out books for any member.

18. Any member may only have 4 books checked out at any one time.

19. Librarian can have the option to cancel any operation.

20. Easily identify overdue books for any member.

21. Juvenile members must have a valid adult member to sponsor them.

22. Notify Librarian if a adult membership has expired.

24. David S. Pitcher dpitcher75@hotmail.com 8 Library Patron Information Screen

25. Check Out Items David S Pitcher dpitcher75@hotmail.com 9

26. David S Pitcher dpitcher75@hotmail.com 10 Add Adult & Juvenile Member

27. David S Pitcher dpitcher75@hotmail.com 11 Custom Exception Library Class – SQL and Windows Errors.

28. David S Pitcher dpitcher75@hotmail.com 12 Custom Exceptions called from Library Classes (Used in all visual classes that communicate with the database) , this instance is from the AddAdult.cs

29. David S Pitcher dpitcher75@hotmail.com 13 Data Access Layer communicates with the SQL Server database through the Entities Layer (DP.LibraryEntities). These are identified as views or as stored procedures if additions or modifications are required to the data. Following are some of those stored procedures.

30. David S Pitcher dpitcher75@hotmail.com 14 Add Adult Stored Procedure Transaction based Validation on input

31. David S Pitcher dpitcher75@hotmail.com 15 Called view - ‘VItems’

33. Keep a similar look and feel in the web application as in the windows form application.

34. Restrict access to the web application through the use of Membership Roles .

35. Use the ViewState and SessionState for post backs.

36. Reuse of both the Business and Data Access layers.

39. Catch’s both server & client side errors.

40. Validation Summary used for centralized user error messaging.

41. Required and validated fields all cued for errors.

44. Implement as a WCF Service website, using WsHttpBinding.

45. Authentication using ASP.NET membership

46. Authorization using ASP.NET roles (PrincipalPermission)

47. Use DataContracts for the entities.

49. David S. Pitcher dpitcher75@hotmail.com 21 Implementing the Library Interface, Service Classes

50. David S. Pitcher dpitcher75@hotmail.com 22 Library Fault class

51. David S. Pitcher dpitcher75@hotmail.com 23 Web config & App config settings

52. David S. Pitcher dpitcher75@hotmail.com 24 Summary SetFocus provides a learning environment very similar to what I have experienced in my role as a consultantontractor. Business requirements are gathered, documentation is written (requirements and scope of project) and the developer will work in the guidelines of the shop to deliver what was in the requirements. Each phase of the project required 40-60 hours of work to complete, no extensions or reduction of requirements was allowed. All of the technologies specified in the requirements was expected to be incorporated into that particular phase of the project (i.e. ADO.NET, LINQ etc.) Students were expected to find the answers to there questions raised about a phase of the project, within the documentation and training provided. Though instructors and TA’s were available the student was never given a direct answer , but always directed to where they might find the answer.