| CEN4020-CEN4021: Software Engineering I-II |
up ↑ |
References
Scrum
Web2Py
Text Book Websites
- Student support
site for Dennis, Wixom, Tegarden's Systems Analysis &
Design with UML, 3rd Edition, including:n
- Instructor support site for Baase's A Gift of Fire
Unified Process
IEEE Software Engineering Body of Knowledge (SWEBOK)
Association for Software Quality Practice Quizzes
A Tutorial Case Study on OO Analysis and Design (ATM Simulation)
Tutorials on the use of CRC Cards
Use Case Diagrams & Descriptions
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.
Sequence Diagrams
A sequence diagram is used for each use case.
It shows how the object interact with each other.
Entity-Relationship Diagrams (ERD)
Design Document Examples
You can find 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
Ethics Links
UP References
UML References
- OMG UML 2.0 standard, in two parts:
- 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
- Some background readings may be taken from the book Software Engineering (7th Edition) by Ian Sommerville.
- 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 (2004 Version)
- Recommended Approach to Software Development.
Software Engineering Laboratory Series, Revision 3, June 1992, SEL-81-305. NASA (1992).
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.
