Acceptance Test: College Catalogoraserv.cs.siena.edu/~perm_initech/docapr.pdf · Initech Corp. 3 Acceptance test Section 1: Product Overview and Summary A College Catalog is one of

Initech Corp. 1 Acceptance test

Acceptance Test:

College Catalog

Initech Corp

Prepared by:

Evan Drosky Sean Fallon Charles Flood, Team Leader Mike Haddad Gus Weloth

Clients:

Ms. Kate Zimmerman Programs Administrator, Academic Affairs

Siena College

Mr. Brian Smith College Webmaster

Siena College

Ms. Lisa Veino Academic Affairs

Siena College

April 26, 2005


Table of Contents: Sections: 1: Product Overview and Summary ..……………………………………….3

2: Deliverables ………………………………………………….…..………3

3: External Interfaces ……………………….…………………..………….4 .

4: User Command Summary ………………….………….........................14

5: Testing Requirements…………………………………………………..16

6: Testing Forms …………………………………………………….….....18

7: Source Code File Listing………………………………………………..43 8: How to Use the System…………………………………………………44

9: Environmental Constraints/Specs……………………………………….45

Appendices:

A: Glossary of Terms……………………………………………………..46


Section 1: Product Overview and Summary

A College Catalog is one of the most important resources a perspective student has for looking at a school. The catalog is also very important to current students because it contains vital information about graduation requirements. The catalog is a binding contract for students concerning their academic affairs. The Siena College Catalog is currently compiled using an outdated system that is both labor and paper intensive. Our clients Ms. Kate Zimmerman, Programs Administrator, Academic Affairs, Siena College; and Mr. Brian Smith, College Webmaster, Siena College, have requested the development of a program that puts the College Catalog in a database that will be accessible through a web-based application. Department and school officials will be able to request changes to the catalog that will be submitted to Academic Affairs for review via the application. The purpose of the software is to more efficiently view, and make changes to, the Siena College Catalog. By incorporating a web-based application that accesses a database containing the college catalog, we will be able to automate and replace the current process.

Section 2: Deliverables

Our deliverables include a hard copy and a compact disk containing our acceptance test document. The compact disc will also have our team website (with all of the past documents), project website, and our source listing.


Section 3: External Interfaces Login Page

This is the login screen where the user can enter a user name and password and login the system.


Welcome Page (Level 1)

This is the basic welcome screen that will be different for ever user depending on what level of access you have. (Level 2 Access Shown)


Welcome Page (Level 2)

This is the same welcome screen but for a user that has level 2 access.


Welcome Screen (Level 3)

This is the basic welcome screen for Academic Affairs where they can Add/Edit/Delete users, generate output, manage dates, or just view a list of all the sections.


Edit Catalog

This is the side-by-side text editor that will be used by the users to change the old catalog with information for the next year.


Edit/Add/Delete User

This is the Add/Edit/Delete user page, where the Academic Affairs will have the ability to add, edit, or delete users that will have access to the system.


Generate Output

This is the generate output screen where the user will be able to create a file that will have all of the updated catalog information.


Enter Deadlines Page

This is the manage date screen where Academic Affairs will be able to set dates that parts of the catalog will have to be complete by.


Pre-Edit Screen

This is the history revision page of a file that has not been access or changed by any user yet


Post-Edit Screen

This is the post revision screen where the user can see who was the last person to update the file, what access level they have, and the date that it was modified.


Section 4: User Command Summary Log-In: All users will be supplied with a user name and password to use. Before accessing any of the pages of the College Catalog System, the user will be required to login. After the user’s user name and password is authenticated against our database, they will be brought to a welcome page that will have a list of files that they have access to. If the system does not recognize the user name or password, then an authorization-failed page will be displayed to the user. Department Head & Assistant Dean/Senior Administrators Welcome Screen: This screen will be the same as the Academic Affairs Welcome screen except it will not have the options to edit/add users or generate catalog output. It will have a list of all the College Catalog sections they are allowed to edit. Once again, the list of files also contains an indication of what level of completion the file is in. Clicking on any of these files will bring give you more information about the revision history of that section. Academic Affairs Welcome Screen:

