Software Portfolio - SetFocus


Published on

PowerPoint Presentation of my software projects portfolio.

Published in: Technology, Education
  • 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

No notes for slide

Software Portfolio - SetFocus

  1. 1. .NET Portfolio<br />Alexander F Vogel<br /><br />(608) 481-3624<br />
  2. 2. Table of Contents<br /><ul><li>Framework Project – p.3
  3. 3. Library Phase 1: Windows Front-End – p.6
  4. 4. Library Phase 2: Business and Data Access Layers – p.9
  5. 5. Library Phase 3: Web Application – p.12
  6. 6. Library Phase 4: Distributed Programming & Web Services – p.14
  7. 7. SetFocus Testing Application – p.17</li></li></ul><li>Framework Project<br /><ul><li>Objective:
  8. 8. In this project, the goal is to create and test two assemblies for the business tier of a retail company. The first, Foundation, will contain various interfaces and base classes as specified in the design document. The second, AppTypes, will contain various entity, collection, and exception classes used by various business processes. The business processes have already been implemented.
  9. 9. Project Goals:
  10. 10. Code in C# using Visual Studio 2008
  11. 11. Implement interfaces, classes, properties, constructors, serialization, enums, and delegates according to design specifications
  12. 12. Implement IEnumerable and IEnumeration on a class and override methods (Equal and GetHashCode) and operators (==, !=, <, >, <=, >=)
  13. 13. Produce XML documentation on public members</li></li></ul><li>Framework ProjectFoundation Class Diagram<br />
  14. 14. Framework ProjectAppTypes Class Diagrams<br />
  15. 15. Framework ProjectAppTypes Class Diagrams<br />
  16. 16. Framework ProjectProduct Class Overview<br />
  17. 17. Framework ProjectProduct Class Sample Code<br />
  18. 18. Framework ProjectProduct Class Sample Code<br />
  19. 19. Library Phase 1: Windows Front-End <br /><ul><li>Objective:
  20. 20. A database has been created 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. An assembly has been created that contains classes and interfaces that provide access to the database for these functions.
  21. 21. In this project, the goal is to create 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.
  22. 22. Project Goals:
  23. 23. Design and develop a front end application that satisfies the four basic functionalities: Add Adult Member, Add Juvenile Member, Check In a book, Check Out a book
  24. 24. Develop code that is easily maintainable
  25. 25. Provide validation for all required fields (as detailed in specifications)
  26. 26. Provide adequate error handling
  27. 27. Produce a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization</li></li></ul><li>Library Phase 1Windows Forms and UI Design<br />
  28. 28. Library Phase 1Windows Forms and UI Design<br />
  29. 29. Library Phase 1Presentation Layer Sample Code<br />
  30. 30. Library Phase 2: Business and Data Access Layers<br /><ul><li>Objective:
  31. 31. In this project, the goal is to design and implement new business entity and data access tiers to replace those used in Library Phase 1 in order to take advantage of Linq and LinqToSql’s rapid code development and abstraction techniques. Use the LinqToSql designer to build and Model the Item and Member classes (Member, Adult, and Juvenile) off of the Member view created earlier. Once this is done, use the datacontext to get data from the Database and return the appropriate class.
  32. 32. Since the data is coming from a view it is read only, a stored Procedure must be written to send data back. Add these to the LinqToSql model so you can call them from the DataContext and abstract away the details for connection and command objects. The stored procedures must be commented thoroughly and the code should not contain any SQL statements that were not auto generated.
  33. 33. Project Goals:
  34. 34. Redesign and replace the Business Entity and Data Access layers
  35. 35. Create appropriate T-SQL stored procedures for storing and retrieving data from the database
  36. 36. Create LINQ to SQL class in the Entities layer and use the appropriate LINQ query to retrieve information from the database on the Data Access layer
  37. 37. Develop code that is easily maintainable
  38. 38. Provide adequate error handling
  39. 39. Use database-programming techniques that provide maximum programming flexibility and
  40. 40. control while minimizing resource utilization
  41. 41. Use LinqToSQL to develop object models and abstract away data provider code
  42. 42. Reference the User Interface from Phase 1</li></li></ul><li>Library Phase 2Business Layer & Validation<br />
  43. 43. Library Phase 2Class Diagram of LINQ and Dataset<br />
  44. 44. Library Phase 2Data Context<br />
  45. 45. Library Phase 2T-SQL Stored Procedures<br />
  46. 46. Library Phase 3: Web Application<br /><ul><li>Objective:
  47. 47. Create a web application that supports all the functionality required for Library Phase 1 and 2.
  48. 48. Project Goals:
  49. 49. Design and develop a front end web application that can Add Adult Member, Add Juvenile Member, Check In a book, Check Out a book, and Renew Membership
  50. 50. Create Add Item web form for adding new items to the library
  51. 51. Modify the Member Information page to use two AJAX controls, the Update Panel control and the Update Progress control
  52. 52. Reference the Business, Data Access, and Entities layers from Phase 2
  53. 53. Reference the T-SQL stored procedures from Phase 2
  54. 54. Use Forms-based authentication and authorization
  55. 55. Only members of the Librarian role can use the web application</li></li></ul><li>Library Phase 4: Distributed Programming & Web Services<br /><ul><li>Objective:
  56. 56. Our library system roll-out has been very successful. As the potential to acquire libraries and creating partnerships with others increases, we see the need to take the library system to the next level – allow interoperability with other systems. With the success on the library system thus far, we need to provide a proof of concept implementation that utilizes Web services.
  57. 57. Use Windows Communication Foundation (WCF) to implement the service. To provide the proof of concept system, implement a system that uses Web services to offer access to the business layer. Due to the possibility of utilizing the service between our own systems and those of our partners, security must be employed. Use the existing presentation front-end for the client layer.
  58. 58. Project Goals:
  59. 59. Create a WCF service that calls into the business layer
  60. 60. Update the presentation (UI) layer to call the WCF service
  61. 61. The WCF Service must be implemented with or support the following:
  62. 62. WCF Service Library project, WCF Service Website, WsHttpBinding, Authentication using ASP.NET membership, Authorization using ASP.NET roles
  63. 63. Use DataContracts for entities
  64. 64. Use certificates, signing, encryption, and secure session for security
  65. 65. Support all previous functionality from Phase 3</li></li></ul><li>SetFocus Testing Application<br /><ul><li>Objective:
  66. 66. SetFocus is a company that specializes in training business professionals in a variety of programming disciplines. After lecture weeks students will be tested on the material reviewed during class. The testing link is sent via email. Students are able to answer questions, review answers, and submit their exams for grading.
  67. 67. The objective of this project is to create a windows based application for creating the test that will link to a web based application that will allow participants to respond with the answers to the test. 
  68. 68. The development teams will be provided with a draft version of the database. They will also be given access to stored procedures that are currently used for the testing application.
  69. 69. Project Goals:
  70. 70. Design and develop a windows application that will satisfy the below listed user functions
  71. 71. Create stored procedures for the required functionality
  72. 72. Use a multi-tiered programming approach when designing the application
  73. 73. Follow the provided naming conventions when creating the stored procedures
  74. 74. Develop code that is easily maintainable and well commented
  75. 75. Produce a user interface that is intuitive and requires minimal training for the user
  76. 76. Employ Framework 2.0, ADO.NET 2.0, ASP.NET 2.0, and SQL Server 2005 technologies</li>