Your SlideShare is downloading. ×
Delma Hagen Portfolio
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Delma Hagen Portfolio

636

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
636
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. .NET Portfolio
    Library System
    Delma Hagen
    Delma.Hagen@SetFocus.com
    (973) 263-4013
  • 2. Table of Contents
    • Library Phase I - Windows Front-End Application
    • 3. User Interface Samples
    • 4. Library Phase II - Windows Business & Data Access tiers
    • 5. Business Layer Code Sample
    • 6. Data Access Code Sample
    • 7. Store Procedure Code Sample
    • 8. Library Phase III - Web Application
    • 9. User Interface Samples
    • 10. Markup Code Sample
    • 11. Code Behind Sample
    • 12. Library Phase IV – Web Service Application
    • 13. Web Service Code sample
    • 14. Web Method Code Sample
    • 15. Secured Remote Invocation Code Sample
    • 16. Certificate Policy Configuration
    • 17. Class Using XML Include Attribute Sample
  • Library Phase I Windows Front-End Application
    • Develop a Windows desktop front-end to allow librarians perform daily operations managing library items and members:
    • 18. Add Adult Member, Display Adult Information
    • 19. Add Juvenile Member, Display Juvenile Information
    • 20. Check Out an Item
    • 21. Check In an Item
    • 22. .Net 2.0 Multi-tired application
    • 23. Presentation Layer: Windows Forms 2.0
    • 24. Data Access Layer: ADO.Net 2.0
    • 25. Database: SQL Server 2005
    • 26. Techniques used
    • 27. User input validation using error provider, regular expression checking and event handlers
    • 28. Data binding to a data grid control and related manipulation
    • 29. MDI application format
    • 30. Effective exception handling
  • User Interface Add Adult Member
    • MDI Application format
    with dropdown menus
    allowing user select the
    function
    • Textbox to enter member
    information
    • Input validation using
    error provider and regular
    expression checking
    • OK and Cancel button
    to process or cancel
    the function
  • 31. User Interface Add Adult Member
    • When the input data is
    validated and the User
    press OK button the
    Adult Member is added
    to the Library
    • If the User press the
    Cancel button the
    transaction is canceled
  • 32. User Interface Display Adult Member Information
    • New member info is
    displayed to confirm
    that was added to
    the Library
    • The Check Out menu is
    activated allowing the
    items to be checked out
    for the new member
    • Grid shows the items
    checked out for the
    member – no items are
    checked out for the new
    member yet
  • 33. User Interface Add Juvenile Member
    • Text box is used to
    enter data to Add a
    Juvenile member on
    the Library
    • Error provider
    indicating error
    with additional
    information
    • Status strip used
    for communicating
    errors
  • 34. User Interface Display Member Information
    • The Juvenile member
    Information is displayed
    to confirm that was added
    • The Check Out menu
    is activated allowing
    the Librarian to check
    Out an Item
    • Grid shows the items
    checked out for the
    member. Item overdue
    is in red.
  • 35. User Interface Check Out Item
    • When Checking Out an
    Item is given to the
    Librarian an option
    to continue with the
    checkout or not
    • If the Librarian answer
    YES the item is checked
    out and added to the
    grid
  • 36. User Interface Check Out Item
    • When the item is
    already checked out
    is given an option to
    Check In the Item first
    • If the Librarian answer
    Yes the Item is Checked
    In and Checked Out
    for the member
    that requested the
    transaction
  • 37. User Interface Check In Item
    • When Check In an Item
    is given to the user an
    option to continue with
    the checkout or not
    • If the User answer YES
    the Item is checked Out
    and displayed on the
    GRID
  • 38. Library Phase II Windows Business & Data Access tiers
    • Requirements:
    • 39. Use stored procedures to make database operations more efficient
    • 40. Provide adequate error handling.
    • 41. Use database-programming techniques that provide maximum programming flexibility and control while minimizing resource utilization.
    • 42. Design and Implement your own Business and Data Access tiers
    • 43. Check the item if it is “loan able” and prevent from being checked out if it’s not.
    • 44. Convert juvenile membership to adult member ship when juvenile became and adult
    • 45. Techniques used:
    • 46. Developed stored procedures for the processes (Add Member, Get Member, Check In, Check Out, Get Item, Get Items)
    • 47. Created a Data Access Layer that calls stored procedures and return data or throw errors to Business Layer
    • 48. Produced a project of Entities classes accessible to all layers (Member, Adult, Juvenile, Item, ItemsDataSet and Library Exception)
  • Business Layer Code SampleAdd Adult Member
  • 49. Data Access Layer Code SampleCheck Out Item
  • 50. Stored ProcedureRenew Member membership
  • 51. Library Phase III Web Application
    • Requirements:
    • 52. Create a web application that supports all the functionality required for Phase I and Phase II of the Library project.
    • 53. When displaying an adult’s information, the application should detect if the card is expired and give the librarian a chance to renew the card.
    • 54. Overdue books, shown in any display must be highlighted.
    • 55. The librarian must be able to enter a new book into the database. If the ISBN already exists in the database, all that is needed is to add a record for a new copy number. If the ISBN does not yet exist in the database, you must add all necessary records for the new ISBN and a new copy number 1 for that ISBN.
    • 56. Use Forms-based authentication and authorization. Only members of the Librarian role must be able to access the web application.
    • 57. Techniques used:
    • 58. Developed a ASP.NET 2.0 Web Application and coded according with the requirements
    • 59. Reused the Data Access Layer and the Business Layer from the Windows Desktop Application Library Phase I.
  • User Interface Authentication
    • Security using ASP.NET
    membership and role
    management
    • Functionality restricted
    to Librarian role members
  • 60. User InterfaceAuthentification
    • Only members of the
    Librarian role are able
    to login and access
    the Web Application
  • 61. User Interface Display Member Information
    • Display Member
    Information and
    Items Checked on
    the GRID - Overdue
    items are in red
  • 62. User Interface Display Member Information
    • When displaying
    an adult member
    detect if the
    membership is
    expired and give
    the Librarian a
    chance to renew
    the card
  • 63. User Interface Adding a Juvenile member
    • Error provider
    indicating error
    with additional
    information
  • 64. User Interface Adding a Juvenile member
    • All fields are
    validated and
    Librarian can
    Add or Cancel
    the process
  • 65. User InterfaceDisplaying the member Info added
    • Display the information
    for the new member
    added to the Library
    • A message is displayed
    informing that are not
    books checked out for
    the new member
    • The Check Out button
    is activated allowing
    the Librarian to check
    Out an Item for the
    new member
  • 66. User Interface Adding an Item
    • When adding a new
    Item do the Library
    and the Item already
    exist, give an option
    to add a new copy
    • If the Librarian
    confirm the new
    copy is added and
    the confirmation is
    displayed to confirm
    the new copy added
  • 67. User InterfaceAdded a copy of the Item
    • The page is displayed
    to confirm that the
    copy was added to
    the library and also
    to display the copy
    number
  • 68. Markup Code SampleAdd Juvenile Member
  • 69. Code SampleAdd Juvenile Member
  • 70. Library Phase IV Web Service Application
    • Requirements:
    • 71. Create a Web Service that calls into either the business or data layer.
    • 72. Update the layers in the system to use the service as deemed appropriate.
    • 73. Make sure the Web service supports the Basic Profile. The service also should use Document/Literal formatting of the Soap messages.
    • 74. Customize formatting of XML for some of the business types.
    • 75. Employ WSE 3.0 security using Certificates. Signing, encryption and secure session are required.
    • 76. Techniques used:
    • 77. Created a ASP.NET 2.0 Web Service
    • 78. Added a secured service layer to the library Application
    • 79. Improved the existing Web Application Library Phase III to consume the new Web Service secured with WSE 3.0
  • Web Service Code Sample
  • 80. Web Method Code Sample
  • 81. Secured Remote Invocation Code Sample
  • 82. Certificate Policy Configuration
  • 83. Class Member using XMLInclude attribute
  • 84. What is SetFocus?
    SetFocus is equivalent to 2-3 years of hands on experience. 
    I received over 500 hours of in-depths hands on experience focused on .NET Development.
    SetFocus projects are real world projects that are distributed just as I would receive in a position. I received project specifications and was expected to identify best courses of action with deadlines set for completion.

×