2-3 pagesComplete the documentation plan section of your project plan. Your plan should address the following (at a minimum):Which user documentation will be provided (at least 3 types) When develo

SYSTEM ARCHITECTURE 30

Group Project

Group 1

Participating Members

John Holmberg, Sean Austin, Christian Dillon, Charles Williams, Matthew Serdy, Frank Opoku

Non-Participating Members

5/29/2019

IT488 – IT Capstone II (IT488-1902B-01)

Henrietta Okoro

Table of Contents

Section 7 – Quality Assurance Plan 3

TestCase01 - 5

TestCase02 – 6

TestCase03 – 7

TestCase04 – 8

TestCase05 – 9

TestCase06 – 10

TestCase07 – 11

TestCase08 – 12

TestCase09 – 13

TestCase10 – 14

Integration – System – Regression testing – 21

Regression testing – 22

Quality Metrics – 23

Defects - 23

References 27

Quality Management Report 28

Planning Background for QMR: 28

Section 7 – Quality Assurance Plan

The quality assurance plan is to consist of various aspects to ensure the best product is delivered to the stakeholders. This plan is made up of key testing and quality checks to verify overall quality, availability, stability and maintainability. These plans are done at the end of each stage of development to once again, check for any issues or risks that develop.

Test cases –

The testing phases are to consist of test cases that follow each completed aspect of development. Some of the following test cases are interchangeable and can be used multiple times during development. Below we have compiled a list of 10 fundamental test cases that are the baseline of go forward testing. As more of the project goes through completion, more of these test cases can be developed and implemented.

Test Case Name	Scenario	Test information
TestCase01	Account Creation	Tester will attempt to create an account with a used account and an unused account
TestCase02	Test password security and password policy enforcement	When creating the account, the tester will make sure password security and the password policy are enforced
TestCase03	Test Login	This is to test a current valid user id to access system
TestCase04	Navigation buttons	Test app navigation buttons
TestCase05	Testing upload / download / share / delete documents	Document management tests
TestCase06	Check for data integrity	Verification of data
TestCase07	Data retention / backups	Verify data deletes after time out / backup viability
TestCase08	Test application load times	Speed of application under normal circumstances
TestCase09	Run stress testing on the application	Stress test to verify app can manage 500 simultaneous accounts
TestCase10	Contact email verification	App to send emails using default email application

TestCase01 -

EiS Testing Phase

Test Case #	TestCase01	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Create Account			Completed date:
Description:	Creation of New user account

Pre-Condition:	Known Account does not exist in database
Dependencies:	Space availability / check for known accounts
Post-Condition:	Completed creation

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Enter new email to test for current accounts	[email protected]	Return - account exist or available	Available	Passed
	Enter used email to test for current accounts	[email protected]	Return - account exist or available	Account Exists	Passed
	Enter user information, name / address / contact	Bob Burbaker - 123 Anywhere road, any town USA 12345	Fields filled and stored	Missing Zip	Corrected relationship / Passed	Testing staff corrected database
	Display user info	n/a	Display current information based on user	All information Correct	Passed	n/a
	Change zip / Save	zip changed 23456	Zip field stored	zip changed correctly	passed	n/a

TestCase02 –

EiS Testing Phase

Test Case #	TestCase02	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Password Policy			Completed date:
Description:	Password complexity and policy enforcement

Pre-Condition:	Blank password field
Dependencies:	Database and policy check to enforce security policy / Account information entered
Post-Condition:	Verification of / weak / good / strong password / Check on name policy

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Enter new password	password	return weak guessable	Weak Try again	Passed
	Enter new password	Passw0rd132!#$	Return good	Good	Passed
	Enter new password	ThisIsMyPasswordItHas1234!#$%	Return strong	Strong	Passed
	Enter new password	BobBrubaker	return cannot use account Name information	Invalid user name cannot be used	Passed
	Reset password	ThisIsMyPasswordItHas1234	Success	Password Changed	passed
	Expiration	Change clock forward on server +90 days	Password expired please reset	Password reset prompt	passed

TestCase03 –

EiS Testing Phase

