EP |
Topic |
PDF |
| 00 |
OO Design and Development I |
|
| 1 |
How
to design practical test cases |
|
2 |
Concepts
in Configuration Management Systems |
|
3 |
Verification
and Validation People Can Be More Than Technical Advisors |
|
4 |
How
Good is Good Enough |
|
5 |
SW
Engineering Code of Ethics |
|
6 |
Software Engineering Graduate Project Effort Analysis
Report |
|
7 |
Guide to the Software Engineering Body of Knowledge
|
|
8 |
Better Writing for Software Engineers
|
|
9 |
Test Case Development
|
|
10 |
Quality Focal Point |
|
| MT-1 |
The
Tar Pit |
|
| MT-2 |
Spiral
Development: Experience, Principles, and Refinements |
|
MT-3 |
Anchoring
the Software Process |
|
MT-4 |
Software
Risk Management: Principles and Practices |
|
MT-5 |
Mastering
rapid delivery and change with the SAIV process model |
|
MT-6 |
Understanding
the Spiral Model as a Tool for Evolutionary Acquisition |
|
MT-7 |
Theory-W
Software Project Management: Principles and Examples |
|
| MT-8 |
Avoiding the Software Model-Clash Spiderweb |
|
MT-9 |
Software
Requirements Negotiation: Some Lessons Learned |
|
MT-10 |
Requirements
Engineering, Expectations Management, and the Two Cultures |
|
| MT-11 |
Value-Based
Software Engineering |
|
MT-12 |
When
Models Collide: Lessons from Software Systems Analysis |
|
| |
Optional but recommended papers below
|
|
MT-13 |
Software
Architecture Validation with Mappings to MBASE and CS577 |
|
MT-14 |
Using
Multimedia Domain Specific Techniques |
|
MT-15 |
Bank
Of Aamerica's Masternet System: A Case Study in Risk Assessment |
|
MT-16 |
The
Art of Expectations Management |
|
MT-17 |
Using
the WinWin Spiral Model: A Case Study |
|
MT-18 |
Escaping
the Software Tar Pit: Model Clashes and How to Avoid Them |
|
MT-19 |
Making
RAD Work for Your Project |
|
