Ray,
I try to explain a bit of what I posted. I am sure you know at least some of them. Anyway, it may be useful for others as well.
In the 70s/80s, methodologists proposed Structured Analysis to tackle the analysis and design requirements for procedural systems developed at that time. Structured Analysis mainly use Data Flow Diagams (DFD) to document the process flow. Systems were considered as data flowing from one process to another. That's why they use DFD for analysis and design.
At the same time people use Entity Relationship Diagrams (ER Diagrams) to model tables and their relationships (primary key, foreign keys, etc). They then use normalisation to split/combine tables into Third Normal Forms (an optimal form for relational tables). A lot of designers are still using it. (Erwin is the best known tool that supports drawing/re-engineering ER Diagrams). Even you use flat files or index sequential files, ER Diagrams are still useful to capture the semantics of the system.
As both DFD and ER Diagrams have data in it, you should be able to find the same piece of data in both kind of diagrams. If you find Shipping Charge in the ER Diagram but not in any of the DFD diagrams, then something is missing in the DFD, or one of the process in DFD that calculates the Shipping Charge is omitted. You can tell whether the architect is up to the task or not.
An architect should always consider non-functional requirements as well. If it is so hard to use and so slooooow in running, who's going to use it?
SDLC is System Development Life Cycle that includes everything from gathering user requirements, analysis, design, testing, implementation, maintenance, training.
I hope you can pick some questions to ask in the short interview.
Edward