This screen serves as a homepage for the academic affairs officials. It has a list of all the sections in the College Catalog that they can edit. There is also a list of options on the left side where the administrator will be able to view the list of files, edit/add users, generate catalog output, and log out. The list of files also contains an indication of what level of completion the file is in. Clicking on any of these files will bring give you more information about the revision history of that section. Pre-Edit Screen:

This screen will display the catalog section and its revision history. It will list the name of who made changes to that section and when. It will also have a link to a screen where you can edit that section. Edit Catalog Section Screen: This screen will display the catalog section in two text areas that are side by side in the browser. The text area on the left will be a read-only version of the catalog section. This will be the section from the start of the year that does not change. In the right text area will be the editable section. This will be the section that was most recently revised. This text area will allow you to make changes to the catalog section. Once you have made your changes, click the submit button and you will be brought to the Post-Edit screen.


Post-Edit Screen: This screen will be the same screen as the Pre-Edit screen. However, it will be updated with the latest revision information from your change. Edit/Add/Delete User Screen: This screen will only accessible for top Academic Affairs official (in this case Ms. Zimmerman). Here they will have the option to add, edit, or delete users. If they add a user, they will have to supply a username, password, full name, title, access level, section, and sub-section. There will also be a “grant user edit permission” field that will allow that user to edit other users. At the start, Ms. Zimmerman will only have this privilege and it will be up to her discretion as to who else gains this privilege. Generate Output Screen: This screen will have a link that will generate a full college catalog output. Enter Deadlines: This screen allows someone with “grant user edit permissions” to enter deadline dates for level one and level two users. The level one and level two users must submit their changes to their respective sections before the deadline dates, or they will be blocked from entering their changes into the system.


Section 5: Testing Requirements Testing of the software package can be considered one of the most important phases of the development process. Once the project has passed the design stage, it is important to thoroughly test the system in order to correct any design flaws that were previously overlooked. The testing provisions of this system are listed below: The Siena College Catalog interface will be a web-based system that will allow users to make changes to the College Catalog database. We will create this database and get the course information and directory information from the Banner database that is currently used by the Registrar. The users will have to login and then make changes to the section that they have permission to make changes in. The permissions will be defined in the Privileges and Authorization database via a Add/Edit page, which will only be accessible to Ms. Zimmerman or other Academic Affairs officials. This page will display access information for an entered user; from here Ms. Zimmerman will be able to change the users access permissions. When a user logs in, a log will be created that will track the changes made by a user - when and what it was. This is important because we can then see what changes were made by whom and when. Once logged in, the user will be able to view and make changes to their section during the set deadline dates. Ms. Zimmerman will enter certain deadline dates via the web interface. There will be a certain time period for department heads and then school administrators to enter changes. After those deadlines, changes will not be allowed through the web application and must be done through hard copy. This will ensure that changes are made in a timely manner and will create a clear distinction of who should be making changes and when. When changes are complete the old version of that section of the catalog will be viewed side by side with the new version of the catalog. Once all the changes are made, the school administrators will then review the changes and make appropriate changes if necessary. After all changes have been reviewed by Ms. Zimmerman, the whole database with the updated information will be turned into a text file that will be sent out to the publisher.

• • The following will be necessary for Academic Affairs:

1. An online page to login. 2. An online page that displays links for all of the sections in the College Catalog System. 3. A way to navigate between viewing and editing the College Catalog System. 4. Allow Academic Affairs to view newly edited sections, along with the previous versions side-by-side. 5. Allow Academic Affairs to view changes easily by comparing the newly edited section to the pervious section. 6. Allow Academic Affairs to change privileges for all users by interacting with the privileges and authorization database 7. Allow Academic Affairs to enter in deadline dates. 8. Allow Academic Affairs to make the final approval for sections. 9. Allow Academic Affairs to receive a correctly outputted file from the College Catalog System.


