1. Meghe Group of Institutions Department for Technology Enhanced Learning 1

2. VI SEM CSE UNIT I SOFTWARE ENGINEERING & PROJECT MANAGEMENT SOFTWARE ENGINEERING – AN INTRODUCTION By Mr. Vaibhav V. Bhujade DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING DMIETR, Sawangi (Meghe)

3. SYLLABUS Introduction to Software Engineering Software Myths Software Process Framework Software Process Model :- – The Waterfall Model, Incremental Process Model – Evolutionary Process Model, Specialized Process Model – The Unified Process Model, Agile Process Model 3 UNIT I

4. LEARNING OBJECTIVES At the end of this unit student are able to know :- Basic things about software. About software myths Also various types of development model for software. 4 UNIT I

5. SOFTWARE Software is developed not manufactured. Software doesn’t “wear out”. Industry is moving toward component based construction, most software continues to be custom build. 5 UNIT I

6. CATEGORIES OF SOFTWARE System s/w Application s/w Engg/Scientific s/w Embedded s/w Product Line s/w 6 UNIT I Web Application AI Software Ubiquitous Computing Net sourcing Open Source

7. SOFTWARE MYTHS Management Myths Customer Myths Practitioner’s Myths 7 UNIT I

8. Management Myths We already have book of standard and procedure for building software. If we get behind schedule, we can add more programmer. We outsource software project to third party then be relax. 8 UNIT I

9. Customer Myths Begin writing the programs, later we can fill the details. Requirement continually change & change can easily adopted as software is flexible. 9 UNIT I

10. Practitioner’s Myths Once we write the program & get it to work, our job is done. When the program is in running then we can not access the quality. Working software is the final product. Create unnecessary documentation so slow down the speed of development. 10 UNIT I

11. SOFTWARE ENGINEERING – A LAYERED TECHNOLOGY 11 UNIT I

12. PROCESSPROCESS 12 UNIT I FRAMEWORKFRAMEWORK

13. WATERFALL MODEL 13 UNIT I

14. INCREMENTAL PROCESS MODEL Incremental Model RAD Model 14 UNIT I

15. Incremental Model 15 UNIT I

16. RAD Model 16 UNIT I

17. EVOLUTIONARY PROCESS MODEL Prototype Model Spiral Model 17 UNIT I

18. Prototype Model 18 UNIT I

19. Spiral Model 19 UNIT I Estimation Scheduling Risk analysis Delivery feedback Code test Analysis design

20. SPECIALIZED PROCESS MODEL Component Based development Formal Method Model Aspect Oriented Software Development 20 UNIT I

21. Phases of Unified Process 21 UNIT I

22. 22 INCEPTION PHASE Vision Document Initial use case model Initial project glossary Initial business case Initial risk assessment Project plan phases & iteration Business model if necessary One or more prototype ELABORATION PHASE Use case model Supplementary requirement Including nonfunctional Analysis model s/w architecture description Executable architectural prototype Preliminary design model Revised risk list Project plan including Iteration plan Adaptable workflow Milestone Technical work product Preliminary user manual CONSTRUCTION PHASE Design model s/w component Integrated s/w increment Test plan & procedure Test cases Support documentation user manual installation manual description of current increment TRANSITION PHASE Delivered s/w increment Beta test report General user feedback UNIT I MAJOR WORK PRODUCT FOR UP PHASE

23. AGILITY Agile means Nimble (able to respond to changes). Changes in the s/w to built, team member, new technology or all kind of change that impact on product. It is effective response to change. Adopt customer as a development team. 23 UNIT I

24. AGILE PROCESS MODEL Extreme Programming Adoptive Software Development Dynamic System Development Method Scrum Crystal Feature Driven Development Agile Modeling 24 UNIT I

25. Extreme Programming (XP) 25 UNIT I

26. Adoptive Software Development 26 UNIT I 1111

27. DYNAMIC SYSTEM DEVELOPMENT METHOD – 80% Work Feasibility Study Business Study Functional Model Iteration Design & Build iteration Implementation 27 UNIT I

28. Scrum Backlog (changes are managed) Sprints – Backlog are frozen for work in stable environment. Scrum Meeting – Scrum master assesses response from each person Demos – Does not contain all functionality 28 UNIT I

29. Scrum Continues......... 29 UNIT I

30. Feature Driven Development As feature are small block of functionality so user can describe it easily. Organize into hierarchical business related group Team develop operation feature every 2 week Design & code representation are easier to inspect Planning, scheduling & tracking are driven by feature hierarchy. 30 UNIT I

31. FDD Continues......... 31 UNIT I

32. Design Walkthrough Design Design Implementation Code Code Inspection Promote to built 32 UNIT I FDD Continues.........

33. Agile Modeling When large or business critical system are going to built then:- Everyone can better understand what need to be done. Problem can be partitioned effectively among all who can solve it. Quality can be access at every step as system is being built. 33 UNIT I

34. Agile Modeling Continues......... Model with purpose Use multiple model Travel high Content is more important than representation Know the model & tool using for development Adopt locally 34 UNIT I

35. SUMMARY We describe the software & Different categories of software. Types of software myths. Different types of software development model. 35 UNIT I

36. REFERENCE Software Engineering – A Practitioner’s Approach (VI Edition) by Roger S. Pressman 36 UNIT I

37. Thank you. 37