Assignment

Instructions

Please see attachment for Supporting Files 

Assignment 1

Classes

Purpose

The purpose of this assignment is to review the IT Online Training Project Requirements and begin the modeling of the requirements by using the noun analysis technique to identify domain classes, attributes, operations, and requirements.

In this assignment we will begin the analysis for a case study, the IT Online Training Project, which will be used for your assignments throughout the course.  You will need to review the IT Online Training Project Requirements 2018R2 document and become familiar with it. 

For the analysis portion of the project, you will use the Analysis Specification Template 2018R4 and fill in sections as the course progresses each week.  The  Analysis Specification Template is a Word file that has predefined sections and you will need to fill them in each week until the specification is completed.  It has instructions also in the document as to how to use it.  It is common practice in systems development to use templates for various types of documents to standardize the documentation and development practices throughout an organization. 

For this assignment, you will complete Section 1 of the Analysis Specification Template 2018 which will come directly from the IT Online Training Project Requirements.  You will also complete Section 4.3 List of Classes with Definitions, Attributes and Requirement Number by creating a list of classes with definitions,  attributes, operations, and requirement number by analyzing the IT Online Training Project Requirements document.

In the Analysis Specification, complete the following Sections:

Sections: 1, 1.1, 1.2, 1.3, 4.3, and 4.3.1.

Instructions

1.  Review the

Quick Resources

at the end of this Assignment.

2.  Review the IT Online Training Project Requirements 2018R2  and the Analysis Specification Template 2018R4 .

3.  Open the Analysis Specification Template and save it as Assignment1FirstNameLastname substituting your name.

4.  Sections 1, 1.1., 1.2, 1.3.  Using the Online Training Project Requirements document, complete Section 1 in the Analysis Specification Template.  Use your own words for Sections 1, 1.1, and 1.2.  You can copy and paste the Sponsor requirements from the case study to the Analysis Specification for Section 1.3.  See the template for details.  Make certain that you retain the requirement numbers as you will use these for traceability.

5.   Review the noun analysis technique which is used to identify potential classes for an application. See the links on

Finding Classes

at the end of this assignment.  The RMB1905 videos use a version of our CASE tool.  The Blaha videos use another CASE tool.  Your focus should be on the technique for analyzing text to discover classes and not the CASE tool at this point.  See the  

ITOT Noun Analysis Example 2018

example before you begin your analysis. It provides an example of noun analysis for your case study.

6.  Using the Online Training Project Requirements document identify and create a list of all potential classes,  definition for each each class, attributes, operations (methods),  and requirement number. Place your list in the Classes, Attributes, Operations(Methods), Requirements table below.  Note that it is already included  for you in the specification. The classes, attributes, and operations are in the Requirements document.  If you do the analysis you will find them.  

For example if you look at REQF2.1 you will find the mention of a Class called Customer with attributes customerId, firstName and lastName, address, WorkPhoneNumber f and cellPhoneNumber.  For operations, your system must be able to create and delete Customer as well as get and set each of the attributes values.  Example:  getCustomerID(), setCustomerID(), getCustomerFirstName(), setCustomerFirstName(), etc. This is salos documented in the Customer-SchecudleCourse-User document below.  Other attributes may be determined later!

The following list provides a starting list of classes which has already been referenced in the course.  You must identify the remaining classes from the Requirements document:

Starting List of Classes

As a result of reading/using the course resources listed below, at least 9 different classes are already identified for you and you should  include them as well as the remaining classes you will discover with  noun analysis of the Requirements document.  

Course Resource

Location in Course

Potential ITOT Classes Identified

ITOT Noun Analysis Example 2018
Assignment 1

Lesson 1

ScheduledCourse, SelfPacedCourse, Course, Product, Video, and Book

Assignment 1
Assignment 1

UserAccount with attributes and operations

Sample UML Class Diagrams for ITOT Classes

Lesson 1

Instructor, Course, and ExpertiseArea classes with detailed attributes and operations.

Assignment 1 Step 6

Assignment 1 Step 6

Customer with attributes and operations.

The following sections provides additional instructions for completing the Classes, Attributes, Operations(Methods), Requirements table.

