Archive for May, 2013

Dev Cycle 43

0 Commentsby   |  05.28.13  |  Uncategorized

We finished up Development Cycle 43 last week, which spans May 6th through May 24th.  Here are some of the highlights for this cycle:

  • OpenClass – We pushed out multiple updates to the jobs that create courses, delete courses and manage course enrollment.  We continue to provide support to the Adams Center and Pearson as we identify the Blackboard courses that need to be converted to OpenClass.
  • NCAA Compliance Assistant integration – We loaded Spring 2013 degree progress information from Banner last week.  We started discussing phase two, pushing financial aid package information, and plan to start work on this later in the summer.
  • Fire Engine Red graduate admissions application – We are working with Graduate Enrollment Marketing to prepare for their admissions application move to Fire Engine Red (FER).  We are testing the data import processes that will push data from FER to Talisma.
  • myACU and m.acu.edu – We have analyzed the report from a student-led project group in Dr. Brad Crisp’s Analysis and Design class to identify enhancements and changes we might consider for the Fall 2013 term and beyond.  We are considering some of their suggested changes and improvements of myACU in time for Fall 2013.  Additionally, we are working with a design firm to create an updated interface for m.acu.edu.  The new m.acu.edu will streamline the process of accessing personalized information, especially for current students.
  • Ellucian Mobile – We purchased the Ellucian Mobile Platform edition to provide a native application for iOS and Android devices.  Initial setup and preparation will take place in June with the plan to release the applications sometime in the fall.  This will eventually replace all of the functionality provided in m.acu.edu and introduce some new features that Ellucian provides.
  • Meal Plan administration – We finished changes to improve the billing and management process for the 2013 – 2014 school year.  We will deploy all of our updates before the June bill is generated next week.
  • In all, 54 development issues were completed during this development cycle in addition to the on-going projects mentioned above.

See Dev Cycle 43 – Resolved Issues for a more in-depth summary.

Dev Cycle 42

0 Commentsby   |  05.06.13  |  Uncategorized

We finished up Development Cycle 42 last week, which spans April 15th through May 3rd.  Here are some of the highlights for this cycle:

  • OpenClass – Work continues as the campus prepares for the migration from Blackboard to Pearson’s OpenClass.  We completed work to automate the creation of courses and management of enrollment so that this is no longer handled manually.  We continue to provide support to the Adams Center and Pearson as we identify the Blackboard courses that need to be converted to OpenClass.
  • NCAA Compliance Assistant integration – We finished up the first phase of this project, which will provide degree progress data to the system.  We will run this new job after the conclusion of the Spring 2013 term when grades have been entered into Banner.  We will pick up phase two, pushing financial aid package information, this summer.
  • Fire Engine Red graduate admissions application – We are working with Graduate Enrollment Marketing to prepare for their admissions application move to Fire Engine Red (FER).  Our work revolves around planning and implementation of the data import processes that will push data from FER to Talisma.
  • myACU and m.acu.edu – We are working with a student-led project group in Dr. Brad Crisp’s Analysis and Design class to identify enhancements and changes we might consider for the Fall 2013 term and beyond.  The students submitted their final report to us over the weekend and we will be meeting with them this week to discuss their findings and suggestions.
  • Meal Plan administration – We are in the midst of work to implement a few changes in time for the first Fall 2013 bill to be sent out in June.
  • In all, 55 development issues were completed during this development cycle in addition to the on-going projects mentioned above.

See Dev Cycle 42 – Resolved Issues for a more in-depth summary.