More Notes:
1. Review of Day 1 assignments:
a. chapter 1, #5 [limit 1 page, good disaster]
b. intro vb program with at least 1 control
I graded them 10/10, and gave small comments.
-------------------------------------
2. Great 'SOFTWARE' resource of mine:
http://www.sei.cmu.edu/
My book: Personal Software Process by Humphrey
3. I will continue with Chapters 11-14 [we did 11 last
week, kind of skipping 12, going to 14 to start!].
Theme: Traditional Software Development outline,
that is what these 4 chapters will be.
--------------------------------------------------------------
My favorite chapter is 14!
Data Flow Diagrams can be partitioned as to:
1. transactions
2. transforms
One DFD method is PSPEC...
----------------------------------
Lisa's rule:
3 Layers of transactions are plenty
---------------------
print cards:
a. ask me
b. another rule: "not my printer cartridge", so
s115/E152 don't charge for printing
-------------------------
Homework rules:
1. you can turn in on disk/cd, digital dropbox, email, hard copy.....
It really doesn't matter to me.
2. How do I grade? Not severely, the main things I look for:
a. I like to see your own thinking
b. if you cite sources, that is good also
c. the grades are posted in Blackboard
[the two things not posted are the inclass VB!]
-------------------------
One more rule to mention:
80/20 rule
Pareto rule: 80% of $$ are owned by 20% of the people
Project management rule:
80% of your project problems are caused by 20% of your project items
Homework rule:
you will get 80% of your grade with 20% effort
In this class, limit your time on items that may be taking too long
[remember this rule!!].
Don't spend a HUGE amount of time on one of these questions, limit yourself
and go on to the next thing.
----------------------------
VB task assistance/clarification for Day 3 assignment:
1. Write a small program that interfaces with Access.
If Access won't behave, make a clever substitution:
either another reference or component:
Word, clipboard, etc.
find cool ideas from VB--project--REFERENCE/Components
[this is your first step anyways!].
Chapter 10 procedure:
1. skim the reading in one hour.
1b. for interesting time, go to Book website quiz and
'glance' at the multiple choice questions. Answer
Three - but don't print out, I will believe you.
www.mhhe.com/pressman
2. pay most close attention to page 258's list of
requirements to ask.
Don't memorize all Eight!!
3. scan the problems to see if any look interesting, choose
one if possible.
4. if not practical, do the following:
Using your own project [at this point, all you have is a cool idea],
make a list of questions to 'elicit' requirements from your user.
Limit one page, use the templates in the chapter or problem 10.8
for ideas].
--------------------------------------------------------------
IMPORTANT ANNOUNCEMENTS:
Since I didn't cover chapter 20 AT ALL!! Skip that homework,
we'll worry about it next week!
------------------------
Chapter 10 Self-Check Quiz
----------------------------------------------------------------------------
----
1. Software engineers do not need to consider hardware
when designing a
computer-based system.
a. True
b. False
----------------------------------------------------------------------------
----
2. Which of the following can be elements of computer-based systems?
a. Documentation and data
b. hardware and software
c. people
d. all of the above
----------------------------------------------------------------------------
----
3. The system engineering process usually begins with the
a. detailed view
b. domain view
c. element view
d. world view