Transcript No Slide Title

University of Southern California
Center for Systems and Software Engineering
CS 577b: Software
Engineering II
Class Introduction
University of Southern California
Center for Systems and Software Engineering
Outline
• Overview
• Schedule
– In-Class Team Discussion
– Guest Lecturers
– Individual Research Presentation
• Marks Allocation
• Possible 577b risks
• Team Re-Formation
(C) 2012 USC-CSSE
2
University of Southern California
Center for Systems and Software Engineering
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) 2012 USC-CSSE
3
University of Southern California
Center for Systems and Software Engineering
CS 577b Course Goals
•
•
•
•
Teaching & Learning
Research
Product delivering
Stakeholders Satisficing
(C) 2012 USC-CSSE
4
University of Southern California
Center for Systems and Software Engineering
ICSM –Class Milestones
02/08
(C) 2012 USC-CSSE
03/23
04/09
04/27
5
University of Southern California
Center for Systems and Software Engineering
(C) 2012 USC-CSSE
6
University of Southern California
Center for Systems and Software Engineering
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: WikiWinWin; Benefit Chain; Rational
Software Modeler; Subversion; USC COCOMO II; MS Project;
USC Incremental Commitment Spiral model method
(C) 2012 USC-CSSE
7
University of Southern California
Center for Systems and Software Engineering
Stakeholder Win-Win Approach
Stakeholders
Win Conditions
•Full range of SW Engr. skills
•Students,
Employers
•Real-client project experience
•Non-outsourceable skills
•Advanced SW tech. experience
•Useful applications
•Project
clients
•Advanced SW tech. understanding
•Moderate time requirements
•Faculty,
Profession
•Educate future SW Engr. leaders
•Better SW Engr. technology
•Applied on real-client projects
(C) 2012 USC-CSSE
8
University
University of
of Southern
SouthernCalifornia
California
Centerfor
Center
forSystems
Systems
and
and
Software
Software
Engineering
Engineering
Project Schedule –Spring 2012
Jan. 10 to 27
Feb. 6
Feb. 8-10
Mar. 28-30
Apr. 9
Apr. 11-13
Apr. 18-20
May 4
May 7
- Re-form teams
- Draft RDCR
- RDCR ARB
- Core Capability Drivethru
- Draft Transition Package on Web
- Transition Readiness Reviews
- Installation and Transition
- Operational Commitment Review for IOC
- Client Evaluations
9
University of Southern California
Center for Systems and Software Engineering
Timelines: Spring 2012
Dec. 12, 2011..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
Mar 28 to 30: Core Capability Drivethrough (Clients exercise systems)
Apr 11- Apr 13: Project Transition Readiness Reviews
Apr 21: Installation and Transition
–Install Product
–Execute Transition Plan
May 3-4: Operational Commitment Review for Initial Operational Capability
May 7: Client Evaluations
10
University of Southern California
Center for Systems and Software Engineering
Main Challenge for Clients
• Products are delivered on or before April 19th
– Design Code Review: April 18th
• Finals: May 7-14
• Students disappeared by May 14, or earlier
(C) 2012 USC-CSSE
11
University of Southern California
Center for Systems and Software Engineering
Course Etiquette
• Observe normal rules of classroom etiquette
– Be on time!
• If you are late, don’t slam the door
– ONE conversation at a time
– ONE topic at a time
– Direct all comments to the instructor
– Encourage (rather than criticize) other students
– E-mail & browsing at breaks or after class only
– Turn off/silent cell phones
(C) 2012 USC-CSSE
12
University of Southern California
Center for Systems and Software Engineering
Outline
• Overview
• Schedule
– In-Class Team Discussion
– Guest Lecturers
– Individual Research Presentation
• Marks Allocation
• Possible 577b risks
• Team Re-Formation
(C) 2012 USC-CSSE
13
University of Southern California
Center for Systems and Software Engineering
Course Schedule
• See
– http://greenbay.usc.edu/csci577/spring2012/schedule.php
• In-Class Team discussion
–
–
–
–
January 27, March 11
Iteration planning and assessment
Retrospective analysis
Q&A
(C) 2012 USC-CSSE
14
University of Southern California
Center for Systems and Software Engineering
Potential Guest Lecturers
•
•
•
•
•
Boeing
Aerospace Corporation
Disney
TestMax
Cornerstones
(C) 2012 USC-CSSE
15
University of Southern California
Center for Systems and Software Engineering
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 07
• Each student most cover a different aspect of
a topic
• 10 minutes presentation
• April 20-25
(C) 2012 USC-CSSE
16
University of Southern California
Center for Systems and Software Engineering
Outline
• Overview
• Schedule
– In-Class Team Discussion
– Guest Lecturers
– Individual Research Presentation
• Marks Allocation
• Possible 577b risks
• Team Re-Formation
(C) 2012 USC-CSSE
17
University of Southern California
Center for Systems and Software Engineering
Marks Allocation
Category
%
Individual Score (HW/In-Class)
22%
Individual Critique
10%
Individual Research Presentation
8%
Individual Contribution
5%
Team Score
50%
Client Evaluation
5%
100%
(C) 2012 USC-CSSE
18
University of Southern California
Center for Systems and Software Engineering
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) 2012 USC-CSSE
19
University of Southern California
Center for Systems and Software Engineering
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) 2012 USC-CSSE
20
University of Southern California
Center for Systems and Software Engineering
COTS & External Component
Risks
• COTS risks
– Immaturity
– Inexperience
– Incompatibility with
• Application
• Platform
• Other COTS
– Controllability
(C) 2012 USC-CSSE
21
University of Southern California
Center for Systems and Software Engineering
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) 2012 USC-CSSE
22
University of Southern California
Center for Systems and Software Engineering
Top 11 - Risk distribution in CSCI577
12
10
8
6
4
2
0
08/26/11
©USC-CSSE
23
University of Southern California
Center for Systems and Software Engineering
Comparing between risks in Fall and Spring
6
5
4
3
2
Fall
1
Spring
0
08/26/11
©USC-CSSE
24
University of Southern California
Center for Systems and Software Engineering
Heads-Up: CS 577b Planning
Common LCP Problems @ 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) 2012 USC-CSSE
25
University of Southern California
Center for Systems and Software Engineering
Outline
• Overview
• Schedule
– In-Class Team Discussion
– Guest Lecturers
– Individual Research Presentation
• Marks Allocation
• Possible 577b risks
• Team Re-Formation
(C) 2012 USC-CSSE
26
University of Southern California
Center for Systems and Software Engineering
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) 2012 USC-CSSE
27
University of Southern California
Center for Systems and Software Engineering
Outline
• Overview
• Schedule
– In-Class Team Discussion
– Guest Lecturers
– Individual Research Presentation
• Marks Allocation
• Possible 577b risks
• Team Re-Formation
(C) 2012 USC-CSSE
28
University of Southern California
Center for Systems and Software Engineering
577b project roles
•
•
•
•
•
•
Project Manager
Implementer
Tester
Trainer
IIV&Ver
Quality Focal Point
(C) 2012 USC-CSSE
29
University of Southern California
Center for Systems and Software Engineering
(C) 2012 USC-CSSE
30
University of Southern California
Center for Systems and Software Engineering
577b Project Activities
Rebaselined Foundations Phase
(C) 2012 USC-CSSE
31
University of Southern California
Center for Systems and Software Engineering
577b Project Activities
Development Phase – Construction Increment
(C) 2012 USC-CSSE
32
University of Southern California
Center for Systems and Software Engineering
577b Project Activities
Development Phase – Transition Increment
(C) 2012 USC-CSSE
33
University of Southern California
Center for Systems and Software Engineering
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
– CCD Report
• Transition and Support set
– Transition Plan, Training Materials
– Regression Test Package
– User Manual
(C) 2012 USC-CSSE
34
University of Southern California
Center for Systems and Software Engineering
#
Team Reformation
Project
OnCampus
OffCampus
1
1
5
1
Plan
1 Improving Thai CDC
2 Using Social Media
3 ISTARTONMONDAY
4 LEMA - Integrated Family Accountability System
5 LACGC Employment Opportunities Online App
6 Mission Science Information and Data Mgnt Sys
1
7 Leamos
1
Continue
8 LADOT SCANNING
1
9 Amer i Can Re-Up
10 LACGC Employment Opportunities Online App
11 Central Avenue Business District Operating System
3
12 LEMA Pilot School Integrated Scheduling Sys
1
1
13 Los Angeles Community Garden Inventory and Locator
3
1
Continue
14 Transportation Grant Fund Database
4
1
Continue
(C) 2012 USC-CSSE
Continue
35
University of Southern California
Center for Systems and Software Engineering
#
Project
Team Reformation
OnCampus
OffCampus
1
1
5
1
Plan
1 Improving Thai CDC
2 Using Social Media
3 ISTARTONMONDAY
To team 12
4 LEMA - Integrated Family Accountability System
5 LACGC Employment Opportunities Online App
6 Mission Science Information and Data Mgnt Sys
1
To team 12
7 Leamos
1
To team 11
1
To team 11
8 LADOT SCANNING
9 Amer i Can Re-Up
10 LACGC Employment Opportunities Online App
3
+ Jeff T.
+ David W.
12 LEMA Pilot School Integrated Scheduling Sys
1
1
+ Thammanoon K.
+ Mark V.
+ Kathleen B
13 Los Angeles Community Garden Inventory and Locator
3
1
14 Transportation Grant Fund Database
4
1
11 Central Avenue Business District Operating System
(C) 2012 USC-CSSE
36
University of Southern California
Center for Systems and Software Engineering
Feedback on lectures - Favorite lectures
Count
Favorite Topics
16
10
8
8
5
5
4
4
4
3
3
3
2
2
Software Architecture (Booch)
B-Chain & B-Realization
ICSM
VBSE
Architecture in general
Risk Management
OOA&D
Requirements Prioritization
WinWin negotiation
Agile Concepts
Ethics
Life Cycle Management
Cost Estimation
Prototype
(C) 2012 USC-CSSE
37
University of Southern California
Center for Systems and Software Engineering
Feedback on lectures – Beneficial lectures
Count
Favorite Topics
11
Software Architecture (Booch)
9
B-Realization & WW negotiation
6
ICSM
5
Architecture
5
VBSE
4
COCOMO
4
Risk Management
3
Architecture Workshop &Modeling
3
Client Interaction
3
Prototype & UI
3
Software Process Models
(C) 2012 USC-CSSE
38
University of Southern California
Center for Systems and Software Engineering
Feedback on lectures – should be added
Count
Favorite Topics
5
Design Pattern
4
Software processes used in the industry
4
Team Dynamics
3
Client Communication & Negotiation
3
COCOMO Formula & Calculation
3
Guest Lecturer for various industries
3
Testing
2
Cloud Computing
2
Configuration Management
2
Domain specific topics (e.g. Healthcare)
2
how to select NDI/NCS
2
More interactive classes
2
Real Agile Experience
2
Technical Writing
(C) 2012 USC-CSSE
39
University of Southern California
Center for Systems and Software Engineering
Feedback on lectures – should be removed
Count
Favorite Topics
15
NONE
5
Agile concepts
5
Client interaction
5
COCOMO II
5
OOA&D
3
Duplicate of ICSM
3
Software Ethics
3
Testing
3
VBSE
2
History of SE
2
Project Management
2
Schedule estimation and improvement
2
Software process models - join with others
(C) 2012 USC-CSSE
40