6.1  Define each class using the phrase “A classname is a ….”  and then complete the definition.  Note that classes are named as nouns or noun phrases and begin with a capital letter.  Make certain that you create the definitions according to the template! You must use the phrase “is a” in your definition.

6.2  For each class, list  its definition, attributes, operations (methods), and Requirement number.  You will find many of the attributes and operations in the Requirements document.

6.3  Use a table format with the class name and its definition as columns like the table in the Customer-SchecudleCourse-User document below.  You should use these examples in your own table. Classes will be easier to locate if you put your table in alphabetical order by class name. 

6.3.1 Class names must be singular (not plural) and must be one word.  You can capitalize the first letter of each word in the name like ScheduledCourse.  See Lesson 1 for additional information about naming classes and their properties.

6.3.2 Attributes are properties of a class like for Customer one attribute would be “customerID”.  Attributes begin with a lowercase letter.

6.3.4 Operations are actions that a class can perform and begin with a lower case letter followed by parentheses ().  If an operation needs a parameter like workPhone, we put the name of the parameter (attribute) inside the parentheses. We can create a new instance of a class (Create), delete an instance of a class (remove), get ( read) values of the attribute, or set (change) values of the attribute.  See the examples in the table below.  The examples below include all of the getter/setter methods for the attributes.  You do not need to include them in this assignment, but for Assignment 2 when you create your class diagram, you can use the features of our CASE to so that the getter/setter methods will automatically be added. For now you can use a high level modify() and read() to represent the getter/setter methods.  Later in design changes will be made depending on the technology used.

Classes, Attributes, Operations(Methods), Requirements (Section 4.3 in your Analysis Specification) Example

For an example of completing the table you can view the document Customer-ScheduledCourse-User Analysis Example . 

It illustrates the result of the analysis of the Customer, ScheduledCourse, and User classes in the requirements document. For each class the attributes, operations (methods), and requirement number were documented.

7.  Section 4.3. Add your completed table of classes, definitions, attributes, and operations.   

8. Section 4.3.1 Discuss your list of classes and why you chose them. You may want to reference the case study document.

 

Submission Instructions

1. Make certain that your name and course number are at the top of your document.

2.  Submit this first version of your Analysis Specification as a Word file and name it as indicated above Assignment1FirstNameLastName. Make certain that all sections are included exactly like the template.

Your assignment will be graded with the following rubric:

 

Rubric for Assignments

Points

Content & Development 50%

50/50

Organization 20%

20/20

Format 10%

10/10

Grammar, Punctuation, & Spelling 15%

15/15

Readability & Style 5%

5/5

Timeliness (late deduction 10 points) Optional

 

Total

100/100

 
Quick Resources

Case Study

1.  IT Online Training Project Requirements 2018R2

2. Analysis Specification Template 2018R4

Finding Classes

1. See this video on how to find classes using the noun technique: RMB1905. (2009, March 9). 4.11_Finding Classes. [Video file]. Retrieved from https://www.youtube.com/watch?v=DYasVJfgyeU&list=PL46FE8B2506D9EE0 C&index=29

2. In your textbook, see the ATM Case Study (see p. 178 Section 11.3.1 in your textbook)  and then read about how to use the noun technique to identify classes for the ATM Case Study on pp. 183-187.

3.  See the  ITOT Noun Analysis Example 2018 example which demonstrates the noun analysis technique for the ITOT case study.

4. See ENTD321 Week 1 Web Resources for videos by one of the authors of your textbook, Michael Blaha on finding classes and class diagrams.  It also contains links to videos on classes and objects using our selected CASE tool.

 

IT Online Training (ITOT) Analysis Specification

with the word “Insert” or “Provide” are explanatory and should be removed from your document after you follow the directions. Other symbols <> require you to insert names.

This document is intended to provide a partial analysis specification for the project case study, IT Online Training. This document includes an introduction, use case diagrams, detailed use cases, activity diagrams, domain class diagrams, and domain state diagram. Parts of this specification will come from the IT Online Training Specification and from your assignments. This document integrates some of the analysis diagrams and project specification details to provide a single reference. Headings are used to provide easier navigation. To see the heading navigation, in Word click on the View tab and check the Navigation Pane box.

