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 12:17 PM
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 2:54 PM
User is offline Kimbo
450 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

m_anst
m_anst
What Does Success Look Like? I challenge Business Analysts to view requestors’ requirements as an opportunity to define success. Too often, teams fall into a trap focused on requestors’ prescriptive requirements that are meant to serve as roadmaps for developers and testers. When you limit your view of requirements to this prescripti...
0 Responses
Mariya Kotsupalova
Mariya Kotsupalova
They say the best criteria of Business Analyst’s success are a happy customer (business) and a happy engineering team. But what does it mean? How can we break down happiness and measure it? These are precisely the questions my 8 BAs team and I tried to answer this year. The result was a surprisingly efficient pair of surveys we developed and ...
0 Responses
Rajesh-N
Rajesh-N
Explore the Benefits of RPA's Adoption Across Segments In the past few years, we have seen steady growth in Robotic Process Automation (RPA). It gathered momentum in 2019 and became a hot topic in IT and business circuits in 2020. The power of process automation will be felt even more strongly, propelling its adoption as a replacement f...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC