9
Instructor Note (1) * The Psychology Of A One-Hit Wonder Teaching BIT285 6 is probably a one-shot deal for me this quarter. I'm only teaching because Dr. Brian Bansenauer, who normally teaches this class, is gone Winter Quarter on a limited sabbatical and then will be spending half-a-quarter teaching inNOT TEACHING THE COURSE RIGHT NOW. As such, as I have never taught this class before and won’t teach it until this quarter next year, the earliest. Also, have I mentioned that I’m teaching 4 courses (instead of the normal 3) AND that it’s been a while since I’ve taught BIT 116? This does not mean that I'm going to be giving you a shoddy product—only that this class is going to be more ‘student driven’ than, say BIT 142/143 (which I’ve taught over an over for years, and as a result now have excruciatingly detailed instructions for those classes. I will be counting on each of you more than usual to help me take up the stretches of slack or outright gaps. This means that we're all in the same boat together, and we are all expected to help each other out. So: we must all work together, or risk falling together. Capisce? *The Fine Print

10
The Big Idea This course is being split down the middle: 1)Project management / software engineering (SE) lite In ASP.Net WebForms 2) MVC (ASP.Net MVC, then later Angular.js) The plan is to alternate between SE and tech lessons This way you’ll have some time to complete the SE work outside of class Many of the SE lessons will have in-class work that you’ll need to finish outside of class for the points The SE lessons will be mostly/all group work – each group can hand in a single copy of the work

13
Software Engineering / Project Management 1.It’s important to have some systematic approach Even if it’s the wrong one for your project it can still serve as a starting point for discussing pros/cons & finding a better one We’re going with an amalgamation of stuff 2.It won’t write the software for you It’s a process to make sure that you dot your i’s and cross your t’s It’ll keep you organized while working through the project But you still need to know which technologies to use, when, why, and how

14
Software Requirements Specification (SRS) “A software requirements specification (SRS) is a description of a software system to be developed, laying out functional and non-functional requirements, and may include a set of use cases that describe interactions the users will have with the software.” – Wikipediasoftware systemfunctionalnon-functional requirementsuse cases Wikipedia “In software engineering (and systems engineering), a functional requirement defines a function of a system and its components. A function is described as a set of inputs, the behavior, and outputs (see also software).” -Wikipediasoftware engineeringsystems engineeringsystemsoftwareWikipedia “a non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors” -WikipediarequirementWikipedia

15
Lecture 01: In-Class Exercise From the menu bar, select Lectures and go to the Lectures 01 bar and select Lecture 01 ICE to begin working on today's in-class exercises.