Monthly Archives: December 2016

V-Model Testing (WEEK 12)

The meaning of V-Model is Verification and Validation model. This model has the shape of V, the V-shape model is a path of executions which is followed in a logical order. Each phase must be completed before the next phase begins.When we have test a product must be planned in parallel with the corresponding phase in V-Model. First is very important to understand the Verification and Validation techniques before we learn about V-Model. Verification testing technique is done without executing any code and Validation testing technique is done by executing the code, Verification is a static analysis technique, Validation is a dynamic analysis technique. Both techniques are par of the V-Model. There are 7 phases that take place in V-Model. Here I’m listing the seven phases of V-Model: Requirement Specification, Preliminary Design, Detailed Design, Coding, Unit Testing, Integration Testing and System Testing. We usually apply V-Model for small to medium sized projects where requirements are clearly defined and fixed.

This design shows the sequential path of execution process of V-Model.

In this paragraph I’m covering the pros and cons of V-Model. Some of the pros are: Development and progress is very organized. This model works well for smaller and medium sized projects. Another positive factor is easy to manage as each phase of this model. Some of the cons of V-Model are : V-Model doesn’t work for big and complex projects. The V-Model is not suitable if the requirements are not compatible.

To learn more about V-Model Testing please visit the website below.

Citation

http://www.softwaretestinghelp.com/what-is-stlc-v-model/

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Pass by object reference

Python’s passes parameters by object reference. What does that mean? Let’s first explore the pass-by-reference and pass-by-value parameter passing paradigms.

Pass-by-reference:

In pass-by-reference, the variable is passed directly into the function.

capture

The new variable points to the same object as the old variable. We just created a new reference to point to the same object.

Pass-by-value:

In pass-by-value, the function receives a copy of the argument objects passed to it and is stored in a new location in memory.

The new variable points to a different object (a copy of the old object).

Pass-by-object-reference:

Python is different than languages like Java(pass-by-value) in that it supports both pass-by-value and pass-by-reference. Variable in Python are not like the variable we know from other programming languages: variables in Python are object references. The value stored in a python variable is the memory address of the value, not the actual value. It is the memory address that is passed into a function, not the actual value. This means Python’s functions support call by object-reference semantics.

Based on the type of the object referred to, the actual call semantics used will differ. If the variable refers to a mutable value, call-by-reference is used. If variable refers to a immutable value, call-by-value is used.

References:

http://robertheaton.com/2014/02/09/pythons-pass-by-object-reference-as-explained-by-philip-k-dick/
Head First Python, 2nd Edition by Paul Barry

From the blog Software Testing – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 17:09:00

Ankit Gupta
Week – 12

Software Technical Reviews

A review process can be defined as a critical
evaluation of an object. It includes techniques such as walkthroughs. The objective
of the reviews is to search out design weaknesses, faulty designs, or designs
which may be cost drivers. Problems can often be identified early from the data
item submissions, and attempts can be made to clarify these problems on a case-by-case
basis before the review to avoid major problems and surprises at the meetings. Program includes a functioning requirement
Research and Development. Technical reviews would be basic to monitor growth. Program includes a functioning requirement but
no Research and Development. The system is mostly commercial off the shelf gear.
It could include some non-developmental items and limited trainer unique
equipment like brackets or cabinets to mount the COTS equipment or maybe some
panels built to simulate to body of weapon. Limited technical reviews held in
conjunction with scheduled progress reviews would be necessary. Program includes a performance
specification but no Research and Development. The system is all commercial off the shelf
equipment. It could include some non-developmental items but no trainer
unique equipment. If the software were complex, then limited technical reviews
held in conjunction with scheduled progress reviews would be necessary. If the
software is not complex, then only progress reviews might be necessary. Program includes a functioning requirement and no Research and
Development. The Government is mostly concerned with schedule in this case as implementation
is already determined and the contract type will be fixed price. Scheduled
progress reviews would be all that is basic.