How To Choose A Software Requirements Model
Do you find that you're always trying to use process flows on your projects, but they just don't seem to fit your needs?
Do you need to start modeling requirements, but can't quite decide what models to use?
There are quite a few requirements models out there to choose from, ranging from the mundane (process flow), to the amorphous (use case) to the exotic (fishbone diagram). Knowing which models may be most helpful to you can be a bit tricky, but the following tips can help!
Choosing the Right Software Requirements Model
If your application has:
Check out these detailed explanations.
Do you need to start modeling requirements, but can't quite decide what models to use?
There are quite a few requirements models out there to choose from, ranging from the mundane (process flow), to the amorphous (use case) to the exotic (fishbone diagram). Knowing which models may be most helpful to you can be a bit tricky, but the following tips can help!
Choosing the Right Software Requirements Model
If your application has:
- Lots of User Interaction - useful models can be Org Charts, Use Cases, System Context Diagrams
- A Complex UI - useful models can be Org Charts, Use Cases, Wireframes
- Lots of Involvement with Different Systems - useful models can be System Context Diagrams, Data Flow Diagrams
- Data Processing - useful models can be Entity Relationship Diagrams, Data Flow Diagrams, System Context Diagrams
Check out these detailed explanations.
Labels: data dictionaries, decision trees, process flow, requirements modeling, requirements models, software requirements, state tables, use case, visualization
posted by Jennifer at 7/02/2008 08:20:00 AM
1 Comments:
I like as simple and obvious as possible. I often start by drawing a simple Pert style chart of a users process, which shows decisions, flows, parallel paths, and key events. From this simple diagram I can identify processes, different agents/actors, classes/entities, and potential problems. Use-case and data models can then be easily developed, as can the narrative to describe the requirements for the parts of the process to be aided or automated by a system.
Post a Comment
<< Home