1. ISU Alumni Association Online Store May05-39 Dr. Srinivas Aluru, CprE ISU Alumni Association Faculty Advisor: Client: Jon RuhnkeAndrew Kirpalani Jordan JumpKeith Dahlby Team Members:

2. Presentation Outline Andrew Kirpalani Closure Material Jordan Jump Screenshots, Resources and Schedules Keith Dahlby Project Activity Description Jon Ruhnke Introductory Material

3. Jon Ruhnke

4. Important Definitions Microsoft Desktop Engine – Freely redistributable version of Microsoft SQL Server that integrates well with Windows and the.NET Framework. MSDE Subversion - a version control system for controlling access to a software project and it’s files. SVN Cascading Style Sheets - a simple format for attaching style information to HTML and XML documents. CSS Microsoft-created, object-oriented programming language similar to Java, with many features designed specifically for the.NET Framework. C# Newest version of ASP, with many significant improvements over “classic” ASP. ASP.NET Active Server Pages - a Microsoft technology that allows web pages to be dynamically generated. ASP Provides a common set of tools for developers on the Windows platform..NET Framework

5. Acknowledgements  Dr. Srinivas Aluru, for his support and guidance as the project advisor.  Kate Bruns and the staff at the ISU Alumni Association, for guidance as well as origination of the project.

6. Problem Statement General Problem Statement ISUAA Online Store exists to promote the university and its alumni Current implementation is vastly outdated and inefficient Complete redesign of the storefront and new implementation of administrative tools is needed General Solution Approach New store and tool suite to be implemented by building upon existing C#, ASP, and.NET knowledge. Careful focus on efficient database design and centralized control of administration

7. Operating Environment Served from existing Alumni Association server –Windows 2000 –.NET framework –MSDE database system Public and Administrative access from any modern web browser on the internet –Internet Explorer, Netscape, etc.

8. Intended Users and Uses Intended Users Online Store Customers Alumni Association Staff Intended Uses Customers –Browse catalog –Purchase products –Manage shopping cart –Complete orders Administrators –Add, remove, and update products –Process orders –View reports

9. Assumptions Technical Assumptions User is using a modern web browser User has access to a sufficient Internet connection Client server has sufficient system resources Client server has ASP.NET 1.1 (or later) installed Non-Technical Assumptions Users have previous experience with online stores Alumni Association staff have sufficient experience and ability to operate web-based administrative tools

10. Limitations Access to a dedicated database server –Wanted to use server maintained by the ISU Foundation –Technical difficulties prevented use of the server System resources available on client’s server Team members’ proficiency with ASP.NET

11. End Product and Deliverables Online store capable of: –Presenting merchandise –Accepting orders –Maintaining security New database that eliminates duplication of work Comprehensive suite of administrative tools to allow: –Managing product catalog –Easily processing customer orders –Gathering store data

12. Project Activity Description Keith Dahlby

13. Present Accomplishments Online store with ability to: –Browse product catalog –Add items to a shopping cart Administrative interface to: –Add categories to the catalog –Add products to the catalog

14. Approaches Considered Programming Language: C# –Official language supported by ASP.NET –Many built in classes and functions Database: MSDE –Integrates well with the operating system –Many windows tools available –Seamlessly integrates with ADO.NET Database: MySQL (not used) –Robust, free, and widely supported –Doesn’t integrate as seamlessly Platform: Windows 2000 –Windows best supports ASP.NET –Existing server operating system, yet we suggest upgrading to Windows 2003 when possible Most of these approaches were design constraints from client

15. Project Definition Activities Requirements and technical considerations initially well-defined by client Detailed design questions resolved during project design, in consultation with client

16. Research Activities Database system –Decision between MSDE and MySQL –Considerations: Integration with Windows 2000 Server and ADO.NET Interface for database design and configuration Future upgrade path ASP.NET –.NET Framework v2.0 –Performance questions: Caching Efficient access to database

17. Design Activities Design Constraints Primary audience using modern web browser with sufficient bandwidth –Internet Explorer 5.0 or later –Netscape 6.0 or later –Safari –Mozilla Firefox Users with non-traditional or legacy web browsers require a functional user experience Web applications present inherent limitations on user experience System resources available on existing client server Limited to Windows 2000 Server running IIS and ASP.NET

