Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  How to conduct requirements for single sign on solution
Previous Previous
 
Next Next
New Post 2/26/2016 2:50 AM
User is offline Jayman21
28 posts
9th Level Poster


How to conduct requirements for single sign on solution 

Hello, I am currently working on a Single Sign On project. The project looks to use a single portal as access to several (15) services offered by a financial service body. The users to access this service via the single portal comprise of both internal and external users. This means there is need to define the users groups and also the security access level for the users and the services.

Question:

1.       How do you go about conducting requirements for this project? What areas to look into? E.g Portal component, Registration component, sign On component , Authentication and Authorisation component and Admin portal Component

2.       Can anyone advise on a generic infrastructure design / model which can be used / deployed in a complex organisation? And which will show how the solution works / will work and how data is requested and exchanges. 

3.       Any sample requirement document for SSO as a guide to what to look for, what component to research and gather information.

4.       How to handle Authentication and Authorisation

5.       How to go about defining the security access levels for the services and also for the user groups

6.       What technical challenges should I be looking out for

7.       Any advice / recommendations 

Thanks and look forward to your contributions.

 
New Post 3/8/2016 3:02 AM
User is offline Jayman21
28 posts
9th Level Poster


Re: How to conduct requirements for single sign on solution 

Hello All,

 

Still no response. Am thinking I may be asking the wrong questions. Any advice or pointing in the wright direction will do.

thanks

 
New Post 3/10/2016 9:01 AM
User is offline Chris Adams
307 posts
5th Level Poster






Re: How to conduct requirements for single sign on solution 

I think you have asked a pretty tough question for anyone who hasn't been involved in a Single Sign On project.  I would caution about mixing your business and technical requirements.

Start with the business requirements.  Think about the following.

  • Registration
  • Role assignment
  • Registration/Role Approval
  • System Access based on Role
  • Single Sign On/Login

Then you have the Architecture/Technical Requirements to consider.  Most of these will need to be determined by an Architect or whomever is managing the development side.  They will start to jump the chasm between requirements and solution design. These will include things like:

  • Authentication
  • Authorization
  • Security and Encryption

There are probably some best practices available but finding them could be difficult. Many companies have implemented a Single Sign On solution, so I wouldn't reinvent the wheel.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
New Post 4/9/2016 11:23 AM
User is offline L-Analyst
1 posts
No Ranking


Re: How to conduct requirements for single sign on solution 
Modified By Chris Adams  on 4/12/2016 11:18:10 AM)

If you require a comprehensive requirements specification template, outlining the business as well as functional requirements for a system, you can find it here: https://www.fiverr.com/liezlfive/write-a-system-requirement-specification-template. Also offering to create a comprehensive document based on your project/system. 

 
New Post 5/17/2016 9:14 PM
User is offline Jayman21
28 posts
9th Level Poster


Re: How to conduct requirements for single sign on solution 
 Chris Adams wrote

I think you have asked a pretty tough question for anyone who hasn't been involved in a Single Sign On project.  I would caution about mixing your business and technical requirements.

Start with the business requirements.  Think about the following.

  • Registration
  • Role assignment
  • Registration/Role Approval
  • System Access based on Role
  • Single Sign On/Login

Then you have the Architecture/Technical Requirements to consider.  Most of these will need to be determined by an Architect or whomever is managing the development side.  They will start to jump the chasm between requirements and solution design. These will include things like:

  • Authentication
  • Authorization
  • Security and Encryption

There are probably some best practices available but finding them could be difficult. Many companies have implemented a Single Sign On solution, so I wouldn't reinvent the wheel.


 

Thanks Chris Adams for your comment. I have been working on the project and as a team we came up with the key areas to capture requirements via user stories:

. Registration

. Log In & Authentication

. Identity

. Self-Service & Web Portal

. Assisted Digital & Trusted Helpers

For each one of the above we tried to capture the As Is situation and he To Be situation (user stories forming the requirements for the new solution). As you rightly said the technical architect will then be responsible for defining the solution options. We do not intend to build from scratch but use existing off the shelf solutions via a vendor. 

The approach is to capture common needs across the impacted business areas (at the minimum) level then work through each impacted business area one after the other literately and incrementally.

Any thoughts regarding the approach?

Kind regards


 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to conduct requirements for single sign on solution

Community Blog - Latest Posts

Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
0 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
1 Responses
SarikaA
SarikaA
Pega systems(Software Company) is the leading provider of business process management (BPM) and customer relationship management (CRM) software solutions. Pega systems motto is “Build For Change” and their goal is to “eliminate software coding” and “automate manual work”. Pega systems has bee...
0 Responses




Latest Articles

The Crucial Art of Pre-Project Problem Analysis
Aug 13, 2017
0 Comments
Business analysis is a broad discipline and we have a whole range of tools and techniques at our disposal. We may get involved within projects, but al...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC