Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Here are some samples for bottom->top approach: extract the model from everything that is said and modelize it properly, find common behaviour to implements for multiple cases : forms validation & error messages, specific components like grids/tree, search engine. For top->bottom approach, you_ would start by group use cases together to form a coherent set of functionnalities that will work together, from that create an API representing each set of functionnalities. Each of those coherent should be the master of their own datas (tables, validation). Commented Oct 12, 2017 at 12:48
  • What does 'Insert' mean? Description of the type of information (e.g. geral supplier information) only serves to clutter the 'flow' descriptions. Add a 'Notes' section where you'd record random stuff like that and leave the 'flow' clean. Each sentence should say who does what to whom. Thus, 2 should be more like 'The administrator submits the product information to the system'. Now you can create a sequence diagram from that sentence. Also, notice how I gave an explicit name to the information instead of 'filled information'. What happens after the information is submitted? Commented Oct 12, 2017 at 17:24