Types of Software Maintenance, Re-Engineering, Reverse Engineering, Forward Engineering, The SCM Process, Identification of Objects in the Software Configuration, Version
Control and Change Control
A detail review of configuration and change management. This lecture provides details about how to manage different software versions of same software in a market with different customers clients and different set of functionalities.
A detail review of configuration and change management. This lecture provides details about how to manage different software versions of same software in a market with different customers clients and different set of functionalities.
In software engineering, software configuration management (SCM or S/W CM) is the task of tracking and controlling changes in the software, part of the larger cross-disciplinary field of configuration management. SCM practices include revision control and the establishment of baselines.
This Presentation explains the SCM Process.
Software coding & testing, software engineeringRupesh Vaishnav
Coding Standard and coding Guidelines, Code Review, Software Documentation, Testing Strategies, Testing Techniques and Test Case, Test Suites Design, Testing Conventional
Applications, Testing Object Oriented Applications, Testing Web and Mobile Applications, Testing Tools (Win runner, Load runner).
Software Process Models, The Linear Sequential Model, The Prototyping Model, The RAD Model, Evolutionary Process Models, Agile Process Model, Component-Based Development, Process, Product and Process.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
Water billing management system project report.pdfKamal Acharya
Our project entitled “Water Billing Management System” aims is to generate Water bill with all the charges and penalty. Manual system that is employed is extremely laborious and quite inadequate. It only makes the process more difficult and hard.
The aim of our project is to develop a system that is meant to partially computerize the work performed in the Water Board like generating monthly Water bill, record of consuming unit of water, store record of the customer and previous unpaid record.
We used HTML/PHP as front end and MYSQL as back end for developing our project. HTML is primarily a visual design environment. We can create a android application by designing the form and that make up the user interface. Adding android application code to the form and the objects such as buttons and text boxes on them and adding any required support code in additional modular.
MySQL is free open source database that facilitates the effective management of the databases by connecting them to the software. It is a stable ,reliable and the powerful solution with the advanced features and advantages which are as follows: Data Security.MySQL is free open source database that facilitates the effective management of the databases by connecting them to the software.
Low power architecture of logic gates using adiabatic techniquesnooriasukmaningtyas
The growing significance of portable systems to limit power consumption in ultra-large-scale-integration chips of very high density, has recently led to rapid and inventive progresses in low-power design. The most effective technique is adiabatic logic circuit design in energy-efficient hardware. This paper presents two adiabatic approaches for the design of low power circuits, modified positive feedback adiabatic logic (modified PFAL) and the other is direct current diode based positive feedback adiabatic logic (DC-DB PFAL). Logic gates are the preliminary components in any digital circuit design. By improving the performance of basic gates, one can improvise the whole system performance. In this paper proposed circuit design of the low power architecture of OR/NOR, AND/NAND, and XOR/XNOR gates are presented using the said approaches and their results are analyzed for powerdissipation, delay, power-delay-product and rise time and compared with the other adiabatic techniques along with the conventional complementary metal oxide semiconductor (CMOS) designs reported in the literature. It has been found that the designs with DC-DB PFAL technique outperform with the percentage improvement of 65% for NOR gate and 7% for NAND gate and 34% for XNOR gate over the modified PFAL techniques at 10 MHz respectively.
A review on techniques and modelling methodologies used for checking electrom...nooriasukmaningtyas
The proper function of the integrated circuit (IC) in an inhibiting electromagnetic environment has always been a serious concern throughout the decades of revolution in the world of electronics, from disjunct devices to today’s integrated circuit technology, where billions of transistors are combined on a single chip. The automotive industry and smart vehicles in particular, are confronting design issues such as being prone to electromagnetic interference (EMI). Electronic control devices calculate incorrect outputs because of EMI and sensors give misleading values which can prove fatal in case of automotives. In this paper, the authors have non exhaustively tried to review research work concerned with the investigation of EMI in ICs and prediction of this EMI using various modelling methodologies and measurement setups.
6th International Conference on Machine Learning & Applications (CMLA 2024)ClaraZara1
6th International Conference on Machine Learning & Applications (CMLA 2024) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of on Machine Learning & Applications.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
2. Types of Maintenance
•Corrective Maintenance (21%)
• making changes to repair defects
•Adaptive Maintenance (25%)
• making changes to adapt software to external environment
changes (hardware, business rules, OS, etc.)
•Perfective Maintenance (50%)
• extending system beyond its original functional requirements
•Preventative Maintenance (4%)
• modifying work products so that they are more easily corrected,
adapted, or enhanced
3. Maintenance Costs
•Usually greater than the development costs (2
to 10 times as much in some cases)
•Affected by both technical and non-technical
factors
•Increase as software is maintained and system
corruption is introduced
•Aging software can have high support costs (e.g.
old languages, compilers, etc.)
4. Maintenance Developer Tasks
• Understand system.
• Locate information in documentation.
• Keep system documentation up to date.
• Extend existing functions.
• Add new functions.
• Find sources of errors.
• Correct system errors.
• Answer operations questions.
• Restructure design and code.
• Delete obsolete design and code.
• Manage changes.
5. Maintenance Cost Factors
•Staff turnover
• no turnover usually means lower maintenance costs
•Contractual responsibility
• developers may have no contractual obligation to maintain the
delivered system and no incentive to design for future change
•Staff skills
• maintenance staff are often inexperienced and have limited
domain knowledge
•Program age and structure
• as programs age their structure deteriorates, they become harder
to understand and change
6. Maintenance Prediction
•Concerned with determining which parts of the
system may cause problems and have high
maintenance costs
•Change acceptance depends on the
maintainability of the components affected by the
change
•Implementing changes degrade system and
reduces its maintainability
•Maintenance costs depends on number of
changes
7. Configuration Management
•Software changes are inevitable
•One goal of software engineering is to improve how easy
it is to change software
•Configuration management is all about change control.
•Every software engineer has to be concerned with how
changes made to work products are tracked and
propagated throughout a project.
•To ensure quality is maintained the change process must
be audited.
8. Configuration Management
Definition:
The set of activities that have been developed to
manage change throughout the software life
cycle.
Purpose:
Systematically control changes to the
configuration and maintain the integrity and
traceability of the configuration throughout the
system’s life cycle.
9. Purpose of CM
• Identify Change
• Control Change
• Ensure Change is Properly Implemented
• Report Changes to All the people who need to
Know
10. Baseline
•Definition: Specification or product that
• has been formally reviewed and agreed upon,
• serves as the basis for further development, and
• can be changed only through formal change control procedures.
•Signals a point of departure from one activity to the start
of another activity.
•Helps control change without impeding justifiable change.
11. Project Baseline
•Central repository of reviewed and approved
artifacts that represent a given stable point
in overall system development.
•Shared DB for project and kept in consistent
state.
•Policies allow the team to achieve consistent
state and manage the project.
12. Software Configuration Item (SCI)
•Definition: Information that is created as part of the
software engineering process.
•Examples:
•Software Project Plan
•Software Requirements Specification
• Models, Prototypes, Requirements
•Design document
• Protocols, Hierarchy Graphs
•Source code
• Modules
•Test suite
•Software tools (e.g., compilers)
13. Elements of SCM
There are four elements of SCM:
1. Software Configuration Identification
2. Software Configuration Control
3. Software Configuration Auditing
4. Software Configuration Status Accounting
15. Identification Task
• Identification separately names each CSCI and then organizes it in
the SCM repository using an object-oriented approach
• Objects start out as basic objects and are then grouped into
aggregate objects
• Each object has a set of distinct features that identify it
• A name that is unambiguous to all other objects
• A description that contains the CSCI type, a project identifier,
and change and/or version information
• List of resources needed by the object
• The object realization (i.e., the document, the file, the model,
etc.)
16. Change Control Task
• Change control is a procedural activity that ensures quality and consistency as
changes are made to a configuration object
• A change request is submitted to a configuration control authority, which is usually a
change control board (CCB)
• The request is evaluated for technical merit, potential side effects, overall impact on other
configuration objects and system functions, and projected cost in terms of money, time, and
resources
• An engineering change order (ECO) is issued for each approved change request
• Describes the change to be made, the constraints to follow, and the criteria for review and
audit
• The baselined CSCI is obtained from the SCM repository
• Access control governs which software engineers have the authority to access and modify a
particular configuration object
• Synchronization control helps to ensure that parallel changes performed by two different
people don't overwrite one another
17. Version Control Task
• Version control is a set of procedures and tools for managing the
creation and use of multiple occurrences of objects in the SCM
repository
• Required version control capabilities
• An SCM repository that stores all relevant configuration objects
• A version management capability that stores all versions of a configuration
object (or enables any version to be constructed using differences from past
versions)
• A make facility that enables the software engineer to collect all relevant
configuration objects and construct a specific version of the software
• Issues tracking (bug tracking) capability that enables the team to record and
track the status of all outstanding issues associated with each configuration
object
• The SCM repository maintains a change set
• Serves as a collection of all changes made to a baseline configuration
• Used to create a specific version of the software
• Captures all changes to all files in the configuration along with the reason for
changes and details of who made the changes and when
18. Configuration Auditing Task
• Configuration auditing is an SQA activity that helps to ensure that quality is
maintained as changes are made
• It complements the formal technical review and is conducted by the SQA group
• It addresses the following questions
• Has a formal technical review been conducted to assess technical correctness?
• Has the software process been followed, and have software engineering standards been
properly applied?
• Has the change been "highlighted" and "documented" in the CSCI? Have the change
data and change author been specified? Do the attributes of the configuration object
reflect the change?
• Have SCM procedures for noting the change, recording it, and reporting it been
followed?
• Have all related CSCIs been properly updated?
• A configuration audit ensures that
• The correct CSCIs (by version) have been incorporated into a specific build
• That all documentation is up-to-date and consistent with the version that has been built
19. Status Reporting Task
• Configuration status reporting (CSR) is also called status
accounting
• Provides information about each change to those personnel in an
organization with a need to know
• Answers what happened, who did it, when did it happen, and
what else will be affected?
• Sources of entries for configuration status reporting
• Each time a CSCI is assigned new or updated information
• Each time a configuration audit is conducted
• The configuration status report
• Placed in an on-line database or on a website for software developers and
maintainers to read
• Given to management and practitioners to keep them appraised of
important changes to the project CSCIs