Test Case

(Week 1) Section 5: Work breakdown structure

Collection of data and analysis will merge at the same time in the planning phase, which will help to establish the needs of stakeholders. The process is supposed to take one week where the project crew will collect all the information from vendors, customers, and stakeholders. This will help to decide the features expected from the program. The next process is coming up with integration tools and this step will take approximately 3 weeks due to the complex nature of the process.

Time and cost should be well managed and thus testing and development of the project features will be conducted simultaneously. Actual testing of the application on vendors and customers will provide real-time support that greatly aids in the development and implementation of security measures to reduce risk. Real-time support also helps greatly to reduce the effects of malfunctioning on the business and also try to establish the vital features that may not get into the development phase. This phase will take no more than 3 weeks to complete. The development team will actively fix any malfunctioning of the application.

The last process is monitoring how the application is performing. The team will offer oversight for support for example database administration or cloud-based services. Cloud-based services always have various security features in place to ensure information communicated through the network resource is reliable and secured properly (Dennis, 2018).

Customer satisfaction is very essential; therefore, there is the need to properly track customer and client communication. To ensure there is monitoring, the application will have to always produce a copy of the communication between the companies; client and other users. This will easily provide an oversight authority for tracking the communications there; the business managers can check if the clients are useful to the business. This approach is very beneficial in determining if the application effectively provides customer satisfaction.

The alignment of stakeholders’ requirements and the applications design will ensure the organization has attained operational effectiveness. The organization will attain improved productivity if the customer service application is working properly (Lin, 2007).

Regarding the quality of communication, the application architecture, this is put together in model form in a way that response will give the preferred quality assurance to the customers by the utilization of automated systems. Using automated alert applications in the automation strategy will ensure that customers’ issues are properly and in time. Communication quality will enhance ability by ensuring every stakeholder’s requirements meet their expectations since different people have different interests. Additionally, it also aids in ensuring the right design gets put together properly.

(Week 2) Section 7: Quality Assurance Plan

· Stability

· Availability

· Reliability

· Timeliness

· Accuracy

· Durability

To ensure that our product meets those criteria, we have decided to implement these specific objectives to produce the best product for the customer. The objectives are as follows:

· Connection speed should allow fast VoIP connection and create and easy connection for customers/employees to utilize the ticketing system.

· Front-line employees should have adequate training on new network capabilities and its usage.

· Ticketing system should connect to the network within the building in approximately 30 seconds while the outside connectors should only experience a 1-minute delay depending on the connection speed of their internet service. **Allow for up to 2.5 minutes with a 50Mbps internet speed connection**

· Employees should be able to connect to the network 99.99% of the time.

· The new network should accurately (90%) deliver service to the customer service application to allow employees the ability to actively connect to satisfy their customer incident reports.

· Network should not experience any drops of service during business peak hours.

· Maintenance needs adequate training and have a 1-2-hour response time, either remotely or if need physically.

Our company is looking to provide a service that is 100% defect free. We will continue to monitor and test until the system is working at the levels that meet the customer’s requirements and our own.

After the objectives are in place it is time to put a QA team together. Once we have the team together, we will then assign roles. Each role has a specific duty that needs assigning to team members where they need to follow the detailed specifications outlined in the requirements and specification phase of the waterfall method (Unknown, 2018). The roles are breaking down in the following matter:

QA Manager (QAM): The QA Manager responsibility will be to supervise the actions of the members of his/her team. He/she is responsible for selecting the members of his team and providing them with the job assignment that fits their skill set. The QA Manager will be the person that is responsible for creating and disseminating the final report for the QA assessment.

Manual QA Engineer (MQAE): The responsibility of the MQAE is to develop the software/hardware needed in order to manually test components and/or separate sections of application software.

Test Automation Engineer (TAE): The responsibility of the TAE is to develop the software that will be using to conduct the portions of the system that run automatically.

Business Analyst (BA): Acts as the liaison between the upper management and the QA teams. Ensures that the application and the network it runs on is meeting expectations.

