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:
- where particular subroutine or procedure invoked?
- what arguments, results , predicates of particular function?
- how flow of control reach particular location?
- where particular variable set, used or queried?
- where particular variable declared?
- where particular data object accessed, i.e. created, read, updated or deleted?
- 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:
- first, ask myself "what's software's purpose?": try identify how users going interact application;
- 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
Post a Comment