Scribd
Upload
4 views4 pages

SE Assig 02

The document discusses the importance of Use Case Diagrams in software development, highlighting their role in capturing system requirements, enhancing communication, defining system scope, facilitating design, improving validation, and supporting documentation. It also outlines the structured process for defining requirement specifications, which includes elicitation, analysis, documentation, validation, and management. Additionally, it provides a structured specification example for a requirement related to storing and retrieving patient information in a healthcare context.

Uploaded by

studyhumayun0712
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 views4 pages

SE Assig 02

The document discusses the importance of Use Case Diagrams in software development, highlighting their role in capturing system requirements, enhancing communication, defining system scope, facilitating design, improving validation, and supporting documentation. It also outlines the structured process for defining requirement specifications, which includes elicitation, analysis, documentation, validation, and management. Additionally, it provides a structured specification example for a requirement related to storing and retrieving patient information in a healthcare context.

Uploaded by

studyhumayun0712
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/ 4

Software Engineering

Assignment 02
Department of Computer Science
BAHRIA UNOVERSITY, ISLAMABAD

Name: Humayun Tariq Enrollment: 01-134231-028


Class: BS(CS) - 5A
Question # 01 (CLO 2)

(a): Why Use Case Diagrams Are Used in Software Development?

Use Case Diagrams are essential in software development as they visually represent system
functionalities and interactions between users (actors) and the system. Based on the lecture
slides, the key reasons for using Use Case Diagrams include:

1. Capturing System Requirements


o Helps in identifying functional requirements by modeling user interactions.
o Provides a high-level overview of system behavior.
2. Enhancing Communication
o Acts as a bridge between stakeholders, developers, and designers.
o Ensures all parties have a shared understanding of system functionalities.
3. Defining System Scope
o Clearly outlines the boundaries of the system by specifying what the system
will and will not do.
4. Facilitating System Design
o Serves as a foundation for further system design, including class diagrams and
sequence diagrams.
5. Improving Requirement Validation
o Helps verify and validate requirements by ensuring all necessary interactions
are considered.
o Allows for early detection of missing or incorrect requirements.
6. Supporting System Documentation
o Provides a visual representation that is easy to reference during system
development and maintenance.

Use Case Diagrams are a crucial part of the Unified Modeling Language (UML) and play a
significant role in requirement analysis, design, and communication.

b) Use Case Diagram for Insulin Pump Case Study


c) Draw Use case Diagram for ilern Case study.

Question # 02 (CLO )

(a): How Requirement Specifications Are Defined

Requirement specifications are defined through a structured process that ensures clarity,
completeness, and correctness in understanding system needs. The key steps include:

1. Requirement Elicitation
o Involves gathering requirements from stakeholders, including users,
customers, and system analysts.
o Techniques used: Interviews, questionnaires, workshops, document analysis,
and observation.
2. Requirement Analysis
o Evaluating and refining gathered requirements to remove ambiguities,
inconsistencies, and redundancies.
o Prioritizing requirements based on system needs and stakeholder importance.

3. Requirement Documentation

o The finalized requirements are documented in a Software Requirements


Specification (SRS) document.
o The document includes:
§ Functional Requirements – Defines what the system should do (e.g.,
user authentication, data processing).
§ Non-Functional Requirements – Defines system properties (e.g.,
performance, security, usability).

4. Requirement Validation
o Ensuring that requirements accurately reflect stakeholder needs through
reviews, walkthroughs, and prototypes.

5. Requirement Management
o Continuous tracking and updating of requirements to adapt to project changes.
o Version control and impact analysis are used to manage changes effectively.

(b): Structured Specification of a Requirement for Mentcare Case Study

Function

Store and Retrieve Patient Information

Description

Allows healthcare providers to store, retrieve, and update patient medical records, ensuring
accurate and timely access to critical health information.

Inputs

• Patient ID (pID)
• Patient medical history (pHist)
• Current diagnosis and treatment details (pDiag, pTreat)

Source

• Patient ID and medical history from the hospital database


• Diagnosis and treatment details from healthcare provider inputs

Outputs

• Updated patient record (pRecord)


Destination

• Centralized patient database

Action

• If the patient ID exists in the system, update the corresponding record with new
diagnosis and treatment details.
• If the patient ID does not exist, create a new record with the provided details.
• Ensure data integrity by validating input fields before saving.

Requirements

• Secure authentication mechanism for access control


• Database connection for storing and retrieving patient records

Pre-condition

• The database must be online and accessible.

Post-condition

• The updated or newly created patient record is securely stored in the system.

Side Effects

• None, provided data validation and security measures are upheld.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy