Project Name Online Retail Grocery Store website’s software dev.docx

Project Name: Online Retail Grocery Store website’s software
development
Project Sponsor: Blake Andrews
Project Manager: Naga Srinivas Guntupalli
Date
Version
Description
Preparer
01/23/2020
0.1
Initial Draft
Naga
01/25/2020
0.2
All the sections filled with content information
Naga
01/28/2020
0.3
Project charter final review
Naga
Table of Contents
1. Project description and justification
2. Project Objectives
3. Project Scope
3.1 Out-of-Scope:
4. summary milestone Schedule
5. assumptions and constraints
6. Project Success Criteria

7. Key stakeholders
8. Project Charter Approval
Project Charter
Page |2
Project Description and Justification:
The main reason to start project is to make sure that issues
faced by the individuals who cannot travel far to the grocery
stores physically and buy the products which they actually need.
This project is software website development project which is
built in order to bring the grocery items to the customer door so
that customers need not travel to the grocery or individuals
who don’t have car to travel where customer have to book the
cab to reach the store physically. The project is undertaken
because after analysis customers faced issues in purchasing the
products where there is necessity to show up physically at
stores in order to purchase the products that they need. It would
be very tough job for few to handle more number of products at
time and if this project is successful the orders can be made
online and customer need not struggle for carrying grocery or
retail products.
The project is prestigious to the organization where it is
considering the issues of customers who are in need of grocery
or retail products where the customer’s homes are far from the
retail grocery store, individual who have transportation issues
and individual who don’t have time or cannot give time to visit
the grocery stores physically. By considering all the issues, the
organization has got a chance to take an advantage of this
opportunity through building a new software website
application so that the customers can purchase the products
through online ordering which are needed and the organization

can make profits once the project is successfully completed.
The organization will provide employment opportunity for
giving further technical assistance to the customers.
The business value where this project can bring to sponsors and
stakeholder would be profits in terms of return on investment
once the website application goes live or launched the
customers as online users will dramatically increase a lot which
good for organization. Stakeholders will be benefited by adding
value in terms of delivery of products with no travel and also
good value to the individuals in terms of employment.
Stakeholders include customers, banks and e-commerce who can
benefit from this project. The organization would held
responsible for site management where organization
contribution will be there for generating revenue. Banks can get
benefit from the online purchases made through cash back
offers and transactions made.
Project Objectives
· 1.) The primary most objective is to add value to the
customers and future employees.
· 2.) The secondary is where to add recognition to the product’s
brand with which the online web application is dealing with.
· 3.) The objective is to eliminate the travelling of customers to
the store and get groceries by online ordering where customers
can do comfortably from homes and get the product delivered
on time which makes customers satisfied.
· 4.) The objective is to generate employment for the
individuals who are delivering the grocery products and also to
the individuals who are taking care of customer service by
giving best technical support to the customers so that customers
will not issues in ordering and making payments.

Project Scope
· Gather the project requirements and document those
requirements in the name of functional requirement and
business requirement i.e. BRD and FRD
· Develop the application in such a way that customer should
able to navigate application for selecting the products needed
and making payment successfully.
· The application needs to be tested in all the environments i.e.
development, testing, production and pilot before the
deployment and application goes live where the application is
free from all bugs and errors.
· The online web application should be maintained in a secured
direction where credit/debit information will be safe through
enhanced cyber security or ethical hacking to keep away from
hackers.
· To develop the application the environment set up is necessary
so that application can best tested for its quality assurance
purposes.
· Need signatures for approving the project so that for this
project resources can be added anytime to finish the project.
Out-of-Scope:
· Buy the cars to the individuals who needs to deliver the retail
or grocery products.
· Marketing the retails product’s brand which is dealt by the
website application.
· Provide bonus to individuals who completed this project on
time.

Summary Milestone Schedule:
It is estimated that the project is going to complete in five
phases of the project in total, which includes initiation,
planning, execution, monitoring and closing.
· Project Initiation Phase:
· Exploring ecommerce website built and determining project
resources which are required to initiate and acquiring of
resources. (Start date: January 8th End date: March 3rd)
· Project Planning Phase:
· Development of project charter, resource plan, work plan, on
boarding of resources into the project. Getting the domain name
for the application and gather requirements. (Start date: March
4th End date: April 6th )
· Project Execution Phase:
· Selection of temple which best suites the application as per
the requirement, developing the application as per template and
testing the application in all the environment and deployment
adding the names of the products, payment method setup and
sorting the shipment settings. (Start date: April 7th End date:
July 7th)
· Project Monitoring & Control:
· With the help of web analytics where the total number of
visits and duration can be figured out. (Start date: July 8th End
date: August 8th)
· Project Closing:
· Implementing necessary adjustment and any change requests
from the users as per the application results (Start date: August

9th End date: September 12th)
· Application launch for the users (September 13th)
Summary Milestone Schedule
January- March
April -June
July - September
8th January
2nd Feb
3rd March
6th April
10th May
5th June
7th July
8th August
12th September
Project initiation
Finding the best ecommerce website builder