You will submit this document for each assignment with new sections completed and added to it. You can revise any previous sections as needed. Remember to insert you name and class information at the top of this document.>

1. Introduction

1.1 Problem Description

1.2 Sponsor Project Description

1.3 Sponsor Requirements

2.

System Use Case Diagram

2.1 System Use Case Diagram

Customer

”.>

2.2 Use Case Diagram Description

2.3 List of Actors and Definitions

“An actorName is a

…

”.

Then add additional details as necessary. Use the following table format.>

Actor Name	Definition
	Customer	A Customer is a person who purchases ITOT products.
	…

2.4 List of Use Cases and Description

…

Use Case Name	Description
Create Customer	This use case creates a new Customer including customer id, first and last name, address, phone numbers for work and cell phone.

3. Detailed Use Case and Activity Diagram

3.1. Use Case

above with the actual name of your use case Manage Shopping Cart Use Case. For example it might read Manage Shopping Cart Use Case.>

3.1.1. Use Case Description/Scenario

above with the actual name of your use case, for example, Manage Shopping Cart Use Case Description/Scenario. In this section insert a description/scenario for this use case.>

3.1.2 Use Case Detailed Steps

.

Use Case and History

Use Case ID:	Use Case Name: Manage Shopping Cart
Created By:	Date Created:	Last Updated By:	Date Last Updated:

Actors, Description, Preconditions, Postconditions

Actors:

Description:

Preconditions:

Postconditions:

Normal Path

	User Action		System Action
1. This use case begins when….(you need to complete the sentence)	2.

Alternative Path

User Action

System Action

Use Case Related System Issues

Exceptions:

Includes:

Priority:

Frequency of Use:

Business Rules:

Special Requirements:

Assumptions:

Notes and Issues:

3.1.3 Form/Screen Mockup and Dialog

above with the actual name of your use case like Manage Shopping Cart so that it reads Manage Shopping Cart Form/Screen Mockup.

Provide a mockup (image) of whatever forms/screens that are used to illustrate the activities in your use case. Include a description of your forms/screens. These should support and illustrate your use case. For example for a Create Customer use case, a Create Customer screen with customer id, first and last name, address, phone numbers for work and cell phone boxes and a Submit Button would be an example of a form or web screen.

