1 / 12

EIN 6133 Enterprise Engineering

EIN 6133 Enterprise Engineering. Chin-Sheng Chen Florida International University. T9: Enterprise systems design. Process: System analysis and specification System modeling and analysis System design System implementation design System deployment design. Need analysis.

tuari
Download Presentation

EIN 6133 Enterprise Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EIN 6133Enterprise Engineering Chin-Sheng Chen Florida International University

  2. T9: Enterprise systems design • Process: • System analysis and specification • System modeling and analysis • System design • System implementation design • System deployment design

  3. Need analysis • Define scope (application industry & business scope) to support • Outline the overall enterprise (system) lifecycle to support • Define business performance measures and control requirements to support • Define major business/engineering/project functions (& structure) to support • Define operation/production strategy to support • Define the nature of organization (& structure) to support • Define the nature of work (& structure) to support • Define the generic strategic decision process to support • Define the generic operational decision/execution process to support

  4. System specification • Translate the above needs into system specifications (functionality requirements) • Develop benchmarks (metrics and values) for the system

  5. System modeling and analysis • Model (& decompose) business functions for intended application scope • Model (& decompose) business objects for intended application scope • Resources capability and capacity • Model (& decompose) business processes (i.e., object dynamics) for intended application scope • Status, state, trigger event & control, actor, & activity (method)

  6. System design (1) • Determine system configuration capability to support • Add/modify enterprise strategies • Add/modify system parameters • Add/modify functional modules • Add/modify business processes • Add/modify workflows & its parameters

  7. System design (2) • Determine strategies for ramp-up, operation modes and upgrades to support • Support for legacy data migration • Support for one operation mode to another • Single user • Managerial system • Collaborative system • Support for version upgrade

  8. System design (3) • Determine the system environments to support • Hardware support & infrastructure (& Web-based vs. client-server) • Software support & infrastructure • Single site vs. multiple sites • Computation/database distribution and/or federation • Support for communication (means) and interface (to 3rd party systems) • Determine the application functionality to support

  9. System design (4) • Specify default application functionality for each operation mode • Design the overall system architecture • Design for the system configuration and management module • Design the detailed functionality for the business process/workflow design module. • Work (de-) composition & planning • Scheduling • Schedule control & sequencing • Cost control • Quality control • Reporting (& communications) • Viewing

  10. System design (5) • Design for the functionality for process components definition • Generic, basic business activity • Generic resource capability • Generic work structure and element • Design for the system’s user interface • Forms & flows design • Messages design • Online “i” & search design • Design for the system’s database (tables) • Design for default settings (of modules/processes/parameters) for each operation mode

  11. System implementation (selection) • Determine implementation environment & tools (for coding, validation, and management) • Establish a collaborative R&D environment for changes management and version control • Set up guidelines for code structure, user interface design, and documentation • Establish standard libraries and inventory of system vocabulary, terminology, abbreviations, components (of different levels) for consistency and efficiency. • Establish a test policy and a library of test cases for automatic testing

  12. Deployment design • Deployment strategy design • Breadth first vs. depth first • System modeling & analysis process design • Fixed procedure and forms for each mode • Installation process design • Automatic vs. manual • Upgrades • Training process design • Design of user cases • Training programming (top down vs. bottom-up) • Online training • Data migration/entry process design • Automatic vs. manual • Validation and switch-over design • Parallel vs. ? • Systems interface (integration) • Intermediate tables • Direct access to database

More Related