TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Prepared by : URMILA MAHOR Subject Name: Software Engineering & Project Management Subject Code: CS-403 Semester: 4 th UNIT-V Software Maintenance Software Maintenance is the process of modifying a software product after it has been delivered to the customer. The main purpose of software maintenance is to modify and update software application after delivery to correct faults and to improve performance. Need for Maintenance – Software Maintenance must be performed in order to: Correct faults. Improve the design. Implement enhancements. Interface with other systems. Accommodate programs so that different hardware, software, system features, and telecommunications facilities can be used. Migrate legacy software. Retire software. Categories of Software Maintenance – Maintenance can be divided into the following: 1. Corrective maintenance: Corrective maintenance of a software product may be essential either to rectify some bugs observed while the system is in use, or to enhance the performance of the system. 2. Adaptive maintenance: This includes modifications and updations when the customers need the product to run on new platforms, on new operating systems, or when they need the product to interface with new hardware and software. 3. Perfective maintenance: A software product needs maintenance to support the new features that the users want or to change different types of functionalities of the system according to the customer demands.
39
Embed
UNIT V Software Maintenance V.pdf · Software Maintenance Software Maintenance is the process of modifying a software product after it has been delivered to the customer. The main
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Subject Name: Software Engineering & Project
Management
Subject Code: CS-403
Semester: 4th
UNIT-V
Software Maintenance
Software Maintenance is the process of modifying a software product after it has been delivered
to the customer. The main purpose of software maintenance is to modify and update software
application after delivery to correct faults and to improve performance.
Need for Maintenance – Software Maintenance must be performed in order to:
Correct faults.
Improve the design.
Implement enhancements.
Interface with other systems.
Accommodate programs so that different hardware, software, system features, and
telecommunications facilities can be used.
Migrate legacy software.
Retire software.
Categories of Software Maintenance – Maintenance can be divided into the following:
1. Corrective maintenance: Corrective maintenance of a software product may be essential either to rectify some bugs
observed while the system is in use, or to enhance the performance of the system.
2. Adaptive maintenance: This includes modifications and updations when the customers need the product to run on
new platforms, on new operating systems, or when they need the product to interface with
new hardware and software.
3. Perfective maintenance: A software product needs maintenance to support the new features that the users want or to
change different types of functionalities of the system according to the customer demands.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
4. Preventive maintenance: This type of maintenance includes modifications and updations to prevent future problems
of the software. It goals to attend problems, which are not significant at this moment but
may cause serious issues in future.
Reverse Engineering – Reverse Engineering is processes of extracting knowledge or design information from anything
man-made and reproducing it based on extracted information. It is also called back Engineering.
Software Reverse Engineering – Software Reverse Engineering is the process of recovering the design and the requirements
specification of a product from an analysis of it’s code. Reverse Engineering is becoming
important, since several existing software products, lack proper documentation, are highly
unstructured, or their structure has degraded through a series of maintenance efforts.
Why Reverse Engineering? Providing proper system documentatiuon.
Recovery of lost information.
Assisting with maintenance.
Facility of software reuse.
Discovering unexpected flaws or faults.
Used of Software Reverse Engineering – Software Reverse Engineering is used in software design, reverse engineering enables the
developer or programmer to add new features to the existing software with or without
knowing the source code.
Reverse engineering is also useful in software testing, it helps the testers to study the virus
and other malware code .
Cost of Maintenance
Reports suggest that the cost of maintenance is high. A study on estimating software
maintenance found that the cost of maintenance is as high as 67% of the cost of entire software
process cycle.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
On an average, the cost of software maintenance is more than 50% of all SDLC phases. There
are various factors, which trigger maintenance cost go high, such as:
Real-world factors affecting Maintenance Cost
The standard age of any software is considered up to 10 to 15 years.
Older softwares, which were meant to work on slow machines with less memory and storage capacity
cannot keep themselves challenging against newly coming enhanced softwares on modern hardware.
As technology advances, it becomes costly to maintain old software.
Most maintenance engineers are newbie and use trial and error method to rectify problem.
Often, changes made can easily hurt the original structure of the software, making it hard for any
subsequent changes.
Changes are often left undocumented which may cause more conflicts in future.
Software-end factors affecting Maintenance Cost
Structure of Software Program
Programming Language
Dependence on external environment
Staff reliability and availability
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Maintenance Activities
IEEE provides a framework for sequential maintenance process activities. It can be used in
iterative manner and can be extended so that customized items and processes can be included.
These activities go hand-in-hand with each of the following phase:
Identification & Tracing - It involves activities pertaining to identification of requirement of
modification or maintenance. It is generated by user or system may itself report via logs or error
messages.Here, the maintenance type is classified also.
Analysis - The modification is analyzed for its impact on the system including safety and security
implications. If probable impact is severe, alternative solution is looked for. A set of required
modifications is then materialized into requirement specifications. The cost of
modification/maintenance is analyzed and estimation is concluded.
Design - New modules, which need to be replaced or modified, are designed against requirement
specifications set in the previous stage. Test cases are created for validation and verification.
Implementation - The new modules are coded with the help of structured design created in the
design step.Every programmer is expected to do unit testing in parallel.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
System Testing - Integration testing is done among newly created modules. Integration testing is also
carried out between new modules and the system. Finally the system is tested as a whole, following
regressive testing procedures.
Acceptance Testing - After testing the system internally, it is tested for acceptance with the help of
users. If at this state, user complaints some issues they are addressed or noted to address in next
iteration.
Delivery - After acceptance test, the system is deployed all over the organization either by small
update package or fresh installation of the system. The final testing takes place at client end after the
software is delivered.
Training facility is provided if required, in addition to the hard copy of user manual.
Maintenance management - Configuration management is an essential part of system maintenance.
It is aided with version control tools to control versions, semi-version or patch management.
Software Re-engineering
When we need to update the software to keep it to the current market, without impacting its
functionality, it is called software re-engineering. It is a thorough process where the design of
software is changed and programs are re-written.
Legacy software cannot keep tuning with the latest technology available in the market. As the
hardware become obsolete, updating of software becomes a headache. Even if software grows
old with time, its functionality does not.
For example, initially Unix was developed in assembly language. When language C came into
existence, Unix was re-engineered in C, because working in assembly language was difficult.
Other than this, sometimes programmers notice that few parts of software need more
maintenance than others and they also need re-engineering.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Re-Engineering Process
Decide what to re-engineer. Is it whole software or a part of it?
Perform Reverse Engineering, in order to obtain specifications of existing software.
Restructure Program if required. For example, changing function-oriented programs into object-
oriented programs.
Re-structure data as required.
Apply Forward engineering concepts in order to get re-engineered software.
There are few important terms used in Software re-engineering
Reverse Engineering
It is a process to achieve system specification by thoroughly analyzing, understanding the
existing system. This process can be seen as reverse SDLC model, i.e. we try to get higher
abstraction level by analyzing lower abstraction levels.
An existing system is previously implemented design, about which we know nothing. Designers
then do reverse engineering by looking at the code and try to get the design. With design in
hand, they try to conclude the specifications. Thus, going in reverse from code to system
specification.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Program Restructuring
It is a process to re-structure and re-construct the existing software. It is all about re-arranging
the source code, either in same programming language or from one programming language to a
different one. Restructuring can have either source code-restructuring and data-restructuring or
both.
Re-structuring does not impact the functionality of the software but enhance reliability and
maintainability. Program components, which cause errors very frequently can be changed, or
updated with re-structuring.
The dependability of software on obsolete hardware platform can be removed via re-structuring.
Forward Engineering
Forward engineering is a process of obtaining desired software from the specifications in hand
which were brought down by means of reverse engineering. It assumes that there was some
software engineering already done in the past.
Forward engineering is same as software engineering process with only one difference – it is
carried out always after reverse engineering.
Component reusability
A component is a part of software program code, which executes an independent task in the
system. It can be a small module or sub-system itself.
Example
The login procedures used on the web can be considered as components, printing system in
software can be seen as a component of the software.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Components have high cohesion of functionality and lower rate of coupling, i.e. they work
independently and can perform tasks without depending on other modules.
In OOP, the objects are designed are very specific to their concern and have fewer chances to be
used in some other software.
In modular programming, the modules are coded to perform specific tasks which can be used
across number of other software programs.
There is a whole new vertical, which is based on re-use of software component, and is known as
Component Based Software Engineering (CBSE).
Re-use can be done at various levels
Application level - Where an entire application is used as sub-system of new software.
Component level - Where sub-system of an application is used.
Modules level - Where functional modules are re-used.
Software components provide interfaces, which can be used to establish communication among
different components.
Reuse Process
Two kinds of method can be adopted: either by keeping requirements same and adjusting
components or by keeping components same and modifying requirements.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Requirement Specification - The functional and non-functional requirements are specified, which a
software product must comply to, with the help of existing system, user input or both.
Design - This is also a standard SDLC process step, where requirements are defined in terms of
software parlance. Basic architecture of system as a whole and its sub-systems are created.
Specify Components - By studying the software design, the designers segregate the entire system
into smaller components or sub-systems. One complete software design turns into a collection of a
huge set of components working together.
Search Suitable Components - The software component repository is referred by designers to search
for the matching component, on the basis of functionality and intended software requirements..
Incorporate Components - All matched components are packed together to shape them as complete
software.
System Configuration Management (SCM) is an arrangement of exercises which controls
change by recognizing the items for change, setting up connections between those things,
making/characterizing instruments for overseeing diverse variants, controlling the changes being
executed in the current framework, inspecting and revealing/reporting on the changes made. It is
essential to control the changes in light of the fact that if the changes are not checked
legitimately then they may wind up undermining a well-run programming. In this way, SCM is a
fundamental piece of all project management activities.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Processes involved in SCM – Configuration management provides a disciplined environment for smooth control of work
products. It involves the following activities:
Identification and Establishment – Identifying the configuration items from products that
compose baselines at given points in time (a baseline is a set of mutually consistent
Configuration Items, which has been formally reviewed and agreed upon, and serves as the basis
of further development). Establishing relationship among items, creating a mechanism to manage
multiple level of control and procedure for change management system.
Version control – Creating versions/specifications of the existing product to build new
products from the help of SCM system. A description of version is given below:
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Suppose after some changes, the version of configuration object changes from 1.0 to 1.1. Minor
corrections and changes result in versions 1.1.1 and 1.1.2, which is followed by a major update
that is object 1.2. The development of object 1.0 continues through 1.3 and 1.4, but finally, a
noteworthy change to the object results in a new evolutionary path, version 2.0. Both versions
are currently supported.
Change control – Controlling changes to Configuration items (CI). The change control
process is explained in Figure below:
A change request (CR) is submitted and evaluated to assess technical merit, potential side
effects, overall impact on other configuration objects and system functions, and the projected
cost of the change. The results of the evaluation are presented as a change report, which is used
by a change control board (CCB) —a person or group who makes a final decision on the status
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
and priority of the change. An engineering change Request (ECR) is generated for each approved
change.
Also CCB notifies the developer in case the change is rejected with proper reason. The ECR
describes the change to be made, the constraints that must be respected, and the criteria for
review and audit. The object to be changed is ―checked out‖ of the project database, the change
is made, and then the object is tested again. The object is then ―checked in‖ to the database and
appropriate version control mechanisms are used to create the next version of the software.
Configuration auditing – A software configuration audit complements the formal technical
review of the process and product. It focuses on the technical correctness of the configuration
object that has been modified. The audit confirms the completeness, correctness and consistency
of items in the SCM system and track action items from the audit to closure.
Reporting – Providing accurate status and current configuration data to developers, tester,
end users, customers and stakeholders through admin guides, user guides, FAQs, Release notes,
Subversion, Perforce, TortoiseSVN, IBM Rational team concert, IBM Configuration
management version management, Razor, Ansible, etc. There are many more in the list.
It is recommended that before selecting any configuration management tool, have a proper
understanding of the features and select the tool which best suits your project needs and be clear
with the benefits and drawbacks of each before you choose one to use.
Difference between Forward Engineering and Reverse
Engineering
Forward Engineering: Forward Engineering is a method of creating or making an application with the help of the given
requirements. Forward engineering is also known as Renovation and Reclamation. Forward
engineering is required high proficiency skill. It takes more time to construct or develop an
application.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Reverse Engineering: Reverse Engineering is also known as backward engineering, is the process of forward
engineering in reverse. In this, the information are collected from the given or exist application.
It takes less time than forward engineering to develop an application. In reverse engineering the
application are broken to extract knowledge or its architecture.
Difference between Forward Engineering and Reverse Engineering:
S.NO FORWARD ENGINEERING REVERSE ENGINEERING
1.
In forward engineering, the application
are developed with the given
requirements.
In reverse engineering or backward
engineering, the information are
collected from the given application.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
2.
Forward Engineering is high
proficiency skill.
Reverse Engineering or backward
engineering is low proficiency skill.
3.
Forward Engineering takes more time to
develop an application.
While Reverse Engineering or backward
engineering takes less time to develop
an application.
4.
The nature of forward engineering is
Prescriptive.
The nature of reverse engineering or
backward engineering is Adaptive.
5.
In forward engineering, production is
started with given requirements.
In reverse engineering, production is
started by taking existing product.
6.
The example of forward engineering are
construction of electronic kit,
construction DC MOTOR etc.
The example of backward engineering
are research on Instruments etc.
Software Re-engineering
Software Re-engineering is a process of software development which is done to improve the
maintainability of a software system. Re-engineering is the examination and alteration of a
system to reconstitute it in a new form. This process encompasses a combination of sub-
processes like reverse engineering, forward engineering, reconstructing etc.
Re-engineering is the reorganizing and modifying existing software systems to make them more
maintainable.
Objectives of Re-engineering:
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
To describe a cost-effective option for system evolution.
To describe the activities involved in the software maintenance process.
To distinguish between software and data re-engineering and to explain the problems of
data re-engineering.
Steps involved in Re-engineering: 1. Inventory Analysis
2. Document Reconstruction
3. Reverse Engineering
4. Code Reconstruction
5. Data Reconstruction
6. Forward Engineering
Diagrammatic Representation:
Re-engineering Cost Factors: The quality of the software to be re-engineered
The tool support available for re-engineering
The extent of the required data conversion
The availability of expert staff for re-engineering
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Advantages of Re-engineering:
Reduced Risk: As the software is already existing, the risk is less as compared to new software
development. Development problems, staffing problems and specification problems are the
lots of problems which may arise in new software development.
Reduced Cost: The cost of re-engineering is less than the costs of developing new software.
Software Engineering:
Software engineering covers not only the technical aspects of building software systems, but also
management issues, such as directing programming teams, scheduling, and budgeting.
Software engineering is an engineering branch associated with development of software product
using well-defined scientific principles, methods and procedures. The outcome of software
engineering is an efficient and reliable software product.
Software project management has wider scope than software engineering process as it involves
communication, pre and post-delivery support etc.
The need of software engineering arises because of higher rate of change in user requirements
and environment on which the software is working.
Large software- It is easier to build a wall than to a house or building, likewise, as the
size of software become large engineering has to step to give it a scientific process.
Scalability- If the software process were not based on scientific and engineering
concepts, it would be easier to re-create new software than to scale an existing one.
Cost- As hardware industry has shown its skills and huge manufacturing has lower down
the price of computer and electronic hardware. But the cost of software remains high if
proper process is not adapted.
Dynamic Nature- The always growing and adapting nature of software hugely depends
upon the environment in which user works. If the nature of software is always changing,
new enhancements need to be done in the existing one. This is where software
engineering plays a good role.
Quality Management- Better process of software development provides better and
quality software product.
RE Engineering:
• Restructuring or rewriting part or all of a system without changing its functionality
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
• Applicable when some (but not all) subsystems of a larger system require frequent maintenance
• Reengineering involves putting in the effort to make it easier to maintain
• The reengineered system may also be restructured and should be re-documented
When do you decide to reengineer?
• When system changes are confined to one subsystem, the subsystem needs to be reengineered
• When hardware or software support becomes obsolete
• When tools to support restructuring are readily available
Economics of Reengineering:
• Cost of maintenance: cost annual of operation and maintenance over application lifetime
• Cost of reengineering: predicted return on investment reduced by cost of implementing
changes and engineering risk factors
• Cost benefit: Cost of re engineering - Cost of maintenance
Re-engineering advantages:
Reduced risk
There is a high risk in new software development. There may be development problems, staffing
problems and specification problems
Reduced cost
The cost of re-engineering is often significantly less than the costs of developing new software
The complete Software Re-Engineering lifecycle includes:
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Product Management: Risks analysis, root cause analysis, business analysis, requirements
elicitation and management, product planning and scoping, competitive analysis
Research and Innovation: Definition of a problem, data gathering and analysis, identifying a
solution and developing best-of-breed or innovative algorithms, verification of quality for data
and results, patent preparation
Product Development: Technology analysis and selection, software architecture and design, data
architecture, deployment architecture, prototyping and production code development,
comprehensive software testing, data quality testing, and product packaging and deployment
preparation
Product Delivery and Support: Hardware/Platform analysis and selection, deployment and
release procedures definition, installations and upgrades, tracking support issues, organizing
maintenance releases.
Project Management: Brings efficiency and productivity to your software re-engineering project
by utilizing modern, practical software project management, software quality assurance, data
quality assurance, and advanced risk management techniques.
Reverse Engineering:
Reverse engineering is taking apart an object to see how it works in order to duplicate or enhance
the object. The practice, taken from older industries, is now frequently used on computer
hardware and software. Software reverse engineering involves reversing a program's machine
code (the string of 0s and 1s that are sent to the logic processor) back into the source code that it
was written in, using program language statements.
Reverse-engineering is used for many purposes: as a learning tool; as a way to make new,
compatible products that are cheaper than what's currently on the market; for making software
interoperate more effectively or to bridge data between different operating systems or databases;
and to uncover the undocumented features of commercial products.
Following are reasons for reverse engineering a part or product:
1. The original manufacturer of a product no longer produces a product
2. There is inadequate documentation of the original design
3. The original manufacturer no longer exists, but a customer needs the product
4. The original design documentation has been lost or never existed
5. Some bad features of a product need to be designed out. For example, excessive wear
might indicate where a product should be improved
6. To strengthen the good features of a product based on long-term usage of the product
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
7. To analyze the good and bad features of competitors' product
8. To explore new avenues to improve product performance and features
9. To gain competitive benchmarking methods to understand competitor's products and
develop better products
10. The original CAD model is not sufficient to support modifications or current
manufacturing methods
11. The original supplier is unable or unwilling to provide additional parts
12. The original equipment manufacturers are either unwilling or unable to supply
replacement parts, or demand inflated costs for sole-source parts
13. To update obsolete materials or antiquated manufacturing processes with more current,
less-expensive technologies.
Software Project Management (SPM)
Software Project Management (SPM) is a proper way of planning and leading software
projects. It is a part of project management in which software projects are planned, implemented,
monitored and controlled.
Need of Software Project Management: Software is an non-physical product. Software development is a new stream in business and
there is very little experience in building software products. Most of the software products are
made to fit client’s requirements. The most important is that the basic technology changes and
advances so frequently and rapidly that experience of one product may not be applied to the
other one. Such type of business and environmental constraints increase risk in software
development hence it is essential to manage software projects efficiently.
It is necessary for an organization to deliver quality product, keeping the cost within client’s
budget constrain and deliver the project as per scheduled. Hence in order, software project
management is necessary to incorporate user requirements along with budget and time
constraints.
Software Project Management consists of several different type of managements:
1. Conflict Management: Conflict management is the process to restrict the negative features of conflict while
increasing the positive features of conflict. The goal of conflict management is to improve
learning and group results including efficacy or performance in an organizational setting.
Properly managed conflict can enhance group results.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
2. Risk Management: Risk management is the analysis and identification of risks that is followed by
synchronized and economical implementation of resources to minimize, operate and
control the possibility or effect of unfortunate events or to maximize the realization of
opportunities.
3. Requirement Management: It is the process of analyzing, prioritizing, tracing and documenting on requirements and
then supervising change and communicating to pertinent stakeholders. It is a continuous
process during a project.
4. Change Management: Change management is a systematic approach for dealing with the transition or
transformation of an organization’s goals, processes or technologies. The purpose of
change management is to execute strategies for effecting change, controlling change and
helping people to adapt to change.
5. Software Configuration Management: Software configuration management is the process of controlling and tracing changes in the
software, part of the larger cross-disciplinary field of configuration management. Software
configuration management include revision control and the inauguration of baselines.
6. Release Management: Release Management is the task of planning, controlling and scheduling the build in
deploying releases. Release management ensures that organization delivers new and
enhanced services required by the customer, while protecting the integrity of existing
services.
Aspects of Software Project Management:
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Advantages of Software Project Management: It helps in planning of software development.
Implementation of software development is made easy.
Monitoring and controlling are aspects of software project management.
It overall manages to save time and cost for software development. Feasibility is defined as the practical extent to which a project can be performed successfully. To
evaluate feasibility, a feasibility study is performed, which determines whether the solution considered to
accomplish the requirements is practical and workable in the software. Information such as resource
availability, cost estimation for software development, benefits of the software to the organization after it
is developed and cost to be incurred on its maintenance are considered during the feasibility study. The
objective of the feasibility study is to establish the reasons for developing the software that is acceptable
to users, adaptable to change and conformable to established standards. Various other objectives of
feasibility study are listed below.
• To analyze whether the software will meet organizational requirements.
• To determine whether the software can be implemented using the current technology and
within the specified budget and schedule.
• To determine whether the software can be integrated with other existing software.
TRINITY INSTITUTE OF TECHNOLOGY AND RESEARCH BHOPAL
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Prepared by : URMILA MAHOR
Types of Feasibility Various types of feasibility that are commonly considered include technical feasibility,
operational feasibility, and economic feasibility.
Technical feasibility assesses the current resources (such as hardware and software) and
technology, which are required to accomplish user requirements in the software within the
allocated time and budget. For this, the software development team ascertains whether the
current resources and technology can be upgraded or added in the software to accomplish
specified user requirements. Technical feasibility also performs the following tasks.
• Analyzes the technical skills and capabilities of the software development team members.
• Determines whether the relevant technology is stable and established.
• Ascertains that the technology chosen for software development has a large number of users so
that they can be consulted when problems arise or improvements are required.
Operational feasibility assesses the extent to which the required software performs a series of
steps to solve business problems and user requirements. This feasibility is dependent on human
resources (software development team) and involves visualizing whether the software will
operate after it is developed and be operative once it is installed. Operational feasibility also
performs the following tasks.
• Determines whether the problems anticipated in user requirements are of high priority.
• Determines whether the solution suggested by the software development team is acceptable.
• Analyzes whether users will adapt to a new software.
• Determines whether the organization is satisfied by the alternative solutions proposed by the