ITSS 3300 Lecture Notes - Lecture 13: Data Flow Diagram, Mir Core Module, Carrying Cost
25 Jun 2018
School
Department
Course
Professor
CH 13 Building information systems
Systems development
Benchmarking business processes: points to specific systems tht needs work or
improvement
Analyze the business process
- AS IS, evaluating the issue as is today
-TO BE, how r things gonna look once we go through this process
SDLC (systems development life cycle—doesn’t really apply for packaged programs)
-phases of project plan
-ERP system, packaged software solutions- ready to use
-business process--->capability---> customize to company's needs. If you customize too much to
the old ways there's a resistance to change and no process.
1)GAP
If the requirements are met by the software or not.
Is tht gap caused by a business process, or other factor?
2)Analysis:
-process of organizing and managing the project
-to answer the problem or situation
-wht r the requirements
3)Design:
-how are we going to solve the issue with the IT knowledge or program we have
-translating business requirements into technical terms
4)Blueprint
-When u r already using an ERP system like SAP, analysis and design are grouped into blueprint.
-configuration: telling software specific elements so tht it behaves the way it needs to for our
needs
5)Development
-programming
-taking requirements and coding
6)testing
-unit testing:
Ex: program tht summarizes employee info
Ex: program B to calculate payroll
-Testing each component/unit separately.
-Test script tells u the process of testing the unit
find more resources at oneclass.com
find more resources at oneclass.com
-integrated testing
-testing all programs together
-to see if cross communication works
-Acctg
-procurement
-both in common system, communicating and sharing data across value chain
-starts with one activity and see how the software trickles and processes this info among the
other departments and how effective the outcomes are.
-acceptance testing:
-if process works they accept it
-using scenarios
-record of results
7) implement and support
-done with process and go over to new system
-cut over plan: if systems fail
-conversion: is a program tht translates all the data from old system (legacy) to new system
using specific conversions
8) production and maintenance
Data flow diagram:
How data is flowing among different entities
Objectory programming
-wht are ur objects in ur business, ex: employees, assets etc.
-object has the data and its process in itself
Ex: data elements and process
-reusability
Prototyping process
-identify basic requirements
-develop a working prototype
-use the prototype if satisfied its an operational prototype
-if not satisfied needs to revised and enhanced
Process Effectiveness
-Quality
-efficiency
-useful for accomplishing its task and strategic intent?
-ex: how well it works in terms of customers and fulfilling orders etc
Process efficiency
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Benchmarking business processes: points to specific systems tht needs work or improvement. As is, evaluating the issue as is today. To be, how r things gonna look once we go through this process. Sdlc (systems development life cycle doesn"t really apply for packaged programs) Erp system, packaged software solutions- ready to use. If you customize too much to the old ways there"s a resistance to change and no process. If the requirements are met by the software or not. How are we going to solve the issue with the it knowledge or program we have. When u r already using an erp system like sap, analysis and design are grouped into blueprint. Configuration: telling software specific elements so tht it behaves the way it needs to for our needs. Test script tells u the process of testing the unit. Both in common system, communicating and sharing data across value chain.