Determining the resources required for the project.
Determining how the resources will be acquired.
Project planning
Choosing the best plan

Get a domain for the store name
Project execution
Pick the ecommerce template
Customizing the ecommerce template

Adding products
Setting up payment methods
Sorting out the shipping settings

Project monitoring
Using google analytics to measure metrics such as total visits
and visit durations.
Project closure
Making the necessary adjustments based on the results of
google analytics.

Launching the project.
Assumptions, Constraints and Risks:
Assumptions:
· The organization’s management can provide all resources
which are needed for the project completion.
· It is important for the management of the organization to
understand both long and short terms advantages where
allocation of resources needs to be analyzed clearly.
· The employees most probably should get engaged in the
project activities where there is no rule every employee should
play key role in decision making and making necessary
recommendations.

· There would be employees who believe that project may not
end up their roles and responsibilities, for them involvement is
less expected.
· The project should be completed as per the planning i,e,
according to the exact schedule and budget by keeping financial
and managerial activities in the execution phase.
Constraints:
· The project budgeting involves funds which had been
allocated for this project may not be enough for project
completion.
· As far as time constraint is concern, the project duration is 9
months, the individuals who are involved in the project may be
having other roles within the organization where they need to
spend less time on their regular work and focus more on the
project to complete project on time.
· The requirement whether it can functional or non-functional
requirements which includes features which are specific should
make the website unique.
· The compliance constraints includes all the government laws,
rules, act and regulations must be aligned correctly during the
development phase of project.
· The integration constraint includes where the application
needs to have collaboration with various organization’s process
and system as implementation partnership.
Risks:
· Application reliability where there are times when application
has got crashed when more number of users login at same time.
In this scenario errors and session time outs are expected.
· The application may be having online security issues like
spamming, hacking.
· There may deployment issues where the testing is not done
correctly and errors may expected due to data issues and bugs.
· Customers personal information is at risk since customer is
providing his/her card details.

· Chances of hackers getting into the website due to lack of
cyber security execution and site can be accessed easily.
· Insecurity of data may lead to data theft which includes all the
important information which may lead malicious activity by a
certain individual.
Risk Tolerance level
Category
High Tolerance
Medium Tolerance
Low Tolerance
Comments
Schedule
X
The budget issues may cause delay for application going live.
Budgeting issues
X
Budget may not sufficient when resource billing rate is high .
Deployment
X
When deployment is not done correctly users may face errors

and be unsatisfied
Navigation
X
The navigation should be in correct way otherwise customer
may raise and negative feedback on the application.
Project Success Criteria· Total number of users: The data of
information of the users should be collected where it explains
how many people are using the applications and it gives
statistics as per analytics.
· Stakeholders Expectations: The stakeholders include both
external and internal where the project should meet the needs
accordingly as shareholder matrix.
· Quality: The quality should be in good mode where the web
design creation should be attractive.
· Average value of transactions: The average value of
transactions performed on site through debit/credit.
· Navigation: Users must be able to move and use application
their own way where it should not effect the application in any
ways.
· Project success: Project needs to be delivered as per the
schedule and budget.
Key Performance Indicators Measurement

KPI
Rating
Project success
1
Stakeholders Expectations
2
Quality
3
Navigation
4
Average value of transactions
5
Total number of users
6
Key Stakeholders:
External Stakeholders
· Banks: Banking services will be available to make sure
customers can make payment for products and services bought.
· Ecommerce website builder: It will manage the entire process
of website design and customizing the customer preference.
· Government: The organization should acquire the necessary
permit required to develop an ecommerce website.
· Customers: Individuals who will be shopping from the
website.

Internal Stakeholders
Name
Role
Power
Interest
Influence
Responsibility
Expectation
Naga Srinivas
Project Manager
High
High
High
Responsible for reporting the updates on the project
Runs the projects successfully, schedules meeting and
communicates effectively.
Blake Andrews
Project Sponsor
High
High
High
Make sure the budget allotment is done correctly
Monitors the project continuously right from the start till end
James Archer
Business Analyst
Medium
High
Medium

Makes sure the requirements are gathered correctly and identify
the stakeholders through RACI matrix
The requirements are gathered should be correct way
Michael Stones
Lead Developer
Medium
Low
Medium
Develops the entire application correctly makes decision on
deployment in all the environments
Deployment is done correctly as per the FRD and BRD.
Ravindra Kumar
Developer
Low
Medium
Medium
Develops the few features, makes bug fixes and reports to the
project manager
Codes the application correctly
Jessica Stevens
Quality Assurance Analyst
Low
Low
Medium
Makes sure the application is bug free
Does all types of testing and creates bugs wherever the issues
are been found.
Project Charter Approval
Signature Authority
Role
Member
Project Manager
Naga Srinivas Guntupalli

Project Sponsor
Blake Andrews
2
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:
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:
Preconditions:
The system can send and receive emails
The system can send and receive alert messages
The SA can view and update the communication method.

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:
Preconditions:
The system can generate enrollment reports
The system can print enrollment reports
The SA can view and update the enrollment report.
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
Test Plan Template:
(Name of the Product)
Prepared by:
(Names of Preparers)
(Date)
TABLE OF CONTENTS
1.0 INTRODUCTION
OBJECTIVES AND TASKS

Objectives
Tasks
3.0 SCOPE
Testing Strategy
Alpha Testing (Unit Testing)
System and Integration Testing Performance and Stress Testing
User Acceptance Testing
Batch Testing
Automated Regression Testing
Beta Testing
5.0 Hardware Requirements
Environment Requirements
Main Frame
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
Approvals

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.
CMS XLC Appendix D: ApprovalsStudent Management
Program SystemUser Documentation and Tutorials
Version 1.0
02/23/2020
Table of Contents

1.Introduction1
2.Overview2
3.Getting Started3
3.1Set-up Considerations3
3.2User Access Considerations3
3.3Accessing the System4
3.4System Organization & Navigation4
3.5The system datastore is up-to-date and on-line. Exiting the
System5
4.Using the System6
5.Troubleshooting & Support7
5.1Error Messages7
5.2Support7
Appendix A: Record of Changes8
Appendix B: Acronyms9
Appendix C: Glossary10
Appendix D: Referenced Documents11
Appendix E: Approvals12
Appendix F: Additional Appendices13
Appendix G: Notes to the Author/Template Instructions14
Appendix H: XLC Template Revision History15
List of Tables
Table 1 - Support Points of Contact7
Table 2 - Record of Changes8
Table 3 - Acronyms9
Table 4 - Referenced Documents10
Table 5 - Approvals11
CMS XLC Table of Contents
UM Version X.X iii <Project and release
name>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 <Project and release name>
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 <Project and release name>
Sheet1Project GoalBusiness RequirementUser
RequirementSystem RequirementNon-Functional
RequirementsAttributeDesign & developmentProject
CharterProject Scope-High Level (What will the project
provide?)As a user I need…The System shall…Status
select onePriority select oneFeature
select oneDesign SpecTest SpecTest Case(s)Test VerifyModify
Req.The goal of the application is having ability to give access
with the help of credentials. We need a new login pageAs a user
I need login page so that I can enter the user id and password to
get accesThe system shall give access towards toward the
application 1. The application should get opned quickly.
2. The customer credentials should be protective as a security.In

ProcessHighAssignThe goal of the application is selecting the
required products comfortably The application needs a search
bar for typing As as user I need a search bar so that I can enter
required products names by typing.The system should able to
give correct results of the products which has been typed by the
user 1. The name of the products should do spell checks while
entering. In ProcessHighAssignThe goals of the application is
credit/debit card details should be entered for checkout.The
application needs entering the payment method. As a user I need
to enter the credit/debit card details so that I can pay for
selected products The system shall have ability to get access
towards any type of cards such as visa, mastercard, amex. 1.
The application should able to do payment process fastly.
2. The application should able to secure the payment details. In
ProcessLowAssignThe goal of the application is selected retail
grocery products should be delivered to the customer's address
The application should have a address bar for adding. As a user
I need to enter the address details which contains street, city,
state and zip code so that the products or items will be delivered
to home. The system should a text boxes and dropdowns for
entering and selecting. The application should have ability to
do spell checks. In ProcessHighAssignThe goal of the
application is to get the customer feedbackThe application
should have customer experience on the products delivered. As
a user I need to get the customer feedback experience page so
that I can give feedback.The system should have radio buttons
for selecting the stars out of 5 and text boxes for writing. The
application should be quick in getting feedback. In
ProcessMediumAssignNot StartedHighAssign
&"Arial,Italic"&14Requirements Traceability FULL Matrix
&P &F
Sheet2
Sheet3

Project Name Online Retail Grocery Store website’s software dev.docx

Project Name Online Retail Grocery Store website’s software dev.docx

Recommended

Recommended

More Related Content

Similar to Project Name Online Retail Grocery Store website’s software dev.docx

Similar to Project Name Online Retail Grocery Store website’s software dev.docx (20)

More from woodruffeloisa

More from woodruffeloisa (20)

Recently uploaded

Recently uploaded (20)

Project Name Online Retail Grocery Store website’s software dev.docx