Lab evaluation 4 – Pooja pande

1. The clauses of ISO 9001 and ISO 9126 standards applicable for the case – From ISO 9126 following features are added –

-fault tolerance




From ISO 9001 following clauses are added –
1.Documentation Requirements
2.Management Responsibility
3.Customer Focus
4.Quality Policy
6.Resource Management
7.Validation of processes for production and service provision
8.Identification & Traceability
9.Measurement Analysis & Improvement
10.Customer Satisfaction
11.Internal Audit
12.Monitoring and measurement of processes
13.monitoring and measurement of product
14.Control of nonconforming product

2. Software configuration management process used for build and process management
Traditional SCM process is looked upon as the best fit solution to handling changes in software projects. Traditional SCM process identifies the functional and physical attributes of a software at various points in time and performs systematic control of changes to the identified attributes for the purpose of maintaining software integrity and traceability throughout the software development life cycle.

The SCM process further defines the need to trace the changes and the ability to verify that the final delivered software has all the planned enhancements that are supposed to be part of the release.

The traditional SCM identifies four procedures that must be defined for each software project to ensure a good SCM process is implemented. They are

1. Configuration Identification

Software is usually made up of several programs. Each program, its related documentation and data can be called as a”configurable item”(CI). The number of CI in any software project and the grouping of artifacts that make up a CI is a decision made of the project. The end product is made up of a bunch of Cis. The status of the CIs at a given point in time is called as a baseline. The baseline serves as a reference point in the software development life cycle. Each new baseline is the sum total of an older baseline plus a series of approved changes made on the CI

A baseline is considered to have the following attributes

Functionally complete
A baseline will have a defined functionality. The features and functions of this particular baseline will be documented and available for reference. Thus the capabilities of the software at a particular baseline is well known.

Known Quality
The quality of a baseline will be well defined. i.e. all known bugs will be documented and the software will have undergone a complete round of testing before being put define as the baseline.

Immutable and completely recreatable
A baseline, once defined, cannot be changed. The list of the CIs and their versions are set in stone. Also, all the CIs will be under version control so the baseline can be recreated at any point in time.

2. Configuration Control
The process of deciding, co-ordinating the approved changes for the proposed CIs and implementing the changes on the appropriate baseline is called Configuration control.
It should be kept in mind that configuration control only addresses the process after changes are approved. The act of evaluating and approving changes to software comes under the purview of an entirely different process called change control.

3. Configuration Status Accounting
Configuration status accounting is the bookkeeping process of each release. This procedure involves tracking what is in each version of software and the changes that lead to this version.
Configuration status accounting keeps a record of all the changes made to the previous baseline to reach the new baseline.

4. Configuration Authentication
Configuration authentication (CA) is the process of assuring that the new baseline has all the planned and approved changes incorporated. The process involves verifying that all the functional aspects of the software is complete and also the completeness of the delivery in terms of the right programs, documentation and data are being delivered.
The configuration authentication is an audit performed on the delivery before it is opened to the entire world.

3. Features to be tested –

1.Reliability- Software Reliability is the probability that software will work properly in specified environment and for given time.

Probability = Number of cases when we find failure / Total number of cases under consideration
-Test cases and test procedure for each software module
-Time constraints are handled by applying fix dates or deadlines to the tests to be performed
-Mean Time to Failure (MTTF) , Mean time Between failure (MTBF). Mean time to repair(MTTR) are calculated.

2.Compatibility – Here non-functional parts of software are tested.
-Computing capacity of Hardware Platform
-Operating systems; Linux, Windows, etc.
-Other System Software (Web server, networking/ messaging tool, etc.)
-Browser compatibility (Chrome, Firefox, Netscape, Internet Explorer, Safari, etc.)

3.Usability – For usability testing, people of various age groups are asked to access the web frame work and the response in mainly four areas is measured-
-Efficiency — How much time, and how many steps, are required for people to complete basic tasks? (For example, find something to buy, create a new account, and order the item.)
-Accuracy — How many mistakes did people make?
-Recall — How much does the person remember afterwards or after periods of non-use?
-Emotional response — How does the person feel about the tasks completed? Is the person confident, stressed? Would the user recommend this system to a friend?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: