NOBY Senior Project - Customer Meeting Minutes

going to make parameters cleaner
stored procedures used by placement needs to make years in 20071 format instead of current 071 format

Authorization catches all service requests
Activity service not returning data on production box
- data is in the database
- appears the view is not being populated on production box
- on test box the stored procedue doesn't exist
- need to further investigate this issue
Went over testing goals
- automatic testing of every service method
- data quality will be assured in the automated tests
Poster
- no specific requirements from the customer
- poster will emphasize benefits of the design (since our project is about the architecture of the new system)
Need to follow up on ITS/Financial aid discussion
Professor Ludi has master's students analyzing our project
- will see about getting them a dump of our bug tracker and course code

Spring Co-op Status
- Phil
- New Co-op (John)
- UI developer
- Ken part time (4 hours/week)
Test Server
- Phil is looking at login issue
- Phil will ask about version control by Friday 22 morning
  - tentatively - SVN on test server
  - Place ticket as reminder
Deployment/transition
- Phase in with current system
- Phil checks with office if there is any existing plan/idea

covered the issue of VS on the dev box (ended up being a non-issue)
reviewed the modified architecture document
- will focus on web pages as the primary consumer of the services
- still keep to SOAP standard to allow for possibility of other non-web clients
- will work with Ken and Phil on the authorization contract to allow for secure access (ticket no.20)
- architecture will allow for addition of 'custom services' that can make use of lower level services (student, employer, etc.)
- covered the addition of database pooling for speed optimization
- update for next week to reflect full authorization model and how other services can fit in
discussed other possibilites of speed optimization
- database indexing - something that team will look into as part of this project
- use of current compiled tables or views
  - as long as they are already created, the risk of out of date data is acceptable
  - if team creates new views/tables we must research as to how often they are updated
- caching - out of scope for project, but still possible after completion
covered features/access points for placement service
- add in the possibility for filtering of international placements
- can combine the summary and detailed views for the student report
- agreed upon all other mentioned access points
discussed some of the other possible services such as alerts
team needs a requirements doc to fully describe all features that are in the scope of this project

Discussed test server:
- MS SQL Server 2000 & 2005
- Develop on Drive E: (aka SETeam folder)
Project Plan:
- Will send updated copy this weekend
- Discussed Deadlines, Sprints, and Metrics (code and document
  metrics)
Discussed Queries:
- Standard overall in time
  - Biggest and slowest is when you find out everything from a person or a company
- Placement table the most important / recommended starting point
Job Zone:
- We have accounts on it now.

Reviewed draft project plan with customer
- explained project process
- defined project scope
- approved web services proposal
Outlined project schedule
- planned for 2 week early completion requirement
Discussed metrics to be collected
Explained test server needs, Co-op Office is getting the server setup

Discussed the system to be developed in further detail
- more technical talk
- went over current web service design in prototype built by Ken, their current co-op employee
Customer provided database schema and screen shots of the current system
Provided access with internal bug tracker
Started process of obtaining a test server and database

Initial kick off meeting
Discussed system to be developed
Gathered high level requirements and performed a quick walk through of the current system