kailash k mishra

• Jun 19th, 2007

 

steps::
1)since there are lots of fields, carry out validation checks for the fields.(int ,float..)
2)spend more time on QC activities rather than QA activities.
3)check for the database connectivity since data is very complex and comes from different paths.
4)try to figure out which fields are mandatory and display appropriate messages if they are left blank.
5)since the data has some interdependency between them check out whether its being truncated or not.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 19th, 2009

 

This could be a costly and time-consuming endeavor.  Depending on the software development model used in our company, the project's value to our company and the amount of time we have to prepare and test, I would do all or a combination of the following:

1) Require a great deal of integration and system testing throughout the software development life cycle (SDLC).

2) Insist that expert users are involved in the creation of functional requirements.
 
3) If possible, work closely with persons who define requirements throughout the SDLC.

3)  Identify all interdependent high level system components.

4) Identify all of the functional areas within each component. 

5) Identify all tasks users can perform within each functional area.

6) Produce wireframes of pages within each functional area.

7) Produce work-flow diagrams that illustrate the various paths that users can take throughout the system.  These diagrams should cover all inputs, outputs, and decision points.   Business logic should be clearly expressed by this documentation. 

8) Assign integrated functional areas to individual testers and make sure they understand the interdependencies between their own and other areas.

9) Produce prototype or mock-up and conduct usabiity tests with expert users to gain valuable feedback.