class_3 - Software Engineering 3156 Fall 2001 Section 1...

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

View Full Document Right Arrow Icon
Software Engineering 3156 Fall 2001 Section 1 17-Sep-01 Class #3: Life Cycles, XML, and Tools Phil Gross
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 Administrivia Recitations M: 5:30-6:30 CEPSR 415 T: 2:30-3:30 CEPSR 415 Except next Monday, 24 September 6:15-7:15 IAB 410 Would Friday be better?
Background image of page 2
3 More Admin Stuff Groups Proposals in by tomorrow night Advantages of the disadvantaged Tight schedule
Background image of page 3

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

View Full DocumentRight Arrow Icon
4 Review Standard Model Teams
Background image of page 4
5 Standard Model Requirements Specification Design Implementation Integration Maintentance Retirement
Background image of page 5

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

View Full DocumentRight Arrow Icon
6 Requirements What are we doing and why? Interviews Getting a problem specification out of busy, threatened, very-much-not-programmer types Difficult to simulate in a course, so we’re skipping Prototypes and negotiation Metric: requirements volatility
Background image of page 6
7 Specification Creating the contract What it will do, not how Detailed, so duration and cost can be estimated Classical: DFD, FSM, Petri Nets OO: Use cases, class modeling, state diagrams
Background image of page 7

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

View Full DocumentRight Arrow Icon
8 Design Fill in the “How” Interaction diagrams Sequence Collaboration Interactions determine actions Determine object clients Create detailed design
Background image of page 8
9 Implementation Pick a language: C, C++, Java, Ada, COBOL, LISP, FORTRAN, Standard ML, Forth, PL/SQL, Assembly, etc. Programming standards: comments, meaningful variable names, named constants, etc. Black-box and Glass-box testing
Background image of page 9

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

View Full DocumentRight Arrow Icon
10 Integration Top-down finds design faults early Bottom-up finds operational faults early and isolates them So, “Sandwich Integration” does both at once Product and acceptance testing
Background image of page 10
11 Maintentance Corrective (fix problems) Perfective (improvements) Adaptive (environment changes) Difficult, important, programmers hate it Carefully designed processes are critical
Background image of page 11

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

View Full DocumentRight Arrow Icon
12 Maintenance Costs Money Lots and lots of money Far and away most expensive component When doing cost-benefit analysis, anything that cheapens maintenance generally wins
Background image of page 12
13 Retirement Diminishing returns from patching old code At some point better to rip up and start fresh
Background image of page 13

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

View Full DocumentRight Arrow Icon
14 Note What’s Not A Step Testing Documentation Supposed to be continuous Particularly Documentation
Background image of page 14
15 Capability Maturity Model Not a life-cycle model Set of strategies for improving the software process SW–CMM for software P–CMM for human resources (“people”) SE–CMM for systems engineering IPD–CMM for integrated product development SA–for software acquisition These strategies are being unified into CMMI (capability maturity model integration)
Background image of page 15

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

View Full DocumentRight Arrow Icon
16 SW–CMM A strategy for improving the software process Put forward in 1986 by the SEI Fundamental idea: Improving the software process leads to Improved software quality Delivery on time, within budget Improved management leads to Improved techniques Five levels of “maturity” are defined Organization advances stepwise from level to level
Background image of page 16
Image of page 17
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 75

class_3 - Software Engineering 3156 Fall 2001 Section 1...

This preview shows document pages 1 - 17. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online