Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 1 1 2 2 3 3 4 4 5 5 Objective Roles Definition Blueprint Structure EA Diagrams IZAZI BA Standards EA Integration to Add-On Roadmap Going Forward Q &

Similar presentations


Presentation on theme: "1 1 1 2 2 3 3 4 4 5 5 Objective Roles Definition Blueprint Structure EA Diagrams IZAZI BA Standards EA Integration to Add-On Roadmap Going Forward Q &"— Presentation transcript:

1 1 1 1 2 2 3 3 4 4 5 5 Objective Roles Definition Blueprint Structure EA Diagrams IZAZI BA Standards EA Integration to Add-On Roadmap Going Forward Q & A Workshop 6 6 7 7 8 8 9 9

2 All templates will be standardised across all business streams within IZAZI A central repository for all streams to access, thereby no longer creating duplicate or redundant data. Predefined functions and features with a common understanding, preventing any confusion between the client and IZAZI, and within IZAZI team members. A single source of information containing both business and system processes to base project blueprinting on. Initial project start up phase is defined. 1 1 2 2 3 3 4 4 5 5

3 ProductProject EA EI Add On SOL MAN *Blueprints *Addendum DESIGNDELIVERY UPLOAD FROM EA Business Analysts Functional Consultant

4 The Business Analyst gathers the requirements from the business. They will deal with the ‘what’ not the ‘how’. The Functional Consultant has an in depth understanding of how the SAP product works and what can be done to achieve the business requirement. They will also have the SAP business specific knowledge. 1 1 2 2

5 The Business Analyst will be responsible for the final document including sign-off. 1 1

6 Any queries that the functional consultant has regarding the Blueprint will need to be channelled through the business analyst in order for the functional consultant to complete WRICEF. Any queries with business will need to be resolved by the business analyst, who in return will update the functional consultant. 1 1 2 2

7 The Business Analyst will be responsible for the final document including sign-off. Any queries that the functional consultant has regarding the Blueprint will need to be channelled through the business analyst in order for the functional consultant to complete WRICEF. Any queries with business will need to be resolved by the business analyst, who in returned will update the functional consultant. The final blueprint document will be handed over from the functional consultant to the business analyst who will then obtain sign-off 1 1 2 2 3 3

8 Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner 1 1 BABA

9 Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. 1 1 2 2 BABA BABA

10 Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. Implementation considerations 1 1 2 2 3 3 BABA BABA FCFC

11 Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. Implementation considerations WRICEF 1 1 2 2 3 3 4 4 BABA BABA FCFC FCFC

12 Blueprints will be done per a level 4 business process, therefore each level 4 will be a new blueprint For example: Maintain Business Partner Record Each level 4 process will then need to be broken into the level 5 processes and requirements. These requirements will be very detailed and specific to the clients requirements. Implementation considerations WRICEF Glossary 1 1 2 2 3 3 4 4 5 5 BABA BABA BABA FCFC FCFC

13 13 Requirements Diagram Activity Diagram Class Diagram Business Rules Diagram Fact Diagram Rules Flow Diagram Rules Composer

14 1 1 Link to EA Standards Document Link to Blueprint Template Link to Generated Blueprint EA Model 2 2 3 3 4 4

15 1 1 Requirements - Inserts - Updates Processes 2 2

16 Continual update to the Blueprint and EA standards documents. 1 1

17 Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements 1 1 2 2

18 Continual update to the Blueprint and EA standards documents. Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements Internal training 1 1 2 2 3 3

19 Continual update to the Blueprint and EA standards documents. Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements Internal training Catch up of existing products into EA by product owners -Functional Catalogue (Level 4 Processes & Requirements) -Blueprint (Level 5 Process & Screen Info) 1 1 2 2 3 3 4 4

20 Continual update to the Blueprint and EA standards documents. Data mapping between EA and Add-on  EA gaps further requirements  ADD on gaps and further requirements Internal training Catch up of existing products into EA by product owners -Functional Catalogue (Level 4 Processes & Requirements) -Blueprint (Level 5 Process & Screen Info) Competent MS word expert on templates 1 1 2 2 3 3 4 4 5 5

21

22 Getting Started Level 5 Activity Diagrams Generate Document 1 1 2 2 3 3


Download ppt "1 1 1 2 2 3 3 4 4 5 5 Objective Roles Definition Blueprint Structure EA Diagrams IZAZI BA Standards EA Integration to Add-On Roadmap Going Forward Q &"

Similar presentations


Ads by Google