Software Engineering. Quiz with Explainations. Hans-Petter Halvorsen, M.Sc.

Transcription

1 Software Engineering Quiz with Explainations Hans-Petter Halvorsen, M.Sc.

2 Questions 1. What is Software Engineering? 2. Give an overview of different Roles in Software Development 3. What kind of skills are typically needed by a Software Engineer? 4. List different types of software applications/systems 5. What are the two fundamental types of software products? 6. What are the different phases involved in software engineering? 7. Name the 2 main categories of software development methods/processes/models 8. List different software development methods/processes/models 9. Explain what Agile Software Development is 10. Explain/make a sketch of what Scrum is

3 What is Software Engineering?

4 What is software engineering? Software Engineering - a systematic approach to the design, development, testing, and maintenance of software. System Engineering: The process of analyzing and designing an entire system, including the hardware and the software. An engineering discipline concerned with all aspects of software production from specification to system maintenance. Software Development in a structured way. Other Names: Software development, Application development, software design, designing software, software application development, enterprise application development, or platform development

5 Give an overview of different Roles in Software Development

6 Teams and Roles Customer/Stakeholders Project Manager Software Architect Database Administrator (DBA) UX Designer Developer Tester etc. Software Architect Collaboration! Project Manager Customer/Stakeholders Software Tester DBA UX Designer Programmer 6

7 Software Teams Stakeholders Project Manager Software Tester UX Designer System Engineer Programmer/Developer Software Architect DBA A System Engineer is a general person that could be a Programmer, Architect, Designer, Tester in different phases in the project, or he could be a tester in one project and a programmer in another project all in one person. That is usually the case in small companies, while in larger companies these roles (designer, tester, programmer) could be a full-time job.

8 Collaboration! Project Manager Software Architect Software Tester Stakeholders UX Designer Programmer Collaboration and Communication within the Team and with Stakeholders, etc. is crucial!

9 Scrum Members/Roles Product Owner Sprint Backlog Stakeholders Product Backlog Scrum Master Scrum Team Development Team 3-9 persons

10 What kind of skills are typically needed by a Software Engineer?

11 Knowledge/Skills Skills in System Engineering, Programming skills like C#, C++, Java, Database knowledge, e.g. Microsoft SQL Server Structured Query Language, Web Programming, HTML, JabaScript, Skills in platforms/frameworks like.net, Visual Studio, Mobile Platforms like Android, ios, etc. Agile Development, like Scrum, etc.

12 Typical Software Developer Ad

13 Software Engineer/Software Developer Job Ads Examples (in Norway): 13

14 Software Engineering Project Management Databases Developmen t Processes Cost Estimation Requirements Design Quality Control Architecture Testing Laws and Ethics Programming 14

15 Software Development Planning, Requirements, Design, Implementation, Testing, Deployment, Maintenance, etc. User Application Operating System Hardware Who are going to use the software? Desktop, Web, Mobile Windows, OS X, Linux, Android, ios, etc. PC, Mac, Smartphone, Tablet, SmartTV, etc.

16 Lidenskap og nysgjerrighet! Lidenskap og nysgjerrighet er grunnleggende kvaliteter for en god Systemutvikler (resten kan læres)!

17 List different types of software applications/systems

18 Types of Software Applications/Systems Stand-alone applications: These are application systems that run on a local computer, such as a PC. They include all necessary functionality and do not need to be connected to a network. Interactive transaction-based applications: Applications that execute on a remote computer and are accessed by users from their own PCs or terminals. These include web applications such as e-commerce applications. Embedded control systems: These are software control systems that control and manage hardware devices. Numerically, there are probably more embedded systems than any other type of system. Batch processing systems: These are business systems that are designed to process data in large batches. They process large numbers of individual inputs to create corresponding outputs. Entertainment systems: These are systems that are primarily for personal use and which are intended to entertain the user. Systems for modeling and simulation: These are systems that are developed by scientists and engineers to model physical processes or situations, which include many, separate, interacting objects. Data collection systems: These are systems that collect data from their environment using a set of sensors and send that data to other systems for processing. Systems of systems: These are systems that are composed of a number of other software systems. I. Sommerville, Software Engineering: Pearson,

19 What are the two fundamental types of software products?

20 Generic vs Customized Software Generic Products Stand-alone systems that are marketed and sold to any customer who wishes to buy them. Examples PC software such as graphics programs, project management tools; CAD software; software for specific markets such as appointments systems for dentists. Example: MS Word Customized Products Software that is commissioned by a specific customer to meet their own needs. Tailor-made Solutions Examples: embedded control systems, air traffic control software, traffic monitoring systems, etc. I. Sommerville, Software Engineering: Pearson, 2010.

