|
|
| Our Process |
|
| Development Process |
|
| Writing Use Cases |
|
| |
Once the SRS is approved, the next stage is Use Case modeling. Use Case modeling is a form of Requirements engineering. It is a different way of eliciting and documenting requirements. It partitions the system functionality into transactions meaningful to actors, who are idealized users of the system. Use Case describes an interaction with the actors as a sequence of messages between the system, and one or more actors. The term actor includes humans, time, other computer systems, or processes.
The Use Case model is a prime source for objects and classes. It is the primary input for class modeling. The system architect does the Use Case modeling. Once the Use Case model is completely built, Use Cases are mapped with the actual requirements in the SRS. A Use Case/Requirement matrix is created. This ensures that a Use Case is modeled for every requirement. |
|
| Designing UI Complying with Use Cases |
|
|
Based on the written Use Cases, the systems analyst designs the UI layout of the software. The UI is designed in such a way that all the use cases are satisfied through that UI. This may be the final deliverable interface (Windows Forms\Web Pages), or the dummy UI with placeholders. Creation of the user interface at this stage makes the requirements clearer to the client. |
|
| |
|
|
| |
 |
|
| |
|
|
|
|
|
|
|
