Computer Systems Analyst Mock Interview
Master 25 Computer Systems Analyst interview questions covering system design, requirements analysis, and technical problem-solving.
Question 13 of 25
What types of requirements do you gather when you start working on a new project?
How to Answer
Example Answer
Community Answers
William Swansen has worked in the employment assistance realm since 2007. He is an author, job search strategist, and career advisor who helps individuals worldwide and in various professions to find their ideal careers.
This operational question seeks to understand your planning process when starting a new project or implementing a new design. Computer systems analysts should have definite processes they use to plan, initiate, and execute projects. Typically, these are documented and placed in manuals, which can be referred to when new projects arise or to train new personnel. Being able to describe the requirements you use will demonstrate your qualifications for this role.
William Swansen has worked in the employment assistance realm since 2007. He is an author, job search strategist, and career advisor who helps individuals worldwide and in various professions to find their ideal careers.
"When initiating a new project, there are three types of requirements I seek to understand. These include user, technical, and functional requirements. The technical requirements include details such as the required hardware, network equipment, and software applications. The functional requirements address how these systems interface with each other. Finally, the user requirements help me understand how people will interact with the systems and what tasks they are trying to accomplish."
Interview Coach
Jaymie
A real coach, not AI. I read every answer myself and write back with personalized feedback.
Typically responds within 24 hours.
0 - Character Count
Anonymous Answer
After conducting the preliminary investigation, presenting, and getting approved the business case I move to the requirements gathering phase. Whether we are engaging in a structured approach or an agile methodology I like to use the acronym FURPS DIIP when gathering requirements or user stories. It stands for Functionality, Usability, Reliability, Performance, Supportability, Design, Interface, Implementation, and Physical. Functionality addresses the functional requirements, the URPS addresses non-functional requirements while DIIP addresses constraints. This allows me to cover the solution from most angles, is key to note that the solution doesn't need to address each one. Example: A small webserver hosted on AWS has no physical constraints.
Amanda's Feedback
Great job! This answer exudes confidence and illustrates that this is something you're comfortable doing. You've clearly outlined the steps you take and the kind of requirements you gather, illustrating your analytical skills and ability to organize effectively.
Unlock All 25 Computer Systems Analyst Questions
Unlock expert responses to technical and analytical questions interviewers prioritize.
Get StartedJump to Question