EIN 6133 Enterprise Engineering

Slides:



Advertisements
Similar presentations
DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Advertisements

Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
T-FLEX DOCs PLM, Document and Workflow Management.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Rational Unified Process
1 Samples The following slides are provided as samples and references for the Quarterly Reviews Additional slides will be added.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Tina design review Main design decisions. Top level modules. Responsibilities. Phases A & B. Test plan. Time table.
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
High-Level Assessment Month Year
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
AIIM Presentation Selecting and Implementing A Records Management System June 5, 2008.
Release & Deployment ITIL Version 3
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Effective Methods for Software and Systems Integration
Semester 1, 2003 Week 7 CSE9020 / 1 Software Testing and Quality Assurance With thanks to Shonali Krishnaswamy and Sylvia Tucker.
Configuration Management T3 Webinar Feb 21, 2008 Chuck Larsen ITS Program Coordinator Oregon Department of Transportation.
Rational Unified Process Fundamentals Module 4: Disciplines II.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
ERP Implementation Fundamentals Richard Byrom Oracle Consultant, Speaker and Author
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
COGNOS 8BI Introduction and Architecture
I Copyright © 2007, Oracle. All rights reserved. Module i: Siebel 8.0 Essentials Training Siebel 8.0 Essentials.
Cole David Ronnie Julio. Introduction Globus is A community of users and developers who collaborate on the use and development of open source software,
Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Integration integration of all the information flowing through a company – financial and accounting, human resource information, supply chain information,
EIN 6133 Enterprise Systems Engineering Chin-Sheng Chen Florida International University.
Avanade Confidential – Do Not Copy, Forward or Circulate © Copyright 2014 Avanade Inc. All Rights Reserved. For Internal Use Only SharePoint Insights (BETA)
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Microsoft dynamics Axapta training institute Contact US: Magnific training
PLM, Document and Workflow Management
The Development Process of Web Applications
Support 2001.
Document & Web Content Management
System Design.
Software Engineering Architectural Design Chapter 6 Dr.Doaa Sami
IEEE Std 1074: Standard for Software Lifecycle
Maximo Upgrade Information Session
Ch > 28.4.
Engineering Processes
PSC Group, LLc Office 365/SharePoint Online Migration traps and tricks
Ebusiness Infrastructure Platform
Introduction to Software Testing
Chapter 1 (pages 4-9); Overview of SDLC
Software Development Process
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Component--based development
COGNOS 8 BI - Introduction and Architecture Cognos CoE
Analysis models and design models
OO Design and Development
Delivery of Solutions Information Management
.NET vs. J2EE Architecture
Technical Capabilities
EIDE System Requirements and Specification Documents
System Reengineering Restructuring or rewriting part or all of a system without changing its functionality Applicable when some (but not all) subsystems.
CAD DESK PRIMAVERA PRESENTATION.
Chin-Sheng Chen Florida International University
T-FLEX DOCs PLM, Document and Workflow Management.
UML Design for an Automated Registration System
Problem Statement To transform the traditional system to automated system(ERP). No centralized control. Low data privacy. Huge amount of human resources.
Presentation transcript:

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 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

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

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)

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

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

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

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

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

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

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 Validation and switch-over design Parallel vs. ? Systems interface (integration) Intermediate tables Direct access to database