 |
 |
 |
 |
User login
BUSINESS REQUIREMENT ARCHITECTURE (BRA) 
COURSE DURATION 2 DAYS
SCHEME: SBL KHAS
DESCRIPTION
According to Standish Group”Chaos Summary 2009”, only 32% of the IT project is successful (on time, on budget and fully functional). Forrester Research found that poorly defined applications (miscommunication between business and IT) contribute to 66% of the project failure rate, costing U.S. businesses at least $30 billion every year.
For any businesses, it is always about matching the needs and wants and its no difference with any IT initiatives for it to succeed, which is about getting the right business requirements from the start and presenting them as an accurate and precise Business Requirement for the business users. A sound Business Requirement Architecture (BRA) approach not only capture the right user requirement, but also consider the business value for every project.
This intensive 2-days course will offer a practical and proven business requirement architectural processes that can be applied to an individual’s organisation both for the short term and the long term that will help eliminate project shortfalls and failures.
**Certificate of Fundamental Understanding in Architecting Business Requirement will be awarded upon successfully passing the exam.
Upon completion of this workshop, participants will be able to:
- It provides an easy to understand basis for discussions and understanding for the project to be developed by both business and IT teams
- It helps produce an accurate & precise Business Requirements by matching the needs and wants of the business users that can be used as a common platform
- It provides proper guidance and increases the success rates of IT projects by making the Business Requirements easy to prepare and comprehend
- It will give the stakeholders transparency and makes it easy to identify errors and missing components early in the requirements stage prior to the implementation
- Useful as inputs for multiple audiences involved in the IT project for both technical and non-technical/business roles i.e. Business stakeholders, Users, PM, DBA, Testers, Developers, IT Architects, Engineers, Business Analyst, System Analyst, etc
- The Driving Force of Business Requirement Architecture
- Unified Modeling Language (UML) Notation – an industry standard
- Modeling Technique: Use Case Approach
- Standards and Guidelines for writing Use Cases for user requirement
- Beware to succeed in Use Case Modeling
- Best Practices for Business Requirement - Business Requirement Pattern
- Business Architecture – the missing link between Business & IT
Anyone who need to read, write or approve the requirement for IT project, as well as, anyone that need to ensure the success of IT project (on time, on budget and on functionality).
- Business User involved in the IT project
- Business Analysts
- Chief Architects
- IT Architects
- Software Developers
- Senior Programmers
- IT Managers
- Request for Proposal Team
- System Analysts
- Solution Architects
- Software Architects
- Software Engineers
- Senior Analysts
- Project Managers