10. Allow Academic Affairs to track all changes made by users.

• • The following will be necessary for School Administrators:

1. An online page to login. 2. An online page that displays links for their correct sections in the College Catalog System. 3. A way to navigate between viewing and editing the College Catalog System. 4. Allow School Administrators to view newly edited sections, along with the previous versions side-by-side. 5. Allow School Administrators to view changes easily by comparing the newly edited section to the pervious section. 6. Allow School Administrators to make the final approval for their section.

• • The following will be necessary for Department Heads: 1. An online page to login. 2. An online page that displays links for their correct sections in the College Catalog System. 3. A way to navigate between viewing and editing the College Catalog System. 4. Allow Department Heads to view newly edited sections, along with the previous versions side-by-side. 5. Allow Department Heads to view changes easily by comparing the newly edited section to the pervious section. 6. Allow Department Heads to make the final approval for their section.


Section 6: Testing Forms We are going to test the College Catalog system for the three different types of users (Department Heads, Administers, and Academic Affairs) that are going to be working with the system.


Test One: Login: (Department Heads) This test ensures that the login screen can be viewed using all mainstream web browsers and that the login procedure functions properly.

Event/function Expected Result

Pass/Fail

Comments

1. Welcome page accessible using Microsoft Internet Explorer.

The page displays correctly.

P

Page loads properly.

2. Welcome page accessible using Netscape Navigator.

The page displays correctly

P Page loads properly.

3. Welcome page accessible with FireFox Internet Browser.



4. A valid username and password is entered.

Access is granted to the user.


5. An invalid username and valid password is entered.

An error message is received and access is not granted.

P

Page loads informing user that the username and password entered do not match.

6. A valid username and invalid password is entered.


P


7. An invalid username and invalid password is entered.


P


8. No username is entered and a password is entered.

An error pops up prompting the user to enter a username.

P Error message pops up properly.

9. Username is entered and no password is entered.

An error pops up prompting the user to enter a password.


10. No username and no password are entered.

An error pops up prompting the user to enter a username and password.



Test Two: Welcome Page (Department Heads) This test will ensure that the appropriate information is displayed depending on the user viewing the page. It will also test that the different links and functions specific to this page work properly.

Data Received Expected Result Pass/Fail Comments

1. The correct username and password is received.

The page that corresponds to the Department Head’s username and password is displayed.

P


The Department Head’s name appears the on the top of the screen, welcoming the user.

P All correct fields are displayed.

Links for all of the sections that the department head has access for appear in the web browser.

P Only the sections the dept. head has access toappear.

The approval status for each section appears to the right of its corresponding section.

P

Displayed properly.

The approval status level is displayed at its correct level.

P

Displayed properly.

2. The user clicks on the button to list all of the sections of the catalog.

Links for all of the sections of appear on the page.

P


3. The user clicks on a section of the catalog.

The appropriate page appears in the web browser.

P


4. The user clicks on the buttons on the top of the web page template.

The appropriate Siena College page appears in the user’s browser.

P

Pages load properly.

5. User clicks on ‘logout’ button

User is logged out of the system. P

Logged out.


Test Three: Pre-Edit Screen (Department Heads) This test will ensure that the correct approval status is listed next to the section that you desire to edit.

Event/function Expected Result/Comment Pass/Fail

Comments

1. The page is loaded into the web browser.

The section is listed with the correct status level next to it.


The correct date that the section was edited is listed next to the catalog section.

P Displayed properly.

The faculty member who edited the program is correctly listed next to the correlating date.


2. The user clicks on the section to edit it.

The section is correctly loaded in the text editor inside of the web browser.


3. The user clicks on the ‘logout’ button.

The user is correctly logged out of the system.

P Logged out.


Test Four: Edit Catalog Screen (Department Heads) This test will ensure that the current and the previous versions of the college catalog are displayed side by side and track all changes that the user makes to the old copy.


Comments

1. Edit section screens display The correct section of the catalog is opened for editing.

P Correct section was displayed.

