Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Technical specs for developers
Previous Previous
 
Next Next
New Post 5/30/2020 11:17 AM
Unresolved
User is offline Bounce1991
1 posts
No Ranking


Technical specs for developers  

There is a platform with an admin interface where clients can create accounts.

Legend:

  1. X-Admin has all the permissions. Only a limited number of X-team' members can have Admin role.
  2. X-E is a type of role with almost the same permissions as an X-Admin except that it cant delete users
  3. X-R is a type of role that belongs to the X team. It's permissions are related to support for clients
  4. Partner-Admin is a partner or a client that created an account on the platform
  5. Partner-Editor is a user inside an organization created by a Partner or client
  6. Partner is the default resource in which partners and clients are placed in.
  7. Users are accounts created in the platform. It is not mandatory that users are linked to an organization
  8. All resources are stored in relational databases

This is the interaction diagram:

interaction

This is the permission matrix:

matrix

The request is that based on this information, assuming all users/organizations are already created, platform is build, create the appropriate documentation for the programmers/development team, using tasks and technical specifications, NOT user stories, in ANY granularity, in order for them to use this output for development and create this form of organization/roles/permissions.

Can someone help me with this?

 
New Post 6/4/2020 1:54 PM
User is offline Kimbo
456 posts
5th Level Poster


Re: Technical specs for developers  

Hi Bounce,

without looking at this too hard. Looks like there is a lot of inheritance of permissions and functionality happening.

Suggest you look at a UML Class diagram as one possible way to model it.

kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Technical specs for developers

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC