Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Software Engineering Introduction and Overview: CSE1320 Intermediate Programming, Slides of Software Engineering

software engineering chap 1 ppt

Typology: Slides

2019/2020

Uploaded on 09/10/2020

unknown user
unknown user 🇮🇳

1 document

1 / 19

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Engineering Introduction and
Overview
RA402 jcmt CSE1320 Intermediate
Programming
Essence and Accident
Inherent
Difficulties
Complexity
Conformity
Changeabilit
y
Invisibility
Essence
difficulties
inherent in the
nature of software
Accidents
difficulties
encountered but
not inherent
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13

Partial preview of the text

Download Software Engineering Introduction and Overview: CSE1320 Intermediate Programming and more Slides Software Engineering in PDF only on Docsity!

Overview RA402 jcmt CSE1320 Intermediate

Essence and Accident

  • (^) Inherent

Difficulties

  • (^) Complexity
  • (^) Conformity
  • (^) Changeabilit y
  • (^) Invisibility
  • (^) Essence
  • (^) difficulties inherent in the nature of software
  • (^) Accidents
  • (^) difficulties encountered but not inherent

Overview RA402 jcmt CSE1320 Intermediate

Software Engineering Processes

attempt to maximize QUALITY in the

form of:

  • (^) Reliability
  • (^) Portability
  • (^) Efficiency
  • (^) Human Engineering
    • (^) Testability
    • (^) Understandability
    • (^) Modifiability

Overview RA402 jcmt CSE1320 Intermediate

What are the phases in

the lifecycle of a software product?

  • (^) Requirements
  • (^) Specifications
  • (^) Design
  • (^) Implementation
    • (^) Integration
    • (^) Maintenance
    • (^) Retirement

Overview RA402 jcmt CSE1320 Intermediate

Requirements Phase

“What I need , not what I said I

needed”

  • (^) What does the

problem require

in terms of the

solution?

  • (^) Written document
  • (^) Customer driven
    • (^) Requirements

testing

  • (^) Rapid prototype
  • (^) Mock-up
  • (^) Partial system

Overview RA402 jcmt CSE1320 Intermediate

Design Phase

How does the product do what it is supposed to do?

  • (^) Analysis of the problem
    • (^) Structured analysis : decomposing problem by how data is manipulated (acted upon)
    • (^) Object-oriented analysis: decomposing problem by how data is represented - (^) Developer must make design decisions about: - (^) algorithms - (^) data representations - (^) I/O interfaces - data flow - (^) modules - (^) Design testing - (^) traceability

Overview RA402 jcmt CSE1320 Intermediate

Implementation Phase

Initial CS courses have to focus on this element first

  • (^) Code
  • (^) Documentation
  • (^) Tests
    • (^) Implementation

testing

  • (^) desk checking
  • (^) test cases
  • (^) reviews

Overview RA402 jcmt CSE1320 Intermediate

Maintenance Phase

In the user’s hands

  • (^) Maintenance testing
    • (^) changes
    • (^) regression testing
  • (^) Retirement
    • (^) cost-effective?
  • (^) Why?
  • (^) operation
  • (^) documentation
  • (^) turnover
  • (^) Kinds of maintenance
  • (^) Corrective
  • (^) Adaptive
  • (^) Perfective
  • (^) Preventive

Overview RA402 jcmt CSE1320 Intermediate

Specification principles

  • (^) Separate functionality from implementation
    • (^) A process-oriented systems spec language is required
    • (^) A spec must encompass the system of which the SW is a component
    • (^) A spec must encompass the environment in which the system operates
    • (^) A system spec must be a cognitive model
    • (^) A spec must be operational
    • (^) The spec must be tolerant of incompleteness and augmentable
    • (^) A spec must be localized and loosely coupled

Overview RA402 jcmt CSE1320 Intermediate

Analysis principles and issues

  • (^) Analysis is information-driven
    • (^) First provide a mechanism for representing info then derive function and behavior
    • (^) Common characteristics
      1. mechanism for info domain analysis
      2. approach for functional and/or behavior representation
      3. definition of interfaces
      4. mechanisms for problem partitioning
      5. support of abstraction
      6. representation of essential and implementation views

Overview RA402 jcmt CSE1320 Intermediate

Testing

Testing cannot show the absence of defects, it can only show that software defects are present.

  1. Testing is a process of executing a program with the intent of finding an error.
  2. A good test case is one that has a high probability of finding an as yet undiscovered error.
  3. A successful test is one that uncovers an as yet undiscovered error.

Overview RA402 jcmt CSE1320 Intermediate

Development Testing

  • (^) Debugging approaches
    • brute force
    • (^) backtracking
    • (^) cause elimination
  • (^) Before you fix
    1. Is the cause of this bug also reproduced elsewhere?
    2. What new bug might I be putting in?
    3. What would have prevented this bug?

Overview RA402 jcmt CSE1320 Intermediate

Software Configuration Management

Change is inevitable

  • (^) Activities of SCM
    1. ID change
    2. control change
    3. ensure that change is properly implemented
    4. report change to others
      • (^) SCM output
        • (^) programs
        • (^) documentation
        • (^) data structures

SCM is not the same as maintenance

Overview RA402 jcmt CSE1320 Intermediate

Software Engineering Notes for

CSE1320 Intermediate Programming

  • (^) Sources
    • (^) The Mythical Man-Month, Brooks, Frederick P.; Addison-Wesley Publishing Company, (Reprint)
    • “No Silver Bullet: Essence and Accidents of Software Engineering,”, Computer , Vol. 20, No. 4 (April 1987) pp. 10-
    • (^) Software Engineering,Schach, Stephen R.;Aksen Associates Incorporated Publishers, 1990
    • (^) Software Engineering, A Practitioner’s Approach,Pressman, Roger S.;McGraw-Hill, Inc. 1992
    • Software Engineering, Design, Reliability,and Management,Shooman, Martin L.;McGraw-Hill, Inc. 1983
    • (^) Software Engineering Metrics and Models, Conte, S.D., H.E. Dunsmore, V.Y. Shen;The Benjamin/Cummings Publishing Company, Inc., 1986