About the Course
Self-sufficient MINIMAL but IN-DEPTH
knowledge and skills for a beginner.
Putcha V. Narasimham
Contents and Purpose of the Document:
This is a description of detailed syllabus and training course for ENTRY level Business Analysts & Requirements Engineers. It covers WHAT they need to do in the FIRST six to nine months on the job.
Ask for FULL or Module wise Syllabus with Learning Objectives.
Topics CoveredNine key topics covered—(can be adapted to employers’ specifications)
Highlighted parts have high skill mastering scope
1 Concepts, definitions and representations of Business, Systems and Processes; I discuss and apply General System Theory--principles 1 and 2, principles and models of OOAD, UML--only a few. I use rigorous international standard definitions and interpretation. Professionalism flows from appreciative study and use of precise definitions
2 UML Activity Diagrams and BPMN: I emphasize the IMPORTANCE of showing FLOW OF OBJECTS, material, people, energy & signals, in contrast to flow of information and data. I point out the uselessness of showing ONLY control flow in Activity and BPMN and INAPPLICABILITY of branch, merge, fork and join for object flows. Use of AS IS and TO BE Process Maps using UML Activity Diagrams and BPMN. Storyboarding is also included but not taught.
I deliberately avoid Class Diagrams, Sequence Diagrams etc., to avoid getting too deep into software development and design.
3 Software Engineering Introduction; concepts, definitions and application of data and information, nature of software, quality ISO 9000, KANO's model of customer satisfaction, modeling using graphics and mathematics; Software Development Phases, Waterfall model, Unified Process, Iterative and Incremental Development principles, prototyping, examples, exercises etc. (key principles are discussed and excessive description is cutout).
4 Requirements Engineering—ISO 9000 & IEEE 830 definitions of needs, means, product features: Requirements capture from Vision, Mission, Objectives, Policies, rules documents; Requirements Elicitation through costumer interactions; Templates-- 5Ws and 1 H, Hierarchical Requirements Tables --for Breadth-first-and-depth-on-demand--incremental iterative RE;
5 Use Case Diagram, System boundary; Actors, Use Cases and Associations, introduction of Use Case TABLE of Actors, Use Cases and Goals, Use Cases are viewed as SERVICE DIALOG for clarity and precision.
6 Use Case Description Table---Use Case description is presented as a Service Dialog of messages between the system and Actor. This makes business functionality clear and precise for software development.
7 Problem Solving Methods and Tools -- use of TQM QI Tools, principles and use of Cause-Effect Diagram, End-Means Planning Tool
8 Planning--resource planning and activity planning; contingency planning; forms / tables used for planning; application of planning, review; Demings PDCA cycle
9 Unified Process and OOAD iterative incremental development process: details with reference to waterfall model; benefits of inception, elaboration, construction and transition phases applied to parts of software project / product.
Some topics have up to 3 sub-topics each of 15 slides to 20 slides. They are supplemented by templates and published documents --- about 60
Being competent, effective and efficient is 90% mindset and 10% toolset. ---Roger Tregear
So concepts are discussed and applied using MS Word, PPT and Visio (if available). This course does not have access to software tools. Learners are better off mastering the concepts but not the mechanics of tools. Tools are also important and they have to be learnt separately.
Who should attendAny graduate with good logical and communication skills and interest in business systems--manual or automated.
Those who wish to switch to career in Business Analysis and Requirements Engineering
Pre-requisitesAs at Who Should Attend. Take a trial lecture and see if it suits you.
What you need to bringFull attention and enthusiasm to learn and work.
Key TakeawaysProfessional knowledge and skills to take up and competently carry out BA and RE responsibilities within the first 6 to 9 months of the first job.