Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Categorisation of non-software project requirements
Previous Previous
Next Next
New Post 11/2/2013 11:03 AM
User is offline munkee
3 posts
No Ranking

Categorisation of non-software project requirements 

Hi All,

I am currently working on my first none-software related project where we are looking to move one of our offices to another location. I have picked up the project mid way through after a contractor had collected some "high level" requirements from business areas. It is now down to me to categorise and filter the requirements prior to sign off. The problem I have is that I feel that these high level requirements don't seems as though they should fit in to the usual general/functional/non-functional buckets due to not actually delivering anything software related.

I have a number of requirements related to communication to employees and vendors about the changes and update of documentation with addresses etc. I also have requirements related to legal matters, moving hardware, removing access for certain staff from old software, migration of paperwork and moving of physical furniture. Should I be going down the typical route of general/functional/non-functional and their related sub categories? It is hard to picture how these should be set out, its almost as if I want to jump straight in to sub categorisation such as security & access, legal, constraints, security and create some further categories for communication etc.

Any advice on how I should tackle this and any experiences of working on non-IT delivery projects?

New Post 11/9/2013 7:36 PM
User is offline Chris Adams
323 posts
5th Level Poster

Re: Categorisation of non-software project requirements 

I think you answered your own question.  Why would you force requirements into categories that don't make sense?

What categorize at all?  What's the purpose?  To organize a large number of items for easier consumption, correct?  So use the categories you mentioned such as Security, Legal,  Communication, etc.

Chris Adams
Core Member –
LinkedIn Profile
New Post 11/13/2013 7:56 AM
User is offline dldelancey
61 posts
8th Level Poster

Re: Categorisation of non-software project requirements 

You might also think of other ways of categorization rather than just type of requirement.  Maybe separate them by responsibility (i.e. things to be done in-house, things to be done by 3rd parties)?  Or by timeframe of delivery (i.e. things to do week 1, week 2, week 3, etc.)?

Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Categorisation of non-software project requirements

Community Blog - Latest Posts

If you're looking to visualize, analyze, and share data insights with ease, Power BI might be the solution you need. In this article, we'll cover what Power BI is, why it's important, and how to get started with it. What is Power BI? Power BI is a business analytics service provided by Microsoft that helps users visualize and anal...
How to Write Business Analyst Resume
Business analysts must have an up-to-date, visually appealing resume to be able to stand out from the competition. A strong business analyst resume should accurately reflect your skills, experience and qualifications while also highlighting your accomplishments and successes. We will provide invaluable advice on how to build a strong, effective bus...
Are you testing your product in the most effective way?
Today covid-19 pandemic has completely flipped the business model. Various conventional Business models like banking and health had to adopt the digital era. Even the school and colleges have to create various applications so that they can provide online learning for their students. All these statements justify the modern business model as complete...



Copyright 2006-2023 by Modern Analyst Media LLC