Scribd
Upload
2 views

software engineering

Assignment introduce software engineering diagram lucid app

Uploaded by

malikmalikayaan99
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

software engineering

Assignment introduce software engineering diagram lucid app

Uploaded by

malikmalikayaan99
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Introduction software engineering

Course code--------- Cmp-222

Name : mariam

Roll no : 28

Smester: 5th ssdp

Course code: cmp.222

Assignment: software engineering

Submitted By:

Dr.Hamid
Sequence Diagram

Actors/Entities:

Customer

Bank System

Account Database

Steps:

1. The customer initiates the fund transfer request.


2. The system validates the customer’s credentials.

3. The system checks the account balance.

4. If valid, the system deducts the amount from the source account.

5. The system credits the amount to the destination account.

6. The system confirms the transaction to the customer.

Activity diagram

1. Process Starts

The activity begins with the customer initiating the fund transfer.
2. Validate Credentials

The system validates the customer's credentials.

Decision Point:

If the credentials are valid, the process continues to the next step.

If invalid, the system sends a notification of invalid credentials to the customer,


and the process stops.

3. Check Account Balance

Once credentials are validated, the system checks the balance in the source
account.

Decision Point:

If the balance is sufficient:

The system deducts the transfer amount from the source account.Credits the
transfer amount to the destination account.

Confirms the successful transaction to the customer.

If the balance is insufficient:

The system notifies the customer about the insufficient balance.

The process stops.

4. Transaction Success Notification

If all validations and checks are successful:

The system confirms the transaction to the customer (e.g., via a success message
or receipt).

The process ends.


5. Possible Termination Points

The activity can terminate at different points depending on the scenario:

1. If credentials are invalid → Notify Invalid Credentials → Stop.

3. If the transaction is successful → Confirm Transfer Success → Stop.

Example Flow for Success

1. Customer initiates a transfer of $100 from Account A to Account B.

2. System validates the customer’s login credentials successfully.

3. The system checks the balance in Account A (e.g., $500 available).

4. The system deducts $100 from Account A and credits $100 to Account B.

5. The system sends a success notification to the customer.

6. The process ends.

Example Flow for Failure

Invalid Credentials:

1. Customer enters incorrect credentials.

2. System validates and finds the credentials invalid.

3. System sends a notification: "Invalid credentials."

4. The process ends.

Insufficient Balance:

1. Customer initiates a transfer of $1000 from Account A (with $500 available).

2. System validates credentials successfully.

3. System checks the balance in Account A and finds it insufficient.


4. System sends a notification: "Insufficient balance."

5. The process ends.

Use case Diagram

Actors:

1. Customer: Initiates the fund transfer.

2. Bank System: Processes the request.

3. Account Database: Stores account details and transaction history.

Use Cases and Relationships:

1. Initiate Fund Transfer: Customer provides transfer details.

2. Validate Credentials: The system verifies the customer's authentication details.

<<include>> relationship with Check Login Details.

3. Check Balance: Ensures there are enough funds in the source account.

4. Process Transfer: Deducts from the source account and credits to the
destination account.

5. Notify Status: Confirms success or failure to the customer.

Symbols:

1. Actor: Represents entities (Customer, Bank System).

2. Use Case: Ovals that describe system functionalities (e.g., "Initiate Fund
Transfer").
3. Association: Solid lines connecting actors to use cases.

4. <<include>>: Dashed arrow indicating a mandatory behavior included in a use


case.

5. <<extend>>: Dashed arrow showing optional or conditional behavior.

You might also like