2. Side-by-side view is correct Current section and section to be edited are displayed together.

P Loaded properly.

Two web based text editors open up side by side.

P Loaded properly.

Information from the previous section is loaded into the text editor on the left side of the text editor.

P Loaded properly.

Information from the current section is loaded into the text editor on the right side of the text editor.

P Loaded properly.

3. Save function is called Catalog section is saved as a new file and section status is updated

P Loaded properly.

4. Exit function is called Catalog section is saved, side-by-side view closes and post-change screen is displayed

P Page terminates correctly.

5. Edit view is closed Changes save to database P Changed were saved.

6. User inputs text on left screen.

Text changes but no changes are saved. P No changed are made.

7. User inputs text on right screen.

The text appears on the left side of the screen.

P Text updates.


Test Five: Post Edit Screen (Department Heads) This test will ensure all of the functionality of the post edit screen will be working correctly.


Comments



P Page loaded properly.


P Correct date was shown.


P Correct name was displayed.

The page is updated to reflect the current change.

P Page updated properly.


The section is correctly loaded in the text editors inside of the web browser.




P User logged out.


Testing of School Administrator use case This set of tests will ensure that all of the functionality for users with the School Administrator status will work according to our requirements specification. Test One: log-in: (School Administrators) This test ensures that the login screen can be viewed using all mainstream web browsers and that the login procedure functions properly.

Event/function Expected Result Pass/Fail

Comments



P Page loads properly












P

Page loads informiuser that the username and password entered dnot match.



P




P




P Error message popsup properly.








Test Two: Welcome Page (School Administrators) This test will ensure that the appropriate information is displayed depending on the user viewing the page. It will also test that the different links and functions specific to this page work properly.

Data Received Expected Result Pass/Fail

Comments


The page that corresponds to the School Administrator’s username and password is displayed.

P


The School Administrator’s name appears the on the top of the screen, welcoming the user.





P

Displayed properly.




Links for all of the sections of appear on the page.







P Pages load properly.

5. User clicks on ‘logout’ button User is logged out of the system. P Logged out.


Test Three: Pre-Edit Screen (School Administrators) This test will ensure that the correct approval status is listed next to the section that you desire to edit.


Comments













P Logged out.


Test Four: Edit Catalog Screen (School Administrators) This test will ensure that the current and the previous versions of the college catalog are displayed side by side and track all changes that the user makes to the old copy.


Comments




P Loaded properly.


P Loaded properly.


P Loaded properly.


P Loaded properly.


P Loaded properly.





Text changes but no changes are saved. P No changed are made.



P Text updates.


Test Five: Post Edit Screen (School Administrators) This test will ensure all of the functionality of the post edit screen will be working correctly.

T


Comments















P User logged out.


est One: Log-in (Academic Affairs) Test to verify login procedure of software. This test will ensure that the entered username and password are authenticated by the database before allowing access into College Catalog System.

Event/function Expected Result Pass/Fail

Comments



P

Page loads properly


The page displays correctly P Page loads properly


The page displays correctly P Page loads properly






P

Page loads informinuser that the username and password entered donot match.



P




P












Test Two: Welcome Page (Academic Affairs) This test will ensure that the appropriate information is displayed depending on the user viewing the page. It will also test that the different links and functions specific to this page work properly.


Comments


The page that corresponds to the Department Head’s username and password is displayed.

P


The Department Head’s name appears the on the top of the screen, welcoming the user.







P

Displayed properly.


Links for all of the sections of appear on the page, in the order that they appear in the catalog.

P


3. The user clicks on the button to add, edit, or delete users.

The add/edit/delete users page is loaded. P Page loads properly.

3. The user clicks on the Generate Output button.

The correct page that allows the user to generate the final version of the catalog appears in the web browser.


4. The user clicks on the Manage Dates button.

The correct page that allows the user to Manage Dates appears in the browser.




P




P Pages load properly.

5. User clicks on ‘logout’ button User is logged out of the system. P Logged out.


