Download Software Engineering Notes Pdf for B.tech. We provide B.tech Software Engineering study materials to B.Tech student with free of cost and it can download easily and without registration need. You can Check Software Engineering of B.Tech Subjects Study Materials and Lecture Notes with Syllabus and Important Questions Below. From the following B.tech Software Engineering Notes, you can get the complete Study Material in Single Download Link.
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.
Also, Read The following links for More Information
Software Engineering Notes Pdf for CSE
Computer programs and associated documentation such as requirements, design models, and user manuals. Software products may be developed for a particular customer or may be developed for a general market. Software products may be Generic – developed to be sold to a range of different customers e.g. PC software such as Excel or Word. Custom – developed for a single customer according to their specification. New software can be created by developing new programs, configuring generic software systems or reusing existing software.
Introduction to Software Engineering
The term software engineering is composed of two words, software and engineering. Software is more than just a program code. A program is an executable code, which serves some computational purpose. Software is considered to be a collection of executable programming code, associated libraries and documentations. Software, when made for a specific requirement is called software product. Engineering on the other hand, is all about developing products, using well-defined, scientific principles and methods. So, we can define software engineering as an engineering branch associated with the 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 Engineering Easy Notes Pdf
Software Engineering Notes for CSE | |
Software engineering notes for CSE pdf | |
Software engineering lecture notes pdf | Download |
Software engineering lecture notes ppt | Download |
Software engineering Question Paper Pdf | Download |
List of Software Engineering Reference Books- 2nd Year
- Software Engineering A practitioner’s Approach, Roger S. Pressman, Seventh Edition McGraw-Hill International Edition.
- Fundamentals of Software Engineering, Rajib Mall, Third Edition, PHI.
- Software Engineering, Ian Sommerville, Ninth edition, Pearson education
- The Software Engineering: A Primer, Waman S Jawadekar, Tata McGraw-Hill, 2008
- Software Engineering, A Precise Approach, PankajJalote, Wiley India,2010.
- The Software Engineering, Principles, and Practices, Deepak Jain, Oxford University Press.
- Software Engineering1: Abstraction and modeling, Diner Bjorner, Springer International edition, 2006.
Software Engineering Syllabus – 1st semester
UNIT-I:
Software and Software Engineering: The Nature of Software, The Unique Nature of WebApps, Software Engineering, Software Process, Software Engineering Practice, Software Myths. Process Models: A Generic Process Model, Process Assessment and Improvement, Prescriptive Process Models, Specialized Process Models, The Unified Process, Personal and Team Process Models, Process Terminology, Product and Process.
![Engineering Engineering](/uploads/1/2/3/7/123715522/505864454.jpg)
UNIT-II:
Requirements Analysis And Specification: Requirements Gathering and Analysis, Software Requirement Specification (SRS), Formal System Specification. Software Design: Overview of the Design Process, How to Characterise of a Design?, Cohesion
and Coupling, Layered Arrangement of Modules, Approaches to Software Design
and Coupling, Layered Arrangement of Modules, Approaches to Software Design
UNIT – III:
Function-Oriented Software Design: Overview of SA/SD Methodology, Structured Analysis, Developing the DFD Model of a System, Structured Design, Detailed Design, Design Review, an overview of Object Oriented design. User Interface Design: Characteristics of Good User Interface, Basic Concepts, Types of User Interfaces, Fundamentals of Component-based GUI Development, A User Interface Design Methodology.
UNIT – IV:
Coding And Testing: Coding, Code Review, Software Documentation, Testing, Unit Testing, Black-Box Testing, White-Box Testing, Debugging, Program Analysis Tool, Integration Testing, Testing Object-Oriented Programs, System Testing, Some General Issues Associated with Testing
UNIT – V:
Software Reliability And Quality Management: Software Reliability, Statistical Testing, Software Quality, Software Quality Management System, ISO 9000, SEI Capability Maturity
Model. Computer-Aided Software Engineering: Case and its Scope, Case Environment, Case Support in Software Life Cycle, Other Characteristics of Case Tools, Towards Second Generation CASE Tool, Architecture of a Case Environment
Model. Computer-Aided Software Engineering: Case and its Scope, Case Environment, Case Support in Software Life Cycle, Other Characteristics of Case Tools, Towards Second Generation CASE Tool, Architecture of a Case Environment
UNIT – VI:
Software Maintenance: Software maintenance, Maintenance Process Models, Maintenance Cost, Software Configuration Management. Software Reuse: what can be Reused? Why almost No Reuse So Far? Basic Issues in Reuse Approach, Reuse at Organization Level.
OUTCOMES:
Define and develop a software project from requirement gathering to implementation. Obtain knowledge about principles and practices of software engineering. Focus on the fundamentals of modeling a software project. Obtain knowledge about estimation and maintenance of software systems
Define and develop a software project from requirement gathering to implementation. Obtain knowledge about principles and practices of software engineering. Focus on the fundamentals of modeling a software project. Obtain knowledge about estimation and maintenance of software systems
Software Engineering Review Questions List
- What is the Advantage of Prototype Model.?
- What is functional and nonfunctional Software requirement?
- Explain What is Code and Code Review.?
- Describe prototype model with diagram.
- What are the advantage and disadvantage of Spiral model?
- Explain What is Black Box Testing?
- What is Code and code review?
- Describe agile model.
- Explain What is software requirement specification (SRS)?
- Describe SEI CMM?
- What is software Reengineering process?
- Explain What is Object Oriented Design and Describe its important concepts of Object-Oriented Design
- What are Cohesion and coupling?
- Explian cyclomatic complexity measure? Describe with an example.
- What is software reusability?
- What is client-server technology? Describe three tiers Client-server architecture with suitable example.
- What is Service-oriented architecture (SOA) and Describe its
advantages and disadvantages. - Explian What are the advantage and disadvantage of Black Box Testing.?
- What are different types of maintenance?
- Explian What is software Crisis?
- What is SCRUM?
- Draw the diagram of SPIRAL model.
- What is command line interface (CLI)?
- What are the components of DFD?
Buy Software Engineering Books for 2nd year Online at Amazon.in
Sale Reliability and Safety Engineering (Springer Series in Reliability Engineering)- Ajit Kumar Verma, Srividya Ajit, Durga Rao Karanki
- Springer Nature
- Edition no. 2nd ed. 2016 (10/09/2015)
- Hardcover: 571 pages
- Springer
- Ralph E. White, Venkat R. Subramanian
- Springer
- Edition no. 2010 (04/14/2010)
- Hardcover: 860 pages
- Sofie Pollin, Michael Timmers, Liesbet Van der Perre
- Springer
- Edition no. 2011 (05/29/2013)
- Paperback: 140 pages
- Springer
- David Ratledge
- Springer
- Edition no. 1999 (11/18/1998)
- Paperback: 184 pages
- Engineering Quality Software A Review of Current Practices Standards and Guidelines including New Methods and Development Tools
- D.J. Smith, K.B. Wood
- Springer
- Edition no. 2nd ed. 1989. Softcover reprint of the original 2nd ed. 1989 (10/04/2011)
- Paperback: 284 pages
- Springer
- Zlatan Stojkovic
- Springer
- Edition no. 2012 (11/06/2012)
- Hardcover: 418 pages
We provided the Download Links to Software Engineering Notes Pdf for B.tech- Download Study materials, Books, Lecture Notes, for Engineering Students. Any University student can download given B.Tech Notes and Study material or you can buyB.Tech 2nd Year Software Engineering Books at Amazon also. Share this article with your classmates and friends so that they can also follow Latest Study Materials and Notes on Engineering Subjects. For any query regarding on Software Engineering Pdf Contact us via the comment box below.
Note : Submit your name, email, state and updates category below.
Let us first understand what software engineering stands for. The term is made of two words, software and engineering.
Software is more than just a program code. A program is an executable code, which serves some computational purpose. Software is considered to be collection of executable programming code, associated libraries and documentations. Software, when made for a specific requirement is called software product.
Engineering on the other hand, is all about developing products, using well-defined, scientific principles and methods.
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.
Definitions
IEEE defines software engineering as:
(1) The application of a systematic,disciplined,quantifiable approach to the development,operation and maintenance of software; that is, the application of engineering to software.
(2) The study of approaches as in the above statement.
Fritz Bauer, a German computer scientist, defines software engineering as:
Software engineering is the establishment and use of sound engineering principles in order to obtain economically software that is reliable and work efficiently on real machines.
Software Evolution
The process of developing a software product using software engineering principles and methods is referred to as software evolution. This includes the initial development of software and its maintenance and updates, till desired software product is developed, which satisfies the expected requirements.
Evolution starts from the requirement gathering process. After which developers create a prototype of the intended software and show it to the users to get their feedback at the early stage of software product development. The users suggest changes, on which several consecutive updates and maintenance keep on changing too. This process changes to the original software, till the desired software is accomplished.
Even after the user has desired software in hand, the advancing technology and the changing requirements force the software product to change accordingly. Re-creating software from scratch and to go one-on-one with requirement is not feasible. The only feasible and economical solution is to update the existing software so that it matches the latest requirements.
Software Evolution Laws
Lehman has given laws for software evolution. He divided the software into three different categories:
- S-type (static-type) - This is a software, which works strictly according to defined specifications and solutions. The solution and the method to achieve it, both are immediately understood before coding. The s-type software is least subjected to changes hence this is the simplest of all. For example, calculator program for mathematical computation.
- P-type (practical-type) - This is a software with a collection of procedures. This is defined by exactly what procedures can do. In this software, the specifications can be described but the solution is not obvious instantly. For example, gaming software.
- E-type (embedded-type) - This software works closely as the requirement of real-world environment. This software has a high degree of evolution as there are various changes in laws, taxes etc. in the real world situations. For example, Online trading software.
E-Type software evolution
Lehman has given eight laws for E-Type software evolution -
- Continuing change - An E-type software system must continue to adapt to the real world changes, else it becomes progressively less useful.
- Increasing complexity - As an E-type software system evolves, its complexity tends to increase unless work is done to maintain or reduce it.
- Conservation of familiarity - The familiarity with the software or the knowledge about how it was developed, why was it developed in that particular manner etc. must be retained at any cost, to implement the changes in the system.
- Continuing growth- In order for an E-type system intended to resolve some business problem, its size of implementing the changes grows according to the lifestyle changes of the business.
- Reducing quality - An E-type software system declines in quality unless rigorously maintained and adapted to a changing operational environment.
- Feedback systems- The E-type software systems constitute multi-loop, multi-level feedback systems and must be treated as such to be successfully modified or improved.
- Self-regulation - E-type system evolution processes are self-regulating with the distribution of product and process measures close to normal.
- Organizational stability - The average effective global activity rate in an evolving E-type system is invariant over the lifetime of the product.
Software Paradigms
Software paradigms refer to the methods and steps, which are taken while designing the software. There are many methods proposed and are in work today, but we need to see where in the software engineering these paradigms stand. These can be combined into various categories, though each of them is contained in one another:
Programming paradigm is a subset of Software design paradigm which is further a subset of Software development paradigm.
Software Development Paradigm
This Paradigm is known as software engineering paradigms where all the engineering concepts pertaining to the development of software are applied. It includes various researches and requirement gathering which helps the software product to build. It consists of –
- Requirement gathering
- Software design
- Programming
Software Design Paradigm
This paradigm is a part of Software Development and includes –
- Design
- Maintenance
- Programming
Programming Paradigm
This paradigm is related closely to programming aspect of software development. This includes –
- Coding
- Testing
- Integration
Need of Software Engineering
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 he 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.
Characteristics of good software
A software product can be judged by what it offers and how well it can be used. This software must satisfy on the following grounds:
![Software engineering notes in bca Software engineering notes in bca](/uploads/1/2/3/7/123715522/401625268.jpg)
- Operational
- Transitional
- Maintenance
Well-engineered and crafted software is expected to have the following characteristics:
Operational
This tells us how well software works in operations. It can be measured on:
- Budget
- Usability
- Efficiency
- Correctness
- Functionality
- Dependability
- Security
- Safety
Transitional
This aspect is important when the software is moved from one platform to another:
- Portability
- Interoperability
- Reusability
- Adaptability
Maintenance
This aspect briefs about how well a software has the capabilities to maintain itself in the ever-changing environment:
- Modularity
- Maintainability
- Flexibility
- Scalability
In short, Software engineering is a branch of computer science, which uses well-defined engineering concepts required to produce efficient, durable, scalable, in-budget and on-time software products.