HW7_Developing_a_Functional_Architecture_from_Functional_Requirements__

HW7_Developing_a_Functional_Architecture_from_Functional_Requirements__

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

View Full Document Right Arrow Icon
Developing a Functional Architecture from Functional Requirements – An Example P. Jackson
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
Unorganized Functional Requirements
Background image of page 2
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
Background image of page 4
Satisfies (h) Satisfies (j), mechanism Satisfies (i), almost (feedback control)
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
Background image of page 6
Satisfies (j), almost (software algorithm)
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
Background image of page 8
Comments We are not enforcing the “jump” rule when
Background image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: connectors cross • Feedback control could be to a different function (does not have to be to same function) • Toy catapult system had no software so the closest thing to a software algorithm would be a checklist...
View Full Document

{[ snackBarMessage ]}

Page1 / 9

HW7_Developing_a_Functional_Architecture_from_Functional_Requirements__

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

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