Please answer all questions. Thanks 1. Explain the objectives of BPR. 2. How is
ID: 3823269 • Letter: P
Question
Please answer all questions. Thanks 1. Explain the objectives of BPR. 2. How is BPR consistent with the object and client/server models. 3. What is a business area? 4. Explain the relationship between BPR and structured tools. 5. What is a CRUD diagram? 6. How should BPR be introduced to users and IT personnel? 7. What is the SDLC? Why is it called a waterfall approach? 8. Compare the SDLC with the OOLC. 9. What is the significance of the spiral approach and how does it support the development of reusable objects? 10. Describe the procedures to implement a pilot application. Why is this so important in BPR? 11. Describe the philosophy of reengineering an enterprise system. 12. What is the difference between a transaction database and a data warehouse? 12. Briefly summarize the importance of the IT team in the go-live and support phases.
Explanation / Answer
OBJECTIVES OF BPR:Business process reengineering (BPR) is the practice of rethinking and redesigning the way work is done to better support an organization's mission and reduce costs.Reengineering starts with a high-level assessment of the organization's mission, strategic goals, and customer needs.Re-engineering recognizes that an organization's business processes are usually fragmented into sub-processes and tasks that are carried out by several specialized functional areas within the organization. Often, no one is responsible for the overall performance of the entire process. Reengineering maintains that optimizing the performance of sub-processes can result in some benefits, but cannot yield dramatic improvements if the process itself is fundamentally inefficient and outmoded. For that reason, re-engineering focuses on re-designing the process as a whole in order to achieve the greatest possible benefits to the organization and their customers. This drive for realizing dramatic improvements by fundamentally re-thinking how the organization's work should be done distinguishes the re-engineering from process improvement efforts that focus on functional or incremental improvement.
5.
CRUD:In computer programming, create, read, update, and delete refer to crud.A CRUD matrix is a table showing the Functions in an application containing SQL statement affecting parts of a database.The CRUD Matrix is an excellent technique to identify the Tables in a Database which are used in any User interaction with a Web Site.example of an website taking survey:
It is very valuable to combine a CRUD Matrix with the analysis of possible User Scenarios for the Web Site.
The analysis helps to identify any Tables which are not used, and any Tables which are used heavily, and may therefore be a performance bottleneck.
The application of this technique to a Portal Web Site is shown below.
It identifies the different kinds of Users who can access the Web Site.
For each kind of User, the User Scenario is defined as a series of User Actions, and the corresponding Tables are identified. This Table shows the User Scenarios for a Casual User.
Here is a typical CRUD Matrix for a Portal Web Site :-
sno . USER ACTION CREATE READ . UPDATE DELETE
1
Enter the Web Site
---
---
---
---
2
Complete User Survey
UserSurvey
SurveyMaster
---
---
3
Search the Site
---
Site Directory
---
---
4
Go Shopping
Orders, ProductOrders, ProductOrderOptions
Products, ProductOptions, Merchants
ID Table
---
5
Post to the Message Board
Comm_messages
Comm_messages
ID Table
---
6
Check the News Items
---
News
---
---
7
Leave the Web Site
---
---
---
---
11. TRANSACTION DATABASE VS DATA WAREHOUSE
Source of data
Operational data; OLTPs are the original source of the data.
Consolidation data; OLAP data comes from the various OLTP Databases
Purpose of data
To control and run fundamental business tasks
To help with planning, problem solving, and decision support
What the data
Reveals a snapshot of ongoing business processes
Multi-dimensional views of various kinds of business activities
Inserts and Updates
Short and fast inserts and updates initiated by end users
Periodic long-running batch jobs refresh the data
Queries
Relatively standardized and simple queries Returning relatively few records
Often complex queries involving aggregations
Processing Speed
Typically very fast
Depends on the amount of data involved; batch data refreshes and complex queries may take many hours; query speed can be improved by creating indexes
Space Requirements
Can be relatively small if historical data is archived
Larger due to the existence of aggregation structures and history data; requires more indexes than OLTP
Database Design
Highly normalized with many tables
Typically de-normalized with fewer tables; use of star and/or snowflake schemas
Backup and Recovery
Backup religiously; operational data is critical to run the business, data loss is likely to entail significant monetary loss and legal liability
Instead of regular backups, some environments may consider simply reloading the OLTP data as a recovery method
1
Enter the Web Site
---
---
---
---
2
Complete User Survey
UserSurvey
SurveyMaster
---
---
3
Search the Site
---
Site Directory
---
---
4
Go Shopping
Orders, ProductOrders, ProductOrderOptions
Products, ProductOptions, Merchants
ID Table
---
5
Post to the Message Board
Comm_messages
Comm_messages
ID Table
---
6
Check the News Items
---
News
---
---
7
Leave the Web Site
---
---
---
---