The document discusses software engineering and software maintenance. It describes how software maintenance involves enhancing software products, adapting them to new environments, and fixing problems. It also discusses how development activities like requirements analysis, using standards and guidelines, design principles, coding practices, and documentation can enhance a software product's maintainability over its lifespan of 5-10 years of maintenance following 1-2 years of development.

1. SOFTWARE ENGINEERING
NADAR SARASWATHI COLLEGE OF ARTS AND SCIENCE
BY
V.SAKTHIPRIYA
II-MSC(IT)

2. INTRODUCTION
• The term “software maintenance” is used to describe the
software engineering activities that occur following
delivery of a software product to the customer.
• The development cycle for a software product spans 1 or 2
yrs ,while the maintenance phase spans 5 to 10 years

3. SOFTWARE MAINTENANCE
 maintenance activities involve making enhancements to
software products, adapting products to new environment
and correcting problem.
• Software product may involve providing new functional
capablities ,upgrading external document,internal
documentation,or upgrading the performance
characteristic of a system.

4. ENHANCING MAINTAINABILITY DURING
DEVELOPMENT
 Many activities performed during software development
enhance the maintainablity of a software product.
a. Analysis activities
b. Standards and guidelines
c. Design activities
d. Implementation activities
e. Supporting documents

5. ANALYSIS
ACTIVITIES
STANDARDS
AND
GUIDELINES
DESIGN
ACTIVITIES
IMPLEMENTING
ACTIVITIES
SUPPORTING
DOCUMENTS

6. ANALYSIS ACTIVITIES
 The analysis phase of software development is concerned
with customer requirements and constraints,and
establishing feasability of the product.
 Specify quality assurance procedures and identify likely
product enhancements.
 Estimate maintenance costs.

7. STANDARDS AND GUIDELINES
 Standards and guidelines can be developed to enhance the
maintainability of software standard formats for
requirements and design specification,codingconvention
and supporting documents.
 Develop standards and guidelines.

8. DESIGN ACTIVITES
 Architectural design is concerned with developing the
functional components ,conceptual data structure and
interconnections in a software system.
 The criteria may include coupling and cohesion of
modules and efficiency considerations.
 Design notations such as dataflow diagrams,structure
charts and HIPO should be used in design activities.

9. IMPLEMENTATION ACTIVITIES
 The primary goal of producing software that is easy to
understand and easy to modify single entry single exit
coding constructs.
 In addition ,input and output assertions side effects and
exceptions and exception handling action should be
documented in the prologue of each routine.

10. SUPPORTING DOCUMENTS
 The maintenance guide provides a technical description of
the operational capabilities of the entire system and
hierarchy diagrams,call graph and cross-reference
directories for the system.
 An external description of each module,input and output
assertions ,side effects,global data structure and exception
handling.