18. Design Activities (cont.) Design Overview

19. Design Activities (cont.) Database Schema

20. Design Activities (cont.) Primary Use Case

21. Implementation Activities Item Options –Problem: Custom fields for certain items Future items with unknown options Parameter choices affect price –Changes: Options stored as serialized objects in database Organized items in the cart by item -Simplifies management of item options -Simplifies administrative metrics Objects –Problem: Re-conceptualized object oriented structure needed to better fit presentation requirements –Changes: Cart Object Picture Object CreditCard Object

22. Testing Activities Testing performed throughout development –Test pages while creating new objects –High-level custom web controls’ boundary conditions tested with sample pages –Database tested with concurrent development of administrative interface pages Client testing and feedback –Individual components released to staff members Problems exposed by non-dev users Feedback acquired Future testing –Release private version of store to entire ISUAA staff Comprehensive testing/feedback on a larger scale

23. Other Significant Activities Alumni member login integration – Lack of proprietary ASP.NET module to retrieve user information – Unable to test member functionality Site redesign – No styling information provided to group – Unable to match appearance with other Alumni services Upcoming releases (could enhance implementation) – SQL Server Express 2005 – Visual Studio 2005 – ASP.NET 2.0

24. Screenshots, Resources, and Schedules Jordan Jump

25. Screenshots Original Front Page

26. Screenshots (cont.) Original Item Description Page

27. Screenshots (cont.) Original Shopping Cart Page

28. Personal Effort Requirements 123.5Jon Ruhnke 661 Total HoursName 166Andrew Kirpalani 171Jordan Jump 200.5Keith Dahlby

29. Other Resource Requirements $17.49Binding $102.51 Total $10.00Printing & Copying $75.02Project Poster CostItem

30. Financial Requirements $6610.00 Subtotal $1235.00 Jon Ruhnke $1660.00 Andrew Kirpalani $1710.00 Jordan Jump $2005.00 Keith Dahlby Labor at $10.00 per hour $102.51 Subtotal $17.49 Binding $10.00 Printing & Copying $6712.51$102.51 Total $75.02 Project Poster Materials: W/ LaborW/O Labor Item

31. Schedule Fall 2004: Project Schedule

32. Schedule Fall 2004: Revised Project Schedule

33. Schedule (cont.) Fall 2004: Project Deliverables

34. Schedule (cont.) Spring 2005: Project Schedule

35. Schedule (cont.) Spring 2005: Revised Project Schedule

36. Schedule (cont.) Spring 2005: Project Deliverables

37. Project Evaluation Partially MetEnd-product Testing Partially MetEnd-product Implementation Not AttemptedEnd-product Documentation Fully MetProject Reporting/Deliverables Fully MetEnd-product Design ExceededTechnology Considerations and Selection Fully MetProject Definition

38. Closing Material Andrew Kirpalani

39. Commercialization Commercialization for this product is not considered, as it is a specific customized upgrade to an existing system

40. Additional Recommendations Multiple product images Extended category structuring Frequent use of stored procedures Database backup/recreation script Windows Server 2003 upgrade Integration of administrative functionality with administration of other Alumni web applications

41. Lessons Learned What went well? Meetings with Alumni Association staff Good brainstorming, solid design Good scan of technology options, proved useful when original database was found to be inadequate What did not go well? Slow development early on Duplication of work due to changes in system

42. Lessons Learned (cont.) What technical knowledge was gained? New development skills with C# and ASP.NET Web-based development experience What non-technical knowledge was gained? Small team development interactions Long-term project planning What would be done differently? More discipline and vigilance in adhering to schedule

43. Risk and Risk Management Anticipated potential risks Loss or corruption of code –SVN Breakdown of communication –Recurring scheduled meetings and direct contact info Anticipated risks encountered Second semester communication and missed meetings –Email meeting info, and other avenues of communication Unanticipated risks encountered Restricted access to ISU network from off-campus –VPN software set up Resultant changes due to unanticipated risks Use of VPN software, moving to campus location otherwise

44. Closing Summary Re-designed Iowa State Alumni Association Online Store Raises money and promotes ISU Attractive and functional storefront Streamlined administrative back-end New efficient database

45. Questions?