Lead Allocation System - Attribute Driven Design (ADD)

Lead Allocation System Attribute Driven Design By, A3, Inc.

Introduction ADD Steps ADD Inputs ADD Outputs (Architecture Design)

Introduction (Cont.) ,[object Object],[object Object]

Business Opportunity ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Success Criteria ,[object Object],[object Object],[object Object],[object Object],[object Object]

Stakeholder’s Goals ,[object Object],[object Object]

Business Risks ,[object Object],[object Object],[object Object]

Major Features ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Major Features ,[object Object],[object Object],[object Object]

Constraints ,[object Object],[object Object],[object Object],[object Object]

Quality Scenarios ,[object Object],[object Object],[object Object],[object Object]

First Iteration ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object],[object Object]

[object Object],Low High 1.2 Constraint 4 Primitive API calls only 10 Low Medium 1.2 Constraint 3 OOD used 9 Low Medium 1.2 Constraint 2 Run in .NET CLR 8 Low Medium 1.2 Constraint 1 Compiled DLLs 7 High High 1.1 Requirement 2 Allocate Lead 6 Medium High 1.1 Requirement 1 Acquire Lead 5 Medium High 1.3 Scenario 4 Secure access 4 Medium High 1.3 Scenario 3 Trusted access only 3 Medium Medium 1.3 Scenario 2 System availability 2 High Medium 1.3 Scenario 1 Allocate Lead Performance 1 Difficulty Importance Section Discussed In Architectural Drivers #

[object Object],[object Object],Modifiability, Localize Modification 10 Modifiability, Prevent Ripple Effect 9 Modifiability, (N/A) 8 Modifiability, Localize Modification 7 Modifiability, Prevent Ripple Effect 6 Modifiability, Prevent Ripple Effect 5 Security, Resisting Attacks 4 Security, Resisting Attacks 3 Availability, Fault Recovery 2 Performance, Resource Arbitration 1 Design Concern AD#

[object Object],Use an Intermediary Pros – Easy to understand. Cons – Tedious to implement. Hide information Pros – Traditional. People are most familiar with it Cons – Depends strongly on skills and talents of the person implementing it. Modifiability, Prevent Ripple Effect 5 Maintain Data Confidentiality Pros – Software such as SSL exist and is easy to implement Cons – Need to purchase SSL certificate. Authenticate Users Pros – Easy to use in conjunction with Authorize users Cons – Need additional software or man power to manage user registration Security – Resisting Attacks 4 Authorize users Pros – Dynamic. Easy to modify Cons – Need additional software such as Active Directory Limit Access Pros – High Security Cons – Need to know IP address of incoming request Security - Resisting Attacks 3 Active Redundancy Pros – Data will be up to date. Also, recovery time will be milliseconds. Cons – Need additional monitoring and switching software Spare Pros – Easy to configure Cons – Data will not be up to date and recovery time will be minutes. Availability – Fault Recovery 2 Fixed-Priority Pros - Flexibility for priority Cons – Difficult to implement FIFO Pros - Easy to implement Cons – No flexibility for priority Performance - Resource Arbitration 1 Pattern (pros/cons) Pattern (pros/cons) Design Concern AD #

[object Object],Anticipate Expected Changes Pros – Fits in nicely with Maintain Semantic Coherence pattern. Cons – Difficult to determine what to anticipate for. Generalize the Module Pros – Makes communication with modules much simpler. Cons – Makes the inner workings of the module somewhat more complex, hence requiring more qualified people. Modifiability – Localize Modifications 10 Use an Intermediary Pros – Easy to understand. Cons – Tedious to implement. Hide information Pros – Traditional. People are most familiar with it Cons – Depends strongly on skills and talents of the person implementing it. Modifiability, Prevent Ripple Effect 9 N/A N/A N/A 8 Limit Possible Options Pros – Requires zero development time Cons – Requires senior management buy in Maintain Semantic Coherence Pros – Creates reusability as well as preventing ripple effects Cons – Time consuming. Requires talented professionals. Modifiability – Localize Modifications 7 Use an Intermediary Pros – Easy to understand. Cons – Tedious to implement. Hide information Pros – Traditional. People are most familiar with it Cons – Depends strongly on skills and talents of the person implementing it. Modifiability, Prevent Ripple Effect 6

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object]

