Applied Systems Analysis Fall 2003. Class Notes 2. Douglas Low (315) 456-3372 (work) 2 min question (315) 703-6297 (home) 5 min question (315) 445-6044 (Lemoyne mailbox) leave message. Session 2. Handout Project Assignment Discuss Reading Assignment Discuss Homework
Class Notes 2
(315) 456-3372 (work) 2 min question
(315) 703-6297 (home) 5 min question
(315) 445-6044 (Lemoyne mailbox) leave message
My wife shall have at least two childeren.
My wife shall be faithful.
My wife shall be under five foot eight.
My wife shall be educated with a college degree.
My wife shall vacum once a week.
My wife shall dust the house once a week.
My wife shall have a job if she wants.
My wife shall be a brunet.
My wife shall have a career before we marry.
Subjective Requirements from the customer must be converted into achievable and agreed to Requirements
All Requirements are defined in the requirements database as one and only one of the following types:
Ø Functional “… shall automatically track airborne targets…”
Ø Performance “…shall discriminate targets within 3 minutes…”
Ø Capacity “…shall maintain 300 tracks in the …”
Ø Constraint including cost, specific equipment, legacy components etc.
Ø Reliability “ MTBF shall be 100 days”
Ø Interface “ … shall use RS-232 interface to … “
Ø Test “… the system test shall stress the system …”
Ø Safety “ “in accordance with SPCL-610 and BI-431
Ø Data “…shall depict target range in meters…”
We should do this but we don’t.
It helps Partition Requirements or
place the requirement in the proper document section.
We will model a software system using UML and document the software model it in an SRS.
(Verb - Noun)
These are fluffy
I don’t use them unless they mean something to the design like an interface
Gold Creator System
All Requirements that are verified by “TEST”
have an associated Use Case
Use Case 1 Documentation Set