-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add correctness, reliability, usability and verifiability from Ghezzi…
…1991 text book
- Loading branch information
Showing
2 changed files
with
23 additions
and
1 deletion.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -170,6 +170,11 @@ \subsection{\notdone{Correctness} \oo{owner}} | |
\citet{VanVliet2000}.) | ||
\end{defn} | ||
|
||
\begin{defn} | ||
``A program is functionally correct if it behaves according to its stated | ||
functional specifications'' \citep{ghezzi1991fundamentals}. | ||
\end{defn} | ||
|
||
\noindent \textbf{Proposed Definition} | ||
|
||
Definition~\ref{CorrectDefnSelected} | ||
|
@@ -302,6 +307,11 @@ \subsection{\notdone{Reliability} \oo{owner}} | |
\citet{VanVliet2000}.) | ||
\end{defn} | ||
|
||
\begin{defn} | ||
``Informally, software is reliable if the user can depend on it'' | ||
\citep{ghezzi1991fundamentals}. | ||
\end{defn} | ||
|
||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
JacquesCarette
Collaborator
|
||
\noindent \textbf{Proposed Definition} | ||
|
||
\wss{Needs to be completed.} | ||
|
@@ -377,7 +387,9 @@ \subsection{\notdone{Performance} \pmi{owner}} | |
|
||
\noindent \textbf{Proposed Definition} | ||
|
||
Combined definition \ref{PerformanceDefnSelected} and \ref{PerformanceDefnSelected2}: The degree to which a system or component accomplishes its designated functions within given constraints, such as speed | ||
Combined definition \ref{PerformanceDefnSelected} and | ||
\ref{PerformanceDefnSelected2}: The degree to which a system or component | ||
accomplishes its designated functions within given constraints, such as speed | ||
(database response times, for instance), throughput ( transactions per second), | ||
capacity (con-current usage loads), and timing (hard real-time demands). | ||
|
||
|
@@ -439,6 +451,11 @@ \subsection{\notdone{Usability} \jc{owner}} | |
\citet{VanVliet2000}.) | ||
\end{defn} | ||
|
||
\begin{defn} | ||
``A software is usable - or user fridendly - if its human users find it easy to | ||
use'' \citep{ghezzi1991fundamentals}. | ||
\end{defn} | ||
|
||
\noindent \textbf{Proposed Definition} | ||
|
||
\wss{Still needs to be completed} | ||
|
@@ -1070,6 +1087,11 @@ \subsection{\notdone{Verifiability} \wss{owner}} | |
|
||
\wss{When I get the Ghezzi text back from Olu, | ||
I'll check to see if they have anything to add to this definition.} | ||
|
||
\begin{defn} | ||
A software system is verifiable if its properties can be verified easily | ||
\citep{ghezzi1991fundamentals}. | ||
\end{defn} | ||
|
||
\noindent \textbf{Proposed Definition} | ||
|
||
|
Does Ghezzi also give a formal definition of reliability? I thought they also had a definition based on stats?