1.3 Scope of the Product

Include a brief narrative here, which describes the product as you intend it to be realized. Use this section to define boundaries and set expectations. (look at SOW)

Please expalin Scope of the Product

This system will help effectively track, manage and communicate with KSU Alumni all the way from the graduation class of 1995 to present. Keeping all KSU Alumni in one centralized location.

1.4 Business Context for the Product Please explain Business Context of Product

This product is required in order to successfully track, manage, and communicate with alumni of Kennesaw State University (KSU). The goal of the SKU Alumni Association is to support KSU through maintaining and building alumni relations. This project will contribute to the vision of the university (found at the end of this section), by assisting with the following goals:

providing employment incentives

fundraising

The vision of Kansas State University is:

Kansas State University will be a world-class comprehensive university recognized for its excellence in education, discovery, innovation, technology, and community engagement at all levels from local to global. The KSU experience will empower the members and graduates of the university community to have the vision, ability, and courage to transform the future.

Why is the product required? How will it contribute to the goals of your institution? This section can be used when requirements are being negotiated, to assess whether a particular change is a good idea. This section also helps readers understand why certain requirements have been included.

Please explain bold text

1.5 Overview of the requirements Document Please explain Overview of the requirements

If your project is small to medium in size, include a summary of the requirements here. This may be a numbered list of the most important requirements. The purpose of this section is to give the reader a general understanding of the requirements and focus attention on the most critical ones. This section may also help point readers to the specific requirements that are of particular interest to them.

Requirements: please explain Requirements

Ability to modify (Add/Remove) Alumni as needed

Send out emails to all recipients and embed Attachments in emails

Ability to Track Alumni from graduation class of 1995-present

Provide the KSU Alumni options to opt-out and be added to mailing listservs

Allow KSU Alumni to be able to communicate back and forth with other Alumni

2.0 General Description Please explain General Description

This section will give the reader an overview of the project, including why it was conceived, what it will do when complete, and the types of people we expect will use it. We also list constraints that were faced during development and assumptions we made about how we would proceed.

This section contains a nontechnical description of the project, usually in narrative form, which may serve to acquaint new reader with the purpose of the project. It also sets the stage for the specific requirement listing which follows.

Alumni software is needed to provide methods of maintaining and building relationships between KSU and KSU alumni.

When complete, the software will Track and manage all KSU Alumni from 1995 to present and allow the Alumni to communicate back and forth with each other.

There are two main user groups of this system. They are KSU Alumni and KSU Alumni Association Alumni Relations Team.

Every feature added in the system must be tested in a specific order before it gets promoted to the production level environment. Starting with Manual testing, Automation testing, and User Acceptance Testing. This will make a time constraint as small features will take a long time to make it to production.

2.1 Product Perspective

This product has been initiated to create a new computer program designed to allow the Kennesaw State University (KSU) Alumni Association to track, manage, and communicate with alumni. The primary stakeholders in this project are:

Kennesaw State University

Kennesaw State University Alumni Association

Diana Rabah, Project Director

State of Georgia

KSU Alumni

UAK, Inc. **These are our last name initials put into our business**

Diana will serve as the project director of this project for KSU Alumni Association, with Mark , Lorir, and Bani serving as project directors representing UAK, Inc.

The beneficiaries of this product will be KSU alumni, the KSU Alumni Association, employers, and Kansas State University.

Why have you chosen to initiate this product? What need does it serve? Who are the primary stakeholders, who is responsible for the project, and who will benefit from the finished product?

2.2 Product Functions Please explain Product Functions

What does your product do? What activities can users perform while using it? List the main functions that you will build into your product here.

2.3 User characteristics Please explain User Characteristics

Who do you expect to use your finished product, and why? What is their technical background, their training or education, their motivation to use it? What obstacles might they encounter, and what you will build into your product here.

KSU Alumni and KSU Alumni Association Alumni Relations team will be using the finished product. There will be end user training available for the system.

2.4 General Constraints Please explain General Constraints