QA Analyst (QAA): The QAA is the person that goes beyond the testing and does an evaluation of the network. It’s often said that this member of the team goes off script to see if they can find anything that unusual with the product.

(Eisenberg, 2019)

In terms of coordination, this basically involves making sure that the QA plan does not overlap or contradict another plan in place. It is vital that we plan and check with other plans in the work such as risk management plan. The QAM will be responsible to ensure that the QA plan does not contradict another plan and vice versa.

The objective of the unit testing plan is to provide the team doing the testing the help needed in validating the quality of the software that is in the testing phase. It also helps those outside of the testing team like developers and others involved in the process. “In the test plan there are important aspects that are documented such as test scope, test strategy, and test estimation.” (Guru99, 2019) Unit testing is one of the levels of testing within a quality assurance plan. In my opinion it is the most important of all testing sequences. It is the first level of testing. The testing in done in individual units or components, whether it is software or any other type of product being in development. The main purpose of a unit testing plan is to validate each unit of a product or software meet what the design is to do.

Within the Unit Test Plan there are test cases that will need documenting and each one scheduled. I will show ten major test cases relating to this project shown in a table form.

Phase 1 (Partial Test) – When a new update/feature when added to the system, the team will test the modules it directly affects. This will help identify early bugs and errors. If the test results in no errors, then the full testing won’t happen. If bugs/errors occur or if the system fails to operate after, we will proceed to phase 2 testing.

Phase 2 (Full test) – The system test, will help identify bugs/errors across the entire system.

Product quality metrics

· Defects

· Customer issues

· Customer Pleasure

Process quality metrics

· Defects during network testing

· Defect arrival pattern during network testing

· Phase defect removal

· Effectiveness of defect removal

The main source of input for system defects or irregularities will be the internal Quality Assurance Team, the idea is to catch any major defects with the system before the users of the system notice them. If a User reports a defect, it’s given a higher prioritization for repair than one reported by the internal team. This is to fix any issues in the practical function of the program, allowing business to continue to operate with minimal impact from system errors (Ivanova, 2019).

To assist the quality assurance team in their task of examining the system for potential defects, there are several formulae that will help compare the system’s current performance to ideal thresholds. These will also assist in informing other quality metrics like the total bug count, the defect removal efficiency rate or DRE and the Bug burn down (the projected amount of time to close out all remaining bugs in the system).

Tracking the DRE will show how effective the QA team is at removing bugs from the product before they effect the experience of the end user, represented as a percentage. The Calculations made by taking the number of bugs found in development and dividing that by all the bugs found in both production and development then multiplying by 100 to get the percentage of DRE (Arnold, 2019). Keeping track of this number will give a good representation of the team’s ability to get ahead of potential issues as well as provide valuable data on bug burn down, BBD.

BBD is a projection used to determine the potential length of time the QA team will need to research and fix open bug tickets, based on the average closure amount over the previous lifecycle of the project (Data, 2017). If there are 100 open bug tickets and after 5-weeks, 10-tickets closed per week, you could average it would take another 5 weeks to finish the bug tickets. If the project has a completion date within 4 weeks, you could use that project to assign extra resources to accomplish the task sooner.

Measuring the fixed defects percentage will also assist in tracking the success of the QA team in repairing the bugs reported by users or QA testers and should be under review by management to determine overall quality and success. Calculations made by dividing defects fixed by defects reported and multiply by 100 to get the percentage.

(Reichert, 2019)

Positive risk is a questionable circumstance that prompts a gainful result. A negative risk then again is one that outcomes in a misfortune (Doherty, 2000). Cost, execution, preparing, plan and legally binding dangers are overall negative dangers. They are dangers instead of chances

Utilized for recording risks, is a risk register, the guides made against that risk and the administration of each risk (Funtowicz and Ravetz 2010). The register is basic to fruitful administration of dangers. Likelihood and effect lattice are the way toward surveying the probabilities and significances of dangers when they occur. Each risk evaluated on its probability of event and the effect on a target on the off chance that it occurs. It very well may be in use in my task to characterize the degree of the dangers that can emerge and the likelihood against the outcomes of the dangers. It can combine both parts onto a similar scale.