Test Three: Edit/Add/Delete Users (Academic Affairs)This test will be broken up into three different parts: Add User, Edit User, and Delete User. Add User: This test will ensure that the user will be able to add a user to the College Catalog.


Comments

1. The user clicks on the enter username text box.

The user is allowed in enter text into the text box.

P

Text box works.

2. The user clicks on the enter user password text box.


P Text box works.

3. The user clicks on the confirm password text box.


P Text box works.

4. The user clicks on the full name text box. The user is allowed in enter text into the text box.

P Text box works.

5. The user clicks on the title drop down box. The user is allowed to select the appropriate level for the faculty member.

P

Drop down menu works.

The correct access level is selected by the College Catalog system that corresponds with the selected title.

P

Access level is set correctly.

If Academic Affairs is selected then the section and subsection drop down boxes are grayed out.

P

Boxes are not selectable.

6. The user clicks on the section drop down box.

The user is allowed to select the appropriate section for the faculty member.

P Drop down menu works.

If the school of Science, Liberal Arts, or Business is selected then the sub-section drop down box can now be selected, otherwise, it is grayed out.

P Works as it should.


Add User Continued:


Comments

7. The user clicks on the sub-section drop down box.

The user is allowed to select the appropriate sub-section for the faculty member.

P

Drop down menu works.

8. The user clicks on the grant user edit permission drop down box.

The user is allowed to give the faculty member permission to edit/add/delete users.

P Drop down menu works.

9. The user clicks on the update button. The information the user has entered for the faculty member is correctly added to the College Catalog system.

P Information is updated properly.

10. The user clicks on the clear button All of the fields on the web page are reset to null.

P All fields are cleared.

11. The user clicks on the logout button User is logged out of the system.

P

User is logged out.

12. The user clicks on the list of sections button The correct page that lists all of the sections of the catalog appears in the web browser.

P


13. The user clicks on the Generate Output button. The correct page that allows the user to generate the final version of the catalog appears in the web browser.

P


14. The user clicks on the Manage Dates button. The correct page that allows the user to Manage Dates appears in the browser.


15. The user clicks on the Edit/Add user button. The correct page that allows the user to edit/add users in the system appears in the web browser.



Edit User: This test will ensure that the user will be able to edit a user that is already in the College Catalog System.


Commen

1. The user clicks on a user’s name to edit their information

The user’s username appears in the username text box.

P

Name appeacorrectly.

The user’s password appears in the password text box.

P Password appears correctly.

The user’s password appears in the confirm password text box.

P Password matches.

The user’s full name appears in the full name text box.

P Name appeacorrectly.

The user’s title is correctly loaded in the drop down box.

P

All fields displayed properly.

The user’s access level is correctly loaded in the drop down box.

P

All fields displayed properly.

If applicable, the user’s section is loaded into the drop down box.

P

Section loadwhen its suppose to.

If applicable, the user’s sub-section is loaded into the drop down box.

P Sub-section loads when applicable.

The user’s edit/add user ability is correctly loaded up in the drop down box.

P All fields displayed properly.


Edit User Continued:


Comments

2. The user clicks on the enter username text box.


P

Text box works properly.

3. The user clicks on the enter user password text box.


P Text box works properly.

4. The user clicks on the confirm password text box.



5. The user clicks on the full name text box. The user is allowed in enter text into the text box.


6. The user clicks on the title drop down box. The user is allowed to select the appropriate level for the faculty member.

P

The drop down menu works correctly.

The correct access level is selected by the College Catalog system that corresponds with the selected title.

P

Access level is set correctly.

If Academic Affairs is selected then the section and subsection drop down boxes are grayed out.

P

Box is Grayed out.

7. The user clicks on the section drop down box.

The user is allowed to select the appropriate section for the faculty member.

P The drop down menu works correctly.

If the school of Science, Liberal Arts, or Business is selected then the sub-section drop down box is now enable to be selected, otherwise, it is grayed out.



Edit User Continued:


Comments

8. The user clicks on the sub-section drop down box.