Did you work under any constraints such as platform or development environment? Did you have to make your product compatible with any existing software or other products currently in use?

2.5 Assumptions & Dependencies Please explain Assumptions and Dependencies

In this section, list any assumption you made about your project (for example, did you assume that the finished product would need to be delivered over the internet?) If your project depends on any particular technical infrastructure, or requires administrators or others with specific skills, note that here.

3.0 Specific Requirements Please explain Specific Requiremnts

This section of the document lists specific requirements for name of project. Requirements are divided into the following sections:

1.)User requirements. These are requirements written from the point of view of end users, usually expressed in narrative form.

2.)System requirements. These are detailed specifications describing the functions the system must be capable of doing.

3.)Interface requirements. These are requirements about the user interface, which may be expressed as a list, as a narrative, or as images of screen mock-ups.

3.1 User Requirements User requirements for this system include the customers ability to:

Create a username and password for the system;

Login to the system;

Reset passwords;

Reset usernames;

Connect with IT support for the system;

Create a new alumnus record;

Edit an existing alumnus record;

Remove existing alumnus record;

Code individual alumnus records to be added and removed from mailing lists;

Create and maintain multiple mailing lists of alumni;

Search for individual alumnus records by one or more of the following variables: first name, last name, Social Security Number, date of birth, graduation year, KSU ID number, degree earned, graduation status, donation history, street address, country/state of residence, phone number, e-mail address.

Filter alumnus records one or more of the following variables: first name, last name, Social Security Number, date of birth, graduation year, KSU ID number, degree earned, graduation status, donation history, street address, country/state of residence, phone number, e-mail address.

3.2 System Requirements

List detailed system requirements here. If your system is large, you may wish to break this into several subsections.

3.3 Interface Requirements Please explain

List interface requirements here; or include screen mockups. If you use mockups, be sure to explain major features or function with narrative to avoid confusion or omission of desired features.

3.3.1 User Interfaces Please explain

3.3.1.1 The Home Screen Please explain

The home screen will show the KSU Alumni Association logo.

The home screen will have links to the following screens:

Login Screen

Create New Customer Screen

Catalog Main Screen

First Category Product Screen

Hardware

The home screen will give general information about the company, catalog, help, login (existing customer), new customer and contact information.

3.3.1.2. Login Screen

The login screen will include the KSU logo, hidden login fields for username and password (existing customer), a link to the Create New Customer Screen, and contact information for KSU support (e-mail, phone number).

3.3.1.3 Create New Customer Screen

The Create New Customer Screen will have the following fields to be filled out in order to create a new customer: (1) first name; (2) last name; (3) username; (4) password; and (5) KSU Alumni Association ID Number. The system would require network access approval by a KSU Alumni administrator. The screen will include a link to help.

This screen will allow a new customer to create a login and password.

3.3.1.4 Catalog Main Screen

This screen will list the main categories for products.

3.3.1.4.1 First Category Product Screen

This screen lists the products in the first major category.

3.3.2 Hardware Interfaces

The cloud will be hosting the information, so the hardware requirements to access this program will be internet connectivity, enough free hard drive space to download the program, and enough RAM to run a modern browser.

All necessary hardware interfaces will be provided by the host operating system

3.3.3 Software Interfaces

The system shall be compatible to work on, at a minimum, Microsoft Internet Explorer, Microsoft Edge, Google Chrome, Mozilla Firefox, Apple Safari, and Opera.

The system shall be compatible to work on Internet Explorer or Netscape web browsers.

3.3.4 Communications Interfaces

The system needs to be able to communicate with the bank for verification of funds or credit card information.

4. Appendices

If you wish to append any documents, do so here. You may wish to include some or all of the following:

Personas and scenarios developed for this project

Transcripts of user interviews, observations, or focus groups

Copies of communications which contain user requirements

Original project proposals or other historical documents

List of similar projects or products, with notes about how they differ from yours

A list of requirements, which were wish-listed or marked unfeasible at present.

Original screen mockups, if they are relevant

Please explain every text in Red