A=high (rating 100)

B=medium rating (rating 50)

C=low (low rating 10)

Probability occurrence (in percentage)

A= 80-100

B= 60-80

C=30-60

Risk in a development project is unpreventable. As much as one may prepare totally, certain perils may happen due to unavoidable conditions. Perils either present minute or long stretch to the security of the people, prosperity and condition, are immaterial. This risk could either have a negative or constructive outcome on the endeavor if it occurs. It may have in any event one reason and besides at any rate one impact.

The strategy of risk management the board is a total commitment (Froot, Scarfstein and Stein, 2013). The legally binding specialists and the assignment group need to work inseparable to ensure that the vulnerabilities reduced or oversaw appropriately. The critical responses to risks join controlling, enduring, help, move, sharing, avoiding improving and abusing.

(Week 3) Section 8: Documentation plan

User Documentation

Upon completion of the product, a manual for the network admins will be created and disseminated via email. This document will provide the user with the ability to know the ins and outs of the network and how to troubleshoot the system if need be. We believe that the document should be given out via email and a hard copy should also be produced in case of a situation where the admin does not have access to the computer to complete the troubleshoot. Timeline for product dissemination is after the December 17th date but further down the line where the project is also complete, preferably a week after product completion to give time to make edits to the document.

The end user manual is the most detailed manual that we have decided to create. It does into full detail on how to operate, troubleshoot, install, and perform routine maintenance. This document has a completion date of December 17th, 2019 as well. However, dissemination will not begin until the project is complete, and all tests have passed audits. This manual will need to be in review and tested for cohesiveness in order to pass the requirements expectation. Once that is complete, we expect the document to be ready for release about a month before launch of new system.

Sections that are currently being worked on will be identified by a version number, time stamp and an employee code to identify and trace the work being done. Official Documentation should be marked as such, with signatures on approvals updates or changes being made only by the project team’s lead. Changes to documents should be marked to identify physical or electronic to update the appropriate area and track any changes being made (F, 2018). An additional table of contents should be provided for any sub along with image and video references in the sections where applicable.

Document creation, updates or approvals will be performed by the Network System Administrator and authorized then released by the Management. The IT staff will be responsible for the completion and hard copy storage of new materials. Management will determine what information is accessible to the different versions released to different Users.

The categories of documents include but are not limited to Project Administration, Presentations, Cost Analysis Breakdown, contracts, employee assignments, version tracking, help sections and research materials.

The Storage of the documents, once created, will be handled by management to ensure the secure storage of sensitive materials. Hardcopies stored will also include any official project materials, including contracts, contacts proposals and licenses. Electronic Versions will include copies of the materials above, and will be identified clearly by name, date, version number and uploader. These will be materials will be sub sectioned by project folders in the database that will be clearly identified by the Projects name and subsequent version.

The different versions of documentation will be maintained in the same manner by staff, though the availability of information in the documents will be different. Management will be provided with the complete contents of the documents provided, including any sensitive or proprietary information to be able to formulate administrative or financial changes and respond to various interests. Network System Administration, or NSA will be provided a document oriented at the system itself, with less emphasis on financial interests and sensitive information not directly impacting the projects operations (Akinci, 2010). With multiple clearance levels on the NSA staff, each employee login will provide the appropriate clearance to view the sections needed for that job code. Policies, procedures and included forms are

End Users will be provided the least technical documentation on the back end of operations with a focus on the appropriate uses and available functions of the systems applications. The emphasis is instead placed on the order of operations and the types of information the system can process. The help section should also be more robust with outside reference materials, training videos and help contacts.

Network System Administration is responsible for assigning IT associates to the completion of the project reports required. Once completed, the documents will be reviewed for accuracy of information and conformation to the document control standards. This should include, associates name and title, a summary of the reported work, the information changed, the date and the version number. The associate will alert their admin by email when the work is completed to be complied into the new version.

End Users will be alerted by email or program startup when a new version of the help or instructional documents are changed or updated. The updates and changes to the User Documents will be scheduled for once every six months, to be made by the IT support team, following the procedures outlined above. The NSA will approve, or request changes then the contact will be put into place by the Management to ensure the security, availability and accuracy of the materials supplied.