The user is allowed to select the appropriate sub-section for the faculty member.

P

The drop down menu works correctly.

9. The user clicks on the grant user edit permissions drop down box.

The user is allowed to give the faculty member permission to edit/add/delete users.


10. The user clicks on the update button. The information the user has entered for the faculty member is correctly added to the College Catalog system.

P Information is updated correctly.

11. The user clicks on the clear button All of the fields on the web page are reset to null.

P All fields are reset.

12. The user clicks on the logout button User is logged out of the system.

P

User is logged out.

13. The user clicks on the list of sections button The correct page that lists all of the sections of the catalog appears in the web browser.

P


14. The user clicks on the generate output button. The correct page that allows the user to generate the final version of the catalog appears in the web browser.

P


15. The user clicks on the Manage Dates button. The correct page that allows the user to Manage Dates appears in the browser.


16. The user clicks on the Edit/Add user button. The correct page that allows the user to edit/add users in the system appears in the web browser.



Delete User: This test will ensure that the user will be able to delete a user that is already in the College Catalog System.


Commen

1. The user clicks on a user’s name to delete their information

The user’s username appears in the username text box.

P

Text box is displayed properly.

The user’s password appears in the password text box.

P Text box is displayed properly.

The user’s password appears in the confirm password text box.


The user’s full name appears in the full name text box.


The user’s title is correctly loaded in the drop down box.

P


The user’s access level is correctly loaded in the drop down box.

P


If applicable, the user’s section is loaded into the drop down box.

P


If applicable, the user’s sub-section is loaded into the drop down box.


The user’s edit/add user ability is correctly loaded up in the drop down box.


2. The user tries to enter text or select a value in a drop down box.

The user is unable to change any of the information.

P No info coube entered.

3. The user clicks on the update button. The user is correctly removed from the College Catalog System

P The user is deleted.


Test Four: Pre-Edit Screen (Academic Affairs) This test will ensure that the correct approval status is listed next to the section that you desire to edit.


Comments











3. The user clicks on the log out button.


P Logged out.


Test Five: Edit Catalog Screen (Academic Affairs) This test will ensure that the current and the previous versions of the college catalog are displayed side by side and track all changes that the user makes to the old copy.


Comments




P Loaded properly.


P Loaded properly.


P Loaded properly.


P Loaded properly.


P Loaded properly.





The user is unable to edit the text. P No changed are made.



P Text updates.


Test Six: Post Edit Screen (Academic Affairs) This test will ensure all of the functionality of the post edit screen will be working correctly.


Comments













3. The user clicks on the log out button.


P User logged out.


Test Seven: Generate Output (Academic Affairs) This test will ensure that Academic Affairs will be able to compile all of the College Catalog information into one file.

Test Eight: Manage Dates (Academic Affairs)


Comments

1. The user clicks on generate output link.

The generate output page is correctly loaded in the web browser.

P New window appears with the College Catalog outputted on it.

2. The user clicks on the link to generate a full College Catalog file.

The complete College Catalog is compiled in corrected order and the file will be saved on the users’ computer.

P New window appears with the College Catalog outputted on it.


This test will ensure that Academic Affairs will be able to set cut off dates for level 1 and level 2 access to edit the catalog.


Comments

1. The user can select the level and dates to terminate access for selected level.

The users level is displayed and the correct deadline date is displayed.

P All fields display properly.


The next set of tests will be devoted to testing the database to ensure that information is saved and retrieved correctly. Test One: Banner Database This test will ensure that information from the Banner database is retrieved correctly.

Test Two: College Catalog Database This test will ensure that information from the Banner database is retrieved correctly.


Comments

1. Banner information is accessed from the College Catalog system.

The information is correctly retrieved from the banner database.

P The directory was correctly gathered.

2. The user tries to change the information in the banner database.

The user is unable to change the data.

P Its not possible for the user to change the database.

3. The user compiles all of the catalog information.

The user is able to get all information vital to the College Catalog from banner.

P User can access all information necessary.


