Your SlideShare is downloading. ×
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF Portfolio
LKF 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

LKF Portfolio


Published on

A sample of my programming work.

A sample of my programming work.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1.
    • .NET Portfolio
    • Leon K. Francis
    • Email:
    • Phone: (801)651-0863
  • 2. .NET Framework Project
    • Build parts of the business tier for a retail company.
    • Create and test two assemblies:
      • The first assembly is a class library project called Foundation, containing various interfaces and base classes.
      • The second assembly is a class library project called AppTypes, containing various entity, collection and exception classes.
  • 3. Classes of Many Types Required
  • 4. Sample Code
  • 5. Library Database Project
    • Introduction: A database has been created to support the principal functions of a lending library’s day to day operations: checking books in and out, and adding new members (adult and juvenile)
    • Audience: Users of the library database (i.e. librarians).
    • Project Goals: Provide an easy to use user interface to access and manipulate the data in the database.
  • 6.
    • Layered Architecture
    • Data transport between layers using Entities
    • User-friendly Interface.
    • Menu driven Navigation.
    • Well Covered Validations
    Design Highlights
  • 7. Library Phase I
    • Requirements:
      • Develop a Windows front-end with four functions
        • Add adult member
        • Add juvenile member
        • Check in an item
        • Check out an item
    • Two Projects Developed:
      • Windows Client
        • Form control
        • Validation
      • Business Layer
        • Business layer enforcement
        • Data access layer communication
  • 8. Project Sample (Get Member Info)
    • Can view member information
    • Highlights out dated card expiration
    • Highlights over due books
  • 9. Project Sample (Add Adult Member)
    • Combo box populated from XML file
    • Icon and tool tip used to communicate errors
  • 10. Hi-light expired membership
  • 11. Library Phase II
    • Develop stored procedures for seven processes:
      • Add member
      • Get member
      • Check in an item
      • Check out an item
      • Get item (returns an item with a specific ISBN and copy #)
      • Get items (returns all items a member has checked out)
      • Convert juvenile to adult membership
    • Create a data access layer:
      • Call stored procedures in the database
      • Return data or throw errors to the Business layer
    • Create Entities classes accessible to all layers:
      • Member
      • AdultMember (derived from Member)
      • JuvenileMember (derived from Member)
      • Item
      • ItemsDataSet
      • LibraryException
  • 12. ADO.NET code in Data Access Layer
  • 13. Stored Procedure (ConvertJuvenileToAdult)
  • 14. Library Phase III
    • Convert Windows interface to Web interface
    • Add functionality:
      • Add new item to the database (new ISBN or copy of existing ISBN)
      • Ability to renew membership card
    • Add Security:
      • Add a Librarian role to the database with users
      • Prevent everyone except the Librarian role from accessing library functions
  • 15. Log-in screen on startup for security
  • 16. All functionality from Windows UI remains in Web UI
    • In addition, user has the option to renew an expired card
  • 17. Use of validators to provide error checking
  • 18. Sample code to add member to database
  • 19. Library Phase IV
    • Create a Web service that calls into the business layer
    • Update the presentation (UI) layer to call the Web service
    • Employ WSE 3.0 security using certificates
    • Support previous project functionality
  • 20. Sample code implementing the Web service
  • 21. Summary
    • Six projects (Framework, Library Phase I – IV, Evaluation Surveys (team project))
    • 10,000+ lines of C# code
    • 1000+ lines of supporting code (SQL, XML, HTML)
    • 240+ project hours