analysis - Things you look for when trying to understand new software -


i wonder sort of things when start working on existing, new you, system? let's system quite big (whatever means you).

some of things identified are:

  1. where particular subroutine or procedure invoked?
  2. what arguments, results , predicates of particular function?
  3. how flow of control reach particular location?
  4. where particular variable set, used or queried?
  5. where particular variable declared?
  6. where particular data object accessed, i.e. created, read, updated or deleted?
  7. what inputs , outputs of particular module?

but if more specific or of above questions particularly important please share :)

i'm particularly interested in extracted in dynamic analysis/execution.

i use "use case" approach:

  1. first, ask myself "what's software's purpose?": try identify how users going interact application;
  2. once have "use case", try understand objects more involved , how interact other objects.

once did this, draw uml-type diagram describe i've learned further reference. happens after depends on task i've been assigned, i.e. modify code, document code etc.


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

aspxgridview - Devexpress grid - header filter does not work if column is initially hidden -

c# - How to execute a particular part of code asynchronously in a class -