[object Object],Active Redundancy 2 Redundant LAS servers 1, 2, 3 6 Authenticate Users, Maintain Data Confidentiality, Authorize Users 3, 4 Security Service 5 FIFO 1 Allocate Lead FIFO computation 4 Hide information 6 Allocate Lead Service 3 Hide information 5 Acquire Lead Service 2 Generalize the Module, Hide information, Maintain Semantic Coherence, Anticipate Expected Change 7, 8, 9, 10 LAS API Adapter 1 Pattern (s) Architectural Driver Element Name Element #

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],N/A N/A Redundant LAS servers 1, 2, 3 TO ALLOCATE LEAD SERVICE: Trusted user security information TO ACQUIRE LEAD SERVICE: Trusted user security information FROM ACQUIRE LEAD SERVICE: Trusted user information FROM ALLOCATE LEAD SERVICE: Trusted user information Security Service TO ALLOCATE LEAD SERVICE: Lead request from queue. Lead bid from queue. FROM ALLOCATE LEAD SERVICE: Lead request information. Lead bid information. Allocate Lead FIFO Computation TO ALLOCATE LEAD FIFO COMPUTATION: Lead request information. Lead bid information. TO SECURITY SERVICE: Trusted user information FROM LAS API ADAPTER: Lead request information. Lead bid information. Trusted user information Allocate Lead Service TO SECURITY SERVICE: Trusted user information FROM LAS API ADAPTER: Lead information. Trusted user information Acquire Lead Service TO LEAD PROVIDER: A lead recorded successful message and transaction reference number. TO LEAD ACQUIRER: A lead heading. An interface to allow the lead provider to place a bid, and the full lead if the lead acquirer decided to buy the lead. The interface should also provide a transaction reference number. TO ACQUIRE LEAD SERVICE: The lead information TO ALLOCATE LEAD SERVICE: The request for a lead information Primitive type input from lead providers or lead acquirers. This would be lead information from the lead providers and lead request information from lead acquirers. It would also require trusted user information such as a username and password. LAS API Adapter Provides Requires Element

Second Iteration ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],Low High 2.6 Constraint 1 Active Directory 4 Medium High 2.6 Scenario 3 Trusted access only 3 Medium High 2.4.2 Scenario 2 Authenticate Users 2 High High 2.4.2 Scenario 1 Authorize User 1 Difficulty Importance Section Discussed In Architectural Drivers #

[object Object],[object Object],Modifiability, Localize changes, Prevent Ripple Effect 4 Security, Resisting Attacks, Maintain integrity 3 Security, Resisting Attacks, Authenticate User 2 Security, Resisting Attacks, Authorize User 1 Design Concern AD#

[object Object],N/A Prevent Ripple Effect Pros – Enterprise standard, and easy to configure Cons – Need to add every partner. Modifiability, Localize changes, Prevent Ripple Effect 4 N/A Maintain Integrity Pros – Software such as SSL exist and is easy to implement Cons – Need to purchase SSL certificate. Security, Resisting Attacks, Maintain integrity 3 N/A Authenticate Users Pros – Reduce time, because for authenticate Enterprise uses active directory Cons – Needs extra resource for the configuration. Security – Resisting Attacks, Authenticate User 2 N/A Access Matrix / Authorization [1] Pros – Flexible Cons – Need additional resources to maintain the user profile and their roles Security - Resisting Attacks, Authorize User 1 Pattern (pros/cons) Pattern (pros/cons) Design Concern AD #

[object Object],[object Object],[object Object]

[object Object],[object Object],Active Directory User Role Database LAS Services LAS Gateway

[object Object],Maintain Integrity 3 Gateway of LAS 3 Access Matrix / Authorization 2 User role database 2 Authenticate, Prevent Ripple Effect 1, 4 Active Directory 1 Pattern (s) Architectural Driver Element Name Element #

[object Object],It provides the 128 bit encryption for the entire LAS system. Set up and configuration for LAS system. Gateway It provides authorization for LAS services. A setup as well as tables needs to be created for each and every LAS service user. And also identify the role. User role database It provides authentication and a system will be secure after implementing this element. A setup and configuration need to require for entire LAS services. Active Directory Provides Requires Element

Lead Allocation System - Attribute Driven Design (ADD)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Lead Allocation System - Attribute Driven Design (ADD)

Similar to Lead Allocation System - Attribute Driven Design (ADD) (20)

More from Amin Bandeali

More from Amin Bandeali (9)

Recently uploaded

Recently uploaded (20)

Lead Allocation System - Attribute Driven Design (ADD)