3156-9 - COMS W3156: Software Engineering, Fall 2001...

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

View Full Document Right Arrow Icon
COMS W3156: Software Engineering, Fall 2001 Lecture #9: Classical specification, service discovery Janak J Parekh janak@cs.columbia.edu
Background image of page 1

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

View Full DocumentRight Arrow Icon
Administrativia v0.9 of the requirements out – we’ll talk about it shortly New specification document – better? Rose will be installed by Friday Homework 1 submission instructions up Webboard – use it! http://groups.yahoo.com – private webboards On asymmetric groups…
Background image of page 2
Next class Planning and Estimation Read Schach 9, second part of MMM HW2 will probably include a little of MMM MS Project Amazingly useful little program
Background image of page 3

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

View Full DocumentRight Arrow Icon
Today’s class Talk a little about classical specifications Informal techniques Semiformal techniques Formal techniques Talk about service discovery, especially LDAP Continue project discussion
Background image of page 4
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 5

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

View Full DocumentRight Arrow Icon
Informal specifications Xhosa!? Mostly prose Easy to screw up and make ambiguous: English sucks My MTA example from second class
Background image of page 6
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 7

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

View Full DocumentRight Arrow Icon
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 8
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 9

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

View Full DocumentRight Arrow Icon
Other semiformal techniques PSL (problem statement language) and PSA (problem statement analyzer) – computer-aided SADT (box-and-arrow-based structural analysis
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 34

3156-9 - COMS W3156: Software Engineering, Fall 2001...

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

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