1. CS 577b: Software Engineering II
CS 577b Software Engineering II -- Introduction
27 May 2018
CS 577b: Software Engineering II
Class Introduction
© USC Center for Software Engineering

2. Outline Overview Schedule Marks Allocation Possible 577b risks
In-Class Team Discussion
Guest Lecturers
Individual Research Presentation
Marks Allocation
Possible 577b risks
Team Re-Formation
(C) 2013 USC-CSSE

3. CS 577b Software Engineering II -- Introduction
27 May 2018
CS 577b Course Objective
Learn how to go
From a successful RDC package
To a successfully "delivered" software system
Main elements
Coping with “devils in the details”
Doing cost-effective quality management
Understanding how stakeholders will operate & maintain system
Using IICSM-Sw Architected-Agile project guidelines
(C) 2013 USC-CSSE
© USC Center for Software Engineering

4. CS 577b Course Goals Teaching & Learning Research Product delivering
Stakeholders Satisficing
(C) 2013 USC-CSSE

5. ICSM –Class Milestones
02/11
03/23
04/01
04/15
(C) 2013 USC-CSSE

6. (C) 2013 USC-CSSE

7. Software Engineering Project Course (CS 577)
Fall: Develop Life Cycle Architecture Packages
Ops. Concept, Requirements, Prototype, Architecture, Plan
Feasibility Rationale, including business case
Results chain linking project results to desired outcomes
Spring: Develop Initial Operational Capability
Software, personnel, and facilities preparation
2-week transition period
then the student teams disappear
Tools and techniques: WinBook; Benefit Chain; Visual Paradigm; Subversion; USC COCOMO II; MS Project; USC Incremental Commitment Spiral model method
(C) 2013 USC-CSSE 7

8. Stakeholder Win-Win Approach
Stakeholders
Win Conditions
Full range of SW Engr. skills
Real-client project experience
Non-outsourceable skills
Advanced SW tech. experience
Students, Employers
Useful applications
Advanced SW tech. understanding
Moderate time requirements
Project clients
Educate future SW Engr. leaders
Better SW Engr. technology
Applied on real-client projects
Faculty, Profession
(C) 2013 USC-CSSE 8

9. Project Schedule –Spring 2013
Jan. 14 to 27 - Re-form teams
Feb Draft RDCR
Feb RDCR ARB
Apr Core Capability Drivethru
Apr Draft Transition Package on Web
Apr Transition Readiness Reviews
Apr Installation and Transition
May 6 - Operational Commitment Review for IOC
May 10 - Client Evaluations
(C) 2013 USC-CSSE 9

10. Timelines: Spring 2013
Dec. 12, Jan. 9 to Feb. 11: Work with [parts of] teams:
Rebaseline prototype, prioritize requirements
Plan for CS 577b specifics, including transition strategy, key risk items
Participate in ARB review
Feb 15 to April 30: Scheduled Weekly Meetings with Teams to:
Discuss status and plans
Provide access to key transition people for strategy and readiness discussions
Apr 1 to 5: Core Capability Drivethrough (Clients exercise systems)
Apr 15- Apr 19: Project Transition Readiness Reviews
Apr 22: Installation and Transition
Install Product
Execute Transition Plan
May 3-4: Operational Commitment Review for Initial Operational Capability
May 10: Client Evaluations
(C) 2013 USC-CSSE 10

11. Main Challenge for Clients
CS 577b Software Engineering II -- Introduction
27 May 2018
Main Challenge for Clients
Design Code Review: April 24th
Finals: May 8-15
Students disappeared by May 10, or earlier
(C) 2013 USC-CSSE
© USC Center for Software Engineering

12. Outline Overview Schedule Marks Allocation Possible 577b risks
In-Class Team Discussion
Guest Lecturers
Individual Research Presentation
Marks Allocation
Possible 577b risks
Team Re-Formation
(C) 2013 USC-CSSE

13. CS 577b Software Engineering II -- Introduction
27 May 2018
Course Schedule
See
In-Class Team discussion
Risk Analysis
Iteration planning and assessment
Retrospective analysis
Q&A
(C) 2013 USC-CSSE
© USC Center for Software Engineering

14. Potential Guest Lecturers
Boeing
Defense Acquisition University
Aerospace Corporation
WSR Consulting Group, LLC
TestMax
Cornerstones
(C) 2013 USC-CSSE

15. Outline Overview Schedule Marks Allocation Possible 577b risks
In-Class Team Discussion
Guest Lecturers
Individual Research Presentation
Marks Allocation
Possible 577b risks
Team Re-Formation
(C) 2013 USC-CSSE

16. Marks Allocation Category % Individual Score (HW/In-Class) 22%
Individual Critique
10%
Individual Research Presentation 8%
Individual Contribution 5%
Team Score
50%
Client Evaluation
100%
(C) 2013 USC-CSSE

17. CS 577b Software Engineering II -- Introduction
27 May 2018
Primary CS577b Risk Items
Personnel
Commitment
Compatibility
Ease of communication
Skills (management, web/java, Perl, CGI, data compression, …)
Schedule
Project scope
IOC content
Critical-path items (COTS, platforms, reviews, …)
COTS
See next chart
Multiple COTS
(C) 2013 USC-CSSE
© USC Center for Software Engineering

