1. Software Engineering – Fall 2015 (CSC 4350/6350) TR. 5:30 pm – 7:15 pm Rao Casturi 09/01/2015 http://cs.gsu.edu/~ncasturi1

2. GSU: Software Engineering - CSC4350/6350 - Rao Casturi 2 Drop Box Folder Structure Includes Individual Bio- Data Information

3. GSU: Software Engineering - CSC4350/6350 - Rao Casturi 3 Class Project Discussion Documents and project list Project Team names Project Team Leads

4. Project List GSU: Software Engineering - CSC4350/6350 - Rao Casturi 4 1.Online Shopping cart 2.Cell phone app ? 3.Online SQL Database Engine 4.Inventory for a small company 5.Online Hotel Management System 6.Scheduler 7.Attendance System

5. Introduction to Software Engineering 5 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

6. What I asked and What did I get? Acknowledgements to unknown author 6 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

7. Software Engineering Failures The explosion of the Ariane 5 (June 4 th. 1996) – $7bn Cost, Decade of development – 64 bit floating point conversion to a 16 bit signed integer Y2K Bug C-17 unnecessary complexity – $500 mm over budget – 19 onboard computers – 80 microprocessors and 6 different languages Mariner 1 (Venus flyby) 1962 July 22 nd. 7 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

8. What is Software Engineering? 1.Modeling Activity  Complexity through modeling  Focus on relevant details  Ignore other details not related to the problem  Model is an abstract representation of the system that can answer questions about the system  Size, Cost, Time, Complexity  Application Domain and Solution Domain  OO Methods combine App. Domain and Solution Domain modeling activates into one 8 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

9. 9 Modeling Activity – Cost, Time & Scope Any one variable will impact other variables Adding people at the end of the project will cut short the project time?

10. What is Software Engineering? 2. Problem Solving Activity  Through models we search for a solution  Best fit Method (Trial and Error)  Usually involves 5 simple steps Formulate the problem Analyze the problem Search for the solutions Decide on the appropriate solution Specify the solution 10 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

11. Requirement Elicitation Analysis System Design Object DesignImplementation What is Software Engineering? 2. Problem Solving Activity Object – Oriented Software Development usually includes 6 steps Testing 11 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

12. 3. Knowledge Acquisition Activity  Knowledge acquisition is NOT LINEAR  New knowledge about the system can through all the acquired knowledge  Different Methodologies  Risk-based  Issue-based What is Software Engineering? 12 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

13. 4. Rationale Activity  Why the solution was proposed is critical to capture  Not easy activity What is Software Engineering? 13 GSU: Software Engineering - CSC4350/6350 - Rao Casturi

14. Problem Solving Knowledge Acquisition Rationale Modeling Software Engineering 14 GSU: Software Engineering - CSC4350/6350 - Rao Casturi What is Software Engineering?

15. Software Engineering Concepts Software Engineering - Fall 2014 CSC4350/6350 - Rao Casturi 15 Software engineering concepts depicted as a UML class diagram. [Bruegge, Dutoit] Projects – Activity – Tasks and Work Product

16. Work Product Work Product : – Is an artifact produced during the development – System – Specification Document – Operational Manual – Status Reports – Testing Manual Software Engineering - Fall 2014 CSC4350/6350 - Rao Casturi 16

17. Roles and Responsibilities Client – Provide high level requirements – Scope – Fund – Set delivery time, quality User – Provide knowledge about the system – Feedback – Testing Project Manager – Overall management – Face to the Client Software Engineering - Fall 2014 CSC4350/6350 - Rao Casturi 17 Developer Construction of the system Testing Technical Writer Documentation Reference manual Support Product support Installation

18. Functional and Non Functional Requirement Functional – Specification a system should support – Need to have Non Functional – Constraint on the System – No direct relation to the function of the system Software Engineering - Fall 2014 CSC4350/6350 - Rao Casturi 18

19. Software Engineering Development Activities Requirement Elicitation (Gathering) Analysis System Design Object Design Implementation Testing Software Engineering - Fall 2014 CSC4350/6350 - Rao Casturi 19 Requirements Analysis System Design Object Design Implementation Testing

20. Managing Software Development Communication – Time consuming activity – Critical for the project Rational Management – Justification – Complex activity Software Configuration – Version controls – Maintenance Project Management – Art Software Life Cycle – Putting it all together is the life cycle of the Software Development Software Engineering - Fall 2014 CSC4350/6350 - Rao Casturi 20

21. Questions ? 21 GSU: Software Engineering - CSC4350/6350 - Rao Casturi