Scribd
Upload
4 views5 pages

ASSIGNMENT-02-SE Compiler Design Compiler Construction Notes

The document outlines an assignment for a Software Engineering course at Bahria University, focusing on use case diagrams and requirement specifications. It details the purpose of use case diagrams in software development, provides examples for an insulin pump and an e-learning platform, and describes the steps for defining requirement specifications. Additionally, it includes a structured requirement specification for a mental health care management system, Mentcare.

Uploaded by

za241967
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views5 pages

ASSIGNMENT-02-SE Compiler Design Compiler Construction Notes

The document outlines an assignment for a Software Engineering course at Bahria University, focusing on use case diagrams and requirement specifications. It details the purpose of use case diagrams in software development, provides examples for an insulin pump and an e-learning platform, and describes the steps for defining requirement specifications. Additionally, it includes a structured requirement specification for a mental health care management system, Mentcare.

Uploaded by

za241967
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

BAHRIA UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE


Assignment # 02

Subject Name: Software Engineering Time Allowed: 01week


Subject Code: SEN-220 Marks: 10

Question # 01 (CLO 2)

a) Why use case diagram used for software development process.

A use case diagram is used in the software development process for the following
reasons:
1. Visual Representation of Requirements: It provides a visual representation of
the functional requirements of the system, showing how users (actors) interact
with the system.
2. Identify System Functionality: It helps in identifying the key functionalities of
the system and the interactions between users and the system.
3. Communication Tool: It serves as a communication tool between stakeholders
(e.g., developers, clients, and end-users) to ensure a common understanding of the
system's behavior.
4. Scope Definition: It helps in defining the scope of the system by outlining what is
included (and excluded) in the system.
5. Requirement Analysis: It aids in requirement analysis by breaking down
complex processes into simpler use cases.
6. Foundation for Testing: It provides a foundation for creating test cases by
identifying all possible scenarios of user interaction.

b) Draw Use Case Daigram for Insulin Pump case study

• Actors:
o Patient: The primary user who interacts with the insulin pump.
o Doctor: A medical professional who configures and monitors the pump.
o Nurse: Assists the patient and monitors the pump.
• Use Cases:
o Deliver Insulin: The pump delivers insulin based on the patient's glucose
levels.
o Monitor Glucose Levels: The pump continuously monitors the patient's
glucose levels.
o Configure Pump Settings: The doctor or nurse configures the pump
settings (e.g., insulin dosage).
o Alert for Low/High Glucose: The pump alerts the patient or nurse if
glucose levels are too low or high.
o Battery Check: The pump checks and alerts when the battery is low.

c) Draw Use case Diagram for ilern Case study. .

• Actors:
o Student: A user who takes courses on the platform.
o Instructor: A user who creates and manages courses.
o Admin: Manages the platform and user accounts.
• Use Cases:
o Enroll in Course: A student enrolls in a course.
o Take Assessment: A student takes quizzes or exams.
o Create Course: An instructor creates a new course.
o Upload Content: An instructor uploads course materials.
o Manage Users: An admin manages user accounts (e.g., add/remove
users).
o Generate Reports: An admin generates reports on platform usage.
Question # 02 (CLO )

a) How requirement specification were defined.

Requirement Specification is defined through the following steps:


1. Requirement Elicitation: Gathering requirements from stakeholders through
interviews, surveys, workshops, and observation.
2. Requirement Analysis: Analyzing the gathered requirements to identify
inconsistencies, ambiguities, and conflicts.
3. Requirement Documentation: Documenting the requirements in a structured
format, such as a Software Requirements Specification (SRS) document.
4. Requirement Validation: Validating the requirements with stakeholders to
ensure they accurately represent their needs.
5. Requirement Management: Managing changes to requirements throughout the
project lifecycle to ensure consistency and traceability.

b) Define structured specification of a requirement for Mentcare Case study.

The Mentcare case study involves a system for managing mental health care. Below is a
structured specification for a requirement:
• Requirement ID: MC-001
• Requirement Title: Patient Registration
• Description: The system shall allow healthcare providers to register new patients
in the Mentcare system.
• Actors: Healthcare Provider (Doctor/Nurse)
• Preconditions:
o The healthcare provider must be logged into the system.
o The patient must not already be registered in the system.
• Postconditions:
o The patient's details are stored in the system.
o A unique patient ID is generated.
• Functional Requirements:
o The system shall capture patient details (e.g., name, age, contact
information, medical history).
o The system shall validate the entered data for accuracy and completeness.
o The system shall generate a unique patient ID upon successful registration.
• Non-Functional Requirements:
o The system shall ensure data security and confidentiality.
o The registration process shall be completed within 2 minutes

You might also like