All the requirements mentioned in SRS documents are addressed in this phase and work in direction of designing the solution. High level design takes the second place in SDLC, wherein there is a high probability of finding bugs.
Therefore high level/design must be verified as next step stop in early testing.
If bug goes undetected in high level design phase, then its cost of fixing increases with every phase.
High level design is divided in three parts -
Data design.
Architectural design.
Interface design.
i) Data design :
It creates model of a data that is represented at a high level of abstraction.
At the program component level, the design of data structure and associated algorithms required to manipulate them is essential to create high quality applications.
Verification of Data Design.
Check for sizes of data structure have been estimated properly.
Check the provisions of overflow.
Check consistency of data format with requirements.
Check data usage is consistent with its declaration.
Check for relationship among data object in data dictionary.
Check consistency of database and data warehouse with requirement specified in SRS.
ii) architectural design :
- it focuses on representation of structure of s/w component, their properties and interactions.
Verification of architectural design :
check for every functional requirement from SRS is included in design.
check all execption handling conditions.
Verify process of transform mapping and transaction mapping transition from requirement model to architectural design.
Check functionality of each module according to requirement specified.
Check interdependence and interface between modules.
Tester should also verify for coupling and cohesion. A good design should have low coupling and high cohesior.
iii) interface design :
- It creates effective communication medium between interfaces of different software modules, interfaces between
software systems and any other external entity and interface between user and software system.
Verification of interface design :
Check all interfaces between modules according to architectural design.
Check all interfaces between software and non human producer and consumer information.
Check interfaces between human and computer.
Check interfaces for their consistency.
Check response time for all interface within required ranges.
Check for help facility and error handling messages.
For typed command interactions, check mapping between every menu option and their corresponding command.
iv) Verification of low level design :
In low level design a detailed design of modules and data are prepared such that an operational software is ready. For this SOD is preferred where all modules and their interfaces are defined.
For verification of low level design SRS and SDD of individual modules are referred.
4 verify SRS of individual module.
4 verify SDD of each individual module.
4 in low level design, data structure, interfaces and algorithms are represented by design notations, verify the consistency of every item with their design notations.
and 2 others joined a min ago.
teamques10
★ 68k