| 3.1 Change
16. Business Requirement Manager | |
|---|
| 3.1.16. Business Requirement Manager: | | 1. Introduction | | 1.1. Title, Description | | 1.2. Glossary, Definitions, Acronyms, Abbreviations | | 1.3. Change Control, Traceability | | 2. Executive Summary | | 2.1. Ownership | | 2.2. Context | | 2.3. Purpose | | 2.4. Data Controller | | 2.5. Data Processor | | 3. Project Requirement | | 3.1. Cost Requirement | | 3.2. Time Requirement | | 3.3. Quality Requirement | | 4. Data Requirement | | 4.1. Data Model | | 4.2. Data Dictionary | | 4.3. Life Cycle | | 5. Functional Requirement | | 5.1. User Functions | | 5.2. Archive Retrieval | | 5.3. Training Requirement | | 6. Risk Analysis | | 6.1. Security Requirement | | 6.2. Privacy Requirement | | 7. Performance Requirement | | 7.1. Infrastructure | | 7.2. Capacity | | 7.3. Availability | | 7.4. Latency | | 7.5. Archive Recovery |
| Business Requirements: | | Continual improvements happens with formal change control procedures with quality manual track and trace. If a defect is discovered, its entire life cycle is plain to track and procedures put in place to ensure that such a defect can never happen again. |
| Improvements: | | Improvements can be made to business rules with very little impact of other business rules. Business requirements are owned by the company that authors their own bespoke requirements - business rules are bespoke. Business requirements must specify WHAT the company wants and not focus on technical matters of design or how something works. |
| Scope: | | An improvement to deliver a report may appear simple, but precision and diligence is needed to create long lasting business rules. Many people may use the same business rules many times for many years, so the investment in getting things complete and correct will always be cost effective. |
| No Software: | | ASP does not distribute software, does not sell software, does not install software and recommends that every person has a policy to stop software - its obsolete. Other people write software, software with vulnerabilities, bugs and malware built in - all application software is obsolete and avoidable. Software is no longer safe and secure. Software needs daily update patches to rewrite bad code. Software is licensed with maintenance releases and auditable price increases without limit. Software needs downtime to be patched, needs complex versioning procedures so all computers are updated on the same day. | | ASP has moved beyond software into knowledge engineering of business rules. |
| Business Rules: | | Knowledge engineering with business rules enables dynamic improvements to be made without downtime. Business rules cannot be hacked, cannot have vulnerabilities and cannot be attacked by malware. But business rules must be specified with very high levels of accuracy - sloppy rules lead to sloppy application services. |
|
|