Escolar Documentos
Profissional Documentos
Cultura Documentos
Assurance
McCalls factor model tree
Define and give example of
each
Usability
Integrity
Efficiency
Correctness
Reliability
Maintainability
Testability
Flexibility
Reusability
Portability
Interoperability
Operability
Training
Communicativeness Usability
Input/Output volume
Input/Output gate Integrity
Access Control
Access Audit Efficiency
Storage efficiency
Execution Efficiency
Correctness
Traceability
Completeness
Reliability
Accuracy
Error Tolerance
Consistency
Maintainability
Simplicity
Conciseness Testability
Instrumentation
Expandability Flexibility
Generality
Self-Descriptiveness Reusability
Modularity
Machine Independence Portability
Software System Independence
Communications Commonality
Interoperability
Data Commonality
Verifiability refers to design and programming features that
enable efficient verification of the design and programming. (Ex. modularity,
to simplicity, and to adherence to
documentation and programming guidelines)
Thus, one can expect that a project will be carried out according to
two requirements documents:
The clients requirements document
The developers additional requirements document.
Formal design reviews (DRs)
- requires formal professional approval of their quality as
stipulated in the development contract and demanded by the
procedures applied by the software developer. It should be
emphasized that the developer can continue to the next phase
of the development process only on receipt of formal approval
of these documents.
Peer reviews (inspections and walkthroughs)
- directed at reviewing short documents, chapters or parts of a
report, a coded printout of a software module, and the like.
Expert opinions
- support quality assessment efforts by introducing additional
external capabilities into the organizations in-house
development process.
Software Testing
based on a prepared list of test cases that represent a variety of expected scenarios
objective of the software tests
detection of software faults and other failures to fill the requirements
formal approval of a module or integration setup so that either the next
programming phase can be begun or the completed software system can be
delivered and installed.
Software maintenance services
Ddoc Dint Duni Ddes Dreq Total Ddoc Dint Duni Ddes Dreq Total
Documentation
ID 35 7.5 42.5 ID 10 5 7.5 4.4 1.0 27.9
PD 17.5 3.8 21.3 %FE=50 PD 5 2.5 3.8 2.2 0.5 14.0 %FE=50
(POD=35
(POD=10)
21.3 14.0
RD 17.5 3.7 21.2 RD 5 2.5 3.7 2.2 0.5 13.9
Design
reviews
RDRC 1 2.5 TRC > 26.8 cu RDRC 1 1 2.5 6.4 16 TRC > 38.9 cu
)
Ddoc Dint Duni Ddes Dreq Total Ddoc Dint Duni Ddes Dreq Total
ID 30 17.5 3.8 51.3 ID 5 2.5 3.8 2.2 0.5 14.0
Unit tests
(POD=30
PD 15 8.8 1.9 25.7 %FE=50 PD 2.5 1.2 1.9 1.1 0.3 7.0 %FE=50
(POD=0)
RD 15 8.7 1.9 25.6 25.7 RD 2.5 1.3 1.9 1.1 0.2 7.0 7.0
System
RDRC 1 2.6 6.5 TRC > 50 cu RDRC 2.5 2.5 6.2 1.6 40 TRC > 50.9 cu
Ddoc Dint Duni Ddes Dreq Total Ddoc Dint Duni Ddes Dreq Total
ID 10 15 8.8 1.9 35.7 ID 2.5 1.2 1.9 1.1 0.3 7.0
Operation by
Integration
RD 5 7.5 4.4 0.9 17.8 17.9 RD 2.5 1.2 1.9 1.1 0.3 7.0
RDRC 1 2.5 6.4 1.6 TRC > 66.3 cu RDRC 6.9 6.9 17 44 110 TRC > 139.2 cu
tests