{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

l15_6up - CSci 1113 C/C for Scientists and Engineers...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
: CSci 1113 C/C++ for Scientists and Engineers Section 010 - evening class Review for Final Prof. Eric Van Wyk and Ted Kaminski Spring 2010 c Van Wyk and Kaminski CSci 1113: C/C++ for Scientists and Engineers, evening class Spring 2010 Page 1 / 19 : Agenda What else you need to know for software development. Review for final exam. Complete evaluation forms. c Van Wyk and Kaminski CSci 1113: C/C++ for Scientists and Engineers, evening class Spring 2010 Page 2 / 19 Software Development Tools : What else you need to know There are many things that we do not cover. Some of you may go on to develop software in projects or in work. You now know some C++, enough to be dangerous . You don’t yet know enough to be an effective software developer. A brief tour a tools and pointers to further reading. c Van Wyk and Kaminski CSci 1113: C/C++ for Scientists and Engineers, evening class Spring 2010 Page 3 / 19 Software Development Tools : Three Legs, No Wobble by Andy Hunt and Dave Thomas 3 pages - describes the importance of Automation tools Version Control tools Testing tools Papers are online: password and userid given in class. A similar paper Where’s the Real Bottleneck in Scientific Computing by Gregory Wilson offers a similar view, but from a more relevant perspective. It also mentions debugging . Another class of tools is dynamic analyzers - these evaluate your program at runtime for errors. c Van Wyk and Kaminski CSci 1113: C/C++ for Scientists and Engineers, evening class Spring 2010 Page 4 / 19 Software Development Tools : Automation make - automates compilation A Makefile
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}