References

Text Book Websites

• Student support site for Dennis, Wixom, Tegarden's Systems Analysis & Design with UML, 3rd Edition, including:n
  • Practice Quizzes
  • Appendices

Unified Process

• Agile Unified Process (AUP)
• Enterprise Unified Process (EUP)
• Essentifial Unified Process (EssUP) -- a lightweight variation by Ivar Jacobson
• Tutorial on the Unified Method http://ootips.org/rup.html

Requirements Elicitations

• Multi Voting
• Brain Storm
• Brain Writing
• Card Swap
• CRC Cards
• CRC Cards (more)

Teams

• Patterns for Effective Meetings

Association for Software Quality Practice Quizzes

• http://www.westfallteam.com/CSQE_Q&A/CSQE_Quizzes.htm

A Tutorial Case Study on OO Analysis and Design (ATM Simulation)

• http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/

Tutorials on the use of CRC Cards

• http://c2.com/cgi/wiki?CrcCard
• http://argouml-stats.tigris.org/documentation/manual-0.28/apg.html

Use Case Diagrams & Descriptions

• http://alistair.cockburn.us/Structuring+use+cases+with+goals Alistair Cockburn's article on use cases.
• http://www.cs.virginia.edu/~horton/cs494/examples/parts/usecases-ex1.html Example of use case descriptions from a course as the University of Virginia
• http://193.174.33.104:7776/UMT/notation_guide_ch5.html
• http://www.smartdraw.com/resources/centers/uml/uml4.htm#whatuse
• http://pigseye.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/use_case.htm
• http://www.sparxsystems.com.au/use_case_model.htm
• http://www.atwebo.com/Use%20Case%20Tutorial.pdf

Class Diagrams

At the analysis level in information systems (but not real-time systems), the class diagram classes and entity relationship entities are the same. At design time they diverge.

• http://pigseye.kennesaw.edu/~dbraun/csis4650/A%26D/UML_tutorial/class.htm
• http://www.hristov.com/andrey/tu-sofia/uml/umlClassDiagrams.pdf
• http://www.ics.uci.edu/~abhor/ics125/class_dia.ppt

Sequence Diagrams

A sequence diagram is used for each use case. It shows how the object interact with each other.

• http://www.objectmentor.com/resources/articles/UMLSequenceDiagrams.pdf
• http://www.ao.net/~juang/CSE5469/UML/SequenceDiag.html

Entity-Relationship Diagrams (ERD)

• http://www.cs.fsu.edu/~stoeckli/COURSES/erd.ppt

Design Document Examples

• http://www.lostclouds.com/2Communicate/project/SDS.pdf
• http://www.cs.utah.edu/~jamesj/ayb2005/docs/SDS_v2.htm

These things tend to disappear from the web quickly. If the above links have gone bad, you can try finding other examples using Google search with key phrase "Software Design Specification". Use the quotes, so that the match is on the entire phrase.

COCOMO Links

• http://www1.jsc.nasa.gov/bu2/COCOMO.html
• http://sunset.usc.edu/research/COCOMOII/index.html
• http://yunus.hun.edu.tr/~sencer/size.html
• http://irb.cs.uni-magdeburg.de/sw-eng/us/java/COCOMO/co_test.shtml

Ethics Links

• IEEE-CS/ACM Software Engineering Code of Ethics and Professional Practices: http://www2.computer.org/portal/web/certification/codeofethics

UML References

• UML reference http://www.uml.org
• OMG UML 2.0 standard, in two parts:
  • http://www.omg.org/spec/UML/2.2/Superstructure/PDF/
  • http://www.omg.org/spec/UML/2.2/Infrastructure/PDF/
• Links to UML tutorials: http://www.uml.org/#Links-Tutorials
• UML. Simon Bennet, John Skelton, and Ken Lunn. Schaum's Outline Series. McGraw-Hill, 2001, ISBN 0-07-709673-8.
• Using UML: Software Engineering with Objects and Components. Perdita Stevens and Rob Pooley. Addison-Wesley, 2000
• UML in a Nutshell: A Desktop Quick Reference. Sinan Si Alhir. O'Reilly, 1998
• Learning UML. Sinan Si Alhir. O'Reilly, 2003
• The Unified Modeling Language Reference Manual. James Rumbaugh, Ivar Jacobson and Grady Booch. Addison-Wesley, 1999.