To: Management

From: Connie Farris and Development Team

Date: 12/02/2019

Subject: Design Plans

We have created this document to inform all management involved in the development project the steps we will be using to provide a system that meets all the requirements and needs of the company and the end-users.

After serious discussion, the development team have decided to use the Waterfall Methodology for this endeavor. Some of the main reasons we will use this method are the following:

· Timescales are kept

· No money related shocks

· Testing is made simple

· The result is precious stone clear

· Bargain with issues within the plan

· What you arrange is what you get

Waterfall takes after a straightforward structure of stages where the comes about of each stage cascade down to the following level of advancement. (Kienitz, 2017) In other words, we’re not so much looking at one huge Niagara Falls, but an arrangement of cascading waterfalls – each with their claim small pool of exercises.

The process documents offer guidance to the development, testing, maintenance and improvement of the systems. The process documents are normally used by managers, engineers, testers and the marketing professionals.

Administration will utilize this program for ticketing framework, ticketing computerization sending framework, VoIP framework for out of nation calls, conveying workflows and dealing with auto upgrades and straightforward to halfway patches. The conclusion clients are not interested to get it the application profoundly, but to know for performing any of the above-mentioned assignments.

The description document which provides the necessary information on the system requirements and the services offered this document is detailed information regarding the software. The end users should read through the provided introductory manual to determine whether it is the required software. The following is a draft of the description document. Revision History

This document will be distributed by sending a copy of the document to each software user either through email or inform of a hard copy by packing together with the software. The maintenance of this document can be ensured through filing or saving in email for easier retrieval.

Secondly is the configuration which is either developed for the system administrator or the end user. This document clearly shows how to configure the software for end use. For the system design or the configuration document, it should have the following in components;

The configuration or system design document will be distributed through the packaging materials for the software or rather sending a softcopy to every software user.

The user guide will be distributed through packing or sending through the software. It should be accompanied with the software either through in form of soft copy or through a hard copy to enable the users to understand how to safely and correctly use the software.

The final section entails information for possible cost and configuration timelines

I would suggest standard server and information center version. This can be included by two virtual OSE. The authorizing show is processor+. The server estimating for this version goes for $890. Information center version goes for $1000. Equipment prerequisite as recorded over will account up to $1000 whereas computer program necessity will go up to $500. Significate cost could be experienced within the staff required for the usage. With this the cost could increase to about $2000

The table shows project plan for full implementation of c

3062 Argyle RD1

Gainesville, Florida

32609

USA

Tel: 352-376-5555 Fax: 352-351-5555

Last edited: 08 December 2019

Copyright © 2019 Galactic IT Services. All rights reserved.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from Galactic IT Services

All copyright, confidential information, patents, design rights and all other intellectual property rights of whatsoever nature contained herein are and shall remain the sole and exclusive property of Galactic IT Services. The information furnished herein is believed to be accurate and reliable.

However, no responsibility is assumed by Galactic IT Services for its use, or for any infringements of patents or other rights of third parties resulting from its use.

PLANNING & DEVELOPING A PROJECT 2

:

Document Name: System Administration Guide

© Galactic IT Services 2019. All rights reserved. Page 6 of 35

Document History

Document History will be recorded here, however there are no documents to place here as of yet.

Revision History

Any time a document is revised it will be recorded in the table below.

Reference Documents

Please see the following documents for more information:

Distribution List

This document has been distributed to those listed in the table below:

This System Administrator Guide provides information on how set up, configure, and deploy the System/Network application for research, development, and instructional use. The Systems Administration Guide serves the purpose of an Operations Guide in distributed client/server applications.

Audience and Assumptions This section introduces and describes the purpose of the Systems Administration Guide, the name of the system to which it applies, and the type of computer operation.

This guide is intended to assist System/Network Administrators in securing workstations, mobile computers, and computers within managed environments and should not be applied throughout an enterprise unless trained and competent System/Network Administrators are available on the staff.

