Network Security and Management

by Professor Brijendra Singh.

Systems Analysis and Design

by Professor Brijendra Singh.

Data Communication And Computer Networks

by Professor Brijendra Singh.

Quality Control And Reliability Analysis

by Professor Brijendra Singh

Tuesday, 31 March 2020

Feasibility Study

Feasibility Study

Feasibility is defined as the practical extent to which a project can be performed successfully. To evaluate the feasibility of the project feasibility study is performed. A feasibility study should be comparatively economical and fast. Estimation is made of whether the recognized user requirements may be satisfied using existing software and hardware technology. The result should notify the verdict of whether or not to go forward with an added comprehensive analysis.
It is important to find out the strengths and weaknesses of proposed project and present guidelines of activities which will improve a project and accomplish desired results. Feasibility study is used to review the project to find out the strengths and weaknesses of project. The nature and components of feasibility study depend mainly on the areas in which analyzed projects are implemented. The acronym TELOS refers to the five areas of feasibility such as: Technical, Economic, Legal, Operational, and Schedule. Technical feasibility is one of the most important and first study that must be conducted after a project has been identified.
For sustainable success of projects economic feasibility is an important aspect to consider. Therefore, project component, investment, reinvestment costs of system, and running costs for its operation were analyzed. The project team has to construct a systematic analysis of the legal issues surrounding the project. Operational feasibility study evaluates the project potential for success and schedule feasibility used to assess of how reasonable the project timetable is. These feasibility studies summarized as:  
Technical feasibility focused on gaining an understanding of the current technical resources of the organization and their applicability to the estimated needs of the proposed system. It is an assessment of the hardware and software and how it meets the requirement of the proposed system. For example: A space organization constructs a prototype to determine if a new type of spacecraft propulsion is technically feasible or not.
Economic feasibility demonstrates the net benefit of a proposed project for accepting or disbursing electronic funds, consider the benefits, costs to the organization, and the common user as a whole. For example: A software organization performs a study to determine if an innovative new software design would be cost competitive given the current cost of required resources, components, machines, technology, and effort.
Legal feasibility determines whether the proposed system conflicts with legal requirements. For example: A bank is considering introduce an innovative novel financial product. They begin with a feasibility study focused on all legal aspects such as regulatory risks and compliance.
Operational feasibility is a measure of how well a proposed system solves the problems, takes advantage of the opportunities acknowledged during scope definition, and how it satisfies the requirements identified in the requirements analysis of software development. For example: A data center investigates the feasibility of power self-adequacy using solar panels and battery systems with the network as a backup.
Schedule feasibility is a measure of how rational the project schedule is. For example: A software project is in the early planning phases with partial scope and no schedule when an executive announces to the world that the project will be completed by July. The project manager rapidly informs the executive that this is might be unfeasible. The executive requests that the project manager make it occur. The project manager responds by conducting a schedule feasibility assessment based on a list of requirements, out-of-scope items, and July deadline.















Product Quality VS. Process Quality




Product QualityVs. Process Quality

Software process used to create software product and achieve quality in software product within a given time and cost. In this chapter, software process quality and software product quality are discussed from several perspectives to see the relationship of software process quality and software product quality.

Because software more and more rule our world and becomes universal and embedded in almost everything we do. We have to make definite that software work in an enhanced way as we desire. The quality of software involves product and process quality. Process-oriented approaches deal with the organization of rules, standards, manuals, principles, guidelines, process definitions, and improvement of software quality processes. The high-quality software product is resulted from high-quality software development process. The absence of software process and product quality, increase troubles during the software development process. Process and product quality are process-driven approaches with detailed steps to achieve software development goals. The process and product quality consider requirement, design, development, and production. Quality assurance is a protective approach from occurring by providing methods and rules which prevents errors and defects from occurring. It starts in the software development process from the early phase of the software development lifecycle. It grants self-assurance to the user concerning the software development process and the software product. It is a systematic and planned pattern of all events essential to provide sufficient confidence that a software product conforms to recognized technical requirements.

Process and product quality declaration are very significant aspects in the development of software. Process and product quality assurance observe the software engineering processes and methods to guarantee software quality. It is the software process of confirming and verifying whether services and products meet the user requirement and expectation or not. The purpose of process and product quality assurance (PPQA) is to offer management and staff with purpose insight into processes and related work products. Process and product quality have become the key to success in the software development lifecycle. For the instance being we identify the fact that software measurement helps us to better evaluate, understand, and control the products, processes, and software projects from the various perspective of evaluating, controlling, tracking, forecasting, and understanding. A suitable measurement process can offer organizations to make improved and appropriate decisions to achieve success in software projects.


Software process quality contributes to software product quality to conform to the software requirement and user expectation using monitoring, reviewing, and evaluation of the software process. Software process impacts on the software product and its quality such as: usability, performance, reliability, security, availability, functionality, maintainability, and safety. Software process quality is having the highest efficiency and best utilization of all resources in software development. Software product quality is having the least defects and higher consumer satisfaction. 

Software process quality is related to how people develop the product. There are mainly effectiveness, efficiency, and predictability aspect of the software. Software product quality associated with the absence of defects in software. Various important quality attributes for software success are usability, efficiency, maintainability, portability, reliability, reusability, and availability. All these software quality totally depends on the quality of software process. 




Monday, 30 March 2020

Quality defined by various gurus

SOFTWARE QUALITY 

When the expression “Software Quality” is used, we usually think in terms of an excellent software product that fulfills our expectations. These expectations are based on the intended use. A number of models have been proposed for evaluation of software quality based on various characteristics

If we are to talk intelligently about the quality of a thing or the quality of the product, we must have in mind a clear picture of what we mean by quality. Quality defined by the various quality gurus in various ways, depending on the user perspective.
  •   Dr. Barry Boehm thinks of quality as Achieving high levels of user satisfaction, portability, maintainability, robustness, and fitness for use.

  •   Phil Crosby has created the definition with the currency because of its publication in his famous book “Quality is free”. He states that quality means “conformance to user requirements”.

  •   Tom McCabe, the software complexity specialist, de- fines quality as “High levels of user satisfaction and low defect levels, often associated with low complexity”.

  •   John Musa of Bell Laboratories states that quality means a combination of “low defect level, adherence of software functions to users needs, and high reliability”.

  • Traditionally, the quality of a product is defined in terms of its fitness of purpose. Although fitness of the purpose is a satisfactory definition of quality for hardware products, but it is not satisfactory for software products.