Comments

1. The user retrieves information from the database.

The information is correctly retrieved from the College Catalog database.

P The directory was correctly gathered.

2. The user saves new data into the database.

The data is correctly updated into the correct tables.

P Data is correctly updated.

3. The user compiles all of the catalog information.

The user is able to get all information vital to the College Catalog from College Catalog database.

P Compiled correctly.


Section 7: Source Code Listing: The source code files that were used to create the College Catalog System are on Oraserv, under the file directory - /home/csis4100405/Initech/public_html/. The files that are used in the system are listed below:

- ccEditAddUsers.php - ccEditSection.php - ccFullOutput.php - ccGenerateOutput.php - ccLogInVerify.php - ccLogOut.php - ccManageDates.php - ccSectionInfo.php - ccUpdateDates.php - ccUpdateSectionChanges.php - ccUpdateUsers.php - ccWelcome.php


Section 8: How to Guide

1. At the Login Screen enter your user name and password and the click Log-in or just press enter.

2. On the left side of the screen there is list of Links. These Links include List of Sections, Add/Edit/Delete Users, Generate Output, Manage Dates, and Logout. All of these options are only available for users with Level 3 access (Academic Affairs), all other levels have List of Sections and Logout only.

3. In the main body of this page there is a list of all College Catalog sections that you will have access to. The number of files you have access to is according to your access level (1, 2, or 3) and what school you belong to.

4. Once you click on a section of the catalog a page loads with the revision history of this section and the option to click and edit that section.

5. If you click edit section link you are brought to a page that has two windows side by side. The window on the left is a read only file with the last year’s version of the file. The window on the right is where you can make changes to that section. You can click in the window and then just type anything you want. Then click submit changes or cancel.

6. Once you submit you changes you are brought back one page and your user name, level of access, and time/date is displayed showing that your changes have been accepted.

7. If you click on Add/Edit/Delete User link you are brought to page where you can change a lot of different options for each user.

8. First you have to choose if you want to add, edit, or delete a user. Then you can fill in or edit information for any user in the system. When finished click on update and all your updates will be saved.

9. The Generate Output link brings you to a page where you can click on a link and create the whole catalog into a text file that can be sent to the publisher.

10. The last link is the Logout link where you are instantly logged out of the system and brought back to the main login page.


Section 9: Environmental Constraints/Specs: Our College Catalog System was created using Oracle 9i to create our database on an Apache server, Dreamweaver, and PHP 4.1.2 to create the web pages. We also used the Windows XP (service pack 2) as an operating system. Our system will run on Windows XP, Windows 2000, Mac OS X, Internet explorer (ver. - 6.0.2800.1106), Firefox, and Netscape (ver 7.1).


Appendix A: Glossary of Terms

Code: A system of symbols and rules used to represent instructions to a computer. Database: A collection of data arranged for ease and speed of search and retrieval. Gantt Chart: A chart that depicts progress in relation to time, often used in planning and tracking a project. GUI - (Graphical user interface) An interface, which uses text boxes and buttons to allow easy access of information by use of a mouse or other pointing device. HTML (HyperText Markup Language): A markup language used to structure text and multimedia documents and to set up hypertext links between documents, used extensively on the World Wide Web. Internet: An interconnected system of networks that connect computers around the world via the TCP/IP protocol. Linear Sequential Model – Classic Waterfall Model: A systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing, and support.

Oracle – Oracle is best known for its database management systems and software. They are the world's leading supplier of information management software.

PHP (PHP: Hypertext PreProcessor) (Recursive Acronym): A server-side, cross-platform, HTML-embedded scripting language used to create dynamic web pages. PHP is Open Source software. Software - Written programs or procedures or rules and associated documentation pertaining to the operation of a computer system and that are stored in read/write memory.

Documents

Acceptance Test: College Catalogoraserv.cs.siena.edu/~perm_initech/docapr.pdf · Initech Corp. 3 Acceptance test Section 1: Product Overview and Summary A College Catalog is one of