This section introduces and describes the purpose of the Systems Administration Guide, the name of the system to which it applies, and the type of computer operation.

The System Administrator's tasks include:

· Backing up and loading databases

· Changing the password of any account

· Creating server login accounts, which includes assigning initial passwords

· Creating user databases and granting ownership of them

· Creating, granting, and revoking user-defined roles

· Diagnosing and reporting system problems

· Fine-tuning [Server] by changing configurable system parameters

· Granting and revoking the Security Officer and Operator roles

· Granting and revoking the System Administrator role

· Granting permissions to [Server] users

· Granting the capability to impersonate another user throughout the server

· Managing disk storage

· Managing the audit system

· Modifying and dropping server login accounts

· Monitoring [Server]'s automatic recovery procedure

· Security Officer - who performs security-related tasks such as:

· Setting the password expiration interval

· Setting up [Server] to use network-based security services

· Setting up groups which can be used for granting and revoking permissions)

Many of the commands and procedures discussed in this guide require the System/Network Administrator or Security Officer role. Other sections are relevant to Database Owners. A Database Owner's user name within the database is "dbo". Various security-related, administrative, and operational tasks are grouped into the following system roles:

System/Network Administrator

By default, the System Administrator (the SA) has the following roles:

· sa_role

· so_role

· oper_role

Operator

An Operator is a user who can back-up and load databases on a server-wide basis. The operator role allows a single user to use commands to back up and restore all databases on a server without having to be the owner of each one. These roles provide individual accountability for users performing operational and administrative tasks. Their actions can be audited and attributed to them.

Document relationships are recorded in the table below

This section will provide a brief description of the system, including its purpose and uses.

Below will be the description of the overall system software and organization.

· List the software modules, programming languages, and development tools.

· Describe all software required to support the system, and specify the physical location of all software systems.

· Identify database platforms, compilers, utilities, operating systems, communications software, etc.

· Identify each software system, subsystem, and program by name, description, and documentation references.

In this section the communications within the system, such as Local Area Networks (LANs), buses, etc. will be described. Included will be the communications architecture(s) being implemented, such as VoIP, Point to Point, DS3, etc.

A diagram will be provided depicting the communications path(s) between the system and subsystem modules.

This is the official address of the site(s).

Primary Site Contacts

This section covers procedures for maintaining the file system.

1. Become super-user or assume an equivalent role.

You need to turn off power to all system devices when you:

· Replace or add hardware.

· Move the system from one location to another.

· Prepare for an expected power outage.

Turn the power off for system devices, including the CPU, the monitor, and external devices such as disks, tapes, and printers.

Use this procedure to boot a system that is currently at run level to run level. This run level is used for system maintenance tasks, such as backing up a file system.

1. Boot the system to run level [x].

2. Type the super-user password.

3. Verify that the system is at run level [x].

This is where the procedures to monitor system usage, performance, and activity will be kept. Installing Programs and Operating System Updates

This is where the procedures for the setup and monitoring of the operating system and application audit trail will be entered

This is where the procedures to create and update maintenance reports are kept

· System Administrators have access permissions on all systems objects at all times.

· Network Administrators have access permissions on all network objects at all times

· Security Officers can always access the audit trail tables in the security database.

The system will recognize the following types of users:

System/Administrator’s privileges. Will be entered in the table below

A description of the procedures for creating and deleting user logins and password accounts will be recorded in the table below

· Security Officer uses will use a command setup for them to create a server login account for a new user.

· System/Network Administrator will use a command set for them to add a user to a database.

· Security officer grants specific roles to the user.

This table summarizes the system procedures and commands used for these tasks.

The procedures to setup servers, including naming conventions and standards will be written up here.

The procedures to create server directories; identify the existing directories will be written here.

The procedures to create server drive mappings; identify existing drive mappings will be written here.

A description of how to use resource limits to restrict the I/O cost, row count, or processing time that an individual login or application can use during critical times. A resource limit is a set of parameters specified by a System Administrator to prevent an individual login or application from:

· Exceeding estimated or actual I/O costs, as determined by the optimizer

