1

AdviseUP

• Team– Sam Burich– Kapua Chandler– Chris Lewis Advisor

Dr. Tammy VanDeGrift

Industry RepresentativeMr. Brian TooleUniversity of Portland Information Services

School of Engineering

2

Introduction

• AdviseUP– Scheduling and advising application– Expedite advising process for students and

faculty– Real client: Dr. Kenneth Lulay– High potential for use in future advising

School of Engineering

3

Accomplishments

• Began Design Document:– Decided on technologies (C#, SQLServer)– Completed GUI design (mockups)– Made progress toward final Database design

• Met with the following people:– Brian Toole (UP Database Expert), Ronan

Cranley (WAS), and Dr. VanDeGrift

School of Engineering

4

Completed GUI Design

School of Engineering

Advisee Uninitialized page

(Schedule Initialized) Advisee Typical View

page

(Click View Info) Advisor Information page Schedule Functions

(Click course on schedule in GV) Course

Information page

(Hover over course in GV) Demonstrations of

Prerequisite on schedule

(Select course from drop down in GV of schedule)

Change Elective page

(Drag and drop functionality within GV)

Move courses on schedule

Illegal course move attempt (Error box

appears)

(Click View Log button) Log page

(Click View/Add Notes) Notes page

(Type note and click Add) Add Note page

(Select List View button)List View Save, Print, Help

(Click Save button) Save (Click Print button) Print (Click Help button) Help page

5

Database Design Progress

School of Engineering

• The database for AdviseUP will need to store information for the following:– Students (Advisees)– Employees (employees of interest are Advisors and

Administrators)– Banner Course Information– Electives (a selection of courses)– Templates (predefined layout of courses)– Advisee Schedules

• Met with the following people:– Brian Toole (UP Database Expert)

6

Plans

• Design classes and methods• Create database queries to display

information in the User Interface (Processor Design)

• Finish other sections of the Design Document

School of Engineering

7

Milestones

School of Engineering

Status Description OriginalTarget

PreviousTarget

PresentTarget

completed Functional Specifications 30 Sep 2011 30 Sep 2011 30 Sep 2011

completed September Program Review 30 Sep 2011 30 Sep 2011 30 Sep 2011

completed Decide on project technologies

7 Oct 2011 7 Oct 2011 7 Oct 2011

completed Create mock screenshots of GUI

14 Oct 2011 14 Oct 2011 14 Oct 2011

completed Finish User Interface section of Design Document

28 Oct 2011 28 Oct 2011 28 Oct 2011

In progress Finish Database and Processor design

5 Nov 2011 5 Nov 2011 5 Nov 2011

Design Document version 0.9

12 Nov 2011 12 Nov 2011 12 Nov 2011

Final Budget 19 Nov 2011 19 Nov 2011 19 Nov 2011

Design Document version 0.95

19 Nov 2011 19 Nov 2011 19 Nov 2011

November Program Review 2 Dec 2011 2 Dec 2011 2 Dec 2011

8

Concerns

• Unfamiliarity with C# Web development (need to create prototypes)

• Unsure of the future of the application

School of Engineering

9

Conclusion

• AdviseUP will:– Expedite the advising process– Be built for a real client– Be completed on time (ideally)

• Finishing design document is the team’s main focus

School of Engineering