Hi everyone,
I work for the Robert Gordon University in Aberdeen, Scotland and I've
just been assigned a new project which is to build a generic online
payment system for the University. The initial objective is to give
our users some kind of shopping cart facility which would allow them
to add general online payment to pages. Examples would be for things
like Parking fees and Conference ticket booking etc.
A phase two for the work would be to bring our other applications
inline with this system so things like Applying Online or Graduating
would be dealt with by this rather than the custom systems we're using
at the moment.
Project was only announced last week but main requirements as it
stands just now are...
- Modular in-build: We use Streamline as our payment provider at the
moment and although we have no plans to move we want the ability to
swap it out easily without affecting the rest of the system. We're
also looking at moving our CMS at some point soon so intergration with
different systems is a must.
- Logging: We need to log user activity through the whole process -
mainly for troubleshooting and reports.
- Integration with Finance: We need to be able to customise the
processed data through to our finance system.
---
I've seen the extensive list of functionality for the project and on
paper it looks great. As this isn't classed as your typical Ecommerce
project though I thought I'd ask if you felt this project would
suitable? Do you have any kind of timeframe for the project?
I'm currently in the research/reporting stage - No specific deadlines
for the project but the report is due at the end of the month and
timescales will be reviewed then.
If you need any further information please let me know.
Thanks,
James
|
