Assessment Details and Submission Guidelines | |
| Trimester | T2 2024 |
| Unit Code | HI5030 |
| Unit Title | Systems Analysis and Design |
| Assessment Type | Group Case Study |
| Due Date + time: | 27/09/2024 11.59 pm (Melb / Sydney time) |
| Purpose of the assessment (with ULO Mapping) | Students are required to work in project teams (groups of 4) to complete a systems analysis and design report based on a real-world case study. Students will be expected to critically evaluate the project requirements and provide an innovative solution. The solution will be presented to the various stakeholders in a formal presentation and report.
Aligned Unit Learning Outcomes:
|
| Weight | 40 % |
| Total Marks | Assignment (40 marks) |
| Word limit | 2000 words |
| Submission Guidelines |
|
Academic Integrity Information | Holmes Institute is committed to ensuring and upholding academic integrity. All assessments must comply with academic integrity guidelines. Please learn about academic integrity and consult your teachers with any questions. Violating academic integrity is serious and punishable by penalties that range from deduction of marks, failure of the assessment task or unit involved, suspension of course enrolment, or cancellation of course enrolment. |
| Penalties |
|
Group Assignment Guidelines and Specifications
Assignment Title: Optimizing Business Processes through Information System Design
Assignment Overview:
You have been provided a list of case studies that your group should select one of them. You can find this in the Group assignment case studies.pdf. In this Assignment, your group will focus on identifying inefficiencies in one of these. business's existing processes and designing an information system to optimize these processes. The goal is to create a system that improves operational efficiency, reduces costs, or enhances service delivery.
Assignment Tasks and Deliverables:
- Group Formation:
- Form groups of 4 students.
- Assign roles: Project Manager, Business Analyst, System Architect, Data Modeler, and (if needed) Prototype Developer.
- Task 1: Business Process Analysis and Requirements Gathering:
- Business Analyst: Identify a business with operational inefficiencies and conduct research to gather system requirements.
- Project Manager: Oversee the research process, ensuring that all relevant stakeholders are interviewed, and all necessary data is gathered.
- Deliverable:
- Introduction to the selected project and system description
- Objectives of project
- Requirementspecification (functional and non-functional) and constraints
- Description of the proposed system
- Logical model design
- Data flow diagrams - Context diagram
- Data flow diagrams - Diagram 0/Diagram [Diagram 1 is optional]
- Data dictionary for all the data stores in level 0 DFD and any 3 selected dataflows of your choice.
- You should identify at least 3 inefficiencies and gather 4 requirements.
- Task 2: Process Modelling and System Design:
- System Architect: Design process models (e.g., Data Flow Diagrams, Use Case Diagrams) based on the requirements gathered.
- Data Modeler: Develop data models (e.g., Entity-Relationship Diagrams) to represent the data flow and storage needs of the system.
- Deliverable: process models, data models, and an initial system architecture.
- Object Oriented Modelling Use a suitable UML diagramming software such as Visual Paradigm (community edition) or Lucid charts to model the following diagrams of your selected project. Hand-drawn diagrams or diagrams developed using office suits are not accepted. Based on your project requirements, you may include the entire model in one diagram or subdivide the model into several subsystem diagrams.
- Use case diagrams
- Activity diagrams – select at least 2 main use cases from your project and develop activity diagrams
- Class diagram
- System sequence diagrams - select at least 2 main use cases from your project and develop system sequence diagrams
- User Interface Design an overall user interface consisting of screens, commands, controls, and features to enable users to use the system. Choose at least 4 main functionalities of your project to develop user interfaces. Your design should demonstrate how data will be input to the system? That includes the physical layout for input, the input design and procedures, and how data will be output from the system. Use suitable wireframing software such as Lucid Charts online wireframe tool, Balsamiq Wireframes, or figma.com to design your interfaces.
- Object Oriented Modelling Use a suitable UML diagramming software such as Visual Paradigm (community edition) or Lucid charts to model the following diagrams of your selected project. Hand-drawn diagrams or diagrams developed using office suits are not accepted. Based on your project requirements, you may include the entire model in one diagram or subdivide the model into several subsystem diagrams.
- Task 3: System Architecture and Prototyping:
- System Architect: Finalize the system architecture, detailing how different components of the system interact.
- Prototype Developer: Create a basic prototype or mock-up of the system, focusing on key interfaces and functionalities.
- Deliverable: The finalized system architecture, prototype screenshots, and design documentation.
- At least one screenshot for each requirement identified.
Marking Criteria
| Criteria | Weight | Excellent (80-100%) | Good (70-79%) | Satisfactory (60-69%) | Needs Improvement (50-59%) | Unsatisfactory (0-49%) |
| Clarity of Business Problem & Requirements Analysis | 10 Marks | Clear, well-defined business problem with comprehensive and accurate requirements analysis. All functional and non-functional requirements are included. | Clearly defined business problem with good requirements analysis. Most functional and non-functional requirements are included. | Business problem is defined, but requirements analysis is adequate with some aspects underdeveloped. | Business problem is somewhat unclear, and requirements analysis is incomplete or lacks accuracy. | Business problem is unclear or poorly defined; requirements analysis is superficial or incorrect. |
| Quality of Process & Data Models | 10 Marks | Process and data models are highly detailed, accurate, and effectively illustrate business processes and data requirements. | Process and data models are detailed, accurate, and effectively represent key business processes and data requirements. | Process and data models are satisfactory but may lack some detail or accuracy. Representation of processes and data is generally clear. | Process and data models are incomplete, with several inaccuracies or unclear representation. | Process and data models are missing, inaccurate, or fail to represent business processes and data requirements. |
| Coherence & Detail of System Architecture | 10 Marks | System architecture is comprehensive, coherent, and well-structured, with clear interactions between components. | System architecture is coherent and well-structured, effectively illustrating system components and interactions. | System architecture is satisfactory but may lack some detail or coherence. Some components or interactions could be more clearly defined. | System architecture is incomplete or lacks coherence; components or interactions are unclear or poorly defined. | System architecture is missing, incoherent, or poorly defined, with significant gaps or errors in component interactions. |
| Quality & Usability of Prototype | 10 Marks | Prototype is highly functional, user-friendly, and effectively demonstrates the key features and interfaces of the system. | Prototype is functional and user-friendly, effectively demonstrating key features and interfaces. | Prototype is satisfactory but may lack some functionality or usability. Key features and interfaces are generally demonstrated. | Prototype is incomplete or lacks functionality. Key features and interfaces are not effectively demonstrated. | Prototype is missing, non-functional, or poorly demonstrates the key features and interfaces of the system. |