Showing posts with label SOFTWARE ENGINEERING. Show all posts
Showing posts with label SOFTWARE ENGINEERING. Show all posts

Sunday, September 1, 2013

PPT ON INTRODUCTION TO SOFTWARE ENGINEERING


Download

Introduction to Software Engineering Presentation Transcript:
1.Introduction to Software Engineering

2.What is Software?
Some of the constituted items of software are described below:
Program: The program or code itself is definitely included in the software.
Data: The data on which the program operates is also considered as part of the software.
Documentation: All the documents related to the software are also considered as part of the software. So the software is not just the code written in Cobol, Java, Fortran or C++. It also includes the data and all the documentation related to the program.

3.Why is it important?
Some of the major areas in which software has played an important role are identified as under. 
Business decision-making
Modern scientific investigation and engineering problem solving
Bioinformatics and the process of DNA decoding is only possible by the use of software systems
Games
Embedded systems
Small microcontrollers used in our cars, televisions, microwave ovens etc. All these systems are controlled through the software. 

4.What is Engineering?
The process of productive use of scientific knowledge is called engineering.”

5.Difference bet. Computer Science & Software Engineering
The Science concerned with putting scientific knowledge to practical use.

“This is the process of utilizing our knowledge of computer science in effective production of software systems.”

6.Difference bet. Software & Other Systems
The major thing that distinguishes a software system from other systems is that:
“Software does not wear out”

7.What does that mean?
Software systems does not affect by the phenomenon of wear and tear.
If a software has any defect then that defect will be there from very first day.

8.Software Crisis
In early 60s software had suffered from different kind of problem to which we call Software Crisis. Techniques that were used to develop small software were not applicable for large software systems. 
In most of the cases that software which was tried to be build using old tools and techniques were not complete. 
Most of the times it was delivered too late. 
Most of the projects were over-budgeted. 
And in most of the case systems were not be able to do what they were expected to do. 

9.Solution
As a result of these problems a conference were held in 1960 in which the term software crisis was introduced.
The major issue discussed was that the development of software is in crisis and we have not been able to handle its complexities.  
In this conference people have said that, we should use engineering principles in developing software in the same way as we use these principles in developing cars, buildings, electronic devices etc.
Software engineering is the result of software crisis when people realized that it is not possible to construct complex software using the techniques applicable in 1960s. An important result of this thing was that people had realized that just coding is not enough.

10.Software Engineering as defined by IEEE
“The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.”

11.Somerville
Another definition of Software Engineering given by Ian Somerville.
 “All aspects of software production’ Software engineering is not just concerned with the technical processes of software development but also with activities such as software project management and with the development of tools, methods and theories to support software production”.

12.Make it clear
These definitions make it clear that the software engineering is not just about writing code. 

13.Software Engineering cover
  Software Engineering cover all things that are used in software production like:
 Programming Language  
 Programming Language Design
 Software Design Techniques 
 Tools 
 Testing 
 Maintenance 
 Development etc. 
  So all those thing that are related to software are also related to software engineering. 

14.Well-Engineered Software
Well-engineered software is one that has the following characteristics:
Provides the required functionality 
Maintainable 
Reliable 
Efficient 
User-friendly 
Cost-effective 

15.Major Challenge for Software Engineer
The major challenges for a software engineer is that he has to build software within limited time and budget in a cost-effective way and with good quality.

Source: Power Point Presentations

PPT ON SOFTWARE ENGINEERING


Download

SOFTWARE ENGINEERING Presentation Transcript:
1.SOFTWARE ENGINNERING

2. THE CONSTRUCTIVE COST MODEL
(COCOMO MODEL)

3.OUTLINE OF PRESENTATION 
OVERVIEW
ARCHITECTURE OF COCOMO MODEL
BASIC CONCEPT OF COCOMO MODEL?
TYPES OF COCOMO MODEL
INTERMEDIATE COCOMO
ADVANTAGE OF COCOMO
DISADVANTAGE OF COCOMO
MULTIPLERS
COST DRIVERS
LIMITATIONS
CHARACTERISTICS OF COCOMO
CONCULSION

4.OVERVIEW
The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry W. Boehm
COCOMO was first published in Boehm's 1981 book Software Engineering Economics[1] as a model for estimating effort, cost, and schedule for software projects

5.ARCHITECTURE OF COCOMO MODEL 

6.BASIC CONCEPT OF  COCOMO MODEL
computes software development effort (and cost) as a function of program size. Program size is expressed in estimated thousands of source lines of code (SLOC)
COCOMO applies to three classes of software projects:

7.BASIC COCOMO EQUATION TAKE FORM
Effort Applied (E) = ab(KLOC)bb [ man-months ]
Development Time (D) = cb(Effort Applied)db [months]
People required (P) = Effort Applied / Development Time [count]

8.TYPES OF COCOMO MODEL
Organic projects - "small" teams with "good" experience working with "less than rigid" requirements
Semi-detached projects - "medium" teams with mixed experience working with a mix of rigid and less than rigid requirements
Embedded projects - developed within a set of "tight" constraints. It is also combination of organic and semi-detached projects.(hardware, software, operational, ...)

9.ITERATIONS COCOMO MODEL

10.INTERMEDIATE COCOMO
PRODUCT  ATRIBUTES
HARDWARE  ATRIBUTES
PERSONAL ATRIBUTES
PROJECT ATRIBUTES

11.PRODUCT ATRIBUTES
Required software reliability
Size of application database
Complexity of the product

12.HARDWARE ATRIBUTES
Run-time performance constraints
Memory constraints
Volatility of the virtual machine environment
Required turnabout time

13.PERSONAL ATRIBUTES
Analyst capability
Software engineering capability
Applications experience
Virtual machine experience
Programming language experience

14.PROJECT ATRIBUTES
Use of software tools
Application of software engineering methods
Required development schedule

15.GRAPH

Source: Power Point Presentations