| Credit- Degree applicable | | Effective Quarter: Fall 2020 | I. Catalog Information
| CIS 95H | Business and Requirement Analysis | 4 Unit(s) |
| | Advisory: EWRT 211 and READ 211 (or LART 211), or ESL 272 and 273. Lec Hrs: 48.00
Out of Class Hrs: 96.00
Total Student Learning Hrs: 144.00 This course provides practice to do a needs assessment, planning, analysis, traceability, monitoring and evaluation of business requirements and processes. |
| Student Learning Outcome Statements (SLO)
| | | Create business requirements being mindful of customer needs, objectives and change management. |
|
II. Course Objectives | A. | Design a business problem using 'problem and opportunity analysis technique' and develop a solution scope statement to provide input to create a business case. |
| B. | Scrutinize the business analysis activities that will occur within the project. This includes establishing tools, policies, and procedures for the requirements management plan, requirements traceability, change management, document control, and acceptance criteria. |
| C. | Apply elicitation, analysis, decomposition, acceptance, approval, specification, and validation of the requirements for a product or project. |
| D. | Demonstrate lifecycle requirements that is comprised of continuous monitoring and documenting of requirements as well as the communication of the requirements status to stakeholders. |
| E. | Critique how well the delivered solution fulfills the requirements and meets the business need. Tasks within this domain include testing the solution, determining if there are gaps, and obtaining sign-off. |
III. Essential Student Materials IV. Essential College Facilities V. Expanded Description: Content and Form | A. | Design a business problem using 'problem and opportunity analysis technique' and develop a solution scope statement to provide input to create a business case. |
| 1. | Define or review a business problem or opportunity using problem and opportunity analysis techniques in order to develop a solution scope statement and/or to provide input to create a business case. |
| 2. | Collect and analyze information from a variety of sources using valuation tools and techniques to contribute to determining the value proposition of the initiative.
|
| 3. | Collaborate in the development of project goals and objectives by providing clarification of business needs and solution scope in order to align the product with the organization’s goals and objectives. |
| 4. | Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved. |
| 5. | Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements. |
| B. | Scrutinize the business analysis activities that will occur within the project. This includes establishing tools, policies, and procedures for the requirements management plan, requirements traceability, change management, document control, and acceptance criteria. |
| 1. | Review the business case, and the project goals and objectives, in order to provide context for business analysis activities. |
| 2. | Define strategy for requirements traceability using traceability tools and techniques in order to establish the level of traceability necessary to monitor and validate the requirements. |
| 3. | Develop requirements management plan by identifying stakeholders, roles and responsibilities, communication protocols, and methods for eliciting, analyzing, documenting, managing, and approving requirements in order to establish a roadmap for delivering the expected solution. |
| 4. | Select methods for requirements change control by identifying channels for communicating requests and processes for managing changes in order to establish standard protocols for incorporation into the change management plan. |
| 5. | Select methods for document control by using documentation management tools and techniques in order to establish a standard for requirements traceability and versioning. |
| 6. | Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements. |
| C. | Apply elicitation, analysis, decomposition, acceptance, approval, specification, and validation of the requirements for a product or project. |
| 1. | Elicit or identify requirements, using individual and group elicitation techniques in order to discover and capture requirements with supporting details (e.g., origin and rationale). |
| 2. | Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected. |
| 3. | Allocate accepted or deferred requirements by balancing scope schedule, budget, and resource constraints with the value proposition using prioritization, dependency analysis, and decision-making tools and techniques in order to create a requirements baseline. |
| 4. | Obtain sign-off on requirements baseline using decision-making techniques in order to facilitate stakeholder consensus and achieve stakeholder approval. |
| 5. | Write requirements specifications using process (such as use cases, user stories), data, and interface details in order to communicate requirements that are measurable and actionable (that is, suitable for development). |
| 6. | Validate requirements using tools and techniques such as documentation review, prototypes, demos, and other validation methods in order to ensure requirements are complete, accurate and aligned with goals, objectives, and value proposition. |
| 7. | Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.
|
| D. | Demonstrate lifecycle requirements that is comprised of continuous monitoring and documenting of requirements as well as the communication of the requirements status to stakeholders. |
| 1. | Track requirements using a traceability artifact or tools, capturing the requirements' status, sources and relationships (including dependencies), in order to provide evidence that the requirements are delivered as stated. |
| 2. | Monitor requirements throughout their lifecycles using a traceability artifact or tool in order to ensure the appropriate supporting requirements artifacts (such as models, documentation, and test cases) are produced, reviewed and approved at each point in the lifecycle. |
| 3. | Update a requirement’s status as it moves through its lifecycle states by communicating with appropriate stakeholders and recording changes in the traceability artifact or tool in order to track requirements towards closure. |
| 4. | Communicate requirements status to project manager and other stakeholders using communication methods in order to keep them informed of requirements issues, conflicts, changes, risks, and overall status. |
| 5. | Manage changes to requirements by assessing impacts, dependencies, and risks in accordance with the change control plan, and comparing to the requirements baseline in order to maintain the integrity of the requirements and associated artifacts. |
| E. | Critique how well the delivered solution fulfills the requirements and meets the business need. Tasks within this domain include testing the solution, determining if there are gaps, and obtaining sign-off.
|
| 1. | Validate the solution's test results, reports, and other test evidence against the requirements acceptance criteria in order to determine whether the solution satisfies the requirements. |
| 2. | Analyze and communicate the solution's identified gaps and deltas using quality assurance tools and methods in order to enable stakeholders to resolve discrepancies between solution scope, requirements, and developed solution. |
| 3. | Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment. |
| 4. | Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition. |
VI. Assignments | A. | Practice exam covering the topics covered in class. |
| C. | Participation in exercises that demonstrate ability to critically evaluate the proper use of appropriate agile software to complete a given set of project related tasks. |
VII. Methods of Instruction | | Lecture and visual aids
Discussion of assigned reading
Discussion and problem solving performed in class
Collaborative learning and small group exercises
Collaborative projects
Guest speakers |
VIII. Methods of Evaluating Objectives | A. | One or two midterm examinations requiring students to apply topics covered in the lectures and reading. To be evaluated on correctness. |
| B. | Final examination requiring students to applying topics covered in the lectures, reading, and assignments. |
| C. | In-class exercises, group exercises, and/or online exercises demonstrating ability to implement requirement analysis to complete a given set of project related tasks. |
IX. Texts and Supporting References | A. | Examples of Primary Texts and References |
| 1. | PMI-PBA Exam Prep: A Course in a book for passing the PMI Professional Business Analysis Exam, Barbara A Carjebirdm, Premier Edition, 2018 (RMC Publications, Inc). |
| 2. | Business Analysis for Practitioners: A Practice Guide, Project Management Institute, 1st edition, 2015 |
| B. | Examples of Supporting Texts and References |
|
