2. Content
1 Perform a test Factor Analysis for the
Requirements Phase
1.1 Methodology Test Factor
1.2 Correctness Test Factor
1.3 Maintainable Test Factor
1.4 Portable Test Factor
1.5 Performance Test Factor
2 Conduct a Requirements Walkthrough
2.1 Establish Ground Rules
2.2 Select Team/Notify Participants
2.3 Project Presentation
2.4 Questions/Recommendations
02/24/15 2NITTTR, Chandigarh
3. Methodology Test Factor
The requirements process is one of fact
gathering ,analysis , decision making,
and requirements in a predefined
manner for use in design.
02/24/15 3NITTTR, Chandigarh
4. Portable Test Factor
The ability to operate the system on
different types of hardware and different
version of the software should be stated
as part of the requirements.
02/24/15 4NITTTR, Chandigarh
5. Ease-of-Use Test Factor
Amount of effort required to use the
system and skill level is necessary
should be defined during the
requirement phase.
Experience shows that difficult-to-use
applications are not often used.
Ease-to-use specifications will be
created by system analyst or
programmer.
02/24/15 5NITTTR, Chandigarh
6. Performance Test Factor
Expected efficiency ,economy, and
effectiveness of the application system
should be established.
These system goals an integral part of
the system design process.
End product of the requirements phase
should be a calculation of the
cost/benefit to be derived from the
application.
02/24/15 6NITTTR, Chandigarh
7. Correctness Test Factor
User satisfaction can be assured when system
objectives are achieved.
Qualitative objectives –such as improving
service to users are unmeasurable objectives
while processing a user order in four hours is
measurable.
02/24/15 7NITTTR, Chandigarh
8. Authorization Test Factor
Authorization requirements specify the
authorization methods to ensure that
transaction are processed accordance
with the intent of management.
02/24/15 8NITTTR, Chandigarh
9. Maintenance Test Factor
Degree of expected maintenance should
be defined, as well as areas where
change is most probable.
02/24/15 9NITTTR, Chandigarh
10. Audit Trail Test Factor
Reconstruction involves both
maintaining the accuracy of processing
and recovery after an identified problem.
Both of these needs involve the
retention of information to backup
processing.
02/24/15 10NITTTR, Chandigarh
11. Continuity-of-Processing Test
Factor
Continuity of processing is dependent
upon the impact of failure.
If system failure causes only minimal
problems , ensuring continuous
processing may be unnecessary.
02/24/15 11NITTTR, Chandigarh
12. Service Level Test Factor
Service level implies response time
based on the requirements.
Service level required will vary on the
requirements.
Example: Service level to process a
specific transaction, service level to
correct a programming error, service
level to install a change and service level
to respond to a request.
02/24/15 12NITTTR, Chandigarh
13. Security Test Factor
Security requirements should be
developed showing the relationship
between system resources and people.
Requirements should state all of the
available system resources subject to
control and then indicate who can have
access to those resources and for what
purposes.
02/24/15 13NITTTR, Chandigarh
14. Conduct a Requirements
Walkthrough
Requirements phase involves creativity ,
experience and judgment as well as a
methodology.
Walkthrough becomes a review process that
complements the objectives of the requirements
phase.
Team of skilled individuals can help the project
team in the development of the project solutions.
02/24/15 14NITTTR, Chandigarh
15. Establish Ground Rules
Walkthrough concept requires the
project people to make a presentation
explaining the functioning of the system.
Ground rules should be understood by
both the project team and the
walkthrough team:
Size and makeup of the walkthrough
team.
02/24/15 15NITTTR, Chandigarh
16. Establish Ground Rules
Responsibility of the walkthrough team
which is usually limited to
recommendations, comments and
questions.
Approximate length, time and location of
the walkthrough.
Confidentiality of information discussed
at the walkthrough.
02/24/15 16NITTTR, Chandigarh
17. Establish Ground Rules
Who will receive the result of the
walkthrough and how are those results
to be used?
02/24/15 17NITTTR, Chandigarh
18. Select Team/ Notify
Participants
Most common participants on a
walkthrough team include:
Information services project
manager/systems analyst.
Senior management with responsibilty
over the computerized areas.
Operations management.
User management
02/24/15 18NITTTR, Chandigarh
20. Project Presentation
Good walkthrough includes presentation
of the following:
Statements of the goals and objectives
of the projects.
List of any exceptions made by the
project team.
Discussion of the alternatives
considered.
02/24/15 20NITTTR, Chandigarh
21. Questions/Recommendations
Project presentation should be
interrupted with questions, comments
and recommendations as they occur to
the walkthrough team.
Appoint one individual as recorder for
the walkthrough. Recorder duty is
capture questions for which appropriate
answers are not supplied during the
walkthrough.
02/24/15 21NITTTR, Chandigarh