CECS 343 Quiz 1
Abbott's Method - ✔️✔️- Identity candidate classes from use cases, domain, and
problem descriptions, glossaries, legacy models, and legacy code
- Develop or reuse classes or modules of code that underlie individual use cases
- nouns are classes, verbs are methods, and adverbs are non-functional requirements
Parts and Purpose of a Use Case - ✔️✔️- Number and name of the case
- Actors, ex. user
- Pre-conditions, ex. no user is logged in
- Flow of control, ex. user clicks on log in button and adds info
- Post-conditions, ex. User is now logged in
- Error-conditions, ex. user enters invalid inputs
- Non-functional requirements, ex. Data should be processed within 5 seconds
Purpose of Request For Proposal - ✔️✔️- A document that a business, non-profit, or
government agency creates to outline the requirements for a specific project
- Uses the RFP process to solicit bids from qualified vendors and identify which vendor
might be the best-qualified
Purpose of a Use Case - ✔️✔️- Showcases set of possible sequences of interactions
between systems and users in a particular environment or goal
Purpose of the Glossary - ✔️✔️- A deliverable that documents terms that are unique to
the business or technical domain, ensures that everyone understands what is meant by
the terminology, acronyms, and phrases used
- Provides an easy-to-access reference for important vocabulary.
Difference between Functional and Non-Functional Requirements - ✔️✔️- Functional
requirements define what they system does or must not do, basic functionality
- Non-functional requirements specify how the system should do it, security,
performance, and general characteristics that affect the user experience
Abbott's Method - ✔️✔️- Identity candidate classes from use cases, domain, and
problem descriptions, glossaries, legacy models, and legacy code
- Develop or reuse classes or modules of code that underlie individual use cases
- nouns are classes, verbs are methods, and adverbs are non-functional requirements
Parts and Purpose of a Use Case - ✔️✔️- Number and name of the case
- Actors, ex. user
- Pre-conditions, ex. no user is logged in
- Flow of control, ex. user clicks on log in button and adds info
- Post-conditions, ex. User is now logged in
- Error-conditions, ex. user enters invalid inputs
- Non-functional requirements, ex. Data should be processed within 5 seconds
Purpose of Request For Proposal - ✔️✔️- A document that a business, non-profit, or
government agency creates to outline the requirements for a specific project
- Uses the RFP process to solicit bids from qualified vendors and identify which vendor
might be the best-qualified
Purpose of a Use Case - ✔️✔️- Showcases set of possible sequences of interactions
between systems and users in a particular environment or goal
Purpose of the Glossary - ✔️✔️- A deliverable that documents terms that are unique to
the business or technical domain, ensures that everyone understands what is meant by
the terminology, acronyms, and phrases used
- Provides an easy-to-access reference for important vocabulary.
Difference between Functional and Non-Functional Requirements - ✔️✔️- Functional
requirements define what they system does or must not do, basic functionality
- Non-functional requirements specify how the system should do it, security,
performance, and general characteristics that affect the user experience
