• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

usecase, HLD, LLD

 
Ranch Hand
Posts: 1491
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What are the inputs are needed for Usecases, HLD(high level design) and LLD(Low level Design)?
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"High" and "Low" are not universally agreed upon, so I'll be a bit vague. The highest level might be pure business, describing business processes without even mentioning computer systems. The lowest would might be technical API designs. In the middle somewhere my team tries to write them to describe user interaction with a particular system, but free of any user interface language like buttons, pages, list boxes, double click. We write a separate doc with those UI details.

I recommend Alistair Cockburn's Writing Effective Use Cases book to nearly everyone. He shows a wide variety of styles and levels for different audiences. Something in there is likely to look like what you need. BTW: Instead of high and low he uses cloud, kite, wave (sea-level), fish and clam.

Try: http://alistair.cockburn.us/
 
We don't have time to be charming! Quick, read this tiny ad:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
reply
    Bookmark Topic Watch Topic
  • New Topic