Automatic Emails

 

 

Dear *USERNAME*,

 

            You have just updated your Contact Information.  This email serves as a

confirmation of the update.  The internship coordinator will be notified immediately.

 

 

 

Dear Internship Coordinator,

 

            Worksite *insert name* has just updated their contact information for review. 

This email serves as a confirmation of the update.

 

 

To view the new contact information, click the hyperlink below:

*INSERT HYPERLINK*

 

 

 

Dear Internship Coordinator,

 

            Student *insert name* has just submitted an intern application for review. 

This email serves as a confirmation of the submission.

 

 

To view the new submission, click the hyperlink below:

*INSERT HYPERLINK*

 

 

 

 

Dear Internship Coordinator,

 

            Student *insert name* has just submitted an internship evaluation for review. 

This email serves as a confirmation of the submission.

 

 

To view the new submission, click the hyperlink below:

*INSERT HYPERLINK*

 

 

 

Dear Internship Coordinator,

 

            A new student has just registered with system.  This email serves as a

confirmation of the update.

 

 

To view the new user, click the hyperlink below:

*INSERT HYPERLINK*

 

 

 

Dear Internship Coordinator,

 

            A new Worksite has just registered with system.  This email serves as a

confirmation of the update.

 

 

To view the new user, click the hyperlink below:

*INSERT HYPERLINK*

 

 

 

Dear Internship Coordinator,

 

            Worksite *insert name* has just submitted a Project Proposal for review. 

This email serves as a confirmation of the submission.

 

 

To view the new submission, click the hyperlink below:

*INSERT HYPERLINK*

 

 

 

 

Dear *USERNAME*,

 

            Thank you for your Intern Application submission.  This email serves as your

confirmation of completion.  The internship coordinator will be notified immediately.

 

 

 

Dear *USERNAME*,

 

            Thank you for your Project Proposal submission.  This email serves as your

confirmation of completion.  The internship coordinator will be notified immediately.

 

 

 

 

Dear *USERNAME*,

 

            Thank you for registering with the Siena College Internship Program

Application system.  This email serves as your confirmation of registration. 

The internship coordinator will be notified immediately.  You may now begin your

 process of applying for an internship.

 

Username:

 

Password:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Email Flow:

 

Intern Application

 

  1. Email from SCIPAnet to Intern               *Submission verification
  2. Email from SCIPAnet to Coordinator  *Notification of submission

 

Site Evaluation by Intern

 

  1. Email from SCIPAnet to Intern               *Submission Verification
  2. Email from SCIPAnet to Coordinator   *Notification of submission

 

Site Project Proposal

 

  1. Email from SCIPAnet to Site                  *Submission Verification
  2. Email from SCIPAnet to Coordinator  *Notification of submission

 

Site Intern Evaluation

 

  1. Email from SCIPAnet to Site                  * Submission Verification
  2. Email from SCIPAnet to Coordinator   *Notification of submission

 

Forgotten Password

 

  1. Email from SCIPAnet to Site                  * Verification with attached password
  2. Email from SCIPAnet to Site                  * Denied verification with attached error
  3. Email from SCIPAnet to Intern   * Verification with attached password
  4. Email from SCIPAnet to Intern   * Denied verification with attached error
  5. Email from SCIPAnet to Coordinator  * Verification with attached password
  6. Email from SCIPAnet to Coordinator  * Denied verification with attached error

 

 

 

 

 

 

 

 

 

 

 

Proposed Company Database Record Fields

 

 

 

 

Proposed Student Database Record Fields

 

 

 

 

Proposed Database Field Structure

 

 

            The previous fields and example database structure offer a preview of the types of data fields that will be needed to correctly run the information system correctly.  The most important field is that of the key field.  This field is a unique field which olds a unique number for each student and company.  With this unique field we will be able to give multiple instances for companies and students as well as give each record its own unique identity for query purposes.

 

            The other field names are very verbose and explain themselves briefly while also complying in the naming scheme for oracle.  These other fields are necessary for holding such information such as company and student names, addresses, phone numbers, etc.

 

   These fields are not set in stone and will be discussed with the client and changed before the final structure is determined.  We will be able to add and or change as many fields as necessary to satisfy the client.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


 