· Returning more than a set number of rows

· Exceeding a given elapsed time

The set of parameters for a resource limit includes the time of day to enforce the limit and the type of action to take. This information will be provided in the table below.

Use the system parameters to:

This section discusses procedures for installing, operating, and maintaining printers.

This section will be used to describe maintenance contracts, procedures to include installation and configuration of printer drivers, and equipment information.

This section will be used to describe procedures to monitor, delete, and prioritize print jobs. Setting up local printers

· Setting up print servers

· Setting up print clients

· Spooling directory space of 8MB (or more)

· Hard disk strongly recommended (not required)

· Memory of 12MB (or more)

· Swap space of 20 to 24MB (or more)

Below is the how to configure a printer on the network, you will need the following configuration information ahead of time.

· Serial (or parallel) device name (required), for example /dev/xxx.

· Unique name for the printer (required).

· Printer type (required).

· Type of file content (required), for example, PS for PostScript, simple for ASCII, or both.

· Print server's Internet Protocol (IP) address in universal address format

· The description of the printer to convey to users (recommended, optional)

· The default printer for each system (recommended, optional).

Steps for setting up local printers.

1. Step 1

2. Step 2

3. Step 3

Steps for setting up print servers.

1. Step 1

2. Step 2

3. Step 3

Steps for setting up print clients.

2. Step 2

3. Step 3

Below is the process for obtaining identifications (IDs) and passwords. Include information concerning network access and confidentiality requirements.

When [server] is installed, a single login called "sa" is configured with the System Administrator and Security Officer roles. This means that the "sa" login has unlimited power.

Use the "sa" login only during initial setup. Instead of allowing several users to use the "sa" account, establish individual accountability by assigning specific roles to individual administrators.

The "sa" login is configured initially with a "NULL" password. Use sp_password to change the password immediately after installation.

Enable auditing early in the administration process so that you have a record of privileged commands that are executed by Security Officers and System Administrators. You might also want to audit commands that are executed by those with other special roles, such as operators when they dump and load databases.

When assigning [server] login names that are the same as their respective operating system login names, it makes logging in to the [server] easier, which simplifies management of the server and operating system login accounts and makes it easier to correlate the audit data generated by the [server] with that of the operating system.

The server will provide network-based security services that enable you to authenticate users and protect data transmitted among machines on a network. In a distributed client/server computing environment an intruder can view or tamper with confidential data. With the server, you can use security services provided by third-party providers to authenticate users, encrypt data, and prevent data tampering.

· Unified login - use a security mechanism to authenticate users once without requiring them to supply a name and password every time they log in to an [server].

· Message confidentiality - encrypt data over the network.

· Mutual authentication - use the security mechanism to verify the identity of the client and the server.

· Message integrity - verify that data communications have not been modified.

· Replay detection - verify that data has not been intercepted by an intruder.

· Out-of-sequence check - verify the order of data communications.

· Message origin checks - verify the origin of the message.

· Remote procedure security - establish mutual authentication, message confidentiality, and message integrity for remote procedure communications.

The passwords helps prevent access by unauthorized people. When you create the password, follow these guidelines:

· Do not use information such as your birthday, street address, or any other word or number that has anything to do with your personal life.

· Do not use names of pets or loved ones.

· Do not use words that appear in the dictionary or words spelled backwards.

· The most difficult passwords to guess are those that combine uppercase and lowercase letters and numbers. Never give anyone your password, and never write it down where anyone can see it.

Follow these rules to create a password:

· Passwords must be at least 6 bytes long.

· Passwords can consist of any printable letters, numbers, or symbols.

· Includes any character other than A-Z, a-z, 0-9,_, #, valid single-byte or multibyte alphabetic characters, or accented alphabetic characters

· Begins with a number 0-9

Describe the licensing agreements and procedures for ensuring that all licenses are current.

The [application] allows a System Administrator to monitor the number of user licenses used in [Server] and securely manage the license agreement data. That is, you can ensure that the number of licenses used on your [Server] does not exceed the number specified in your license agreement. The [application] tracks the number of licenses issued; it does not enforce the license agreement.

