Software Engineering I
CSCI 577a: Fall 2003
csci577@usc.edu


Note: Quiz questions will not be asked from readings marked optional.


EP
Topic
PDF
1
Readings required for HW2 (you still need to buy the book for the course)
2
Requirements Engineering, Expectations Management, and The Two Cultures
3
Required Reading for HW 3 (Simplifier & Complicator) Using Multimedia Domain Specific Techniques
4
Master Case Study (Optional)
5
Escaping the Software Tar Pit: Model Clashes and How to Avoid Them
6
Using the WinWin Spiral Model: A Case Study
7
A Stakeholder Win-Win Approach to Software Engineering Education (Optional)
8
Software Requirements Negotiation: Some Lessons Learned
9
Anchoring the Software Process
10
Easy WinWin Process Guide (Optional)
11
Guidelines for MBASE Project Deliverables
12
Theory-W Software Project Management: Principles and Examples
13
Software Risk Management: Principles and Practices
14
Requirements Engineering, Expectations Management, and The Two Cultures
15
Making RAD Work for Your Project(Optional)
16
Introduction to UML
17
Information Paradox, Chapter II
18
MBASE Deliverables Manager user manual (Optional)
19
Avoiding the Software Model-Clash SpiderWeb
20
MBASE Guidelines (MBASE introduction part)
21
Requirements Inspection: Part A, B, C, D (Optional)

Part A RTF

Part B DOC

Part C DOC

Part D XLS

22
The Spiral Model as a Tool for Evolutionary Acquisition
23
Balancing Discipline and Flexibility with the Spiral Model and MBASE
24
Mastering Rapid Delivery and Change with the SAIV Process Model
25
Balancing Discipline and Flexibility with the Spiral Model, MBASE
26
The Future of Software Economics: Value-Based Software Engineering
27
Software Architecture Validation with Mappings to MBASE and CS577 (Optional)
28
The Art of expectations management
29
Educating Students to Manage Risk (Optional)
30
COTS Integration: Plug and Pray?
31
Composable process elements for developing COTS based systems
32
How good is good enough? (Optional)
33
Software Engineering Code of Ethics
34
Lessons Learned from four generations of Groupware for Requirements Negotiation
35
Software Verification & Validation
36
Spiral Development Model a report
37
Better writing for software engineers
38
Abstract Better & Enjoy Life
39
The Object-Oriented Software Development Method
40
Program Design by Informal English Descriptions
41
When models collide: Lessons from sofware system analysis
CONTACT US