Testing Requirements                                                                     .

 

            Testing will be broken down into 3 phases:

Phase I: Integration Testing:

 

            During initial system development the various functionalities will be programmed and tested separately as modules.  The growing system must then be tested as the modules are assembled.  During the integration of the different modules testing will be done using a bottom-up approach.  This means that modules will be built with similar modules to form clusters which will then be tested extensively.  The process will iterate until the entire system is built.  Using this form of testing will help to reduce the number of driver and stub programs that must be created and help to reduce overall testing time significantly.

 

Phase II: Validation Testing:

           

            Validation testing will be done almost exclusively by the software engineering team due to time constraints.  Validation testing endeavors to show that the requirements have been met.  During limited Alpha testing the Coordinator will be asked to test out coordinator functionality.  Student and work-site functionality will most likely not be given any alpha or beta testing at this time.  Since this subset of overall users is exceptionally large and diverse it is not in best interest of the development to ask all of these users to participate in alpha testing.  The main functionality of these different uses cases will be tested by the coordinator during basic alpha testing.  The main list of validations that have been compiled to date follow:

 

Student:

  • Successfully create accounts
  • Login
  • Fill out all forms and have them stored in a permanent fashion in the database
  • Be able to retrieve and update the previously mentioned forms at any time
  • Communicate effectively with the system from a variety of platforms/browsers
  • Maintain an ease of use that requires minimum help for navigation

 

Worksite:

  • Successfully create accounts.
  • Login
  • Fill out all forms and have them stored in a permanent fashion in the database
  • Be able to retrieve and update the previously mentioned forms at any time
  • Maintain strict confidentiality
  • Communicate effectively with the system from a variety of platforms/browsers
  •  Maintain an ease of use that requires minimum help for navigation

 

Coordinator:

  • View records of all students and worksite currently registered
  • Have various reports generated and readily displayed
  • Use Matcher and Synopsizer software to match potential interns to worksites to fulfill their needs
  • Perform multiple administrative functions that maintain the underlying database from a web interface, i.e. deleting users, modifying passwords and looking at personal information about users.
  • Send Emails to groups or individuals within the different use cases
  • Allow easy and efficient maintenance of the web pages and informational forms.

 

 

Phase III: System Testing:

           

            System testing will also be limited by time constraints.  Security testing will be kept to a minimum as the issue only applies generally to the worksite and coordinator use cases.  These portions of the program have the most potential for abuse, as the information gained here is of a confidential matter.  Performance testing will be more extensively done then system testing.  Of primary concern is maintaining a fast system, one that is easily and quickly viewable from multiple platforms and browsers, and ensuring internet connectivity.  We must not assume that all people who are using the system are using a high-speed connection or are accessing it over the intra-net.  Special detail must be paid to low-speed connections.  The loading times on pages must be bearable for these people as well.  Of further consideration is ADA compliance.  Making the website viewable by the visually impaired is of key importance.

 

 

 

Design Inventory                                                                             .

 

  1. Ensure that nobody can connect to or manipulate the database.
  2. Tables in the database must hold all the information necessary for the internship program to properly function.
  3. Database must be efficiently designed, with minimal, if any, redundancies.
  4. Website must neatly format the data extracted and display it in a manner conducive to easy use and navigation.
  5. All displayed links are operational, bring the user to the correct destination, and complete the action they are supposed to do.
  6. Data input by the user must be verified for correctness and changed if incorrect before it is sent to the database.
  7. Ensure that certain user-sensitive data can only be viewed by the intended user and not others.
  8. Email messaging system is properly functional and sends emails to only those that satisfy specified conditions.
  9. Data previously stored can be updated by users via the webpage.
  10. All buttons, drop-down menus, and forms are correctly labeled, and are selectable providing certain requirements are met.