CIS3002/CIS5302 S1 2015 - Assignment 2 instructions – DRAFT 1.5

  • CIS3002/CIS5302 S1 2015 - Assignment 2 instructions – DRAFT 1.5
    For CIS3002 students all tasks relate to the Case Study which will be provided – except for CIS5302 students who are expected to find their own “real-world” case study
    As an indication of length - Tasks worth 10 marks are expected to take approximately one page of work as appropriate.
    Presentation: search for examples of consulting company reports, your assignment should have a professional look and feel; put your name, student number, course and semester only on the cover sheet – the rest of the assignment should look like a professional Business Analyst’s report.
    ASSIGNMENT 1
    TASK 1.01 Project Journal
    Develop and maintain a project journal for this phase of your project with date, summary of activities undertaken, actions completed and actions planned. (10 Marks)
    TASK 1.02 Draft a problem/opportunity definition (5 Marks)
    TASK 1.03 Define options to address problem/opportunity
    Structure options in a table with pros, cons, risks, expected costs, benefits (10 Marks)
    TASK 1.04 Write a System Vision statement (10 Marks)
    TASK 1.05 Write the Objectives for the project (5 Marks)
    TASK 1.06 Write a scope statement - list what is in-scope and what is out of scope (10 Marks)
    TASK 1.07 Conduct stakeholder analysis and identify all persons, groups and institutions who may have an interest in the project and the nature of their interest (10 Marks)
    TASK 1.08 Develop a work breakdown structure (WBS) (10 Marks)
    Analyse the project and produce a 1-page Work Breakdown Structure
    Task 1.09 Draft an interview agenda for your interview with the CEO, refer to the text and on-line for examples (10 marks)
    TASK 1.10 Provide an “AS IS” process using Business Process Modelling Notation (BPMN) or UML (Unified Modelling Language) (10 marks)
    TASK 1.11 Develop a “TO BE” process using BPMN or UML (10 Marks)
    Assignment 2 (Draft)

  • images-19-1-24
    Using the system information and the TO BE process
    TASK 2.01 Write a list of the key functionality of the system (write a functional and non-functional specification)
    TASK 2.02 Build a product backlog for the system by decomposing the features into stories (using Agile format “As a .... I want to .... so that..”)
    Product backlog should be in a spreadsheet format
    Task 2.03. COMPARE YOUR As is and to be diagrams to prepare a briefing note for the Organisational change and Training Team regarding the anticipated business impact of the system. You should make recommendations on how these business impacts can be managed

  • TASK 2.04 From a business perspective categorise the backlog using the MOSCOW method and identify the stories that makes your minimum viable product
    TASK 2.05 Develop a screen design for two MUST stories created in Task 10 and identify any business rules; justify your design (10 marks)
    TASK 2.06 Write all acceptance criteria for these two stories to be done (10 marks)
    TASK 2.07 Write a Job Description for a Business Analyst (10 marks)
    Marking guide
    10 9 8 7 5 3 0
    Outstanding: High Distinction: Distinction: Credit: Pass: Fail: Not Submitted:
    An outstanding attempt – well formatted and professionally presented piece of work. An excellent piece of work that meets all the specified criteria with very minor omissions or mistakes More than competently meets the criteria specified with only minor mistakes or omissions. Competently meets the criteria as specified with few minor mistakes or omissions. Satisfactorily meets the criteria. Did not sufficiently meet the criteria to pass. No attempt made or different from what is acceptable

Comments