ERP-RequirementsMgmt-v2

ERP-RequirementsMgmt-v2 - ERP Requirements Management...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
1 July 10, 2007 1 ERP Methodology and Project Management ERP Requirements Management Ronald E. Giachetti, Ph.D. Associate Professor Industrial and Systems Engineering Florida International University July 10, 2007 Slide 2 Agenda s ERP Project Scope s ERP Requirements Environment s Requirements Gathering Methods s ERP Requirements s Requirements Management s Summary
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 July 10, 2007 Slide 3 ERP Project Scope s Scope is the logical set of self contained business processes that can be enabled by a standard software solution. s ERP systems can define scope by: Module – each module contains business processes (e.g. in SAP the Business Process Master List (BPML)). By cross-functional business process, which may be obtained by cross module mappings to the implementation reference architecture. July 10, 2007 Slide 4 ERP Requirements Environment s Multiple stakeholders concurrently engineer the requirements and the architecture design to create a solution based on pre-existing ERP components. s Requirements Engineering (RE) team extensively reuses predefined requirement artifacts (such as reference models). s Business process modeling drives the RE cycle and is the key to acquiring, communicating, and validating enterprise knowledge and business requirements. s The organization adopts an architecture-centric approach to manage systems and business changes and to establish and maintain a common information infrastructure across business units. s RE teams emphasize consistency in analytical measures , such as systematic selection of common process and data requirements; constructive measures , such as consistent RE methods and tools; and organizational measures such as institionalized quality assurance procedures.
Background image of page 2
3 July 10, 2007 Slide 5 Managing RE Teams s To manage implementation complexity divide ERP project into subprojects based on the modules. s Each subproject has a dedicated RE team. Responsible for running the RE cycle and delivering the business process requirements document for the module. Team includes: ERP consultants with in-depth knowledge of process and ERP modules. Process owners such as department mgrs and domain experts with knowledge of operational procedures the solution will support. Process Architect to support teams. Knows ERP architecture; consults on requirements reuse, process methods, and RE tools. – Process Architect is shared among all teams. s Identify interfaces between modules, negotiate interface requirements. July 10, 2007 Slide 6 RE in an Iterative Life Cycle Model s Three main activities: Requirements elicitation: finding, communicating, and validating facts and rules about the business. Enterprise modeling: analyzing and representing
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/07/2011 for the course ERP 2000 taught by Professor Giachetti during the Spring '11 term at FIU.

Page1 / 18

ERP-RequirementsMgmt-v2 - ERP Requirements Management...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online