A license is the combination of a host computer name and a user name. If a user logs in to [Server] multiple times from the same host machine, it counts as one license. However, if the user logs in once from host A, and once from host B, it counts as two licenses. If multiple users log in to [Server] from the same host, but with different user names, each distinct combination of user name and host name is counted.

The System Administrator is responsible for ensuring the continued integrity of information stored on the system. One way the system administrator maintains integrity is to back-up the data on the system periodically so that the data can be restored if it is lost.

A ‘backup’ is a copy on external storage media, such as disks or tape, of files on your hard disk. A ‘filesystem backup’ is a copy of the files in the root filesystem or another regularly mounted filesystem. Files and filesystems can be damaged, and data can be lost through:

· Power surges and interruptions

· Hardware failures

· User errors (i.e. accidental removal of important files)

You should back up your filesystems regularly, so you have up-to-date copies from which to restore lost data

Describe the procedures for regularly scheduled backups, including program and data storage, and the creation and storage of backup logs.

This section describes documented daily and weekly backup schedules and procedures. The procedures should include tape labeling, tracking, and rotation instructions.

Before performing a scheduled backup, you might need to format the media.

1. Select the system to back up from the list.

2. Select Run Scheduled from the menu.

3. If necessary, select or enter the correct media device

1. Select the system to back up from the list.

2. Select Run Scheduled from the menu.

3. If necessary, select or enter the correct media device

How do I [enter FAQ]?

Answer:

How do I [enter FAQ]?

Answer:

How do I [enter FAQ]?

Answer:

End-User Manual Template

(Week-4) Section 9: Quality Assurance and results of test-case execution

Purpose: Quality Management Review

Audience: Stakeholders, Client, and project Team Members

Details: This report will review the progress of all phases of the project.

Galactic Customer IT Services is an IT support company located in Gainesville, FL. They have tasked out a project development team to upgrade their ticketing system, upgrade their VoIP capabilities, and an application to automate workflow, updates, and patches. Galactic Customer IT Services is a well-known client in the IT industry. This document will be in place alongside all other deliverables to produce reports, reviews, and tasks that completed throughout the course of the project.

The Project Manager is responsible for:

• Documenting the client’s requirements, expectations, and constraints for the project.

• Communicating with the client and project design teams

• Ensuring the client’s quality objectives identified and documented.

• Identifying the scope of the project and degerming the needs of the project that include refining the requirements, budgets, and all quality assessments.

The Project Design Teams are responsible for:

• Creating a finished product that meets or exceeds the requirements and constraints that the client has identified.

• Delivering the product with all quality assessments accounted and implemented.

• Taking the appropriate steps to ensure quality is at their level.

• Communicating with the Project Manager with identified risks, time frames, and stage/phase completions.

· This system has an expected employee user usage of 250,000 and 250,000 potential customer users.

· Galactic Customer IT Services has several servers at each location.

· Current system software will have an upgrade after completion of this project.

· Several Remote locations across the country.

· Workstations and VoIP hardware.

· VPN

· Current ticketing system

The client and project manager will review the design before this phase becomes complete. Once the design has an approval, the work starts. Design changes will be minimal to reduce risks such as scope creep.

The waterfall method got the approval for use. This methodology will provide detailed documentation throughout the project. The project team is confident is providing all the necessary documentation to ensure the project starts off with as much information as possible. This will help mitigate risks in the later stages of development.

The Work Breakdown Structure (WBS) has a place in the Project Plan document. This WBS will need a review and updated during each phase of the project. Future phases may alter this structure and will be update as needed.

· Daily reports will be available and sent out via email to all team members. This will allow the teams to fully understand the areas that are complete and in progress.

· Weekly reports cover the timeline, budget, main goals for the week, deliverables, and questions or concerns about the previous week.

· Milestone reports has a review period during weekly meetings. These meetings will cover the requirements for completion, completed milestone reviews, deliverable approvals, and project time frames.

· Quality management meetings held weekly to cover the current status of each stage of the project.

· Updates to the communication plan will need approval before any changes made.

