1. .NET PortfolioUsing Library System By Chao W. Thao Chao.thao@setfocus.com 651.330.2420

3. Windows Business and Data Access tiers

5. Designed and implemented a library system to handle day-to-day operations performed by librarians.

6. Audience:

7. Librarians will be the primary users of the applications.

8. Project Goals:

9. Design and develop Windows and Web based applications that allow librarians to add adult and juvenile members, check in and check out books, and maintain an inventory of the library’s books.

10. Design the Entities, Business and Data Access tiers.

11. Develop code that is easily maintainable.

12. Provide adequate error handling.

14. Add Adult Member

15. Validation in code

16. Business Layer for Add Adult

17. Windows Business & Data Access Requirements Develop stored procedures for 6 processes Add member Get member Check in Check out Get item (returns an item with a specific ISBN and Copy #) Get items (returns a member’s checked out items) Create a Data Access Layer Calls stored procedures in database Returns data or throws errors to Business Layer Produce a project of Entities classes accessible to all layers Member Adult (derived class) Juvenile (derived class) Item ItemsDataSet Library Exception

18. Stored Procedure – Adding Juvenile

19. Data access layer calls add juvenile stored procedure

20. Entities use for Add Juvenile

21. Web Application Requirements Replace Windows front-end with Web front-end Add Functionality Add Item either with a new ISBN or new copy of an existing ISBN Automatic Conversion to Adult Membership for Juvenile 18 years and over with notification to Librarian Membership renewal upon Librarian acknowledgement Add Security Add a Librarian role Add 2 users to the Librarian role Prevent everyone except the Librarian role from accessing the library functions

22. Add Item Form and Validations

23. Add Item Codes

24. Get Member Info

25. Get Member Info Codes

26. Setting Security Role

27. Login Screen

29. Develop code that is easily maintainable.

30. Provide validation for all required fields.

31. Provide error handling

32. Produce a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization