Akoka
graphical model. descriptive model. logical model. physical model. |
graphical mathematical descriptive environmental |
users. clients. stakeholders. developers. |
internal users. information users. business users. external users. |
logical prototypes. physical prototypes. discovery prototypes. feasibility prototypes. |
diagrams and schematic representations of aspects of a system. specifications that define the functions to be provided by a system. sequences of steps to process business transactions. models created to verify concepts and then discarded. |
characteristics related to workload measures such as throughput and response time. characteristics related to an organization's environment, hardware, or software. characteristics of the system other than activities it must perform. activities or processes that the system must perform. |
Descriptive Graphical Functional Nonfunctional |
nonfunctional requirements. functional requirements. performance requirements. reliability requirements. |
Technical Performance Usability Reliability |
|
Reliability Technical Performance Usability |
open-ended questions. closed-ended questions. functional questions. open-source questions. |
have a simple, definitive answer. require discussion and explanation. deal with exception conditions. ask about the existing system. |
Delay documenting the interview results for several days to allow time for reflection. Delete unanswered questions from your notes since they are probably unimportant. Avoid any further contact with interview participants. Distribute results to interview participants for confirmation. |
a swimlane. a walkthrough. a prototype. a workflow. |
swimlane. synchronization bar. crow's foot. transition arrow. |
JAD RAD MAD CAD |
an effective early step in identifying possible courses of action. a poor analysis practice that should be avoided. a step to take only after developing your own original solution. a last resort to use only when you fail to think of an original solution. |
for viewing only and not executable. fully working and executable. used to test the effectiveness and efficiency of different programming techniques. able to execute an activity but may lack some functionality. |
a performance review for the analyst. a formal review of findings and models based on those findings. an informal review with colleagues on the project team. an optional activity that can be skipped if necessary to stay on schedule. |