1. CS 577b: Software Engineering II
CS 577b Software Engineering II -- Introduction
18 September 2018
CS 577b: Software Engineering II
Software Mission Assurance
© USC Center for Software Engineering

2. The Incremental Commitment Spiral Model
Mission Assurance
Exploration Phase
- Problem Definition
- Stakeholders Identification
- Product Roadmap and Project Planning
Valuation phase
- Requirements management
- Analysis of Alternative
- Business Case Analysis
- Proof-of-concepts
Foundations phase
- Architecture Design and Evaluation
Development phase
- Continuous Implementation and Testing
- Test-like/what/how-you-fly
Operations phase
- Maintenance and Enhancement
- Tech Refresh
Common activities to all phases
- Risk and Opportunity Management
- Quality Assurance
- Configuration Management
- Stakeholders' Expectation management
- Feasibility Evidence
- Human Factors
- Project and Product Management
- Continuous Improvement : Product, Process, and People
This slide shows the overall concept of the ICM
Commitment and accountability
Success-critical stakeholder satisficing,
Incremental growth of system definition and stakeholder commitment,
Concurrent engineering,
Iterative development cycles,
Risk-based activity levels and milestones
©USC-CSSE

3. Project Management
(C)USC-CSSE

4. “Poor management can increase software costs more rapidly than any other factor.” - Barry Boehm
(C)USC-CSSE

5. “Do same with less; Do more with same”
(C)USC-CSSE

6. “Plans are useless. Planning is essential” -Eisenhower
“A plan is an example of what could happen, not a prediction of what will happen.” - Kent Beck
(C)USC-CSSE

7. “Accept risks, Expect failures, Ensure recovery”
(C)USC-CSSE

8. “Take risk up front where it is manageable”
(C)USC-CSSE

9. “Most of the smartest people work for someone else”
(C)USC-CSSE

10. Rather than “what we want”, ask “what do we have?”
(C)USC-CSSE

11. “Begin with the end in mind”
“Think about the problem before you think about the solution.”
“The hardest part of the problem is defining the problem”
(C)USC-CSSE

12. “Conspiracy of optimism”
(C)USC-CSSE

13. “if you want it bad, you will get it bad”
(C)USC-CSSE

14. "Adding manpower to a late software project makes it later" - Fred Brooks
(C)USC-CSSE

15. Product Management
(C)USC-CSSE

16. “The threat environment is constantly changing, so what is "right" keeps changing”
(C)USC-CSSE

17. One IT decade is 3 years - Tom Soderstrom
(C)USC-CSSE

18. “Refresh when you should… not when you have to.”
(C)USC-CSSE

19. “Faster at the speed of need”
(C)USC-CSSE

20. “May be it is not a requirement if we cannot afford it”
(C)USC-CSSE

21. “All models are wrong; some are useful”
“ “The model said so” is never an acceptable response”
(C)USC-CSSE

22. “Cylinders of Excellence”
(C)USC-CSSE

23. “Incident Detection is important but must be accompanied with Incident Response”
(C)USC-CSSE

24. “Standards, COTS & Open Source used to be NO WAY, but now are OF COURSE”
(C)USC-CSSE

25. Faster, better, cheaper, SAFER
(C)USC-CSSE

26. “Select technologies, not necessarily the best in class but ones that will work together.”
(C)USC-CSSE

27. Build vs Buy vs Grab
(C)USC-CSSE

28. Aggregation vs Disaggregation
Cost is too high to build small
“One size fits all” vs “Tragedy of common”
(C)USC-CSSE

29. Free software isn’t free
(C)USC-CSSE

30. “The true measure of a standard is not that when it should be used, but when it is used when not required.”
(C)USC-CSSE

31. “Evidence needs to be the first class deliverable” - Barry Boehm
“The one who yells the loudest gets the budget”
(C)USC-CSSE

32. “Bake/Built in “-ilities” from day one
(C)USC-CSSE

33. “Don’t fall in love with your best solution”
(C)USC-CSSE

34. “The trouble with quick and dirty is that dirty remains long after quick has been forgotten.” - Steve McConnell
(C)USC-CSSE

35. “Define automation at the beginning rather than asking “what can we automate?” at the end”
(C)USC-CSSE

36. “Before software can be reusable, first it should be designed to be reused”
“Before software can be reusable, first it has to be usable.”
(C)USC-CSSE

37. “About 90% of the downtime comes from, at most,10 % of the defect
“About 90% of the downtime comes from, at most,10 % of the defect.” - Barry Boehm
“ The first 90 percent of the code accounts for the first 90 percent of the development time...The remaining 10 percent of the code accounts for the other 90 percent of the development time.” - Tom Cargill
(C)USC-CSSE

38. Process Management
(C)USC-CSSE

39. “I estimate that 75% of those organizations using Scrum will not succeed in getting the benefits that they hope for from it.” - Ken Schwaber
(C)USC-CSSE

40. “If you wait till the last minute, it only takes a minute.”
(C)USC-CSSE

41. Shu-Ha-Ri-Kokoro (C)USC-CSSE
(C)USC-CSSE

42. People Management
(C)USC-CSSE

43. “Not only the solutions that you are developing, it’s also the team because that will be a key part of your solution”
(C)USC-CSSE

44. “Do not need permission to do good work
“Do not need permission to do good work. It is unethical to underperform things that you have to do”
(C)USC-CSSE

45. IT trends Smart data Open Development
Rapid Development (Agile in everything)
Cloud sourcing
Internet of Things (not only toys)
Programming (start much younger)
Natural User Interface (blink it)
non-traditional partners
cyber security awareness
enterprise architecture  chaotic architecture
E4: Engage and Enable Everyone and Everything
Source: GSAW 2016
(C)USC-CSSE

46. Systems and Software Engineering Trends 2016
System Resiliency
Cyber Security
Virtualization
Enterprise Ground Systems
Open Source Software
Model-Based Engineering
Agile System Engineering
(C)USC-CSSE

47. Software Engineering Trends
Internet of Things – SW embedded systems
Software Product Line Engineering
Micro Services and Containers
Data Analytics and Visualization
(C)USC-CSSE

48. Resources GSAW workshop summary 2013 – 2016 https://gsaw.org/
(C)USC-CSSE