Web-Dev Portfolio

1,329 views

Published on

These projects demonstrated my ability to program Visual Studio .Net with C# as the programming language in 2 separate projects.

The Purpose of the first project was to build parts of the business tier for a retail Company. The goal is to create and test two assemblies. The first assembly is a class library project called Foundation. It will contain various interfaces and base classes.

The second assembly is also a Class Library project and its called AppTypes and it will contain various entity, collection and exception classes used by various business processes.

The Objective of the second project Is to create a database to support the principal functions of a library’s day-to-day operations: adding new members (adult and juvenile) and checking books in and out.

A Windows Forms-based front end application that will provide a librarian with a visual interface through which he or she may perform the desired functions.

And the project goal is to Design and develop a front end application that satisfies the four basic functionalities: Add Adult, Add Juvenile, Check in a book, Check Out a book.
Develop code that is easily maintainable.
Provide validation for all required fields.
Provide adequate error handling.
Produce a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,329
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Web-Dev Portfolio

  1. 1. .Net Portfolio<br />Nana Boama<br />nbwireko@gmail.com<br />(571) 354-9058<br />
  2. 2. Table of Contents<br />.Net Framework ………..………….. 3<br />.Net Framework Project …………… 4-12<br />Windows Project ……………………13-21<br />
  3. 3. .Net Framework<br />Microsoft .Net Platform<br /> .Net Platform provides all of the tools and technologies that you need to build distributed Web Applications. It exposes a language-independent, consistent programming model across all tiers of an application while providing seamless interoperability with, and easy migration from, existing technologies.<br />Programming with C#<br />C# is a new language specifically designed for building .Net applications. It’s a type –safe, object –oriented language that is simple yet powerful, allowing programmers to build a breadth of applications.<br />.Net Framework<br /> The .Net Framework is based on a new common language runtime. The common language runtime provides a common set of services for project build in Microsoft Visual Studio .Net.<br />
  4. 4. .Net Framework Project<br />
  5. 5. Brief Description<br />The Framework Project:<br /> This project demonstrated the ability of each student to program Visual Studio .Net with C# as the programming language. The Purpose of this project was to build parts of the business tier for a retail Company.<br />The Framework Project Goal:<br /> The goal is to create and test two assemblies. The first assembly is a class library project called Foundation. It will contain various interfaces and base classes. The second assembly is also a Class Library project and its called AppTypes and it will contain various entity, collection and exception classes used by various business processes.<br />
  6. 6. Framework Project Specification<br />I-CompanyContact: This interface details require properties for abstractions where a contact is available.<br />I-Address: This details required properties for abstraction with a mailing address<br />I-CountryPhone: This interface details required properties for abstractions with phone numbers.<br />I-ContactInfo: This interface consolidates the requirements defined in ICompanyContact, Iaddress, and ICountryPhone.<br />I-CustomCollection: This interface ICustomCollection is provided as a contract to guarantee that certain basic collection functionality will be available in collection classes that we will be writing.<br />Contac t: Inherits from IContactInfo and it’s the base class for abstraction.<br />
  7. 7. Foundation Class Diagram<br />This Diagram comprises of the classes that make up the foundation assembly.<br />
  8. 8. AppTypes Project<br />DeveloperInfoAttribute: Classes that apply at the Assembly, Class, Interface and Enum Target Levels<br />CustomDescritpionAttribute: Inherits from Attribute and targets all levels but may not be applied in multiples. <br />SupplierTypes: Is provided to insure that the type of each Supplier is limited to one of the known types<br />Class Supplier: Responsibility of the Supplier class is to hold information about various suppliers used by the company.<br />Class AppTypes.AppTypesException: Defines a custom exception that may be thrown from various classes in the AppTypes namespace.<br />Class Suppliers: This class representative of code written before the System.<br />Product: This class is responsible for representing the various products and services bought or sold by the company.<br />ModificationEventStatus: Used to indicate the success or failure of an attempt to modify the collection.<br />ModificationEventArgs: Used to communicate details about the event that was raised.<br />
  9. 9. AppTypes Project Cont.<br />CollectionModifiedHandler: A delegate used to define the event type to be raised anytime the collection is modified.<br />C lass Products: The Product class will be Provided to manage a collection of Product instances. It utilizes the System.Collection.Generic namespace. By virtue of implementing IList<T> where T is Product.<br />Class EventLogger: The purpose EventLogger class is to handle CollectionModified events raised by the product class.<br />GenericCollection<T>: This class will provide a generic template for creating strongly collection classes.<br />
  10. 10. AppTypes Class Diagram<br />This visual App Types Class Diagram comprises of the classes and components that make up the App Types Assembly<br />
  11. 11. Foundation Code Samples<br />Foundation Code Sample<br />This is a code sample of the Foundation Assembly in the ICustomCollection class which guarantees that certain basic collection functionality will be available in the collection classes.<br />
  12. 12. AppTypes Code Samples<br />AppTypes Code Sample<br />This is a visual representation of the sample coding for the App Types Assembly in which This class will provide a generic template for creating strongly collection classes.<br />
  13. 13. Windows Project<br />
  14. 14. Brief Description Windows Project<br />Objective: Is to create a database to support the principal functions of a lending library’s day-to-day operations: adding new members (adult and juvenile) and checking books in and out. A Windows Forms-based front end application that will provide a librarian with a visual interface through which he or she may perform the desired functions.<br />Project Goals:<br />Design and develop a front end application that satisfies the four basic functionalities: Add Adult, Add Juvenile, Check in a book, Check Out a book.<br />Develop code that is easily maintainable.<br />Provide validation for all required fields.<br />Provide adequate error handling.<br />Produce a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization.<br />
  15. 15. N.W.Boama Library Assembly<br />BusinessLayer Class<br />NB.LibraryBusiness<br />This Visual representation of the<br /> Business Layer Class the stored applications on the server database and how to accessthem through the business layer Access.<br />This diagram shows how the validation is done in terms of the requirements for the database. They supply methods and classes to be validated.<br />
  16. 16. Adding Adult Member<br />This visual representation of the Adult Member Show’s the respective steps the interface follows in order to add an Adult Library Member to the Database such as first and last name, middle initial etc.<br />
  17. 17. Adding Juvenile Member<br />This visual representation of the Adding Juvenile Member Show’s the respective steps the interface follows in order to add a Juvenile Library Member to the Database such as first and last name, middle initial etc.<br />
  18. 18. Displaying Member Information<br />This form gives access to<br />the user to view any information about the members whether being it a Juvenile or Adult. And also show what books they’ve checked out and when the due date is for the book to be returned.<br />
  19. 19. Checking In Item<br />This give the user the ability to<br />Check in an item namely books<br />in the library by first entering the<br />Member Number, ISBN number <br />And finally the form number the <br />Respective books to be checked into the Library.<br />
  20. 20. Checking Out Item<br />This give the user the ability to<br />Check out an item name books<br />Out the library by first entering the Member Number, ISBN number And finally the form number the respective books to be checked Out the Library.<br />
  21. 21. Window Project Code Sample<br />This Code sample of<br />the business Layer class<br />displays the front-application Coding and how it works.<br />

×