Test Case #	TestCase03	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Account login			Completed date:
Description:	Testing login verification / with correct and incorrect login information

Pre-Condition:	Test account active
Dependencies:	currnt live test account is valid, unlocked, non-expired
Post-Condition:	Verification of account access

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Enter login info	bob test account w/ incorrect login information	login failure	Login Incorrect please try again	Passed
	Enter login info	bob test account w/ correct login	Verified and change to app front page	Logged in - app went to user account data page	failed - correced redirect	Dev team corrected page redirect
	Log off	Press log out button	Return to login screen	Account logged out redirect to login screen	Passed
	Enter login info	bob test account w/ incorrect 5 consecutive times	login failure / lock	Your account has been locked contact system admin page displayed	Passed w/ exception support # not listed	Support contact number added
	Account unlock by admin	Unlock bob test account	unlock	account unlocked	passed
	Enter login info	bob test account w/ correct login	Log in to app front page	logged in - app front page displayed	passed

(Cited: Deigned by Christian Dillion (C0 2019, design retrieved from https://ebooksbvd.my-education-connection.com)

TestCase04 –

EiS Testing Phase

Test Case #	TestCase04	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	App Navigation			Completed date:
Description:	Test and verify that the navigation / menu / home buttons direct to proper pages.

Pre-Condition:	html code for hyperlinks completed
Dependencies:	all pages live and links defined
Post-Condition:	Navigation success

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Home button	press home button	return to 'home' front page	Front page displayed	Passed
	New document button	press new doc button	Display upload page	Upload page displayed	Passed
	My Documents button	press my documents button	Display user documents	User documents page displayed	Passed
	Share Documents button	press share documents button	Display user doc / share page	User documents page displayed	failed / recode needed	Contacted dev to repair code
	Friends button	press friends button	Display friends page	friends page displayed	passed

TestCase05 –

EiS Testing Phase

Test Case #	TestCase05	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Document management			Completed date:
Description:	Test upload / download / share and document deletion

Pre-Condition:	Available account
Dependencies:	account active / space available / user in friends list
Post-Condition:	documents added / shared / deleted

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Navigate to my documents page	press my documents button	display user documents	User documents page displayed	Passed
	Upload new document	add test.docx to upload	test.docx diplays on my documents	test.docx displays	Passed
	Download document	select document hyperlink	document begins download	document downloaded into my downloads folder	Passed
	Share Documents button	select docx.doc check box / click share	share prompt displays with current friends listed	share page displayed friends list did not	failed / added relationship to friends table	dev corrected table relationship
	Delete document	select docx.doc check and press delete button	document removed from my doc’s page	doc.docx removed from displayed documents	passed
	recylce bin	select recycle bin to display deleted docs	doc.docx displayed in recycle bin	doc.docx in recycle	passed

TestCase06 –

EiS Testing Phase

Test Case #	TestCase06	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Data Integrity			Completed date:
Description:	Testing uploaded docs, when downloaded are exact same as when uploaded

Pre-Condition:	Empty my documents
Dependencies:	account active / space available
Post-Condition:	documents not corrupted after data transfer

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Create doc2.docx add data	doc2.docx created added 5 pages of Wikipedia data	document created	document created containing wiki data	passed
	Navigate to my documents page	press my documents button	display user documents	User documents page displayed	Passed
	Upload new document	add doc2.docx to upload	doc2.docx diplays on my documents	doc2.docx displays	Passed
	Download document	select document hyperlink	document begins download	document downloaded into my downloads folder	Passed
	Open doc2.docx	doc2.docx opened reveal wiki data	document opens reveal correct data	document opened successfully wiki information displayed correctly	passed

EiS Testing Phase

Test Case #	TestCase07	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Data Retention Backup			Completed date:
Description:	Testing Retention policy / Backup / Restore integrity

Pre-Condition:	Documents available in my documents folder
Dependencies:	Retention policy Active / Backup and restore policy active / space available
Post-Condition:	Documents removed after retention expiration / Backup and restore success

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Documents added to my doc’s folder	add 30 random documents to my documents folder	documents added	30 documents listed in my documents page	passed
	Initiate backup	Manually begin system backup process	Complete backup of user data	Backup success	Passed
	Delete all files from my documents	select and manually delete 30 docs and empty recycle bin	all docs removed / recycle bin empty	Cleared my documents and cleared my documents	Passed
	Initiate restore	Manually select and begin restoring process for test account bob	Restore from tape complete documents return to my documents	30 documents listed in my documents page	Passed
	Test restore integrity	Download doc to check data is correct	Document downloads, data correct as upload	download successful, data matches pre-upload doc	passed
	set server clock forward 1 year	Move server clock manually forward 1 year	30 documents removed per retention	zero documents removed	Failed - incorrect retention policy	reconfigured retention to 1 year

EiS Testing Phase

Test Case #	TestCase08	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Page load times			Completed date:
Description:	Testing the time pages load / navigation page changes

Pre-Condition:	Full system operational
Dependencies:	Full navigation completed hyperlinks verified / stopwatch prepared
Post-Condition:	Successful page navigation

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Log in	Log in system bob user id	From log in page to app home page 1 second	login successful, app home page displayed .77 seconds	passed
	My docs load	navigation to my document page	my documents page loads successfully .5 seconds	my documents page loaded .65	passed	plus/minus 20%
	Friends load	navigation to my friend’s page	friends page loads .5 seconds	my friends page loaded .44 seconds	Passed
	New doc load	navigation to upload to my documents page	upload page displays .5 seconds	upload page loaded in .55 seconds	Passed	plus/minus 20%
	Share doc load	navigation to share documents page	navigation to my documents share page loads .5 seconds	my documents share page loaded .36 seconds	passed
	Delete doc completion	remove documents from my documents page	document deletes and refreshed my documents page loads .5 seconds	document removed / page refresh loaded .70 seconds	failed / retry success	retried document deletion 5 times 1 fail 4 success

EiS Testing Phase

Test Case #	TestCase09	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Stress Test			Completed date:
Description:	Testing application functionality and response under load

Pre-Condition:	Full system operational
Dependencies:	500 concurrent log ins with Test accounts
Post-Condition:	Server and database integrity valid

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Replication Logins under database	add dummy logins	500 dummy accounts active	453 dummy accounts online	failed / retry success	47 more accounts added
	Manual Login	login with bob test account	Login successful	Login successful 1.5 seconds to application home page	passed	Note slower login
	Document upload	Navigate to upload page and upload test.docx	Upload success	test.docx uploads 2 second response time to page refresh	Passed	note slower reload
	Document deletion	remove test.docx	document deletes and is moved to the recycle bin	test.docx removed, available in recylce response time .7 seconds	Passed	improvement on time
	Log out	Logging off	Logout successful	Logoff success / login page displayed .5 seconds	passed

EiS Testing Phase

Test Case #	TestCase10	Test Designed by:	Development Team 1	Completed by:	Test Team
Test Case Name:	Email functionality			Completed date:
Description:	Testing contact email navigation

Pre-Condition:	email application closed
Dependencies:	Default email program selected, mailto: hyperlinks coded
Post-Condition:	opened new email address field populated

Step	Test Steps	Test Data	Expected Result	Actual Result	Status	Notes
	Navigate to the contact support page	click the support button	Page displays support.html page	support page displayed	passed
	Click contact support email button	click the email support button	default email app launches	outlook365.exe launched w/new email	passed
	Verify to field populated	make sure that [email protected] in the to field	[email protected] displays into field	[email protected] displayed correctly in the to field	Passed
	Populate body with random issue / send	add key problem details in body / send	email sends via default email application	email sent successfully	Passed
	Check EiS support Mailbox	verify email arrival	problem email arrives	problem email successful in EiS mailbox	passed

The Type of Quality Planning and Association to Stages of Software Development

Quality Assurance Plan is the type of quality planning that will be used during the development of EiS Software. It is the initial step in software quality management plan. The focus of this part of Quality Management is the establishment of the template that will be used in quality management. The parts of the Quality Assurance Plan associating with the stages of software development methodology includes; establishment of goals of quality assurance-project panning, setting and assigning responsibilities of QA-project analysis, collecting vital information on project standards and establishment of compliance criteria-system design, establishment of Quality Assurance metrics and quality measures-system integration, implementation, and testing (Féris, Zwikael, & Gregor, 2017).

Unit Testing Plan and Test Cases

Unit testing is one of the software where units or components of the software are tested individually. It is done before the units are integrated into the one system and the main purpose is to ensure that each unit of the software function as expected and void of errors. Unit testing will be affected using the following frameworks; stubs, drivers, and mocks/fake (Holling, Hofbauer, Pretschner, & Gemmar, 2016, April).

A plan for Test Case

Unit Test Case
Test Case Id	Test Case Name	I/O and test p procedure	Results	Pass or Fail	Test Date
	Log in
	Create Account
	Make Payment
	Edit Study Resource
5	Payment Receipting
	Order Study Resource
	Sell Study Resource
	View Available Study Resources
	Add Study Resource
10	Exit (logout)

Regression, System, and Integration Test Plan

Plan for Integration Testing

The purpose of integration testing is to ensure that components of the system interact or interface with one another as expected from the design (Holling et al., 2016, April). Integration testing is achieved by performing interface testing, whose plan is shown below

Integration Test Plan
Interface Name	Interface Code	Inbound or Outbound	Testing Methods	Pass or Fail
Report Production Interface	RTI-O-01
Order Transaction Interface	OTI-O-02
Payment Transactions Interface	PTI-I-003
Transaction Pre-Validation Interface	TPVI-I-04
Receipting Transaction Interface	RTI-O-05
Fund Management Interface	FMI-I-06

System Test Plan

System testing will be done after unit and interface testing to check whether the units work and integrate as one system. System testing will be achieved by performing different kinds of testing. Below is a plan for System Testing.

System Test Plan
Types of System Teat	Testing Criteria	Results	Suspension and resumption requirements	Pass or Fail
Functionality Testing
Usability Testing
Syed Interoperable testing
System performance, stability, load testing
System scalability testing
System stress testing
System reliability testing
System regression testing
System compliance and regulatory testing

Regression Testing Plan

Regression test is the software test that is performed during the maintenance phase of the software life cycle. It involves re-test of all test cases after the system is re-engineered. The following is a test plan for Retest-all regression testing.

Regression Test Plan
Selected Teat Cases	I/O and test p procedure	Results	Pass or Fail	Test Date
Log in
Create Account
Make Payment
Edit Study Resource
Payment Receipting
Order Study Resource
Sell Study Resource
View Available Study Resources
Add Study Resource
Exit (logout)

The Quality Metrics that will be used

During the establishment of system quality, the development team will use customer satisfaction presented on a scoring card as the quality metrics.

Measurement and Reporting of System Defects

Measurement of system defects will be affected using defect density. It is the measure of the number of effects in a software unit for a given period and it is divided by the size of the software module/unit. The table below shows how system defects will be reported

Defect Reporting Scheme
Date of Defect
Defect Number
Name of the Application
Responsible Peron
Reproducible of Defect
Defect Reference
The version of the Software
The severity of the Defect
Defect Priority

Integration – System – Regression testing –

Through out the quality assurance plan ends, integration, system and regression testing will work toward the end of the plan. As the software is then integrated into the network and the system, the analyzation is necessary to ensure proper integration to the various software applications and systems accessing the application. Below is an example checklist of integration and system testing. As quality assurance is completed, more integration checks will be added to the software, and this list will be continuously updated to reflect the changes.

Integration test table -

	Item	Status	Comment
Launch
Internet Expl	Pages display in IE	Pass Fail
Chrome	Pages display in Chrome	Pass Fail
Safari	Pages display in Safari	Pass Fail
Mozilla	Pages display in Mozilla	Pass Fail
Layout
Menus	Menu items displaying correctly	Pass Fail
Fields	Fields available and displaying	Pass Fail
Text	Text displays color / font correctly	Pass Fail
Consistent	Text fonts consistent throughout	Pass Fail
Buttons
Navigation	Navigate to proper page	Pass Fail
Color	Display color consistent	Pass Fail
Font	Font consistent	Pass Fail
Fields
Names	Names conform to guidelines	Pass Fail
Max length	Max length validations	Pass Fail
Mandatory	Mandatory fields validations	Pass Fail
Rules	Rules associated with questions	Pass Fail
Relationships
Primary key	Primary relationship table validated	Pass Fail
Foreign key	Foreign relationship table validated	Pass Fail
Table names	Names conform to guidelines	Pass Fail
Menus
Function	Open and close functional	Pass Fail
Navigation	items navigate correctly	Pass Fail
Home	Home menu displays correctly	Pass Fail
Support	Support menu displays correctly	Pass Fail
Drop down	Drop down boxes function correctly	Pass Fail
Access
Privileges	All privileges correct to acct type	Pass Fail
Accounts	Default account types set	Pass Fail
Internal	Internal access privileges set	Pass Fail

Regression testing –

Regression testing is extremely important to the overall quality assurance plan. During the regression phase of the plan there are often issues that might arise that will require changes to the system as per the direction and through the feedback from the management and the stakeholder testing. This testing phase takes place with the existing software and hardware already implemented and reviews any chances that may or may not affect the application. Here in lies the very aspect of quality of the application and the system we have developed. The completed software must be fully functional to the requirements of the stakeholders and there should be no issues that could cause issues with client or student use.

This phase often creates a test environment where the changes can be implemented without affecting the live system or affecting live client data. Construction of a smaller test environment on a virtual machine structure will be available to test said changes if any are necessary.

Quality Metrics –

Quality metrics are the standards and values that the quality of the EiS implementation will focus on to ensure the final product is done correctly. These metrics will measure the success of the application as it pertains to the standards and the guidelines agreed upon between EiS and the (Monroe, 2019)testing. Quality control are the aspects of how it pertains to the users and its availability to those users. Failure rate is another testing metric that pertains to the overall failures of any function. Loading, saving, retrieving, screen changes, logging on and off. Failures are based on a percentage of successes. Overall failure rate should be no greater than ½ of 1%. Another important metric to be determine is how well the application is received by the user base and the overall satisfaction. This will be determined through emailed surveys and will also garner feedback on any needed or desired changes.

Defects -

Defects are an issue where the function does not create the desired result, they are often called” bugs”. Defects can be display errors, document errors, even typos. Defects are any errors that result in a failure to conform to specifications or a failure to function/operate properly. (Monroe, 2019) Defects will be reported through the support tool on the systems web page. Issues that arise in the support page, a menu item will be available to “report a bug” which will provide a form for the user to fill out the page, date, and regarded issue. This will be sent via form to the EiS support and maintenance team to resolve the issue.

Risk Management –

Risk Management Strategies

The software development team will use risk avoidance, risk transfer, and risk reduction as the strategies for mitigating risks.

Regarding risk management for EIS we must prioritize our plans and understand what the plans are before we can develop a plan to handle them. We have developed a chart that is continually growing but it assists us in the planning stages of each project we undertake. The scoring for each table is as follows. For likelihood it is from 1 to 5 with 1 being unlikely and 5 being very likely. Regarding impact 1 is low impact and 5 in strong impact.

Risk	Likelihood	Impact
Over Budget
Stress Test determines system cannot handle the load
Login Screen not working properly
Competitor brings similar product to market
System is not loading properly
Data Breach
Not ready by deadline

The list continues to grow as new issues will arise over the life cycle of our software. Many of these issues will be discovered and planned for during our planning and design stage. In planning these risks the first step is to avoid the risk. We will avoid the risk when it comes to meeting our deadlines and timelines by installing managers in place that will control and meet goals. In setting small goals for our teams to achieve, as well as recognizing where there may be an inefficient team, will help us avoid the risk. We will perform regular weekly check-ins to ensure that our team is staying on goal as well as nothing that was avoidable arises during the development phases of our software. In proper planning and budgeting we will avoid the risk altogether. To avoid risk when it comes to the software itself there are numerous ways, we can reduce the risk as well as avoid some of the risk altogether. In performing numerous tests that will determine the quality of our product we will be able to ensure that are system can handle the load we will expect from it. Also, we will perform tests in sections. We will start releasing our system to test markets that will be able to determine if the system is ready for a wider release. So, when we are ready to deploy, we will release our system in a small area we have already planned for rural areas of three states Colorado, Nebraska, and Wyoming. In keeping the population that use our system small we will be able to oversee any issues that may arise and fix them as needed.

To limit the risk of our system in the future and to perform overall maintenance of our system we will have a development team that will continue to work on the system after deployment. This will be overseen by a project manager that will provide updates and hot fixes as well as perform and needed maintenance. This manager will report to the executive team of EIS to be able to ensure proper communication and that our team will always be aware of any issues that arise. Also, we will be able to oversee any large updates and keep them in line as far as timeline and budgetary concerns. This team will also oversee the overseeing control of the security of our system and in keeping with updates to ensure that, along with our security partners will be able to provide piece of mind when it comes to keeping our customers safe and secure.

References

Monroe, S. (2019). Commonwealth of Pennsylvania. Retrieved from www.dhs.pa.gov: http://www.dhs.pa.gov/cs/groups/webcontent/docuements/document/p_031767.pdf

McConnel, S. (1996), Rapid Development, Retrieved from https://ebooksbvd.my-education-connection.com

Féris, M. A. A., Zwikael, O., & Gregor, S. (2017). QPLAN: Decision support for evaluating planning quality in software development projects. Decision Support Systems, 96, 92-102.

Holling, D., Hofbauer, A., Pretschner, A., & Gemmar, M. (2016, April). Profiting from unit tests for integration testing. In 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST) (pp. 353-363). IEEE.

Quality Management Report

The Quality Management Report is that said report that establishes information of the progress of the project and has the abilities of returning to that information later. The following table shows some of the steps that were taken for the first week of the project including the establishment of the project manager and team individuals;

John Holmberg: Skills non-IT personnel, capabilities are some management skills from previous jobs and the understand of documentation.

Christian Dillion: Information Tech background 20 years’ experience.

Charles Williams: Over 14 years of military experience with leadership skills.

Matthew Serdy:

Frank Opoku:

Sean Austin:

Planning Background for QMR:

Continuation of IT Capstone I IT487-1902A-01, establishment of sequence of events as follows;

Established course of action of the educational information system, (IT487)

Establish a project manager, Christian Dillion

Establish team members John Holmberg, Charles Williams, Matthew Serdy, Frank Opoku, and Sean Austin

Overview of the project from IT 487

Selection of Methodology

Establishment of the QMR or Quality Management Report

Establishment of skill sets for each individual team member

The establishment of how the work will be performed and by whom

The establishment of a communication plan through emails, phone calls and the group discussion board which is provided.

Each week of progress will be shown through all communications on the discussion board for ideas, informational technics, and system protocols followed for a product viability.

Weeks	Category	Issues	Corrective Actions	Lessons Learned	Implementation Checklist
Unit1	Metrics Planning	Internal (personnel) Establishment of Group One	Listings of group expectations	Follow directions	Submissions of paperwork assigned
Group One	Time management	Accountability of one’s time	Plan your time successfully	Time management checklist of self
PMGR C. Dillion C. Williams J. Holmberg M. Serdy S. Austin F. Opoku	Lack of knowledgeability Sickness or injury	Read all reading materials Research outside the reading materials	Reading and research create knowledge of material needed	Knowledgeabilities create multiple successes
Unit2	Defects Reporting	Vendor delays	Vendor accountability	Vendor reliabilities established	Vendor deadlines met
	Software/hardware failures	Testing at each implementation	Testing solves issues	Testing fixes issues before they become major ones
		Impracticable deadlines set	Set real world deadlines	Real time deadlines more reliable	Real time deadlines create less stress and more productivity
Unit3	Workload Balance

(Cited: QMR Template provided by Professor H. Okoro for Rapid Development IT488-1902B-01, Template filled out by John Holmberg)