Release Information

Project:	Phoenix Systems Architecture and Engineering
Internal Release Number:	X.Y.Z
Attached worksheets:	LINKS TO WORKSHEETS
Related Documents:	Project proposal [LINK TO BE PROVIDED] LINKS TO RELEVANT STANDARDS LINKS TO OTHER DOCUMENTS Other Usage-Oriented Functional Concerns Glossary

Introduction

Concerns

ID	Attribute	Concern
DE-01	Availability	Operational availability Readiness for usage. The degree to which a system, subsystem, or equipment is operable and in a committable state at the start of a mission, when the mission is called for at an unknown, i.e., a random, time. A measure of the planned up time during which the system is actually available for use and fully operational.
DE-02	Biocompatibility	The ability of a device to perform its intended function, with the desired degree of incorporation in or application to the (biological) host, without eliciting any undesirable local or systemic effects in that host.
DE-03	Privacy	Ensurance that information about a person is free from any intrusion not sanctioned by the person.
DE-04	Reliability	Continuity of service. The rate of failure in the system that renders the system unusable. The ability of the system to keep operating over time.
DE-05	Robustness	Graceful handling of invalid inputs. Ensurance that user input cannot crash the system or corrupt data, even if that user input is abnormal, unexpected, or malicious.
DE-06	Safety	Non-occurrence of catastrophic consequences on the environment
DE-07	Security	Ensurance that information is accessible only to those authorized to have access. A condition of not being threatened, especially physically, psychologically, emotionally, or financially.
	Integrity	Non-occurrence of improper alterations of information. Ensurance that data is "whole" or complete. The condition in which data is identically maintained during any operation, such as during transfer, storage or retrieval.
DE-08	Survivabilty	The degree to which a system can fulfill its mission, in a timely manner, in the presence of attacks, failures, or accidents.

Availability

ONE PARAGRAPH OVERVIEW

Details:

What are the supportability and operability requirements?

Supportability is our ability to provide cost effective technical support. Our goal is to limit our support costs to only 5% of annual licensing fees. The product's automatic upgrade feature will help us easily deploy defect fixes to end-users. The user guide and product website will include a troubleshooting guide and checklist of information to have at hand before contacting technical support.

Operability is our ability to host and operate the software as an ASP (Application Service Provider). The product features should help us achieve our goal of 99.9% uptime (at most 43 minutes downtime each month). Key features supporting that are the ability to do hot data backups, and application monitoring.

Details:

• DETAIL
• DETAIL
• DETAIL

Biocompatibility

ONE PARAGRAPH OVERVIEW

Details:

Privacy

ONE PARAGRAPH OVERVIEW

Details:

Reliability

ONE PARAGRAPH OVERVIEW

What are the reliability and up-time requirements?

Details:

Robustness

ONE PARAGRAPH OVERVIEW

Details:

Safety

ONE PARAGRAPH OVERVIEW

Details:

Survivabilty

ONE PARAGRAPH OVERVIEW

Details: