Explore topic-wise InterviewSolutions in .

There are two types of software sizes:

Technical Size:

• The most technical sizing method is measured in terms of Line of Code per technology.
• The number of lines include in functions, files, classes and tables.
• These are computed with BACKFIRING the Function POINTS.

FUNCTIONAL Size:

• The very common function size is Function Point Analysis.
• FPA is all about measuring the software deliverables.
• FPA is based on the requirements of the user and presents accurate REPRESENTATION of developer and estimator.
• FPA reflects the functionality that is delivered to the client.
• FPA involves in identifying and weighting of INPUTS, outputs and data storage.

There are two types of software sizes:

Technical Size:

Functional Size:

• Implementing proper Application Architecture Practices.
• DESIGN compliance of multi-layer components and their functionality.
• Input validation, Cross SITE Scripting best practices
• Proper HANDLING of error and exceptions.
• Proper ACCESS controls to the program and system functions.

• Practices of implementing Application ARCHITECTURE.
• Interactions with REMOTE resources should be appropriate.
• Proper management of memory, network and disk space.
• Best coding practices.
• Proper and appropriate DATA access performance and management.
• Appropriate compliance with Object Oriented and Structured Programming practices.
• Appropriate compliance with SQL Programming best practices.

The following are the SE Practices and attributes:

• CODING practices / standards.
• Practices of Application Architecture.
• Determining the complexity of the algorithms.
• Determining the multi-layer design compliance.
• Ratio of component and PATTERN usability.
• Determining the software to avoid the PATTERNS which would lead to unexpected results / behaviors.
• Determination of data integrity and CONSISTENCY.

The following are the SE Practices and attributes:

SFQ is pertaining to conformance to the functional requirements. It is measured by the level of END user satisfaction.

The usability and the intuitiveness and RESPONSIVENESS of the use CASES are referred, so as to determine the simplicity / complexity of the operations. SFQ compliances with the original design, and DESIRED testability.

Example: Voice of the Customer can be compared with the level of intuitiveness and responsiveness to measure the quality.

SFQ is pertaining to conformance to the functional requirements. It is measured by the level of end user satisfaction.

The usability and the intuitiveness and responsiveness of the use cases are referred, so as to determine the simplicity / complexity of the operations. SFQ compliances with the original design, and desired testability.

Example: Voice of the Customer can be compared with the level of intuitiveness and responsiveness to measure the quality.

Quality Assurance:

• Focused on planning, documentation and agreeing certain guidelines that ensures quality.
• The outcomes of Quality Assurance are quality plans, inspection plan, test plan.
• QA is to PREVENT defects from entering into SOLUTIONS.

Quality Control:

• Includes the activities that are designed to determine the level of quality.
• QC is a reactive means which measures and MONITORS the quality
• Includes operational activities and techniques to meet the quality NEEDS. 
• QC involves in verifying the desired quality LEVELS.

Quality Assurance:

Quality Control:

• Project Manager: Controls the software ENGINEERING work performed during the software development.
• Designer: Assists the team to complete the overall design of the software project implementation.
• Technical Advisors: Supports to IMPLEMENT all technical aspects and imposes the quality PRACTICES.
• Checkers/Testers: Performs the complete testing of the software project at various levels.
• Quality ASSURANCE Manager: Conforms the software product is as PER the expected result with proper guidance and co-ordination with the development team.

• A PARADIGM that is Goal Question centric.
• A method that control the overall RISK.
• QUALITY Control that involves Plan, Perform, Check, ACTION Model.
• Complete Software Quality Control.
• Software Development Method that INVOLVE the Spiral Model.

• Quantifying the dimensions of the software product, to what extent the RATE of the product is met.
• Qualitative and quantitative approaches provide the aggregate view of the product.
• Linear continuum need to be supplemented by the identification of the critical programming bugs.
• CONSEQUENCES that might lead to CATASTROPHIC outages need to be properly identified.
• The critical application characteristics measurement involves the STRUCTURAL ATTRIBUTE measurement of the application architecture, coding, in-line documentation.

• Clear PURPOSE of the product. All documentation must be clearly written.
• Completeness to the fullest DEVELOPMENT of the product.
• Only needed information and minimum lines of code should present. It is important as the memory is limited.
• The software product should be portable, so that computers of various configurations would support the EXECUTION of the product.
• Product should be maintainable, so that the UPDATING activity can be CONTINUED throughout the life time of the software product.

• QUALITY being part of every day operations, is the internal impact.
• Quality BECOMES as a part of setting and managing the OBJECTIVES, practices.
• The open up of operations to customer AUDITS, is the external impact.
• Procedures and record-keeping improve dramatically.
• The implementation of this standards will obviously takes the work to keep audits and the appropriate follow-ups fluent.

• Functionality: FUNCTIONS that SATISFIES the specified requirements.
• Reliability: A set of attributes that are CAPABLE of software maintenance under specified conditions.
• Usability: A set of attributes that is capable of effort bearing on individual’s PERFORMANCE.
• Efficiency: A set of attributes that are capable of balancing the relationship between performance of software and the resources used.
• Maintainability: A set of attributes that are capable of bearing the effort required for specific MODIFICATIONS.
• Portability: A set of attributes those are capable to bear on the ability of the software to be transferred on another environment.

• TRANSCENDENTAL VIEW: QUALITY can be recognized and not DEFINED.
• User View: Quality as suitable for the needs.
• PRODUCT View: Quality as related to the inherent characteristics of the product.
• Value-based View: Quality is dependent on the number of customers those who are willing to pay for the software product.
• Development View: Quality that is in conformance to specification.

• FUNCTIONALITY: To determine the REQUIRED functionality in the software
• USABILITY: To determine the ease of the software is to use.
• Maintainability: To determine whether the modifications of the software can be made.
• Efficiency: To determine whether the software is efficient.
• PORTABILITY: To determine whether the software can be transferred to another environment.
• Reliability: To determine the reliability of the software as per the CLIENT’s needs.

Following are the BENEFITS of SQC:

• Increased productivity of the DEVELOPMENT team.
• Improved PRODUCT Quality: Test statistics and defect tracking are more precise and up to date.
• DECREASED re-work costs as the detection of defects are found earlier in the software project development lifecycle in every stage.
• Increased confidence levels in existing product management and future product development.
• Increased credibility as the software PRODUCED will be highly qualitative.

Following are the benefits of SQC:

Software Quality Control Nomenclature:

• Verifying: comparing the code predictions
• Validating: Comparing the prediction of code with test data
• Version Testing: Comparing OUTPUT of the current version with output of the PREVIOUS version
• Installation Testing: Comparing the result with newly installed code to the SAMPLE result code
• Development Code: Code TESTED only by the software developer.
• Alpha Code: Testing of the software product internally by selected users.
• BETA Code: Code testing internally by a large numbers of users.
• Released Code: Well tested and documented code that is officially distributed.

Software Quality Control Nomenclature:

The following are the activities of project control:

• Verify the integrity of the DATABASE files.
• Check the transcription ERRORS while inputting and referencing the data.
• Verify the data CONSISTENCY.
• Perform the internal review of documents.
• Perform the COMPLETENESS check.
• Compare the existing results with PREVIOUS results.

The following are the activities of project control:

Quality Control Plan is to analyze the operations needed for the fulfillment of the software project REQUIREMENTS. Quality Control Plan ensures all the specifications are met and the quality of the product is MAINTAINED.

The characteristics of the Quality Plan are as follows:

• Consistent: The plan should adhere to the GUIDELINES and the specific standards.
• Complete: The plan should include project requirements, features and essentially the project plan DOCUMENTATION.
• Clear: The plan should be transparent to the DEVELOPER and also to all the stake holders of the project requirements.
• Correct: The details of the project should be very clear to all stakeholders about project delivery date / postponement / cancellation.

Quality Control Plan is to analyze the operations needed for the fulfillment of the software project requirements. Quality Control Plan ensures all the specifications are met and the quality of the product is maintained.

The characteristics of the Quality Plan are as follows:

The ACTIVITIES that are involved in Software Quality Control are Reviews and TESTING.

Reviews:

1. REVIEW of requirement.
2. Review of design.
3. Review of CODE.
4. Review of deployment plan .
5. Review of test plan.
6. Review of test cases.

Testing: 

1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing

The activities that are involved in Software Quality Control are Reviews and Testing.

Reviews:

Testing: 

A set of ACTIVITIES for ensuring the quality of the software product is known as Software Quality Control. The focus is on IDENTIFYING the defects in the original products produced.

It is LIMITED only for Testing phase of SDLC. Software Quality Control is governed by Software Quality ASSURANCE. Software Quality Control is detection oriented. The SCOPE relates to specific product.

A set of activities for ensuring the quality of the software product is known as Software Quality Control. The focus is on identifying the defects in the original products produced.

It is limited only for Testing phase of SDLC. Software Quality Control is governed by Software Quality Assurance. Software Quality Control is detection oriented. The scope relates to specific product.