Metadata studies: the metadata reveals many relationships and allows some short cuts
Methods for loading data into the new PeopleSoft system
Bundle Processing: PeopleSoft sent upgrades to the software every three months
Maintaining the old system
SQL to modify data bases
State Machine to process documents
Extract programs in SQR and AppEngine
Admissions Processing tiny changes
School of Education screens and reports for certifying teachers and principals
FERPA screens
Fun Salaried to Harassed Hourly
Working on software at APU had been fun. A small crew of four or five maintained or wrote all the software. When the bureaucracy came, hoards of workers, actually people, came and the fun disappeared. Whereas a programmer might have performed every step in the software cycle, the new people did not know the names of the steps and muddled through the motions. Many embedded helpers appeared; directors appeared. Analysts and QA people. The programmers were forced into a tiny box and told that they were now hourly because the scope of work was tiny. (PeopleSoft required so many more tools and skills; the scope was enormous.) No one verified that the specs were workable, because no one knew the overall process.
Several young programmers each had a moment in the sun as some new applications were implemented. Then they also left.
- find pathways from components to roles to users
- find fields on a screen
- compare projects
Methods for loading data into the new PeopleSoft system
Bundle Processing: PeopleSoft sent upgrades to the software every three months
Maintaining the old system
SQL to modify data bases
State Machine to process documents
Extract programs in SQR and AppEngine
- student IDs and information for Library
- student IDs and information for Cafeteria system
- student enrollment info for Learning Management System-- SAKIA
Admissions Processing tiny changes
School of Education screens and reports for certifying teachers and principals
FERPA screens
Fun Salaried to Harassed Hourly
Working on software at APU had been fun. A small crew of four or five maintained or wrote all the software. When the bureaucracy came, hoards of workers, actually people, came and the fun disappeared. Whereas a programmer might have performed every step in the software cycle, the new people did not know the names of the steps and muddled through the motions. Many embedded helpers appeared; directors appeared. Analysts and QA people. The programmers were forced into a tiny box and told that they were now hourly because the scope of work was tiny. (PeopleSoft required so many more tools and skills; the scope was enormous.) No one verified that the specs were workable, because no one knew the overall process.
Several young programmers each had a moment in the sun as some new applications were implemented. Then they also left.