Akinci, U. (2010). How to write a Documentation Plan. Retrieved from https://www.technicalcommunicationcenter.com/online-classes/how-to-write-a-documentation-plan/.

Andrews, M. (2019) The Best 11 Ticketing System Software in 2019. Retrieved from https://blog.hubspot.com/service/it-ticketing-system

Arnold, J. (2019, January 7). 64 Essential Software Quality Testing Metrics for Measuring Success. Retrieved from https://www.qasymphony.com/blog/64-test-metrics/.

Data, N. (2017, November 7). 13 Essential Software Development Metrics to Ensure Quality. Retrieved from https://blog.usenotion.com/13-essential-software-development-metrics-to-ensure-quality-219cfc264ed1.

Dennis, J. (2018). Three unbeatable security advantages of cloud-based solutions for your business. Retrieved from https://www.cloudcomputing-news.net/news/2018/jun/25/three-unbeatable-security-advantages-cloud-based-solutions-your-business

Doherty, N. A. (2000), integrated risk Management: Techniques and strategies for managing corporate risk. New York McGraw-Hill.

Eisenberg, A., (2019.) Does your QA Team Structure Pass the Test. Retrieved from https://igniteoutsourcing.com/it-outsourcing/qa-team-structure-roles-responsibilities/?

F, K. (2018, November 18). Document Control Plan: Introduction, Plan Content, Examples. Retrieved from https://www.brighthubpm.com/monitoring-projects/102112-example-of-a-document-control-plan/.

Froot, K.A., Scharfstein, D.S., & Stein, J.C. (2013) Risk management: Coordinating corporate investment and financing policies. The journal of finance 48, no.5 1629-1658.

Funtowicz, S. O., & Ravetz, J. R. (2010). Three types of risk assessment and the emergence of post-normal science

Guru99, (2019). How to Create a Test Plan (with Example). Retrieved 25 November 2019, from https://www.guru99.com/what-everybody-ought-to-know-about-test-planing.html

Ivanova, I. (2019, November 10). Important Software Test Metrics and Measurements – Explained with Examples and Graphs. Retrieved from https://www.softwaretestinghelp.com/software-test-metrics-and-measurements/.

Jacoby, J., & Kaplan, L. B. (2013). The components of perceived risk. ACR Special Volumes

Kienitz, P. (2017). Pros and Cons of Waterfall Software Development | DCSL Software Ltd. Retrieved 1 December 2019, from https://www.dcslsoftware.com/pros-cons-waterfall-software-development/

Minasi, M. (2014). Mastering Windows Server 2012 R2. Indianapolis: Sybex.

Reichert, A. (2019, January 22). How to write a software defect report. Retrieved from https://techbeacon.com/app-dev-testing/write-software-defect-reports-get-results-boost-credibility.

Rouse, M. (2019, February). waterfall model. Retrieved from TechTarget: https://searchsoftwarequality.techtarget.com/definition/waterfall-model

Spacey, J., (2017.) 14 Examples of Quality Objectives. Retrieved from https://simplicable.com/new/quality-objectives

Stanek, W. R. (2013). Microsoft Windows server 2012 inside out

Telerik. (n.d.). RadEditor End User Manual. Retrieved from https://d31ghwrlt97cgl.cloudfront.net/RadEditorAjaxEndUserManual.pdf

Unknown. (2018.) QA Activities in a Waterfall Process. Retrieved from https://qatestlab.com/resources/knowledge-center/waterfall-process/

Remote Site 1

Remote Site 2Remote Site 3

Remote Site 4 Remote Site 5

Remote Site 6Remote Site 7Remote Site 8

Remote Site 9

Remote Site 10

Gainesville Florida

LosAngeles,Calafornia

ISP

Cloud

ISP

Cloud

T3

T2T2

T2

T2

T2

T2

T2

T2

T2

T2

DS3

DS3

Online Ticketing

Customer Service

Tickets

Persistence

Security

UML Component Diagram: Online Ticketing

order

access

control

encryption

dataAccess

dataAccess

VPN

Internet

Customer