Project Journal: Functional and Non-Functional Requirements

According to Susan and James Robertson in Mastering the Requirements Process, Requirements can be Functional and Non-Functional. “Functional requirements specify what the product must do. And they are the reason for its existence.” They define “non-functional requirements as the properties that your product must have.” These make the product pretty, usable, quick, and reliable. In some of my experiences I have had to collect requirements, though I was not the BA. In my role, I had to think of the needs of more than the user, so to make things simple I also collected the requirements of the project sponsor, IT director, Product Owner, CEO, and the user. The list below shows a few for my BenchPrep project. Day 22 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement #WordPress #BusinessAnalysis #Requirements

The list below the contains the categories that I used for that project. The list below was divided even further but this gives an overview.

• Project
• Technical Due Diligence
• Standards and Browser Support
• Mobile Applications
• Integration
• Branding
• Course Creation
• Administration
• Sessions
• Content Authoring
• Course Authoring
• Assessments
• Social
• Sequencing and Navigation
• Achievements
• Student View
• Teacher App
• Reporting
• Reporting – Client
• Category
• Enrollment
• Access
• Record Learning

This is a sample of how the data was documented. I don’t have the final document. And know that I am not a business analyst, just someone that had to document requirements. 🙂