class_10 - Software Engineering 3156 8-Oct-01#10 Classical...

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

View Full Document Right Arrow Icon
Software Engineering 3156 8-Oct-01 #10: Classical Specs & Service Discovery Phil Gross
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
2 Administrivia Version 1.0 up Keep the webboard stuff going TAs
Background image of page 2
3 A Bit on Chapter 9 Size/cost estimation is painful Obviously necessary in the real world We’re punting Take 4156 to learn details
Background image of page 3

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

View Full Document Right Arrow Icon
4 Metrics LOC Programming language dependent Comments? Tools/throwaway? Generated code? How do you estimate LOC?
Background image of page 4
5 Other Metrics Functions points Data processing oriented Input, output, and master files Degrees of influence, Technical Complexity Factors…
Background image of page 5

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

View Full Document Right Arrow Icon
6 Actual Estimation COCOMO and COCOMO II Based on statistics gathered from real projects Awful, but the best we’ve got Aimed at huge software projects
Background image of page 6
7 Specification document Contract between client and developer Acceptance criteria Solution strategy Keep track of which solutions are kept and those discarded for later justification Cost-benefit analysis
Background image of page 7

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

View Full Document Right Arrow Icon
8 Informal specifications Xhosa!? Mostly prose Easy to screw up and make ambiguous: English sucks My MTA example from second class
Background image of page 8
9 Structured systems analysis Start with Data Flow Diagrams (DFD’s) Show what happens, not how Use stepwise refinement: start with high-level DFD and work down from there UML state diagram generalization of this
Background image of page 9

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

View Full Document Right Arrow Icon
10 DFD After several iterations, quite detailed, but customer can still understand Less data-hiding than object-oriented mechanisms Still useful for formalized contracts
Background image of page 10
11 Remaining structured systems analysis steps Decide, from DFD, what to computerize Determine details of data flows Define process logic Define data stores Define physical resources (files, organization, storage medium, etc.) Determine I/O specs Determine sizing (CPU, size) Determine hardware requirements
Background image of page 11

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

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

{[ snackBarMessage ]}

Page1 / 31

class_10 - Software Engineering 3156 8-Oct-01#10 Classical...

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

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