adviseup: mark ii team hopworks kekai ariola eric bergquist (team leader) megan yamamoto faculty...

7
AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole Sam Burich Client Dr. Kenneth Lulay

Upload: rhoda-mcdowell

Post on 02-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

AdviseUP: Mark IITeam Hopworks

Kekai AriolaEric Bergquist (Team Leader)Megan Yamamoto

Faculty AdvisorDr. Tammy VanDeGrift

Industry AdvisorsBrian TooleSam Burich

ClientDr. Kenneth Lulay

Page 2: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

Project Overview• Inherited project

• Academic planning web application

• Facilitate advising process

Page 3: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

ScorecardMilestone Description Projected

CompletionActual Completion

1 Functional Specifications Document Draft

19 Sep 2012 24 Sep 2012

2 Functional Specifications Document Final Draft

21 Sep 2012

A Hold AdviseUP code review with Sam Burich

5 Oct 2012 2 Oct 2012

B Identify what data must be drawn from banner

8 Oct 2012

3 Design Document Draft 12 Oct 2012

C Registrar approval to use banner database

12 Oct 2012 10 Oct 2012

4 Design Document Final Version 22 Oct 2012

D Complete policy for purging data 24 Oct 2012 24 Oct 2012

Page 4: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

Upcoming MilestonesMilestone Description Scheduled

CompletionEstimatedCompletion

B Identify what data must be drawn from banner

8 Oct 2012 31 Oct 2012

3 Design Document Draft 12 Oct 2012 31 Oct 2012

4 Design Document Final Version 22 Oct 2012 9 Nov 2012

F Complete code for internal database to call stored procedures to access banner data

7 Nov 2012 30 Nov 2012

G Complete CAS authentication code 12 Nov 2012 12 Nov 2012

H Complete code to modify templates 23 Nov 2012 23 Nov 2012

I Test CAS authentication 23 Nov 2012 23 Nov 2012

J Test banner access procedures 28 Nov 2012 7 Dec 2012

K Test course prediction and template procedures

28 Nov 2012 28 Nov 2012

Page 5: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

Design Component

Information to obtain from Banner

Course Employee Advisee

courseID employeeID adviseeID

dptCode UPemail UPemail

courseNumber firstName advisorID

name lastName startTerm

credits location firstName

preReqID phone lastName

coReqID transcript

    graduated

Page 6: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

Issues and Concerns• We don’t have any form of version control at the

moment.

• We don’t completely understand all the code we inherited specifically dynamic code creation.

• We will be using a database link to a view of the information we need from Banner. We don’t know how the data is stored in Banner or in our view.

Page 7: AdviseUP: Mark II Team Hopworks Kekai Ariola Eric Bergquist (Team Leader) Megan Yamamoto Faculty Advisor Dr. Tammy VanDeGrift Industry Advisors Brian Toole

Conclusion

• AdviseUP is scheduling application• Ambitious Schedule