18. Primary CS577b Risk Items (cont.)
CS 577b Software Engineering II -- Introduction
27 May 2018
Primary CS577b Risk Items (cont.)
Requirements & UI
Not matching client user needs
Performance
Memory, Disk Space usage (#Bits)
Bus, Network, CPU utilization & bandwidth (#Bits/sec)
Overhead sources
Reliability of deliver
Safe
Secure
External tasks
Client/operator preparation
Commitment for transition
(C) 2013 USC-CSSE
© USC Center for Software Engineering

19. COTS & External Component Risks
CS 577b Software Engineering II -- Introduction
27 May 2018
COTS & External Component Risks
COTS risks
Immaturity
Inexperience
Incompatibility with
Application
Platform
Other COTS
Controllability
(C) 2013 USC-CSSE
© USC Center for Software Engineering

20. COTS & External Component Risks (cont.)
CS 577b Software Engineering II -- Introduction
27 May 2018
COTS & External Component Risks (cont.)
Non-commercial off-the shelf components
Sources
Reuse libraries
Government (GOTS)
Universities (ROTS)
Issues
Qualification testing
Benchmarking
Inspections
Reference checking
Compatibility analysis
Both
Safety
Dependability
Security
(C) 2013 USC-CSSE
© USC Center for Software Engineering

21. Top 11 - Risk distribution in CSCI577
(C) 2013 USC-CSSE

22. Comparing between risks in Fall and Spring
(C) 2013 USC-CSSE

23. Heads-Up: CS 577b Planning Common LCP Problems @ RDCR
CS 577b Software Engineering II -- Introduction
27 May 2018
Heads-Up: CS 577b Planning Common LCP RDCR
RDCR operational prototype, business-case iterations: What have you done since last semester?
Too many internal-increment deliverables
Lack of core-capability specifics
End-to-end demonstrable capability
Lack of specific team member responsibilities
By artifact & increment; but flexible
Transition preparation
Transition-leader’s success plan (teammates, clients)
(C) 2013 USC-CSSE
© USC Center for Software Engineering

24. CS577 Academic Integrity Guidelines
CS 577b Software Engineering II -- Introduction
27 May 2018
CS577 Academic Integrity Guidelines
Individual Assignments
OK to discuss
Not OK to copy each others’ solution elements
Not OK to copy external sources without attribution
Within “Fair Use Guidelines”
Team Assignments
OK to use other teams’ patterns
e.g. MS Project tasks
Must give credit!!!
Not OK to copy other teams’ complete/partial solutions
e.g. MS course & project schedules
(C) 2013 USC-CSSE
© USC Center for Software Engineering

25. Outline Overview Schedule Marks Allocation Possible 577b risks
In-Class Team Discussion
Guest Lecturers
Individual Research Presentation
Marks Allocation
Possible 577b risks
Team Re-Formation
(C) 2013 USC-CSSE

26. 577b project roles Project Manager Implementer Tester Trainer IIV&Ver
Quality Focal Point
(C) 2013 USC-CSSE

27. (C) 2013 USC-CSSE

28. 577b Project Activities Rebaselined Foundations Phase
(C) 2013 USC-CSSE

29. 577b Project Activities Development Phase – Construction Increment
(C) 2013 USC-CSSE

30. 577b Project Activities Development Phase – Transition Increment
(C) 2013 USC-CSSE

31. 577b Project Artifacts Exploration, Valuation, and Foundations set
OCD, SSRD, PRO, SSAD, LCP, FED
QMP, SID, WW report
Initial Operational Capability set
Test Plan & Cases, Test Procedures & Results
Iteration Plan & Iteration Assessment Report (part of LCP)
CCD Report
Transition and Support set
Transition Plan, Training Materials
Regression Test Package
User Manual
(C) 2013 USC-CSSE

32. Individual Research Presentation

33. Individual Research Presentation
CS 577b Software Engineering II -- Introduction
27 May 2018
Individual Research Presentation
8% of your final grade
Topics, but not limited to
Software Process Improvement
Process Quality Assurance
Emerging Software Engineering topics
Note: must be related to CSCI577ab
Students must select topic and get approval
Due date: March 08
Each student most cover a different aspect of a topic
10 minutes presentation
April 26-May3
(C) 2013 USC-CSSE
© USC Center for Software Engineering

34. Topics, not limited to: New Process Model Risk Management
Project Management
Quality Management and Assurance
Testing
Architecture
Cost Estimation
(C) USC-CSSE

35. Examples of research presentation from previous years
Business Case Analysis and Tool for Software Engineering Course – Kantipa Lumyai (xls)
A Case Study of Web Interface Design Patterns - Mark Villanueva
Video Game Development and Incremental Commitment - Stephen Rice
Green Software Engineering – Sheryl John
(C) USC-CSSE

36. Team Reformation Project On-Campus Off-campus Note 1 PTS-RID 4 2
Mission Science Information
1-sem 3
Web-based product configurator
Arts & Crafts website 5
FlowerSeeker
+ Hiram Garcia 6
Student Scheduling System 7
WEB-Media Modernization 2012 8
Improvement on VITA Website 9
United Direct Marketing
+ Kelvin Zhu 10
XL2
(C) 2013 USC-CSSE