Assessment Brief: BIS3003 IS Capstone Industry Project A Trimester 2, 2022 Assessment Overview Assessment Task Type Weighting Due Length ULO Assessment 1: Project Definition and Scope The report...

project 2



Assessment Brief: BIS3003 IS Capstone Industry Project A Trimester 2, 2022 Assessment Overview Assessment Task Type Weighting Due Length ULO Assessment 1: Project Definition and Scope The report defines the problem, describing the background and context, and detailing the scope of the project to be undertaken. Individual 10% Week 3 1500 words ULO1 ULO2 Assessment 2: Requirements Analysis Students submit a report covering their requirements analysis for the project. Individual 20% Week 6 1500 words ULO2 ULO3 Assessment 3: Project Reflection Reflection on the student’s journey in the unit focused on (a) the skills and knowledge they were able to draw on from earlier parts of the course; (b) the areas where they needed development and how they addressed those; (c) how they would approach a project like this next time; (d) considerations for BIS3006 IS Capstone Industry Project B Individual 30% First: Week 7 and Second: Week 12 2*1000 words ULO5 Assessment 4: Report and Oral Defence Students prepare and the Project Design, Feasibility Analysis, and Initial Implementation Plan and present and defend their solution design through an oral defence. Group Invigilated 40% Week 11 3000 words Presentation 15 minutes maximum; 15 slides maximum (1500 word equiv.) ULO1 ULO2 ULO3 ULO4 Assessment 1: Project Definition and Scope Due date: Week 3 Group/individual: Individual Word count/Time provided: 10% Weighting: 1500 words Unit Learning Outcomes: ULO1, ULO2 Assessment 1 Detail Assessment 1: Project Definition and Scope The report defines the problem, describing the background and context, and detailing the scope of the project to be undertaken. Assessment 1 Marking Criteria and Rubric The assessment will be marked out of 10 and will be weighted 10% of the total unit mark. The marking criteria and rubric are shown on the following page. Assessment 1 Marking Criteria and Rubric Marking Criteria Not Satisfactory (0-49% of the criterion mark) Satisfactory (50-64% of the criterion mark) Good (65-74% of the criterion mark) Very Good (75-84% of the criterion mark) Excellent (85-100% of the criterion mark) Criterion -1 (1 mark) Does the business case is established for the project proposal, and the project scope described . Business case is not established for the project proposal, and the project scope is not described Business case is established for the project proposal, and the project scope generally described Business case is established for the project proposal, and the project scope described Business case is established for the project proposal, and the project scope clearly described Business case is established for the project proposal, and the project scope clearly and specifically described . Criterion-2 (1 mark) Does project charter identifies your goal and sets out the work commitments expected of you Project charter is not identifies your goal and sets out the work commitments expected of you Project charter is generally identifies your goal and sets out the work commitments expected of you Project charter is identifies your goal and sets out the work commitments expected of you Project charter is clearly identifies your goal and sets out the work commitments expected of you Project charter is clearly and specifically identifies your goal and sets out the work commitments expected of you Criterion-4 (8 marks) Does the Vision document demonstrate the ability of spelling out the core idea and the business case justifying the development effort. Business case is not addressed and captures the business value of the proposed system. All stakeholders is not identified. Business needs is not expressed. Functional and Non- functional requirements are related to business needs and identified. Business case is addressed and vaguely captures the business value of the proposed system. Some stakeholders identified. Business needs generally expressed. Some Functional and Non-functional requirements are related to business needs and identified. Business case is addressed and captures the business value of the proposed system. All stakeholders identified. Business needs expressed. Functional and Non- functional requirements are related to business needs and identified. Business case is clearly addressed and captures the business value of the proposed system. All stakeholders clearly identified. Business needs clearly expressed. Functional and Non- functional requirements are related to business needs and clearly and specifically identified. Business case is clearly and specifically addressed and captures the business value of the proposed system. All stakeholders clearly and specifically identified. Business needs clearly and specifically expressed. Functional and Non- functional requirements are related to business needs and clearly and specifically identified. Assessment 2: Requirements Analysis Due date: Week 6 Group/individual: Individual Word count/Time provided: 1500 words Weighting: 20% Unit Learning Outcomes: ULO2, ULO3 Assessment 2 Detail Assessment 2: Requirements Analysis Students submit a report covering their requirements analysis for the project. Assessments 2 Marking Criteria and Rubric The assessment will be marked out of 20 and will be weighted 20% of the total unit mark. The marking criteria and rubric are shown on the following page. Assessment 2 Marking Criteria and Rubric Marking Criteria Not Satisfactory (0-49% of the criterion mark) Satisfactory (50-64% of the criterion mark) Good (65-74% of the criterion mark) Very Good (75-84% of the criterion mark) Excellent (85-100% of the criterion mark) Criterion (5 marks) Does the Interaction Model helps to identify user requirements? Does modelling of highlights the communication problems that may arise. Does Modelling the component interaction helps in understanding if a proposed system structure is likely to deliver the required system performance and dependability. No critical and minor Use Cases identified Some critical and minor Use Cases identified and correctly named. The identified Use Cases completely consistent with needs and features of your proposed system. The use case diagram built including all identified use cases. The use case descriptions provided for all identified use. All Use case diagrams built that show clear and significant interactions between a system and its environment. Sequence diagrams built that show clear and significant interactions between actors and the system and between system components. Several critical and minor Use Cases identified and correctly named. The identified Use Cases completely consistent with needs and features of your proposed system. The use case diagram built including all identified use cases. The use case descriptions provided for all identified use. All Use case diagrams built that show clear and significant interactions between a system and its environment. Sequence diagrams built that show clear and significant interactions between actors and the system and between system components. Almost critical and minor Use Cases identified and correctly named. The identified Use Cases completely consistent with needs and features of your proposed system. The use case diagram built including all identified use cases. The use case descriptions provided for all identified use. All Use case diagrams built that show clear and significant interactions between a system and its environment. Sequence diagrams built that show clear and significant interactions between actors and the system and between system components. All critical and minor Use Cases identified and correctly named. The identified Use Cases completely consistent with needs and features of your proposed system. The use case diagram built including all identified use cases. The use case descriptions provided for all identified use. All Use case diagrams built that show clear and significant interactions between a system and its environment. Sequence diagrams built that show clear and significant interactions between actors and the system and between system components. Criterion (5 marks) Does the structural model of the software display the organization of a system in terms of the components that make up that system and their relationships?. Does it show the dynamic models, which show the organization of the system when it is executing?. No critical and minor classes identified Some critical and minor classes identified based on the identified requirements and correctly named. All Domain Class diagrams built and show the object classes in the system and the associations between these classes. Relationships between domain objects correct. Completely correct concept of inheritance and aggregation/composition shown (if appropriate). All domain class diagrams built without concerning about the implementation detail. No application concepts such as databases or user interfaces present in domain model. Several critical and minor classes identified based on the identified requirements and correctly named. All Domain Class diagrams built and show the object classes in the system and the associations between these classes.