Software Engineering Links

• The SWEBOK homepage (http://www2.computer.org/portal/web/swebok) provides access to the current version of the Guide to the Software Engineering Body of Knowledge
• Recommended Approach to Software Development. Software Engineering Laboratory Series, Revision 3, June 1992, SEL-81-305. NASA (1992).
• Some background readings may be taken from the book Software Engineering (7th Edition) by Ian Sommerville.

Requirements Engineering

• Suzanne Robertson and James Robertson. Mastering the Requirements Process. Addison-Wesley, 1999
• Gerald Kotonya and Ian Sommerville. Requirements Engineering: Processes and Techniques. John Wiley, 1998. The book has an associated set of OHP Transparencies (Powerpoint 4) which may be downloaded from the accompanying website (http://www.comp.lancs.ac.uk/computing/resources/re-gpg/). The VORD method which is introduced in the book as a viewpoint-oriented technique for interactive systems specification has an associated toolset, written in Java, which is available free of charge for all readers of the book
• Ian Sommerville and Pete Sawyer. Requirements Engineering: A good practice guide. John Wiley, 1997. The book presents requirements engineering guidelines which vary from the very simple, such as make sure that your requirements are given a unique identifier, to the very complex, e.g., use formal specification for safety-critical systems. The book also includes three chapters which provide more detailed advice on system modelling, formal methods for specification and viewpoint-oriented requirements elicitation. The accompanying website ( http://www.comp.lancs.ac.uk/computing/resources/re/ provides links to resources with information on requirements engineering
• Dean Leffingwell and Don Widrig. Managing Software Requirements: A Use Case Approach. Addison-Wesley, Second Edition, 2003.

Cartoons

There is a nice series of cartoons about the Scrum development method, at http://www.implementingscrum.com/section/blog/cartoons/.

Most of Scott Adams' cartoons are based on real-life stories, and many of them come from software engineers. In fact, it seems that Dilbert is a software engineering. The strips are educational, about the pitfalls of this field. Just don't take them too seriously.

• www.dilbert.com - the official Dilbert site
• a good one on requirements elicitation
• complex requirements
• need for requirements
• user stories
• proposal writing
• quality assurance
finding bugs
• keeping up with changes in technology
• project planning
• agile programming
• agile programming over-simplified
• extreme programming, in pairs
• pair programming
• linux
• random numbers
• changing coding standards mid-project
• changing requirements
• exceeds expectations
• baseline expectations
• new paradigm
• consultant
• software consultant
• positive feedback
• mauve database
• faxing power
• the old-timer
• failure to delegate
• communication
• redundancy
• marketing
• Cobol programmer
• user interfaces
• cost estimation
• cost estimation run-around
• CMMI
• budget approval process
• workflow process
• process improvment
• process improvment
• performance review
• arbitrary deadlines
• shipping with bugs
• design phase estimatation
• robust products
• losing project
• problem of budget

There are several variants of the software engineering swing cartoon.

• A Color Verseion
• Another Swing

Hans Bjordahl's Bug Bash

• Bad Bug
• Processes
• Trade Secrets
• Configuration Management
• New Software Methodologies
• Code Monkey
• Testing

Drake Emko & Jen Brodik's Hackles

• Hacking
• Lines of Code
• Microsoft Bug

Some others

• pie chart for web design effort
• human obsolescence
• human obsolescence
• can't communicate
• dump analysis
• enterprise architecture
• software engineering without tools

The Cranky Product Manager

• Offshore Developer
• Veteran
• Great One
• Teflon-Gineer
• Hotshot
• Maverick
• Clockwork Mouse

Jorge Cham's PhD Comics include some about software development

• Cave Code
• Debugging
• Student Research

Oliver Widder's Tech Comics includes several about software engineering. Here are a few examples.

• UML diagrams
• Documentation
• Project kick-off meeting
• Yesterday it worked
• On my machine it works
• Continuous integration
• How to rescue a project
• Art of programming
• CS students
• Documentation

Tom Van Vleck's Software Engineering Stories are mostly serious, but contain some cartoons