Create real-world project “Test Plan” as final documentation.
Important: DO NOT create an essay or long description but use maximum content from project deliverables and documentation.
Don't use plagiarized sources. Get Your Custom Essay on
“TEST Plan” for real project using “test plan template”, “documenation” and “Project Deliverable”.
Just from $13/Page
1. test plan template
2. detail documentation
3. Project Deliverables.
CMS XLC
Appendix D: Approvals
2
>
Student Management Program System
User Documentation and Tutorials
Version
1
.
0
02/2
3
/2020
Table of Contents
1.
Introduction
1
2.
Overview
2
3.
Getting Started
3
3.1
Set-up Considerations
3
3.2
User Access Considerations
3
3.3
Accessing the System
4
3.4
System Organization & Navigation
4
3.
5
The system datastore is up-to-date and on-line. Exiting the System
5
4.
Using the System
6
5.
Troubleshooting &
Support
7
5.1
Error Messages
7
5.2
Support
7
Appendix A: Record of Changes
8
Appendix B: Acronyms
9
Appendix C: Glossary
10
Appendix D: Referenced Documents
11
Appendix E: Approvals
12
Appendix F: Additional Appendices
13
Appendix G: Notes to the Author/Template Instructions
14
Appendix H: XLC Template Revision History
15
List of Tables
Table 1 – Support Points of Contact
7
Table 2 – Record of Changes
8
Table 3 – Acronyms
9
Table 4 – Referenced Documents
10
Table 5 – Approvals
11
CMS XLC Table of Contents
UM Version X.X iii
Introduction
This project Student Management Program System has been designed to efficiently manage student and program data, that will provide data management capabilities and analysis needed for student advising and tracking. This document is designed to help the user to understand the how the system works and the way it could be operated.
Overview
The main functionality of the System includes the following:
·
Input, select specific academic programs and general education requirements specific to each program, and process student data
· Provide immediate access to student and program information
· Capture student program and advising data through tracking for review, analysis, and making advising and program decisions
· Integrate student email functions
·
Produce reports on specific program enrollment, student program progress, new or current students, students taking remedial courses.
Getting Started
This system is designed to help the students in the following areas:
1.
Student Enrollment
2. Student re-enrollment/edit the existing information
3. Student data management
4. Accessing the programs
5. Maintain real-time data
6. Generate Customized reports
Set-up Considerations
Student Management Program System screens are designed to be viewed at a minimum screen resolution of 800 x 600. To optimize your access to the SMPS:
Please disable pop-up blockers prior to attempting access to the SMPS.
Use Google Chrome or Firefox.
This application server will support Windows, Linux, and Mac client operating system.
User Access Considerations
1. System Administrator Registration: System Administrator will be able to register in the System by entering the First name, Last name and authenticating by entering the SSN and date of birth details.
2. Student Registration: Once System admin registers the students in the system and generates the Student ID, student should be able to register online by entering the student email Id and student ID provided by the administrator.
3. Student will be able to setup their own password while registering in the SMPS for the first time.
Accessing the System
Student Access:
1. Once the Student Id is generated by the System Administrator students will receive the Student ID and email id via mail.
2. Using the Student Id and the email Id, students will be able to register online and create their own password.
3. Once they login they should be able to access the SMPS dashboard.
System Organization & Navigation
System Administrator:
1.
Once the System Administrator is able to login, identity is authenticated by answering the questions, last four of SSN and date of birth.
2. The SA has necessary training and credentials on file to understand how to setup email services, alerts, setup the program details, enroll and update student information.
Students:
1. Once student is able to login to the system should be able to enroll in the programs of their interest by navigating to their course work page.
2. They can either add the courses or drop the course from the programs page.
3. Students can also check the financial dues and payments from their payments page.
4. Should be able to generate the custom reports. It could be weekly, monthly, quarterly or yearly reports.
5. Should be able to email the reports for SMPS.
The system datastore is up-to-date and on-line. Exiting the System
Should click on the sign out button on the right corner of the dashboard to securely sign out of the system.
Using the System
System Administrator:
1.
Once academic year starts and curriculum available, admin will be able to add Program according to curriculum requirement by navigating to the system admin page.
2. Admin can adjust the existing program by opening the program and clicking on the edit button.
3. Admin has the privileges to drop the program by selecting the inactive button next to the program name.
4. From the enrollment page, admin will be able to either enroll or drop the students from the program.
5. Admin can update the communication plan by accessing the communication tab.
Student:
1. From the dashboard should can view all the courses by selecting the year, term and the major degree.
2. Once the program is selected student will be able to view all the course details, deadlines and other important information related to the course.
3. Based on their program of study students will be able to enroll in the programs of their interest.
4. Once they are enrolled, they would get the enrollment confirmation email.
5. Can drop from the program/course by selecting the manage courses tab.
6. From the reports tab, should be able to generate daily, weekly, monthly or yearly reports.
Troubleshooting & Support
Login issue:
Forgot password: Should be able to recover the password by answering the security questions that were setup during the initial setup phase.
Forgot username: Should email system admin to get the information.
Other Issues: If there is any trouble accessing the system using a particular browser try opening from a different browser. If the issues persist should send email to the IT team and system admin.
Error Messages
Error messages that a user may receive should be sent email to System admin and IT team for the resolution.
Support
In case of emergency contact the student help desk from 8am-6pm EST .
Table 1 – Support Points of Contact
Contact
Organization
Phone
Email
Role
Responsibility
Help desk
MSU
xxxx
xxx
Support Admin
Raise IT ticket
CMS XLC Troubleshooting & Support
UM Version X.X 3
Appendix A: Record of Changes
Table 2 – Record of Changes
Version Number
Date
Author/Owner
Description of Change
1.1
02/23/2020
Group 3
Draft
Appendix B: Acronyms
Table 3 – Acronyms
Acronym
Literal Translation
SMPS
Student Management Program System
Appendix C: Referenced Documents
Table 4 – Referenced Documents
Document Name
Architecture Report
Hardware/Software Specific
Physical Process M
Installation Plan
Change Mgmt Plan
Appendix D: Approvals
The undersigned acknowledge that they have reviewed the User Manual and agree with the information presented within this document. Changes to this User Manual will be coordinated with, and approved by, the undersigned, or their designated representatives.
Table 5 – Approvals
Document Approved By
Date Approved
UM Version X.X 13
Test Plan Template:
(Name of the Product)
Prepared by:
(Names of Preparers)
(Date)
TABLE OF CONTENTS
1.0 INTRODUCTION
Tasks
3.0 SCOPE
- Alpha Testing (Unit Testing)
System and Integration Testing
- Performance and Stress Testing
Batch Testing
Automated Regression Testing
Beta Testing
5.0 Hardware Requirements
Workstation
7.0 Test Schedule
8.0 Control Procedures
9.0 Features to Be Tested
10.0 Features Not to Be Tested
11.0 Resources/Roles & Responsibilities
12.0 Schedules
13.0 Significantly Impacted Departments (SIDs)
14.0 Dependencies
15.0 Risks/Assumptions
16.0 Tools
INTRODUCTION
A brief summary of the product being tested. Outline all the functions at a high level.
OBJECTIVES AND TASKS
Objectives
Describe the objectives supported by the Master Test Plan, eg., defining tasks and responsibilities, vehicle for communication, document to be used as a service level agreement, etc.
Tasks
List all tasks identified by this Test Plan, i.e., testing, post-testing, problem reporting, etc.
3.0 SCOPE
General
This section describes what is being tested, such as all the functions of a specific product, its existing interfaces, integration of all functions.
Tactics
List here how you will accomplish the items that you have listed in the “Scope” section. For example, if you have mentioned that you will be testing the existing interfaces, what would be the procedures you would follow to notify the key people to represent their respective areas, as well as allotting time in their schedule for assisting you in accomplishing your activity?
4.0 TESTING STRATEGY
Describe the overall approach to testing. For each major group of features or feature combinations, specify the approach which will ensure that these feature groups are
adequately tested. Specify the major activities, techniques, and tools which are used to test the designated groups of features.
The approach should be described in sufficient detail to permit identification of the major testing tasks and estimation of the time required to do each one.
Unit Testing
Definition:
Specify the minimum degree of comprehensiveness desired. Identify the techniques which will be used to judge the comprehensiveness of the testing effort (for example, determining which statements have been executed at least once). Specify any additional completion criteria (for example, error frequency). The techniques to be used to trace requirements should be specified.
Participants:
List the names of individuals/departments who would be responsible for Unit Testing.
Methodology:
Describe how unit testing will be conducted. Who will write the test scripts for the unit testing, what would be the sequence of events of Unit Testing and how will the testing activity take place?
System and Integration Testing
Definition:
List what is your understanding of System and Integration Testing for your project.
Participants:
Who will be conducting System and Integration Testing on your project? List the individuals that will be responsible for this activity.
Methodology:
Describe how System & Integration testing will be conducted. Who will write the test scripts for the unit testing, what would be sequence of events of System & Integration Testing, and how will the testing activity take place?
Performance and Stress Testing
Definition:
List what is your understanding of Stress Testing for your project.
Participants:
Who will be conducting Stress Testing on your project? List the individuals that will be responsible for this activity.
Methodology:
Describe how Performance & Stress testing will be conducted. Who will write the test scripts for the testing, what would be sequence of events of Performance & Stress Testing, and how will the testing activity take place?
User Acceptance Testing
Definition:
The purpose of acceptance test is to confirm that the system is ready for operational use. During acceptance test, end-users (customers) of the system compare the system to its initial requirements.
Participants:
Who will be responsible for User Acceptance Testing? List the individuals’ names and responsibility.
Methodology:
Describe how the User Acceptance testing will be conducted. Who will write the test scripts for the testing, what would be sequence of events of User Acceptance Testing, and how will the testing activity take place?
Batch Testing
Automated Regression Testing
Definition:
Regression testing is the selective retesting of a system or component to verify that modifications have not caused unintended effects and that the system or component still works as specified in the requirements.
Participants:
Methodology:
4.7 Beta Testing
Participants:
Methodology:
5.0 HARDWARE REQUIREMENTS
Computers
Modems
ENVIRONMENT REQUIREMENTS
Main Frame
Specify both the necessary and desired properties of the test environment. The
specification should contain the physical characteristics of the facilities, including the hardware, the communications and system software, the mode of usage (for example, stand-alone), and any other software or supplies needed to support the test. Also specify the level of security which must be provided for the test facility, system software, and proprietary components such as software, data, and hardware.
Identify special test tools needed. Identify any other testing needs (for example, publications or office space). Identify the source of all needs which are not currently available to your group.
Workstation
7.0 TEST SCHEDULE
Include test milestones identified in the Software Project Schedule as well as all item transmittal events.
Define any additional test milestones needed. Estimate the time required to do each testing task. Specify the schedule for each testing task and test milestone. For each testing resource (that is, facilities, tools, and staff), specify its periods of use.
8.0 CONTROL PROCEDURES
Problem Reporting
Document the procedures to follow when an incident is encountered during the testing process. If a standard form is going to be used, attach a blank copy as an “Appendix” to the Test Plan. In the event you are using an automated incident logging system, write those procedures in this section.
Change Requests
Document the process of modifications to the software. Identify who will sign off on the changes and what would be the criteria for including the changes to the current product. If the changes will affect existing programs, these modules need to be identified.
9.0 FEATURES TO BE TESTED
Identify all software features and combinations of software features that will be tested.
10.0 FEATURES NOT TO BE TESTED
Identify all features and significant combinations of features which will not be tested and the reasons.
11.0 RESOURCES/ROLES & RESPONSIBILITIES
Specify the staff members who are involved in the test project and what their roles are going to be (for example, Mary Brown (User) compile Test Cases for Acceptance Testing). Identify groups responsible for managing, designing, preparing, executing, and resolving the test activities as well as related issues. Also identify groups responsible for providing the test environment. These groups may include developers, testers, operations staff, testing services, etc.
12.0 SCHEDULES
Major Deliverables
Identify the deliverable documents. You can list the following documents:
Test Plan
Test Cases
Test Incident Reports
Test Summary Reports
13.0 SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs)
Department/Business Area Bus. Manager Tester(s)
14.0 DEPENDENCIES
Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadlines.
15.0 RISKS/ASSUMPTIONS
Identify the high-risk assumptions of the test plan. Specify contingency plans for each (for example, delay in delivery of test items might require increased night shift scheduling to meet the delivery date).
16.0 TOOLS
List the Automation tools you are going to use. List also the Bug tracking tool here.
17.0 APPROVALS
Specify the names and titles of all persons who must approve this plan. Provide space for the signatures and dates.
Name (In Capital Letters) Signature Date
1.
2.
3.
4.
End.
Physical Process Model
Context and Level 0-4.1 Data Flow Diagram
I
D:
Level-0
Level-0:
System Administrator Registration
Description:
The System Administrator (SA) will have access to register the student data along with the program information. System Administrator will register all require student information to the system. Each student will have their unique identifier.
Priority:
High
Trigger:
Students require to register their information for enrollment.
Primary Actor:
System Administrator
Preconditions:
Student enrollment
Normal Course:
System Administrator will enter student’s basic information
Alternative Course:
Hard paper or hand-written form base registration
Admin can also take students fingerprint for unique identification.
Postconditions:
Student record management
Main
Success Scenario:
System Administrator should be able to login and view all student information.
System Administrator can register any new student to the system.
System Administrator can update/delete any student program information.
Exceptions:
Unavailability of student, student data or hardware failure
Summary Input
Source
Output
Destination
SA Id
List of Student Ids
Date Range
Course/Program Id
Student registration
Student
Student data
Program Data
System admin
ID:
Level-1
Level 1.1:
Student Record Management
Description:
The System Administrator (SA) will have the authority of student management. It means that The System Administrator (SA) can add new student record, edit existing student record, and delete student record.
Having admin authority to manage records means admin can easily handle student information and can perform add, edit and delete operation on student data. The System Administrator (SA) also have the authority to search student’s enrollment history.
Maintaining latest student information is very important for any institute. This student record management allow admin to achieve this task easily.
Priority:
Medium
Trigger:
Enrollment of new student – add
Modify or correct existing student info – edit
Student left institution – delete
Search student enrollment – search
Primary Actor:
System admin
Preconditions:
Student enrollment, student data management
Normal Course:
· New student enrollment – add student information
· Existing student – edit or correct existing student information
· Discontinue student – delete student data
· Search Student enrollment – search student information
Alternative Course:
· Handle student information in hard paper (in hard pages record book)
Postconditions:
Updated student information available in system
Exceptions:
Unavailability of student, student data or hardware failure
Main
Success Scenario:
When all student’s information is available, system can easily search, add, edit or delete student information.
Summary Input
Source
Output
Destination
Student registration
Student Ids
Course/Program Ids
Student
Student data
System admin
ID:
Level-2
Level 2.1:
Program Record Management
Description:
The System Administrator (SA) will have the authority of Program management. It means that The System Administrator (SA) can add new Program information, edit existing Program record, and delete existing Program record. Having admin authority to manage records means admin can easily handle Program details and can perform add, edit and delete operation on Programs information.
Priority:
Medium
Trigger:
Require adding new Program info – add
Modify or correct existing Program info – edit
Finish of curriculum – delete
Actor:
System Administrator
Preconditions:
Programs information and curriculum details
The System Administrator (SA) identity is authenticated.
The SA has necessary training and credentials on file.
The system can send and receive emails
The system can send and receive alert messages
The SA can view and update the communication method.
The system datastore is up-to-date and on-line.
Normal Course:
Create new Program to meet curriculum
Edit or modify existing Program details
Delete existing Program once curriculum or academic year has been over
Alternative Course:
Handle Program information in hard paper (in hard pages record book)
Postconditions:
Updated Program information available in system
Exceptions:
Unavailability of Program data or curriculum or hardware failure
Main
Success Scenario:
Once academic year starts and curriculum available, admin can add Program according to curriculum requirement.
If it requires to adjust existing Program, admin do have control to perform edit operation as well.
In case of finish subject or curriculum, admin can delete all Programs associate with that subject as well.
Summary: Inputs
Source
Output
Destination
Course/Program Id
SA ID
System admin
Program details data
System Administrator (SA)
ID:
Level-3
Level 3.1:
Communication Management
Description:
The system will be able to integrate and work with other services like alert messages and Email regarding students’ enrollment. The System Administrator (SA) only has the authority to access/ manage communication method.
Priority:
Medium
Trigger:
Requires sending student enrollment information via Email and alert message.
Actor:
System Administrator
Preconditions:
The System Administrator (SA) identity is authenticated.
The SA has necessary training and credentials on file.
The system can send and receive emails
The system can send and receive alert messages
The SA can view and update the communication method.
The system datastore is up-to-date and on-line.
Normal Course:
System will send alert message and email for Student new enrollment to SA.
System will send alert messages and email for enrollment to SA.
The SA can view all communication page/method
Alternative Course:
The student enrollment is very low. But the student submitted sick certificate manually to professor.
The email server is down.
Postconditions:
The system stores all email and alert communication in the database.
The student enrollment is updated and maintain real-time in database.
The student enrollment notification/alert sent to student and SA.
The student enrollment update/modification alert sent to student and SA.
Exceptions:
The system displays message “The enrollment is too low. Please contact professor or principal office.”
The email server is down and system unable to send the email message to student.
System displays alert notification to student for upcoming change in schedule for the course.
The system terminates the use case
Summary: Inputs
Source
Output
Destination
· Enrollment Id
· List of Student Ids
· Email Id
· Course/Program Id
· Application
· Application datastore
· Email
· Alert message
· Student
· Enrollment report
· System Administrator (SA)
· Student
ID:
Level-4
Level 4:
Report Management
Description:
The system will be able to generate an enrollment report on the weekly, monthly and yearly basis of entry/exit entries. The system admin has the authority to generate reports according to the requirements and print the reports.
Priority:
Medium
Trigger:
Requires generate and print enrollment report
System Admin
Actor:
System Administrator
Preconditions:
The System Administrator (SA) identity is authenticated.
The SA has necessary training and credentials on file.
The system can generate enrollment reports
The system can print enrollment reports
The SA can view and update the enrollment report.
The system datastore is up-to-date and on-line.
Normal Course:
System can send weekly, monthly and yearly enrollment report for Student(s).
System can print weekly, monthly and yearly enrollment report for Student(s).
System can retrieve and print report for selected date range.
Alternative Course:
The professor requested student enrollment for specific date range.
Postconditions:
The system stores all student enrollment in the database.
The student enrollment is updated and maintain real-time in database.
Exceptions:
The system displays message “The printer is offline. Please save your report.”
The database is down due to maintenance. System displays “Schedule maintenance message”
The system terminates the use case
Summary: Inputs
Source
Output
Destination
SA ID
Enrollment Id
List of Student Ids
Date Range
Course/Program Id
Application
Application datastore
Student Enrollment report
System Administrator (SA)
Student
Level-0
Level-0
Level-1.0
Level-1.1
Level-2.0
Level-2.1
Level-3.0
Level-3.1
Level-4.0
Level-4.1
