1. Web Applications for the School of NAS Group #3 09/18/2001

2. Team member and email addresses Daniel Liu: jiandliu@yahoo.comjiandliu@yahoo.com Guoying Yang: guoyingyang@hotmail.comguoyingyang@hotmail.com Nadia Halabi: nadiahalabi@hotmail.comnadiahalabi@hotmail.com Yifan Wang: yfw@hotmail.comyfw@hotmail.com Faculty advisors and mentors Dr. Kwok-Bun. Yue Team Information

3. Web page design  Two frame Web page content  General project information  Deliverables  Project management  Resources  Discussion board http://dcm.cl.uh.edu/capf01gp3/ The Project Web Page

4. Project Overview Work Flow Problems of NAS  Aided by computers to keep records  Rely on paper circulation in many work flows Benefits of Web Solution  Access from any computer with a browser  Paperless processes, no filing, easy look-up  Administrative reporting features  Flexibility for process expansion/modification

5. Module 1 - Course Inventories Current Process Problems  Faculties file a Change Request Form  Multi-level administration comments on form  After Curriculum Committee approval, staffs type course information to UCT  Word files generated separately for Catalog  Primitive Access database in place, but not updated  No statistic/monitoring report features

6. Module 2 – Faculty Annual Report Current Process Problems  Each faculty submit an annual report  Division chair writes an annual report for the school based on reports from the faculty  Faculty reports have free style and format, chair must hunt for information in each report  No statistic/monitoring report features

7. Requirements – In Progress Module 1 – Course Inventories  Faculty can work on a proposal with versions before submitting for approval  Administration can retrieve, review and evaluate a proposal  Staff can generate Words document for Catalog, and statistical reports  Enforce prerequisite structures  Administrative tools for information, such as faculty, program, rubric, CIP, etc.  Enforce security

8. Requirements – In Progress Module 2 – Faculty Annual Report  Faculty can work on a report, save it before submitting  Chair can add comments and generate Words document, and statistical reports  Faculty members can belong to multiple groups/programs in the report  Administrative tools for, program, rubric, type, report grouping, etc.  User friendly

9. Preliminary Design Module 1 – Course Inventories  Flow Chart  Functions prototypes  Preliminary page Module 2 – Faculty Annual Report  Work in progress

10. Progress Overall  Have established a workable platform to pursue the project  Completed team web site, and Utilized Module 1 – Course Inventories  Collected partial requirements, started design partially completed  Need UML diagram and refined functions and page

11. Progress - Continued Module 2 – Faculty Annual Report  Collected partial requirements  Design work starts this week

12. Technical Decisions Overall  Use MS.NET technology to implement this project  Use SQL 2000 for database Module 1 – Course Inventories  Course changes are submitted each year Module 2 – Faculty Annual Report  Application will not process and store traditional annual report

13. Outstanding Technical Issues Overall  Not familiar with UML diagram tools  Learning curve with MS.NET technology Module 1 – Course Inventories  Synchronization with CB database  Generate MS Words document from database  Generate redline/strikeout format from version difference

14. Outstanding Technical Issues Module 2 – Faculty Annual Report  Duplicate records, e.g. authors/co-authors for publication entries