University of Southern California
Center for Systems and Software Engineering
Individual Research
Presentation
Friday April 20
Monday April 23
Wednesday April 25
Friday April 27
© 2011 USC-CSSE
1
University of Southern California
Center for Systems and Software Engineering
Overview
•
•
•
•
9 minutes presentation
2 minutes Q & A
Powerpoint / vdo / audio / demo / prototype
Peer review as in-class quizzes
© 2011 USC-CSSE
2
University of Southern California
Center for Systems and Software Engineering
Presentation Criteria
•
•
•
•
•
•
Interesting
Soundness
Contribution to 577
Benefit to SE students
Quality of Work
Quality of Presentation
© 2011 USC-CSSE
3
University of Southern California
Center for Systems and Software Engineering
Friday April 20
Presenter
Topic
Category
Kathleen Barrera
Continuous Delivery – the good and the bad
Agile
Process
Stephen Rice
Video Game Development and Incremental
Commitment.
Game
Karim Sacre
Games and software engineering
Game
Zhanna Seitenova
Software Development Processes Employed
in Video Game Development
Game
Zhen Huang
The successful features in game developing
Game
Kirill Khistyaev
Open Source Software Development
Processes: the example of the development of OSS
Scientific Software
Adarsh Khare
Software Clones
Reuse
University of Southern California
Center for Systems and Software Engineering
Monday April 23
Presenter
Topic
Category
Cole Cecil
Code Review and Static Code Analysis
V&V
Jeff Tonkovich
A Comparative Analysis of TestLink and Excel as Test
Management Tools
Testing
Eunyoung
Hwang
Automation of Software Test
Testing
Shi-Xuan Zeng Automatic security testing tools for web-based system
Testing
Shipeng Xu
Quality assurance of agile software engineering
QA & Test
Ayman Khalil
Test Driven Development
Agile
Process
© 2011 USC-CSSE
5
University of Southern California
Center for Systems and Software Engineering
Wednesday April 25
Presenter
Topic
Category
Louis DeMaria
Applying product line approaches used in physical
products to software
Cresta Kirkwood
Incorporating aspect-oriented requirements engineering
Agile Process
into agile software development practices
David Wiggins
Survey of Knowledge Management Strategies for
transferring small projects from one team to another
Knowledge
Management
Mark Villanueva
A Case Study of Web Interface Design Patterns
Design Pattern
Muzzammil Imam
An Automated Approach to Robust Software Design
through Architectural Design and Design Patterns
Design Pattern
Ruixin Huang
Developing a Code Sharing and Modifying Tool for CSCI
Tool
577 team project
Thammanoon K
Incremental Commitment Spiral Model (ICSM) for
Embedded Systems
© 2011 USC-CSSE
Software product
line
Embedded systems
6
University of Southern California
Center for Systems and Software Engineering
Friday April 27
Presenter
Topic
Category
Hao Cai
The Use of Grounded Theory in Cooperative and Human
Human Factor
Aspects of Software Engineering
Wenfeng Liu
Team Chemistry: Managing and Mastering Software
Engineering Team Better
Human Factor
Jason Loewy
Cooperative and Human Aspects of Software
Engineering - TrackIt
Collaboration
Chan Li
How to improve our project to high level in CMMI
Process
Improvement
Ardalan Yousefi Software Process Improvement in Small Organizations
Process
Improvement
Fan Xu
Cost estimation and project planning
Cost Estimation
© 2011 USC-CSSE
7
University of Southern California
Center for Systems and Software Engineering
TRR Workshop
CS 577b Software Engineering II
Supannika Koolmanojwong
University of Southern California
Center for Systems and Software Engineering
TRR Package Overview
• Transition Set
– Transition plan
– User manual
• Support Set
– Support plan
– Training materials
• inc. Tutorials & sample data
– Regression test package
– Packaged tools & procedures
© 2011 USC-CSSE
9
University of Southern California
Center for Systems and Software Engineering
Transition Plan
• “Ensure that system’s operational stakeholders
are able to successfully operate & maintain
system”
• Plans for change from development mode to
operational mode
–
–
–
–
Site installation & test
Load data
Pilot Operations
Preparations for roll-out
© 2011 USC-CSSE
10
University of Southern California
Center for Systems and Software Engineering
User Manual
• Teach & guide user on how to use product
i.e., describe
• Steps
– For running SW
– Performing operations
• Expected
– Inputs
– Output(s)
• Measures to be taken if errors occur
© 2011 USC-CSSE
11
University of Southern California
Center for Systems and Software Engineering
Support Plan
• Guide system’s support stakeholders
(administrators, operators, maintainers, …)
on successful
– Operation
– Maintenance [and Enhancement?]
© 2011 USC-CSSE
12
University of Southern California
Center for Systems and Software Engineering
Training Materials
• Identify training
– Objectives
– Schedule
– Participants
• Prepare
– Lectures
– Examples
– Exercises
• Prepare any sample data need for training
© 2011 USC-CSSE
13
University of Southern California
Center for Systems and Software Engineering
TRR Presentation Summary
• Specific requirements for your presentation:
– Your product!
• i.e., fully working IOC version
– Salesman-like discussion of your project’s usefulness
• Base on your business case, etc
• Why is system going to be really great for customer
– Transition issues & transition plan
• if you delivered your product how did it go?
– (you should have by presentation)
• If not, when?
– Support issues
• How will you support product, once deployed?
– E.g. next term, for instance
– OK to say that
» You will never touch it ever again
» Everything’s up to customer 
© 2011 USC-CSSE
14
University of Southern California
Center for Systems and Software Engineering
TRR Agenda (80 Minutes)
10 min. Introduction
– Operational concept overview, TRR specific outline, transition
objective & strategy
15 min.
5 min.
10 min.
25 min.
Demo of IOC (Product status demonstration)
Support Plan
Data Reporting & Archiving
Summary of Transition Plan (as appropriate)
–
–
–
–
–
–
HW, SW, site, staff preparation
Operational testing, training, & evaluation
Stakeholder roles & responsibilities
Milestone plan
Required resources
Software product elements (code, documentation, etc.)
15 min. Feedback
*** Times are approximate ***
© 2011 USC-CSSE
15
University of Southern California
Center for Systems and Software Engineering
Key phase elements (Development Phase)
Goals & Objectives
Entry Conditions
Inputs
Steps (concurrent)
• Develop, V&V, and
transition the nth
increment of capability
• Deliver on schedule,
defer low-priority
features if necessary
• Prepare rebaselined
specifications, plans,
FED for incrementn+1
• Execute next phase of
manufacturing plans
• Acceptable responses
to change requests
• SCSH commitment to
life-cycle plans and
approach
• Stabilized and
prioritized
requirements,
specifications, and
plans
• Adequate staffing;
funding of
development,
rebaselining, and V&V
teams; and
manufacturing
capabilities
• Technology
Development work
products
• Increment
development and V&V
plans
• risk resolution,
infrastructure, plans,
staff, resources
• Change traffic from
previous-increment
users, management,
technology, and
competition
• Stabilized build-tospecifications
development of
increment
• Continuous V&V of
build-to-specifications
artifacts
• Next-increments
rebaselining, FEDs
based on change
traffic inputs
• Development progress
monitoring and scope
adjustment
• Increment installation,
operational test,
training, and
acceptance
• Increment test
preparations
© 2011 USC-CSSE
16
University of Southern California
Center for Systems and Software Engineering
Key phase elements (Development Phase)
Exit Conditions
• Accepted incrementn
operational capability
• Satisfactory disposition of
change traffic
• Validated, rebaselined nextincrements Capability
• Incrementn test plans and
preparations
• Committed to by SCSHs
Work products
• Accepted increment
operational capability
• Satisfactory disposition of
change traffic
• Validated, rebaselined nextincrements Capabilities
• Incrementn test plans and
preparations
• Committed to by SCSHs
• SCSH Commitment
© 2011 USC-CSSE
Pitfalls
• Inadequate phase budgets,
schedules
• Neglecting SCSHs
• Destabilizing incrementn
development
• Inadequate development
monitoring and rescoping
• Inadequate test and transition
plans and preparations
• Inadequate change-source
monitoring and response
• Unvalidated and unprioritized
next-increment capabilities
• Weak manufacturing process
and quality controls
• Inadequate next-phase
budgets, schedules
17