21 What are the different phases involved in software engineering?

22

23 STD System Documentation Testing Software Test Documentation Test Plan Test Documentation End-User Documentation Implementation Code System Documentation User Guides Deployment Maintenance Your Software with Documentation Design Installation Guides SDD Planning SDP Software Development Plan Project Planning Gantt Chart Requirements Analysis SRS Software Requirements Specifications Gantt Chart Software Design Documents with ER Diagram, UML Diagrams, CAD Drawings

24 Installation Deployment Acceptance Testing System Testing Functionality Requirements Planning Initial User Interface Technology Platform Selection Support Requirements Technical Architecture Project Plan Application Architecure Detailed Specifications System Interface Software Design Design Development Finalize User Interface involves a lot! Test Plans Maintenance Testing Integration Testing RegressionTesting Implementation Unit Testing Integration with existing Apps Application Code Development System Interface Development

25 Planning Requirements Design

26 Implementation Testing Deployment

27 Name the 2 main categories of software development methods/processes/models

28 2 Main Approches Traditional/Plan-driven Development Waterfall,... Agile Development Scrum,...

29 Planning to create a new Software Requirement Not Finished? -Go back and Fixit! The Waterfall Model Finished Design Not Finished? -Go back and Fixit! Finished Implementation Not Finished? -Go back and Fixit! A Sequential Process Finished Testing Finished You cannot go to next phase before finsihed the previous phase Not Finished? -Go back and Fixit! Deployment Maintenance Software Finished

30 List different software development methods/processes/models

31 Traditional Plan-driven vs. Agile Software Development Processes Traditional/Plan-driven Waterfall Spiral Scrum Lean Agile exreme Programming Kanban V-model FDD TDD "Cannot" go to next phase before previous phase is finished More flexible, Iterative and Incremental Approach

32 Explain what Agile Software Development is

33 Agile Norsk: Smidig utviklings-metoder A group of software development methods Iterative approach Incremental: Software available to Customers every 2-4 weeks Self-organizing and cross-functional Teams Refactoring Examples: Scrum extreme Programming (XP) 33

34 Software Development Daily Scrum Meetings Sprint Reviews & Planning Beta, RC Testing 2-4 weeks 1-12 months 24 hours Days Working Software at all times. Testing every day Weeks Internal Iterations/Sprints Public Beta, RC Releases Months/Years

35

36 Agile vs. Traditional Development 36 Wikipedia. (2013). Agile Software Development. Available:

37 Agile vs. Traditional 37 Essentials of Software Engineering, Frank Tsui; Orlando Karam; Barbara Bernal, 3 ed., Jones & Bartlett Learning.

38 Explain/make a sketch of what Scrum is

39 What is Scrum? Scrum Basics (15min): Scrum in 7 Minutes: Scrum in 2 Minutes:

40 Scrum Members: Scrum Product Owner Sprint Backlog Product Backlog Stakeholders Scrum Process: Daily Scrum Meetings Max 15 min. Scrum Master Development Team 3-9 persons Sprint Planning Sprint Review

41 The Scrum Method Testing More Flexible No Finished? Yes Deliver Software Implementation Deployment Maintenance Iterations Sprints Design Sprint Backlog Planning Product Backlog Requirements Analysis Less Documentation

42 Product Backlog Sprint Backlog Taskboard Daily Scrum Meeting

43 Daily Scrum Meeting They are short (max 15 min) - and usually stand up meetings in the hallway Daily Scrum Meeting at Microsoft: Bad Scrum Meeting Example: 43

44 Scrum

45 Product Backlog Sprint Backlog Sprint Start Task Board Tasks Not Started Tasks In Progress Tasks Finished ToDo List All Requirements Selected Requirements for one Iteration Today we can use tools like TFS, but many still use a whiteboard with sticky notes Sprint Finished Create Web Interface Create Database Create UML Create GUI Create SCC Project

46 Taskboard Example

47 Remaining Work (Hours) Sprint Start Also available in TFS Burndown Chart Actual Burndown Ideal Burndown Days Tracking the Progress Sprint Finished

48 References Software Development - A Practical Approach Halvorsen, Hans-Petter, 2015 Essentials of Software Engineering Frank Tsui; Orlando Karam; Barbara Bernal, 3 ed., Jones & Bartlett Learning Software Engineering I. Sommerville, 10 ed.: Pearson, 2015 Software Engineering. Modern Approaches E. J. Braude and M. E.Bernstein, 2 ed.: Wiley,

49

50 Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway Blog: