The document discusses the Capability Maturity Model (CMM) and its impact on software quality. It describes the five levels of the CMM and the key process areas within each level. The CMM is designed to help software organizations improve their processes by advancing through the maturity levels. Advancing to higher levels involves institutionalizing effective software engineering practices. The document also presents a problem statement about software projects facing cost overruns and quality issues. It reviews literature on the CMM and outlines a project conversion process framework to assess CMM implementation.
Assessment of cmm and its impact on software qualityIAEME Publication
The document discusses the Capability Maturity Model (CMM) and its impact on software quality. CMM provides guidance for software organizations to gain control of their processes and evolve toward excellence. It consists of 5 maturity levels, with each level comprised of key process areas that must be addressed to improve process capability. Achieving a higher maturity level indicates the organization is better able to manage projects and deliver high quality software. The document outlines the structure of CMM and describes the key process areas that define each maturity level. Overall CMM aims to help organizations implement disciplined, measured software development processes to continuously improve quality.
Lightweight processes are beginning to replace more formal methods. The motivation for this transition is based on many factors. The Internet, time to market, cost reduction, quality increases, market pressures, as well as the popularization of these programming methods. This series of articles will investigate the various lightweight methods, their impact on the management of software development projects and the processes by which managers can determine the appropriateness and usefulness of the various processes. The definition of a lightweight Process is more difficult than it would first appear. This article outlines the foundations of a heavyweight process and describes the appropriate pieces that can be converted to lightweight.
Project monitoring and control measures in cmmiijcsit
Project monitoring and control process is an important process in developing any computer information
system. Monitoring and Control provides an understanding of the project’s progress so that when the
project deviates significantly from the plan appropriate corrective actions can be taken. This research will
identify general measures for the specific goals and its specific practices of Project Monitoring and
Control Process Area in Capability Maturity Model Integration (CMMI). CMMI is developed in USA by
Software Engineering Institute (SEI) in Carnegie Mellon University. CMMI is a framework for assessment
and improvement of computer information systems. The procedure we used to determine the measures is to
apply the Goal Questions Metrics (GQM) approach to the two specific goals and its ten specific practices
of Project Monitoring and Control Process Area in CMMI.
The document provides solutions to exercises from the textbook "Software Engineering 9th edition". It begins with a preface explaining that the solutions manual is intended to help teachers mark student homework and that answers are only provided for about half the exercises. For exercises without answers provided, the preface gives reasons such as the answers being in the text, there being multiple valid solutions, or the questions being intended to stimulate discussion. The solutions provided are meant as a guide and teachers should reward students' credible answers that show thought and knowledge.
An Agile Software Development FrameworkWaqas Tariq
Agility in software projects can be attained when software development methodologies attain to external factors and provide a framework internally for keeping software development projects focused. Developer practices are the most important factor that has to cope with the challenges. Agile development assumes a project context where the customer is actively collaborating with the development team. The greatest problem agile teams face is too little involvement from the customer. For a project to be agile, the developers have to cope with this lack of collaboration. Embracing changing requirements is not enough to make agile methods cope with business and technology changes. This paper provides a conceptual framework for tailoring agile methodologies to face different challenges. The framework is comprised of three factors, namely, developer practices, customer collaboration, and predicting change
The Capability Maturity Model (CMM) is a framework developed by the Software Engineering Institute (SEI) to help organizations improve their software development process in a measurable way. The CMM describes 5 levels of process maturity from initial to optimized. It was created by the SEI, a research center of the US Department of Defense, to address software quality and process issues important to defense projects. While originally created for the DoD, the CMM has been widely adopted as an industry standard.
Process-Centred Functionality View of Software Configuration Management: A Co...theijes
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
Integrated Project Management Measures in CMMIijcsit
Project management is quite important to execute projects effectively and efficiently. Project management
is vital to projects success. The main challenge of project management is to achieve all project goals,
taking into consideration time, scope, budget constraints, and quality. This paper will identify general
measures for the two specific goals and its ten specific practices of Integrated Project management Process
Area in Capability Maturity Model Integration (CMMI). CMMI is a framework for improvement and
assessment of computer information systems. The method we used to define the measures is to apply the
Goal Questions Metrics (GQM) paradigm to the two specific goals and its ten specific practices of
Integrated Project management Process Area in CMMI.
Assessment of cmm and its impact on software qualityIAEME Publication
The document discusses the Capability Maturity Model (CMM) and its impact on software quality. CMM provides guidance for software organizations to gain control of their processes and evolve toward excellence. It consists of 5 maturity levels, with each level comprised of key process areas that must be addressed to improve process capability. Achieving a higher maturity level indicates the organization is better able to manage projects and deliver high quality software. The document outlines the structure of CMM and describes the key process areas that define each maturity level. Overall CMM aims to help organizations implement disciplined, measured software development processes to continuously improve quality.
Lightweight processes are beginning to replace more formal methods. The motivation for this transition is based on many factors. The Internet, time to market, cost reduction, quality increases, market pressures, as well as the popularization of these programming methods. This series of articles will investigate the various lightweight methods, their impact on the management of software development projects and the processes by which managers can determine the appropriateness and usefulness of the various processes. The definition of a lightweight Process is more difficult than it would first appear. This article outlines the foundations of a heavyweight process and describes the appropriate pieces that can be converted to lightweight.
Project monitoring and control measures in cmmiijcsit
Project monitoring and control process is an important process in developing any computer information
system. Monitoring and Control provides an understanding of the project’s progress so that when the
project deviates significantly from the plan appropriate corrective actions can be taken. This research will
identify general measures for the specific goals and its specific practices of Project Monitoring and
Control Process Area in Capability Maturity Model Integration (CMMI). CMMI is developed in USA by
Software Engineering Institute (SEI) in Carnegie Mellon University. CMMI is a framework for assessment
and improvement of computer information systems. The procedure we used to determine the measures is to
apply the Goal Questions Metrics (GQM) approach to the two specific goals and its ten specific practices
of Project Monitoring and Control Process Area in CMMI.
The document provides solutions to exercises from the textbook "Software Engineering 9th edition". It begins with a preface explaining that the solutions manual is intended to help teachers mark student homework and that answers are only provided for about half the exercises. For exercises without answers provided, the preface gives reasons such as the answers being in the text, there being multiple valid solutions, or the questions being intended to stimulate discussion. The solutions provided are meant as a guide and teachers should reward students' credible answers that show thought and knowledge.
An Agile Software Development FrameworkWaqas Tariq
Agility in software projects can be attained when software development methodologies attain to external factors and provide a framework internally for keeping software development projects focused. Developer practices are the most important factor that has to cope with the challenges. Agile development assumes a project context where the customer is actively collaborating with the development team. The greatest problem agile teams face is too little involvement from the customer. For a project to be agile, the developers have to cope with this lack of collaboration. Embracing changing requirements is not enough to make agile methods cope with business and technology changes. This paper provides a conceptual framework for tailoring agile methodologies to face different challenges. The framework is comprised of three factors, namely, developer practices, customer collaboration, and predicting change
The Capability Maturity Model (CMM) is a framework developed by the Software Engineering Institute (SEI) to help organizations improve their software development process in a measurable way. The CMM describes 5 levels of process maturity from initial to optimized. It was created by the SEI, a research center of the US Department of Defense, to address software quality and process issues important to defense projects. While originally created for the DoD, the CMM has been widely adopted as an industry standard.
Process-Centred Functionality View of Software Configuration Management: A Co...theijes
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
Integrated Project Management Measures in CMMIijcsit
Project management is quite important to execute projects effectively and efficiently. Project management
is vital to projects success. The main challenge of project management is to achieve all project goals,
taking into consideration time, scope, budget constraints, and quality. This paper will identify general
measures for the two specific goals and its ten specific practices of Integrated Project management Process
Area in Capability Maturity Model Integration (CMMI). CMMI is a framework for improvement and
assessment of computer information systems. The method we used to define the measures is to apply the
Goal Questions Metrics (GQM) paradigm to the two specific goals and its ten specific practices of
Integrated Project management Process Area in CMMI.
This document discusses software configuration management and describes its key activities and importance. It covers configuration management planning, change management, version management, and the use of tools to support the configuration management process. Effective configuration management is important for managing evolving software systems and controlling the costs of system changes. It aims to manage all products of the software development process, including specifications, designs, code, and documentation.
A Novel Method for Quantitative Assessment of Software QualityCSCJournals
This paper deals with quantitative quality model that needs to be practiced formally through out the software development life cycle at each phase. Proposed quality model emphasizes that various stakeholders need to be consulted for quality requirements. The quality goals are set through various measurements and metrics. Software under development is evaluated against expected value of set of metrics. The use of proposed quantitative model is illustrated through a simple case study. The unaddressed quality attribute reusability in ISO 9126 is also discussed.
CMMI (Capability Maturity Model Integration) is a proven industry framework to improve product quality and development efficiency for both hardware and software
The modern business environment requires organizations to be flexible and open to change if they are to gain and retain their competitive age. Competitive business environment needs to modernize existing legacy system in to self-adaptive ones. Reengineering presents an approach to transfer a legacy system towards an evolvable system. Software reengineering is a leading system evolution technique which helps in effective cost control, quality improvements and time and risk reduction. However successful improvement of legacy system through reengineering requires portfolio analysis of legacy application around various quality and functional parameters some of which includes reliability and modularity of the functions, level of usability and maintainability as well as policy and standards of software architecture and availability of required documents. Portfolio analysis around these parameters will help to examine the legacy application on quality and functional gaps within the application [1].
This document outlines an asset management maturity continuum that progresses from reactive to proactive approaches. It shows increasing levels of optimization from minimal performance tracking up to enterprise-wide asset management integration. Key aspects that progress along the continuum include governance, systems/technology, processes, people/performance measures. The goal is to move from "fix it after it fails" approaches to preventative, predictive and reliability-focused asset management.
Because of my role as Lector Directing ICT sources and services at Hanze University Groningen I have developed a lecture about the CMMi for services quality improvement philosophy. This will help to improve the quality of your ICT service and the competences of you professionals. Special in cases of sourcing projects.
This document discusses the impact of aspect-oriented programming (AOP) on software maintainability based on a literature review and case studies. It summarizes several case studies that measured maintainability metrics like coupling, cohesion, and separation of concerns in object-oriented (OO) systems versus aspect-oriented (AO) systems. The studies found that AO systems generally had less coupling between components, higher separation of concerns, and were more changeable and maintainable than equivalent OO systems. The document also outlines various software metrics that have been used to measure maintainability attributes in AO systems like cohesion, coupling, size, and changeability.
Ian Sommerville, Software Engineering, 9th Edition Ch2Mohammed Romi
This document summarizes key aspects of software processes and models. It discusses the basic activities involved in software development like specification, design, implementation, validation and evolution. It describes process models like waterfall, incremental development and reuse-oriented processes. The waterfall model involves sequential phases while incremental development interleaves activities. Validation includes testing stages from unit to system level. The document also covers designing for change and evolution.
The document provides an overview of CMMI (Capability Maturity Model Integration) version 1.3. It discusses the evolution of CMMI from combining three source models, the coverage of systems engineering, software engineering and integrated product development. It describes the process areas and functional categories in CMMI 1.3 and how they are organized. It also explains the concept of levels in CMMI which characterize process improvement from an ill-defined state to a state of quantitative management.
The document discusses the Capability Maturity Model (CMM), which is used to assess the maturity of an organization's software development processes. It describes the five maturity levels from Initial to Optimizing. At each level, processes become more rigorously defined, measured, and controlled. Level 1 is chaotic with no standard processes, while Level 2 introduces basic management processes. Level 3 establishes standardized processes across projects, and Level 4 measures process quality quantitatively. Level 5 continuously improves processes using data to optimize productivity and quality.
Configuration management involves change management, version management, system building, and release management. It ensures changes to software systems are managed and tracked. Version management tracks different versions of components to prevent interference. System building compiles components into executable systems. Release management prepares software for distribution and tracks released versions.
This document discusses a study that aimed to develop and validate an instrument to measure critical success factors for Enterprise Resource Planning (ERP) system implementations. The study defines 12 constructs related to ERP implementation success. It then describes the methodology used, which involved developing measurement scales for each construct and testing them on a survey of 53 organizations in Australia. The results validated a 65-item instrument measuring seven dimensions of ERP implementation. The document argues this model provides a valuable tool for researchers and practitioners to assess ERP implementation projects.
Software Engineering Past Papers (Short Questions)MuhammadTalha436
1. SWOT analysis is a framework for identifying internal and external factors that can impact a project, product, place or person. It analyzes strengths, weaknesses, opportunities, and threats.
2. Software refactoring is changing software code without altering external behavior to improve internal structure.
3. An embedded system is a programmed system within a larger mechanical or electrical system, often with real-time computing constraints and a dedicated function.
Many software organizations have moved from traditional methods for software development, such as waterfall method to usage of agile methods. Agile methods are used especially in software development and are constantly refurbishing and improving initial plans along the way. In software development the systems usually require frequent changes during the development process. This method is very suitable for small project and organizations, but it is very hard to implement it in large organizations with large projects and teams. This paper
aims to identify weaknesses of two existing scrum frameworks used for large organizations and to present proposed hybrid framework scaled from both existing frameworks. It’s highlighting the importance of predefined life cycle of teams, which is key factor in achieving better timeline and to avoid mistakes that affects the time of release deployment.
Quality is defined as the degree of goodness of a product or service as perceived by customers. Software quality refers to the totality of features and characteristics of software that bear on its ability to satisfy needs. There are various views of quality including the transcendent view, product-based view, value-based view, manufacturing view, and user-based view. Quality is measured using metrics that are linked to quality criteria and can objectively determine the level of a given criterion. Software quality measurement faces issues like quality being non-absolute and multidimensional.
The document discusses several topics related to software project management including risk management, managing people, and teamwork. It describes the key activities of a project manager including planning, risk assessment, people management, reporting, and proposal writing. Specific risks at the project, product, and business levels are defined and strategies for risk identification, analysis, planning, monitoring, and mitigation are outlined. Effective people management is also emphasized, including motivating team members through satisfying different human needs and personality types. A case study demonstrates how addressing an individual team member's motivation issues can improve project outcomes.
This document discusses software processes and models. It covers the following key points:
1. Software processes involve activities like specification, design, implementation, validation and evolution to develop software systems. Common process models include waterfall, incremental development and reuse-oriented development.
2. Processes need to cope with inevitable changes. This can involve prototyping to avoid rework or using incremental development and delivery to more easily accommodate changes.
3. The Rational Unified Process is a modern process model with phases for inception, elaboration, construction and transition. It advocates iterative development and managing requirements and quality.
https://www.mudassiriqbal.net/project-management-terms-and-concepts
There are many concepts and definitions which require special attention by all PMP Aspirants as the terminologies are largely used interchangeably in the real world.
This document discusses key topics in systems engineering, including:
1) Systems engineering involves procuring, designing, implementing, and maintaining sociotechnical systems that include both technical and human elements.
2) Software systems are part of broader sociotechnical systems and software engineers must consider human, social, and organizational factors.
3) Sociotechnical systems have emergent properties that depend on the interactions between system components and cannot be understood by examining the components individually.
Software re-engineering is a process of examining and altering a software system to restructure it and improve maintainability. It involves sub-processes like reverse engineering, redocumentation, and data re-engineering. Software re-engineering is applicable when some subsystems require frequent maintenance and can be a cost-effective way to evolve legacy software systems. The key advantages are reduced risk compared to new development and lower costs than replacing the system entirely.
Design and development of an automotive vertical doors opening system avdosiaemedu
The document describes the design and development of an automotive vertical doors opening system (AVDOS). The proposed system aims to overcome some drawbacks of existing vertical door designs by allowing easier access without requiring side movement. The system uses two hinges, gears, and a gas spring. The hinges are designed to open the door by swinging away from the vehicle. A small vertical push activates the gas spring, which moves the hinge and causes the gears to provide a slight outward movement to clear the door frame. Testing in CAD software validated that the system provides access without hard pushing or slamming doors. The system offers a safer, easier to use, and lower cost alternative to existing vertical door designs.
Towards better control over the distribution of subsidized commoditiesiaemedu
This document summarizes an article from the International Journal of Computer Engineering and Technology. The article presents a mobile-based solution to tackle the problem of fairly and transparently distributing subsidized food in Egypt. The proposed solution provides visibility and control over the distribution process using mobile technologies. It introduces a better mechanism to reduce leakage in the current subsidy system. The solution architecture is discussed, including logical and layered views. Key requirements like usability and minimizing corruption are also summarized.
This document discusses software configuration management and describes its key activities and importance. It covers configuration management planning, change management, version management, and the use of tools to support the configuration management process. Effective configuration management is important for managing evolving software systems and controlling the costs of system changes. It aims to manage all products of the software development process, including specifications, designs, code, and documentation.
A Novel Method for Quantitative Assessment of Software QualityCSCJournals
This paper deals with quantitative quality model that needs to be practiced formally through out the software development life cycle at each phase. Proposed quality model emphasizes that various stakeholders need to be consulted for quality requirements. The quality goals are set through various measurements and metrics. Software under development is evaluated against expected value of set of metrics. The use of proposed quantitative model is illustrated through a simple case study. The unaddressed quality attribute reusability in ISO 9126 is also discussed.
CMMI (Capability Maturity Model Integration) is a proven industry framework to improve product quality and development efficiency for both hardware and software
The modern business environment requires organizations to be flexible and open to change if they are to gain and retain their competitive age. Competitive business environment needs to modernize existing legacy system in to self-adaptive ones. Reengineering presents an approach to transfer a legacy system towards an evolvable system. Software reengineering is a leading system evolution technique which helps in effective cost control, quality improvements and time and risk reduction. However successful improvement of legacy system through reengineering requires portfolio analysis of legacy application around various quality and functional parameters some of which includes reliability and modularity of the functions, level of usability and maintainability as well as policy and standards of software architecture and availability of required documents. Portfolio analysis around these parameters will help to examine the legacy application on quality and functional gaps within the application [1].
This document outlines an asset management maturity continuum that progresses from reactive to proactive approaches. It shows increasing levels of optimization from minimal performance tracking up to enterprise-wide asset management integration. Key aspects that progress along the continuum include governance, systems/technology, processes, people/performance measures. The goal is to move from "fix it after it fails" approaches to preventative, predictive and reliability-focused asset management.
Because of my role as Lector Directing ICT sources and services at Hanze University Groningen I have developed a lecture about the CMMi for services quality improvement philosophy. This will help to improve the quality of your ICT service and the competences of you professionals. Special in cases of sourcing projects.
This document discusses the impact of aspect-oriented programming (AOP) on software maintainability based on a literature review and case studies. It summarizes several case studies that measured maintainability metrics like coupling, cohesion, and separation of concerns in object-oriented (OO) systems versus aspect-oriented (AO) systems. The studies found that AO systems generally had less coupling between components, higher separation of concerns, and were more changeable and maintainable than equivalent OO systems. The document also outlines various software metrics that have been used to measure maintainability attributes in AO systems like cohesion, coupling, size, and changeability.
Ian Sommerville, Software Engineering, 9th Edition Ch2Mohammed Romi
This document summarizes key aspects of software processes and models. It discusses the basic activities involved in software development like specification, design, implementation, validation and evolution. It describes process models like waterfall, incremental development and reuse-oriented processes. The waterfall model involves sequential phases while incremental development interleaves activities. Validation includes testing stages from unit to system level. The document also covers designing for change and evolution.
The document provides an overview of CMMI (Capability Maturity Model Integration) version 1.3. It discusses the evolution of CMMI from combining three source models, the coverage of systems engineering, software engineering and integrated product development. It describes the process areas and functional categories in CMMI 1.3 and how they are organized. It also explains the concept of levels in CMMI which characterize process improvement from an ill-defined state to a state of quantitative management.
The document discusses the Capability Maturity Model (CMM), which is used to assess the maturity of an organization's software development processes. It describes the five maturity levels from Initial to Optimizing. At each level, processes become more rigorously defined, measured, and controlled. Level 1 is chaotic with no standard processes, while Level 2 introduces basic management processes. Level 3 establishes standardized processes across projects, and Level 4 measures process quality quantitatively. Level 5 continuously improves processes using data to optimize productivity and quality.
Configuration management involves change management, version management, system building, and release management. It ensures changes to software systems are managed and tracked. Version management tracks different versions of components to prevent interference. System building compiles components into executable systems. Release management prepares software for distribution and tracks released versions.
This document discusses a study that aimed to develop and validate an instrument to measure critical success factors for Enterprise Resource Planning (ERP) system implementations. The study defines 12 constructs related to ERP implementation success. It then describes the methodology used, which involved developing measurement scales for each construct and testing them on a survey of 53 organizations in Australia. The results validated a 65-item instrument measuring seven dimensions of ERP implementation. The document argues this model provides a valuable tool for researchers and practitioners to assess ERP implementation projects.
Software Engineering Past Papers (Short Questions)MuhammadTalha436
1. SWOT analysis is a framework for identifying internal and external factors that can impact a project, product, place or person. It analyzes strengths, weaknesses, opportunities, and threats.
2. Software refactoring is changing software code without altering external behavior to improve internal structure.
3. An embedded system is a programmed system within a larger mechanical or electrical system, often with real-time computing constraints and a dedicated function.
Many software organizations have moved from traditional methods for software development, such as waterfall method to usage of agile methods. Agile methods are used especially in software development and are constantly refurbishing and improving initial plans along the way. In software development the systems usually require frequent changes during the development process. This method is very suitable for small project and organizations, but it is very hard to implement it in large organizations with large projects and teams. This paper
aims to identify weaknesses of two existing scrum frameworks used for large organizations and to present proposed hybrid framework scaled from both existing frameworks. It’s highlighting the importance of predefined life cycle of teams, which is key factor in achieving better timeline and to avoid mistakes that affects the time of release deployment.
Quality is defined as the degree of goodness of a product or service as perceived by customers. Software quality refers to the totality of features and characteristics of software that bear on its ability to satisfy needs. There are various views of quality including the transcendent view, product-based view, value-based view, manufacturing view, and user-based view. Quality is measured using metrics that are linked to quality criteria and can objectively determine the level of a given criterion. Software quality measurement faces issues like quality being non-absolute and multidimensional.
The document discusses several topics related to software project management including risk management, managing people, and teamwork. It describes the key activities of a project manager including planning, risk assessment, people management, reporting, and proposal writing. Specific risks at the project, product, and business levels are defined and strategies for risk identification, analysis, planning, monitoring, and mitigation are outlined. Effective people management is also emphasized, including motivating team members through satisfying different human needs and personality types. A case study demonstrates how addressing an individual team member's motivation issues can improve project outcomes.
This document discusses software processes and models. It covers the following key points:
1. Software processes involve activities like specification, design, implementation, validation and evolution to develop software systems. Common process models include waterfall, incremental development and reuse-oriented development.
2. Processes need to cope with inevitable changes. This can involve prototyping to avoid rework or using incremental development and delivery to more easily accommodate changes.
3. The Rational Unified Process is a modern process model with phases for inception, elaboration, construction and transition. It advocates iterative development and managing requirements and quality.
https://www.mudassiriqbal.net/project-management-terms-and-concepts
There are many concepts and definitions which require special attention by all PMP Aspirants as the terminologies are largely used interchangeably in the real world.
This document discusses key topics in systems engineering, including:
1) Systems engineering involves procuring, designing, implementing, and maintaining sociotechnical systems that include both technical and human elements.
2) Software systems are part of broader sociotechnical systems and software engineers must consider human, social, and organizational factors.
3) Sociotechnical systems have emergent properties that depend on the interactions between system components and cannot be understood by examining the components individually.
Software re-engineering is a process of examining and altering a software system to restructure it and improve maintainability. It involves sub-processes like reverse engineering, redocumentation, and data re-engineering. Software re-engineering is applicable when some subsystems require frequent maintenance and can be a cost-effective way to evolve legacy software systems. The key advantages are reduced risk compared to new development and lower costs than replacing the system entirely.
Design and development of an automotive vertical doors opening system avdosiaemedu
The document describes the design and development of an automotive vertical doors opening system (AVDOS). The proposed system aims to overcome some drawbacks of existing vertical door designs by allowing easier access without requiring side movement. The system uses two hinges, gears, and a gas spring. The hinges are designed to open the door by swinging away from the vehicle. A small vertical push activates the gas spring, which moves the hinge and causes the gears to provide a slight outward movement to clear the door frame. Testing in CAD software validated that the system provides access without hard pushing or slamming doors. The system offers a safer, easier to use, and lower cost alternative to existing vertical door designs.
Towards better control over the distribution of subsidized commoditiesiaemedu
This document summarizes an article from the International Journal of Computer Engineering and Technology. The article presents a mobile-based solution to tackle the problem of fairly and transparently distributing subsidized food in Egypt. The proposed solution provides visibility and control over the distribution process using mobile technologies. It introduces a better mechanism to reduce leakage in the current subsidy system. The solution architecture is discussed, including logical and layered views. Key requirements like usability and minimizing corruption are also summarized.
Investigation of post processing techniques to reduce the surfaceiaemedu
This document summarizes an investigation into post-processing techniques to reduce the surface roughness of parts created through fused deposition modeling (FDM). Specifically, it examines using chemical treatment methods with different chemicals, concentrations, temperatures, exposure times, and initial part roughnesses. A statistical design of experiments approach is used to identify significant factors affecting surface finish and optimize the chemical treatment process. Results from applying this method to ABS plastics show that simple, inexpensive chemical treatments can satisfactorily improve the surface finish of FDM parts.
Model for prediction of temperature distribution in workpiece for surface gri...iaemedu
This document discusses a finite element model for predicting temperature distribution during surface grinding. It begins by reviewing how various grinding parameters affect temperature and approaches to modeling the grinding zone as a heat source. It then presents the proposed finite element model, which considers the grinding wheel a moving heat source along the workpiece surface. The model calculates the heat flux entering the workpiece based on grinding parameters like wheel speed and cutting depth. Results show maximum temperature occurs at the trailing edge but drops off after due to cooling. The model can provide insight into temperature fields in the workpiece and effects of process parameters on thermal loading and residual stresses.
Throughput improvement of ieee 802.15.4 based medicaliaemedu
This document discusses improving the throughput of IEEE 802.15.4 based medical ad-hoc sensor networks that are used for home healthcare monitoring. These networks experience degraded throughput due to interference from co-existing Wi-Fi networks operating in the same 2.4GHz spectrum. The paper studies the impact of Wi-Fi interference on throughput and uses Clear Channel Assessment (CCA) to improve throughput. Experiments were conducted using Texas Instruments sensor motes and showed that CCA improved throughput by 63% by avoiding transmissions when interference was detected.
Octave wave sound signal measurements in ducted axial fan under stall region ...iaemedu
This document discusses measurements of octave wave sound signals in a ducted axial fan under stall conditions at different rotor speeds. It describes the experimental setup, which includes a ducted axial fan rig with variable speed control and a throttle controller. Sound from the fan is measured using a microphone connected to a data acquisition system and sound spectrum analyzer software. The document provides background on sound measurement techniques, defining concepts like frequency, wavelength, velocity and how the spectrum analyzer system works. Graphs of sound level in decibels are presented for different frequencies at the stall region and throttle position of 4 cm from the casing.
Examining the sustainability of ethics in business an academic perspectiveiaemedu
This document discusses the sustainability of ethics in business from an academic perspective. It examines the role of academics in teaching business ethics and the challenges of ensuring ethics are practiced beyond the classroom. While business ethics courses are now common, the core business curriculum remains focused on functional studies rather than values. Research shows ethics education can influence students' ethical attitudes but other factors like sociocultural norms may have a greater impact. For ethics to be sustained in business, academics must model ethical behavior and develop students' moral character through frameworks beyond case studies alone. Organizational culture also significantly shapes what conduct is deemed ethical.
STATISTICAL ANALYSIS OF METRICS FOR SOFTWARE QUALITY IMPROVEMENT ijseajournal
Software product quality can be defined as the features and characteristics of the product that meet the user needs. The quality of any software can be achieved by following a well defined software process. These software process results into various metrics like Project metrics, Product metrics and Process metrics. Software quality depends on the process which is carried out to design and develop software. Even though the process can be carried out with utmost care, still it can introduce some error and defects. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response
time.
This paper describes the importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature of error captured. To reduce such errors and defects found, steps for corrective actions are recommended.
Process and product quality assurance are very important aspects in development of software. Process
and product quality assurance monitor the software engineering processes and methods to ensure quality.
It is the process of confirming and verifying that whether services and products meet the customer
expectation or not.
This research will identify general measures for the specific goals and its specific practices of Process and
Product Quality Assurance Process Area in Capability Maturity Model Integration (CMMI). CMMI is
developed by Software Engineering Institute (SEI) in Carnegie Mellon University in USA. CMMI is a
framework for assessment and improvement of computer information systems. The procedure we used to
determine the measures is to apply the Goal Questions Metrics (GQM) approach to the two specific goals
and its four specific practices of Process and Product Quality Assurance Process Area in CMMI.
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
The document discusses project planning measures in the Capability Maturity Model Integration (CMMI). It applies the Goal Question Metric (GQM) approach to identify measures for the three specific goals and fourteen specific practices of the Project Planning process area in CMMI. The paper defines questions and measures related to each specific practice by following the three steps of GQM: defining goals, generating quantifiable questions, and defining measures to answer the questions. The identified measures are intended to help evaluate and control software products and processes.
Computer information project planning is one of the most important activities in the modern software
development process. Without an objective and realistic plan of software project, the development of
software process cannot be managed effectively. This research will identify general measures for the
specific goals and its specific practices of Project Planning Process Area in Capability Maturity Model
Integration (CMMI). CMMI is developed in USA by Software Engineering Institute (SEI) in Carnegie
Mellon University. CMMI is a framework for assessment and improvement of computer information
systems. The procedure we used to determine the measures is to apply the Goal Questions Metrics (GQM)
approach to the three specific goals and its fourteen specific practices of Project Planning Process Area in
CMMI.
The DSS presented in this document is a tool that improves the effectiveness of the decision making process that results in estimating, planning, and adapting: the products (software architecture, design specifications and code ), the activities (designing architecture, defining design specifications, and producing code) , and the measures of goodness (number of known requirements met, degree of resilience to new requirements, and degree of reusability) of the design and implementation phases of a Software Development Life Cycle.
The document discusses various software development methodologies and concepts. It describes methodology types like waterfall, rapid application development, spiral, incremental, V-model, and iterative V-model. It also covers the software development life cycle phases of initiation, definition, design, programming/testing, evaluation, and installation. Finally, it discusses defining requirements, methodology maturity, staff competency, configuration management, and measuring the impact of the development process.
Software metric analysis methods for product development maintenance projectsIAEME Publication
This document discusses various software metrics and methods for analyzing metrics to improve the software development process. It begins with an introduction to software metrics and their importance for project management. It then describes common software development phases and associated metrics that can be collected at each phase. The remainder of the document focuses on different methods for analyzing metrics, including pie charts, Pareto diagrams, bar charts, line charts, scatter diagrams, radar diagrams, and control charts. These analysis methods help identify areas for process improvement and determine if changes have led to desired outcomes.
Software metric analysis methods for product developmentiaemedu
This document discusses various software metrics and methods for analyzing metrics to improve the software development process. It begins with an introduction to software metrics and their importance for project management. It then describes common software development phases and associated metrics that can be collected at each phase, such as lines of code, defects, and staff hours. The document proceeds to explain different types of charts and diagrams that can be used to analyze and visualize metrics data, including pie charts, Pareto diagrams, histograms, line charts, scatter plots, radar diagrams, and control charts. These various analysis methods help identify areas for process improvement and determine whether changes have resulted in desired outcomes.
Software metric analysis methods for product developmentiaemedu
This document discusses various software metrics and methods for analyzing metrics to improve the software development process. It begins with an introduction to software metrics and their importance for project management. It then describes common software development phases and associated metrics that can be collected at each phase, such as lines of code, defects, and staff hours. The document proceeds to explain different types of charts and diagrams that can be used to analyze and visualize metrics data, including pie charts, Pareto diagrams, histograms, line charts, scatter plots, radar diagrams, and control charts. These various analysis methods help identify problems, determine correlations, and track performance over time in order to control and improve the software development process.
This document provides a review of systematic quality software designing and development practices. It discusses software engineering processes, quality processes, design and development modeling approaches, and related works. The key points are:
1) Software engineering processes aim to ensure quality, meet deadlines, and manage expectations through defined stages and deliverables. Common models include waterfall, spiral, and agile.
2) Software quality processes evaluate and improve aspects like reliability, maintainability, and interoperability. Metrics and techniques are used to measure qualities.
3) Design and development involve life cycles, methods, and notations to systematically model requirements, architecture, and implementation. Waterfall and rapid prototyping are example models.
A Guideline Tool for Ongoing Product Evaluation in Small and Medium-Sized Ent...IJECEIAES
As consumer demand for user friendly software increases, usability evaluation is crucial to develop software systems which are easy to learn and use. However, implementation of usability evaluation is challenging for small and medium-sized enterprises (SMEs) due to factors such as lack of technical expertise, knowledge and experience of methods and standards. This results in neglect, or poorly executed evaluations of projects, resulting in software that disappoints and frustrates clients. To overcome this loss of competitiveness, we propose here a visual incorporation tool derived from ISO standards that would assist software development teams in SMEs in understanding and implementing usability evaluations. It shows fundamental Usability Engineering (UE) and Software Engineering (SE) activities and artifacts relevant to the usability evaluation and software development process, with potential incorporation points being highlighted. Dependencies and relationships are shown by links between activities and artifacts. Additionally, convergent artifacts of both disciplines were identified and shown. Evaluation of the proposed tool was based on the questionnaire results of software development practitioners from SMEs.
Relational Analysis of Software Developer’s Quality AssuresIOSR Journals
This document discusses relational analysis of software developer quality and measures. It begins by introducing the importance of software architecture and development models in ensuring project success. It then discusses measuring processes, products, and resources in software engineering. Internal attributes like size and complexity can be measured from products alone, while external attributes like reliability require executing the code. The research aims to measure internal attributes of the process. It outlines different types of process and product metrics used to measure properties and quality. Finally, it discusses specific defect and lines of code metrics used during implementation to estimate defects and size code.
IRJET- Factors Affecting the Delivery of Quality Software and their Relations...IRJET Journal
This document discusses factors that affect the delivery of quality software and their relationship to the software development process. It identifies key factors such as the amount of testing, costs involved, time spent, and following proper software development life cycle (SDLC) phases. The document presents a literature review on how these factors influence software quality. It then defines variables, hypotheses, and a regression model to analyze the relationship between delivery of quality software and the identified factors. The results of distributing and analyzing questionnaires indicate that amount of testing, costs involved, and time spent have a statistically significant correlation with delivering quality software. Therefore, paying attention to these factors during development can help improve software quality.
A Comparative Analysis Of Various Methodologies Of Agile Project Management V...Brittany Allen
This document provides a comparative analysis of project management methodologies, specifically comparing the Project Management Body of Knowledge (PMBOK) and various agile project management approaches. It first describes the key processes and knowledge areas of PMBOK. It then outlines some popular agile methodologies like Scrum, Extreme Programming (XP), and Feature Driven Development (FDD). The document aims to identify similarities and differences between the traditional PMBOK framework and more flexible agile approaches.
The document discusses function point analysis (FPA), a method used to estimate the size of a software project based on its functionality. FPA was initially developed by Allan J. Albrecht in 1979 at IBM. It measures the functional size of a software application in terms of function points, which are used to estimate factors like project time and resources required. FPA is independent of programming languages and can be used for various types of software systems. The document also discusses software quality metrics, which focus on measuring the quality of products, processes, and projects. These include metrics like defect density, customer problems, and customer satisfaction.
Software testing is a key part of software engineering used to evaluate software quality and identify errors. There are various software testing techniques and methods, but thoroughly investigating a complex software is more important than following a specific procedure. Testing complex software cannot discover all errors, but can help improve quality. Software engineering involves defining requirements, design, development, testing, and maintenance of software using methodologies like agile development.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
Similar to Assessment of cmm and its impact on software quality (20)
Tech transfer making it as a risk free approach in pharmaceutical and biotech iniaemedu
Tech transfer is a common methodology for transferring new products or an existing
commercial product to R&D or to another manufacturing site. Transferring product knowledge to the
manufacturing floor is crucial and it is an ongoing approach in the pharmaceutical and biotech
industry. Without adopting this process, no company can manufacture its niche products, let alone
market them. Technology transfer is a complicated, process because it is highly cross functional. Due
to its cross functional dependence, these projects face numerous risks and failure. If anidea cannot be
successfully brought out in the form of a product, there is no customer benefit, or satisfaction.
Moreover, high emphasis is in sustaining manufacturing with highest quality each and every time. It
is vital that tech transfer projects need to be executed flawlessly. To accomplish this goal, risk
management is crucial and project team needs to use the risk management approach seamlessly.
Integration of feature sets with machine learning techniquesiaemedu
This document summarizes a research paper that proposes a novel approach for spam filtering using selective feature sets combined with machine learning techniques. The paper presents an algorithm and system architecture that extracts feature sets from emails and uses machine learning to classify emails and generate rules to identify spam. Several metrics are identified to evaluate the efficiency of the feature sets, including false positive rate. An experiment is described that uses keyword lists as feature sets to train filters and compares the proposed approach to other spam filtering methods.
Effective broadcasting in mobile ad hoc networks using gridiaemedu
This document summarizes a research paper that proposes a new grid-based broadcasting mechanism for mobile ad hoc networks. The paper argues that flooding approaches to broadcasting are inefficient and cause network congestion. The proposed approach divides the network into a hierarchical grid structure. When a node needs to broadcast a message, it sends the message to the first node in the appropriate grid, which is then responsible for updating and forwarding the message within that grid. Simulation results showed the grid-based approach outperformed other broadcasting protocols and was more reliable, efficient and scalable.
Effect of scenario environment on the performance of mane ts routingiaemedu
The document analyzes the effect of scenario environment on the performance of the AODV routing protocol in mobile ad hoc networks (MANETs). It studies AODV performance under different scenarios varying network size, maximum node speed, and pause time. The performance is evaluated based on packet delivery ratio, throughput, and end-to-end delay. The results show that AODV performs best in some scenarios and worse in others, indicating that scenario parameters significantly impact routing protocol performance in MANETs.
Adaptive job scheduling with load balancing for workflow applicationiaemedu
This document discusses adaptive job scheduling with load balancing for workflow applications in a grid platform. It begins with an abstract that describes grid computing and how scheduling plays a key role in performance for grid workflow applications. Both static and dynamic scheduling strategies are discussed, but they require high scheduling costs and may not produce good schedules. The paper then proposes a novel semi-dynamic algorithm that allows the schedule to adapt to changes in the dynamic grid environment through both static and dynamic scheduling. Load balancing is incorporated to handle situations where jobs are delayed due to resource fluctuations or overloading of processors. The rest of the paper outlines the related works, proposed scheduling algorithm, system model, and evaluation of the approach.
This document summarizes research on transaction reordering techniques. It discusses transaction reordering approaches based on reducing resource conflicts and increasing resource sharing. Specifically, it covers:
1) A "steal-on-abort" technique that reorders an aborted transaction behind the transaction that caused the abort to avoid repeated conflicts.
2) A replication protocol that attempts to reorder transactions during certification to avoid aborts rather than restarting immediately.
3) Transaction reordering and grouping during continuous data loading to prevent deadlocks when loading data for materialized join views.
The document discusses semantic web services and their challenges. It provides an overview of semantic web technologies like WSDL, SOAP, UDDI, and OIL which are used to build semantic web services. The semantic web architecture adds semantics to web services through ontologies written in OWL and DAML+OIL. Key approaches to semantic web services include annotation, composition, and addressing privacy and security. However, semantic web services still face challenges in achieving their full potential due to issues in representation, reasoning, and a lack of real-world applications and data.
Website based patent information searching mechanismiaemedu
This document summarizes a research paper on developing a website-based patent information searching mechanism. It discusses how patent information can be used for technology development, rights acquisition and utilization, and management information. It describes different types of patent searches including novelty, validity, infringement, and state-of-the-art searches. It also evaluates and compares two major patent websites, Delphion and USPTO, in terms of their search capabilities and features.
Revisiting the experiment on detecting of replay and message modificationiaemedu
This document summarizes a research paper that proposes methods for detecting message modification and replay attacks in ad-hoc wireless networks. It begins with background on security issues in wireless networks and types of attacks. It then reviews existing intrusion detection systems and security techniques. Related work that detects attacks using features from the media access control layer or radio frequency fingerprinting is also discussed. The paper aims to present a simple, economical, and platform-independent system for detecting message modification, replay attacks, and unauthorized users in ad-hoc networks.
1) The document discusses the Cyclic Model Analysis (CMA) technique for sequential pattern mining which aims to predict customer purchasing behavior.
2) CMA calculates the Trend Distribution Function from sequential patterns to model purchasing trends over time. It then uses Generalized Periodicity Detection and Trend Modeling to identify periodic patterns and construct an approximating model.
3) The Cyclic Model Analysis algorithm is applied to further analyze the patterns, dividing the domain into segments where the distribution function is increasing or decreasing and applying the other techniques recursively to fully model the cyclic behavior.
Performance analysis of manet routing protocol in presenceiaemedu
This document analyzes the performance of different routing protocols in a mobile ad hoc network (MANET) under hybrid traffic conditions. It simulates a MANET with 50 nodes moving at speeds up to 20 m/s using the AODV, DSDV, and DSR routing protocols. Traffic included both constant bit rate and variable bit rate sources. Results found that AODV had lower average end-to-end delay and higher packet delivery ratios than DSDV and DSR as the percentage of variable bit rate traffic increased. AODV also performed comparably under both low and high node mobility scenarios with hybrid traffic.
Performance measurement of different requirements engineeringiaemedu
This document summarizes a research paper that compares the performance of different requirements engineering (RE) process models. It describes three RE process models - two existing linear models and the authors' iterative model. It also reviews literature on common RE activities and issues with descriptive models not reflecting real-world practices. The authors conducted interviews at two Indian companies to model their RE processes and compare them to the three models. They found the existing linear models did not fully capture the iterative nature of observed RE processes.
This document proposes a mobile safety system for automobiles that uses Android operating system. The system has two main components: a safety device and an automobile base unit. The safety device allows users to monitor the vehicle's location on a map, check its status, and control functions remotely. It communicates with the base unit in the vehicle using GPRS. The base unit collects data from sensors, determines the vehicle's GPS location, and can execute control commands like activating the brakes or switching off the engine. The document provides details on the design and algorithms of both components and includes examples of Java code implementation. The goal is to create an intelligent, secure and easy-to-use mobile safety system for vehicles using embedded systems and Android
Efficient text compression using special character replacementiaemedu
The document describes a proposed algorithm for efficient text compression using special character replacement and space removal. The algorithm replaces words with non-printable ASCII characters or combinations of characters to compress text files. It uses a dynamic dictionary to map words to their symbols. Spaces are removed from the compressed file in some cases to further reduce file size. Experimental results show the algorithm achieves better compression ratios than LZW, WinZip 10.0 and WinRAR 3.93 for various text file types while allowing lossless decompression.
The document discusses agile programming and proposes a new methodology. It provides an overview of existing agile methodologies like Scrum and Extreme Programming. Scrum uses short sprints to define tasks and deadlines. Extreme Programming focuses on practices like test-first development, pair programming, and continuous integration. The document notes drawbacks like an inability to support large or multi-site projects. It proposes designing a new methodology that combines the advantages of existing methods while overcoming their deficiencies.
Adaptive load balancing techniques in global scale grid environmentiaemedu
The document discusses various adaptive load balancing techniques for distributed applications in grid environments. It first describes adaptive mesh refinement algorithms that partition computational domains using space-filling curves or by distributing grids independently or at different levels. It also discusses dynamic load balancing using tiling and multi-criteria geometric partitioning. The document then covers repartitioning algorithms based on multilevel diffusion and the adaptive characteristics of structured adaptive mesh refinement applications. Finally, it discusses adaptive workload balancing on heterogeneous resources by benchmarking resource characteristics and estimating application parameters to find optimal load distribution.
A survey on the performance of job scheduling in workflow applicationiaemedu
This document summarizes a survey on job scheduling performance in workflow applications on grid platforms. It discusses an adaptive dual objective scheduling (ADOS) algorithm that takes both completion time and resource usage into account for measuring schedule performance. The study shows ADOS delivers good performance in completion time, resource usage, and robustness to changes in resource performance. It also describes the system architecture used, which includes a planner and executor component. The planner focuses on scheduling to minimize completion time while considering resource usage, and can reschedule if needed. The executor enacts the schedule on the grid resources.
A survey of mitigating routing misbehavior in mobile ad hoc networksiaemedu
This document summarizes existing methods to detect misbehavior in mobile ad hoc networks (MANETs). It discusses how routing protocols assume nodes will cooperate fully, but misbehavior like packet dropping can occur. It describes several techniques to detect misbehavior, including watchdog, ACK/SACK, TWOACK, S-TWOACK, and credit-based/reputation-based schemes. Credit-based schemes use virtual currencies to provide incentives for nodes to forward packets, while reputation-based schemes track nodes' past behaviors. The document aims to survey approaches for mitigating the impact of misbehaving nodes in MANET routing.
A novel approach for satellite imagery storage by classifyiaemedu
This document presents a novel approach for classifying and storing satellite imagery by detecting and storing only non-duplicate regions. It uses kernel principal component analysis to reduce the dimensionality and extract features of satellite images. Fuzzy N-means clustering is then used to segment the images into blocks. A duplication detection algorithm compares blocks to identify duplicate and non-duplicate regions. Only the non-duplicate regions are stored in the database, improving storage efficiency and updating speed compared to completely replacing existing images. Support vector machines are used to categorize the non-duplicate blocks into the appropriate classes in the existing images.
A self recovery approach using halftone images for medical imageryiaemedu
This document summarizes a proposed approach for securely transferring medical images over the internet using visual cryptography and halftone images. The approach uses error diffusion techniques to generate a halftone host image from the grayscale medical image. Shadow images are then created from the halftone host image using visual cryptography algorithms. When stacked together, the shadow images reveal the secret medical image. The halftone host image also contains an embedded logo that can be extracted to verify the integrity of the reconstructed image without a trusted third party.