Include a discussion of the form including its content (data elements) and how they will be used. Identify the classes has these attributes. Include a dialog (step by step instructions on what happens when this form is used. While these forms/screens will be used in the application, they are also used as a storyboard to explain the user interface to the sponsors of the project. These can be used to create and verify the steps of your detailed use case. >

3.1.4 Activity Diagram Name for Use Case and Discussion

” above with the actual name of your use case like Manage Shopping Cart. For example, Activity Diagram for Use Case Manage Shopping Cart. Insert the following:

1. An activity diagram for your use case

2. A discussion of the activity diagram.

Remember that the detailed use case steps should be reflected in your activity diagram.>

4. Domain Class Diagram

4.1 Domain Class Diagram(s)

< Insert your Domain Class Diagram here. Remember that classes are named with nouns or noun phrases. A domain class diagram includes classes with attributes and operations for each class and named relationships with multiplicity constraints. Associations need names. You do not need a name for generalization, aggregation, and composition relationships. You must have names for associations.

4.2 Class and Relationship Analysis

Class and Relationship Analysis
Class Name 1	Relationship with Multiplicity	Class Name 2
Instructor	An   Instructor teaches zero or more (0..*) Course A Course is taught by  a single (1) Instructor	Course

Then on the class diagram association between Instructor and Course you can name the association “teaches” and add the multiplicity constraints (1) near Instructor and (0..1) near Course.

4.3 List of Classes with Definitions, Attributes, and Operations

I

T Online Training

 Project Requirements 

2018

document. Remember that class names are nouns or noun phrases. To define a class, complete the phrase “A className is a …”. Additional information can then be added. Attributes are properties of a class like “customerID” and begin with a lowercase letter. Operations are actions that a class can perform and begin with a lower case letter followed by parentheses (). We can create a new instance of a class (Create), delete an instance of a class (remove), get ( read) values of the attribute, or set (change) values of the attribute. See the examples in the table below. The examples below include all of the getter/setter methods for the attributes. You do not need to include them in this assignment, but for Assignment 2 when you create your class diagram, you can use the features of our CASE to so that the getter/setter methods will automatically be added. For now you can use a high level modify() and read() to represent the getter/setter methods. Later In design these will be modified depending on the technology used. During analysis we want to be independent of technology as much as possible.>

Classes, Attributes, Operations, Requirement

Customer

…

…

…

…

Class Name	Class Definition	Attributes	Operations	Requirement Number
A Customer is a person or organization where an Account exists for the purpose of accessing ITOT products.	customerID: string firstName: string lastName: string address: string workPhone:string cellPhone: string	createCustomer() getCustomerID() setCustomerID(customerID) getFirstName() setFirstName(firstName) getAddress() setAddress(address) getWorkPhone() setWorkPhone(workPhone) getCellPhone() setCellPhone(cellPhone) removeCustomer(customerID)	REQF2.1
ScheduledCourse	A ScheduledCourse is a course offered by ITOT at a specific date and time.	courseNumber: string title: string description: string type: string duration: number startDate: string endDate: string prerequisites: string ceuCredits: number fee: number	createScheduledCourse() getCourseNumber() setCourseNumber(courseNumber) getTitle() setTitle(title) getDescription() setDescription(description) getType() setType(type) getDuration() setDuration(duration) getStartDate() setStartDate(startDate) getEndDate() setEndDate(endDate) getPrerequisites() setPrerequisites(prrequisites) getCeuCredits() setCeuCredits(ceuCredits) getFee() setFee(fee) RemoveScheduledCourse(courseNumber)	REQF3.1
User	A User is a person who has credentials to access the ITOT system	username:string password: string	login(username, password) logout() getUsername() setUsername(username)	REQF9.1
				…

4.3.1 List of Classes, Attributes, Operations, and Requirement Number Discussion

4.4 Domain Class Diagram Discussion

5. Domain State Diagram

5.1 State Diagram and Discussion

above with the name of the required class ShoppingCart State Diagram so that it reads like ShoppingCart State Diagram and Discussion. See the examples of state diagrams in the assignment. Complete the following:

1. Insert a state diagram for the class from your class diagram as indicated in the assignment.

2. Provide a brief discussion of your State Diagram.>

6. Sequence Diagrams

6.1 System Sequence Diagram (SSD) for Use Case and Description

above with the name of your detailed Use Case like Manage Shopping Cart so that it reads like System Sequence Diagram (SSD) for Manage Shopping Cart Use Case.

1. Insert a description of your SSD.

2. Insert a UML System Sequence Diagram (SSD) for your use case from Section 3 above. An SSD shows the actor and the System and the messages (including message name and parameters) required to implement the detailed use case description from Section 3. The SSD shows the inputs and outputs to/from the system for the use case.>

6.2 Detailed Sequence Diagram for Use Case and Discussion

above with the name of your use case like Manage Shopping Cart so that it reads like Detailed Sequence Diagram for Manage Shopping Cart Use Case and Description.

1. Insert a UML Detailed Sequence Diagram for your use case. A Detailed Sequence diagram shows the actor and instead of the System like in the SSD, it will show all of the objects (instances of classes) that are required to implement the use case. Your Class Diagram will be helpful here. The net messages should be the same as in your SSD above but you will have more detailed messages including message name and parameters among the different objects that are actually required to implement the use case. So now you will add objects across the top of your diagram and omit System. Include a discussion of your Detailed Sequence Diagram.>

2. Insert a discussion of your Detailed Sequence Diagram.

Appendix.

Analysis Specification 2018R2 Page 7

ENTD321 Object Programming and UML

Week 1 Web Resources

Creating Class Diagrams

The following videos by Mike Blaha, one of the authors of your textbook, illustrate the
process and analysis for creating class diagrams. This will be helpful for Assignment 1.

1. Blaha, M. (2011, January 7) UML Class Modeling — 1 — Problem Statement.
Retrieved March 26, 2013 from

=1

2. Blaha, M. (2011, January 7) UML Class Modeling — 2 — Finding Classes. Retrieved

March 26, 2013 from

=2

3. Blaha, M. (2011, January 7) UML Class Modeling — 3 — Finding Associations.

Retrieved March 26, 2013 from http://www.youtube.com/watch?v=Wj-
VhxszdDo&list=PLEE77921A75E846EB

4. Blaha, M. (2011, January 7) UML Class Modeling — 4 — Finding Generalizations.

Retrieved March 26, 2013 from

5. Blaha, M. (2011, January 7) UML Class Modeling — 5 — Refining the Model.

Retrieved March 26, 2013 from

6. Blaha, M. (2011, January 7) UML Class Modeling — 6 — Layout, Attributes,

Operations. Retrieved March 26, 2013 from

7. Blaha, M. (2011, January 7) UML Class Modeling — 7 — Extending the Model.

Retrieved March 26, 2013 from

Optional Web Readings (Recommended)

Class Diagrams
8. Murphy, Mike. (2011, October 7). UML Class Diagrams. Retrieved from

http://www.youtube.com/watch?v=5Q0ZM6ODBHw

Finding Classes

ENTD321 Week 1 Web Resources Page 1

http://www.youtube.com/watch?v=5Q0ZM6ODBHw

9. RMB1905. (2009, March 9). 4.11_Finding Classes. [Video file]. Retrieved
from

C&index=29

Classes and Objects

The following resources provide details on classes and objects including
attributes, operations, associations, multiplicity, aggregation, composition,
generalization, and constraints and notes.

10.RMB1905. (2009, March 9). 4.01_Classifiers Classes & Objects. [Video file].

Retrieved from https://www.youtube.com/watch?v=-
tmNYtAE0B8&index=19&list=PL46FE8B2506D9EE0C

11.RMB1905. (2009, March 10). 4.02_Attributes & Operations. [Video file].
Retrieved from

&index=20

12.RMB1905. (2009, March 10). 4.03_Stereotypes. [Video file]. Retrieved from

2506D9EE0C

13.RMB1905. (2009, March 9). 4.04_Associations & Multiplicity. [Video file].
Retrieved from https://www.youtube.com/watch?v=eDO-okP-
kaU&index=22&list=PL46FE8B2506D9EE0C

14.RMB1905. (2009, March 9). 4.05_Association Classes. [Video file]. Retrieved
from https://www.youtube.com/watch?v=K5-
V3OYThZM&list=PL46FE8B2506D9EE0C&index=23

15.RMB1905. (2009, March 9). 4.06_Aggregation & Composition. [Video file].
Retrieved from

E0C&index=24

16.RMB1905. (2009, March 10). 4.07_Generalization. [Video file]. Retrieved
from

E0C&index=25

17.RMB1905. (2009, March 9). 4.10 Constraints & Notes. [Video file]. Retrieved
from

B2506D9EE0C

ENTD321 Week 1 Web Resources Page 2

ITOTNoun Analysis Example 2018 Page 1

ITOT Noun Analysis Example 2018

The following is an example on how to get started with the identification of
classes for Assignment 1.

1. Pay particular attention to the definitions and note that they follow the
definition template we are using to ensure accurate naming and
identification of the potential class.

2. Note also that the first word of the class name is capitalized and
succeeding words are also capitalized using camel case to form just one
word.

Consider the first sentence of the ID Online Training Requirement
Specification:

IT Online Training needs to develop an online service for IT training
that includes scheduled courses, self-paced courses, and other training
products like videos and books.

The following table lists and discusses the highlighted nouns and noun
phrases from just the first sentence:

Potential
Class

Analysis and
Discussion Class Definition

IT Online
Training

This is actually the
name of the
application we are
developing and is
thus not applicable
for a domain class
of the application.

N/A N/A

Online
service

This is a reference
to the application
we are developing
and is not applicable
for a domain class
of the application.

N/A N/A

IT
training

This is a reference
to an organizational
unit and is also not
applicable for a
domain class of the
application.

N/A N/A

ITOT Noun Analysis Example 2018 Page 2

Potential
Class
Analysis and
Discussion Class Definition

Scheduled
Course

This is a noun
phrase that does
represent a part of
the application that
we will need to
know about and
model.

ScheduledCourse A ScheduledCourse
is a course that is
offered at a given
date and time.

Self-
paced
Course

This is also a noun
phrase that does
represent a part of
the application that
we will need to
know about and
model.

SelfPacedCourse A SelfPacedCourse
is a course that a
customer can take
at their own pace
but has a time
limit on the
number of weeks
the customer can
take it.

Course This is a noun that I
abstracted from the
two classes
discussed earlier
and we will need to
know about it.

Course A course is a
product that
provides
instruction and
ITOT offers for
customers to
purchase.

Training
products

ITOT offers several
products that
Customers can
purchase. We only
need the word
product.

Product A product is an
offering that ITOT
makes available
for Customers to
purchase.

Videos This noun
represents a
product that ITOT
will market to its
customers and we
will need to know
about it for the
application. We will
use the singular
version of the word.

Video A video is a
product that
provides digital
instruction.

Book This noun
represents a

Book A book is a product
that provides

ITOT Noun Analysis Example 2018 Page 3

Potential
Class
Analysis and
Discussion Class Definition

product that ITOT
will market to its
customers and we
will need to know
about it for the
application.

written instruction
on a topic and is
available in printed
or digital format.

So from the first sentence we have identified six classes and have also
provided definitions using a template: ”

A classname is a ….” and then complete the definition.

You supply the class name and the definition. Using this definition technique
can help to identify relationships among the classes as well.

Next week you will create a class diagram using the classes you identified
this week. A domain class diagram has classes with attributes (properties),
operations, and relationships among the classes. You will have to expand
your classes to include these. Later still in the course we will add operations
to the class. We will discuss this more next week.

You might consider thinking about generalization/inheritance relationships.
For example above we can see that we have Course and different types of
courses. Thus we could create a super class Course with subclasses Self-
paced Course and Scheduled Course. We also have Product and types of
products like Course, Video, and Book.

ITOnline Training Requirements Specifications 2018R2 Page 1

IT Online Training (ITOT) Project
Requirement Specification 2018R

Draft

Description

IT Online Training needs to develop an online service for IT training that includes
scheduled courses, self-paced courses, and other training products like
videos and books. The training service will be initially web-based but
the architecture must have the option that different front-ends like
applets, web services, or other designs can be used. The main
function of the training site is to provide IT courses to its customers
over the Internet. The application must cover various areas including
customer management, course management, learning management system access,
scheduling, purchasing through an online shopping cart; user account
management, and payment management. Customers, instructors, course
administrators, schedule administrators, and other administrators must have access
to functions implemented in the system.

Sponsor Requirements

The sponsors of the project have identified some preliminary requirements of the
system as documented below.

The following are some initial requirements of the application.

Functional Requirements

1. Purchase ITOT Products
REQF1.1 Customers must be able to purchase ITOT Products via an online

shopping cart.
REQF1.2 The Customer must be able to add and remove products from an

online shopping cart.
REQF1.3 Customers must be able to cancel orders.
REQF1.4 Customers must be able to purchase by credit card.
REQF1.5 System must provide certificates of completion for customers.

2. Maintain Customer information
REQF2.1 Customers must be able to create and change customer account

which holds information about the Customer including customer id,
first and last name, address, phone numbers for work and cell phone.
Customer id is issued by the system and cannot be changed by the
customer.

IT Online Training Requirements Specifications 2018R2 Page 2

REQF2.2 The system must be able to store and maintain customer credit
card information for each credit card including account number,
account name, expiration date, and security code.

REQF2.3 The system must maintain a list of accounts in its central database.
REQF2.4 The system must be able to search and display customer

information by instructors, course administrators, schedule
administrators, and other administrators.

3. Maintain Products
REQF3.1 The system must be able to create, modify, and delete ITOT

Products including scheduled courses, self-paced courses, videos, and
books.

REQF3.2 The system must be able to maintain course information including
course number, course title, course description, course type, course
duration, course start date, course end date, course prerequisites, CEU
credits, and course fee.

REQF3.3 The system must be able to maintain video information including
video id, video name, and video fee.

REQF3.4 The system must be able to maintain book information including
title, authors, date, edition, and ISBN.

REQF3.5 The system must maintain course history including offering dates
(beginning and ending), number of students enrolled, and instructor.

REQF3.6 The system must provide search capability for courses based on
title, category, popular course, recent releases, planned courses.

REQF3.7 The system must provide access to all course maintenance features
to the Course Administrator.

4. Maintain Instructor Information
REQF4.1 The system must maintain Instructor information including

instructor id, instructor first and last name, address, cell and home
phone, areas of teaching expertise, bio, and stipend.

REQF4.2 The system must be able to provide reports of instructor schedules
and courses taught

5. Maintain Course Schedules
REQF5.1 The system must be able to create, modify, and delete course

schedule information in its central database including course title,
course number, course description, course prerequisites, course type,
length of course, course outline, schedule dates, and instructor
information.

REQF5.2 The system must be able to query course schedules and display
results for all users based on keyword, title, and schedule.

REQF5.3 The system must provide all course schedule maintenance features
to the Course Schedule Administrator.

IT Online Training Requirements Specifications 2018R2 Page 3

6. Manage Shopping Cart
REQF6.1 The system must be able to provide a shopping cart feature for

customers to select and pay for courses.
REQF6.2 The system must provide a Shopping Cart Item which lists each

item in the Shopping Cart including quantity, item number, item name,
cost, shipping, coupons, discount, and total.

REQF6.3 The system must be able to provide customers with the ability to
update the shopping cart including increasing the number of items,
removing items, calculating shipping costs, and applying coupons and
discounts.

REQF6.3 The system must be able to provide payment options for the
customer including credit cards.

7. Access Credit Card Service
REQF7.1 The system must be able to link to an external Credit Card Service.

8. Access the Accounting System
REQF8.1 The system must provide a link to the Accounting System for the

transfer of customer payment information.

9. Provide User Management
REQF9.1 The system must provide management of User with user name and

password for all users of the system including customers and
employees. Users can login and logout of the system.

REQF9.2 The system must implement a password policy that includes strong
passwords including 8-15 symbols including letters (at least one upper
case), digits, and special symbols like “!”.

REQF9.3 The system must maintain password history and not allow the reuse
of the last three passwords

REQF9.4 The system must encrypt passwords.

Non-Functional Requirements

1. Design a Scalable Architecture
REQNF1.1 The training application must be capable of maintaining customer

accounts for up to 100,000 customer accounts during the first six
month and 1,000,000 after six months.

REQNF1.2 The training application must be capable of servicing up to 1,000
simultaneous customers initially and up to 10,000 after six months.

REQNF1.3 The training application must be capable of handling 100 search
requests per minute and up to 1,000 search requests after six months.

REQNF1.4 The training application must be capable of handling up to 100
purchases per hour and 1,000 after six months.

IT Online Training Requirements Specifications 2018R2 Page 4

2. Implement Security

REQNF2.1 The system shall implement the industry standard security
features, including PCI compliance, for using secure web pages for all
sensitive transactions including account, password, and payment
management.

REQNF2.2 The system shall provide protection from the common web
security threats including Injection, Weak Authentication and session
management; cross site scripting (XSS); Insecure Direct Object
References; Security Misconfiguration; Sensitive Data Exposure;
Missing Function Level Access control; Cross Site Request Forgery;
Using Components with Known Vulnerabilities; Unvalidated Redirects
and Forwards; price manipulation through hidden fields or cookies;
buffer overflow and other security risks detailed in OWASP Top Ten at
https://www.owasp.org/index.php/Main_Page

Note: The above requirements are not complete but represent an initial draft and
are sufficient for our needs.

https://www.owasp.org/index.php/Main_Page

Description
Sponsor Requirements
Functional Requirements
1. Purchase ITOT Products
2. Maintain Customer information
3. Maintain Products
4. Maintain Instructor Information
5. Maintain Course Schedules
6. Manage Shopping Cart
7. Access Credit Card Service
8. Access the Accounting System
9. Provide User Management
Non-Functional Requirements
1. Design a Scalable Architecture
2. Implement Security