Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due

ISYS2110 / COMP9110
Assignment 1: Requirements and Functional Modelling

ISYS2110 / COMP9110

Analysis and Design of Web Info Systems

Credit: Ankit Kapoor

Background and Context

The Galactic Empire is undertaking a major project to develop an advanced operating system for the Death Star. This system serves as the central nerve centre of the station, integrating a wide variety of hardware components and software processes that control vital functions across the facility. The network of hardware consists of an extensive array of sensors, processors, communication devices and power modules, all working together to collect data on energy consumption, security status and environmental conditions throughout the station. Meanwhile, the software interprets this data and coordinates actions among the many sub systems, managing secure command channels, operating the superlaser module with exact timing and monitoring potential external threats.

In addition to these core functions, the operating system manages complex tasks such as co ordinating communication between different modules and controlling unique features like Darth Vader’s distinctive Bacta Tank. The system is designed to process large volumes of information rapidly, responding to routine operations as well as unexpected events. Its architecture reveals a high degree of integration between hardware and software elements, offering a glimpse into the sophisticated technology that drives one of the Empire’s most formidable assets.

However, during a recent attack by the pesky rebels, the central power system was destroyed, taking the innovative operating system with it. The Emperor himself, Lord Sidious, has tasked you with designing a new operating system to fulfil the requirements described above: DeathOS.

Almost as if this were an assignment at a university, this task is mandatory and you must complete it, whether you wish to do so or not, for the fate of the Empire depends on it.

Assignment Objectives

• Conduct a detailed requirements analysis for DeathOS.

• Develop and document the functional and non-functional requirements of the application.

• Model system interactions using use cases, use-case diagrams and activity diagrams.

• Ensure the design incorporates fail-safe mechanisms, secure command interfaces and effective alert management.

Assignment Tasks

You are required to produce a comprehensive UML-based design document for DeathOS. Your submission must include the following components:

1. Written Use Cases (50 points):

Develop 5 detailed use cases that capture the functional requirements of DeathOS. Each use case should include:

Actors: Identify all relevant actors and describe their roles.
Pre-conditions: Specify any conditions that must be met before the use case can commence.
Triggering Events: Describe the event that initiates the use case.
Main Flow: Provide a step-by-step account of the primary sequence of events.
Alternative Flows: Outline any alternative paths or exception scenarios, including error handling and security protocols.
Post-conditions: Describe the expected state of the system once the use case has been executed.

2. Non-Functional Requirements Documentation (10 points):

Provide a detailed list of 10 non-functional requirements for the DeathOS, covering performance, reliability, security, usability, maintainability and compliance. Your docu mentation should clearly justify each requirement in the context of the system’s critical nature.

3. Use-Case Diagram (20 points):

Create one detailed use-case diagram that visually represents the interactions between the system and its actors. You must use at least 5 use cases from Part 1 for your diagram

4. Activity Diagrams (20 points):

Develop two activity diagrams that detail critical workflows within the DeathOS:

(a) Activating the Superlaser: Illustrate the process from command initiation through validation, safety checks and execution of the superlaser activation, including the option for emergency cancellation.

(b) System Alert and Lockdown: Depict the sequence of actions triggered by a security breach or detection of Rebel interference. The diagram should show how the system generates alerts, initiates lockdown procedures and activates fail-safe measures.

Submission Guidelines

Your submission should be a single PDF document submitted to Gradescope. You will need to select the pages that you have used to answer each question.
Clearly label each section of your document and include your name and student ID on the title page.
All diagrams must be legible and adhere to the assignment requirements.
Clearly state any assumptions made during your analysis.

Rubric

Criteria	HD	Distinction	Credit	Pass	Fail	Marks
Written Use Cases	Outstanding analysis; comprehensive, detailed use cases with clear actors, flows, alternatives and post-conditions	Very good use cases; minor omissions in detail or clarity	Adequate use cases; some omissions and inconsistencies	Basic attempt; limited detail and clarity	Inadequate or missing use cases	50
Non-Functional Require-ments	Thorough, well-justified and compre-hensive; all requirements clearly linked to system criticality	Very good; minor omissions in justification or coverage	Adequate; meets basic requirements but lacks depth	Basic; limited detail and justification	Inadequate or missing documentation	10
Use-Case Diagram	Highly detailed and accurate; all actors and use cases clearly represented	Clear and detailed; minor omissions present	Adequate; some inaccuracies in representation	Basic diagram; significant omissions in key interactions	Inadequate or missing diagram	20
Activity Diagrams	Both diagrams are comprehen-sive and precisely depict workflows with fail-safes	Clear diagrams; minor omissions or inaccuracies	Adequate diagrams; some missing details or errors	Basic diagrams; significant omissions in workflow steps	Inadequate or missing diagrams	20

文章

ISYS2110 / COMP9110 Assignment 1: Requirements and Functional Modelling