1

Assignment 1

Draw the Work Breakdown Structure for Library Management System.

The WBS is structured hierarchically with major deliverables and their respective sub-tasks.

So, here is the work breakdown structure for library Management System were each of the section is categorized
and their roles respectively.
 2

Assignment 2

Schedule all the activities and sub-activities of using the PERT/CPM charts.

Event Duration (Weeks) Earliest Start Earliest Finish Latest Start Latest Finish Total Float
1-2 4 0 4 0 4 0
2-3 0 4 4 4 4 0
3-4 7 4 11 4 11 0
1-3 3 0 3 1 4 1
2-4 6 4 10 5 11 1

Drawing the CPM/PERT Network Each activity in a PERT/CPM Network, represented by an arrow symbol. Each
activity is preceded and succeeded by an event, represented as a circle and numbered.

GIVEN PATH FORMED: DEPENDENCY AND PATH DURATIONS:

1. Critical Path:

1–2 → 2–3 → 3–4

Total Duration = 4 + 0 + 7 = 11 weeks
Critical Path (Float = 0)

2. Alternative Path 1:
1–3 → 3–4
Total Duration = 3 + 7 = 10 weeks
Float = 1 week

3. Alternative Path 2:
1–2 → 2–4
Total Duration = 4 + 6 = 10 weeks
Float = 1 week

OUTPUT OBTAINED: DESIRED OUTPUT:

So, the critical path has been found where the

duration is 11 weeks, long to complete along
activities 1-2, 2-3 and 3-4.

The Backward Pass – Latest Finish Time Rule To make

the Backward Pass, we begin at the sink or the final
event and w ork backwards to the first event.
 3

Assignment 3

Draw a Use Case diagram of Library Management System.

Output:

Here is the complete use case diagram of a library Management system were the actors are STUDENT and
LIBRARIAN performing their tasks assigned respectively.
 4

Assignment 4

Identify and analyze all the possible risks and its risk mitigation plan for the system to be automated.

Definition: Risk mitigation planning is the process of developing options and actions to enhance opportunities and
reduce threats to project objectives. Risk mitigation implementation is the process of executing risk mitigation
actions. Risk mitigation progress monitoring includes tracking identified risks, identifying new risks, and evaluating
risk process effectiveness throughout the project.

Example: Evolution of Healthcare Enterprise Risk Management (ERM) ERM encompasses eight risk domains:

ERM Domain 1. Risk Identification 2. Impact 3. Risk 4. Mitigation & Monitoring

Assessment Prioritization
Operational System failure, process Service delays, High SOPs, backups, pilot testing;
disruption patient monitor system logs &
dissatisfaction uptime reports
Clinical Incorrect automation Patient safety risk, Critical Manual override, clinical
in care processes legal exposure validation; track error rates
Strategic Misalignment with Wasted resources, Medium Align with org goals;
goals reputational risk quarterly strategy reviews
Financial High costs, billing Financial loss, High ROI analysis, financial audits;
issues compliance fines monitor budgets & invoices
Human Capital Workforce resistance, Low adoption, Medium Change management,
lack of training increased errors reskilling; staff feedback,
usage metrics
Legal/Regulatory HIPAA/GDPR non- Legal penalties, data Critical Compliance audit, access
compliance breach control; regular privacy
reviews
Technology Cybersecurity threats, Data loss, system Critical Security measures, phased
integration failures outages deployment; real-time
monitoring
Hazard Power failure, disaster System downtime, High DR plans, cloud backup; test
impacts data loss recovery plans, periodic drills
 5

Assignment 5

Draw a Class Diagram of Library Management System using StarUML.

Output:

Here is the class diagram of a Library management system were the class name, Attributes and operations are been
displayed.

In the above diagram users can access CATALOGUE PAGE, PAYMENT BILLING SYSTEM and also receive NOTIFICATION
were as LIBRARIAN ADMIN can access the NOTIFICATION SYSTEM, INVENTORY, CATALOGUE PAGE, PAYMENT
BILLING SYSTEM for regular checking and optimization if required.

Both ends need an approval username and password for login access across the server.
 6

Assignment 6

Draw a Sequence Diagram of Online ticket reservation system using StarUML.

Output:

Here is the sequence diagram

Here the actor is the passenger who is booking a ticket for a flight reservation. The individual steps are given for the
passenger (ACTOR) to get through each process of successfully booking the flight.

The different sequence of an online ticket reservation system are:

 Flights
 Available Flights
 Flight class
 Passenger Information
 Meal and Set
 Payment.
Other Main sequence are:

 Print and
 Cancel.
The passenger can select the respective areas for their progress.
 7

Assignment 7

Draw an Activity Diagram of Library Management System using Star UML.

Output:

Here, is the activity diagram of a library management system, where the system is divided into two major parts
which are LOGIN PAGE AND REGESTRATION PAGE and seconds part are SEARCH, USER DETAILS, ORDER STATUS, AND
DUE DATE CHECK.
 8

Assignment 8

Define the functional and non-functional requirements of Library Management System by using use cases and
document in SRS document.

Procedure:

Clear requirements are crucial for successful projects, serving as a formal agreement between the client and
provider to align on shared goals. Well-defined requirements reduce financial risks and help maintain schedules.
According to the Business Analysis Body of Knowledge, requirements are a usable representation of a need. Creating
them involves elicitation, analysis, specification, validation, and management. Before exploring the process, it’s
important to understand the main types of software requirements.

Business requirements. These include high-level statements of goals, objectives, and needs. Stakeholder
requirements. The needs of discrete stakeholder groups are also specified to define what they expect from a
particular solution. Solution requirements. Solution requirements describe the characteristics that a product must
have to meet the needs of the stakeholders and the business itself.

 Nonfunctional requirements describe the general characteristics of a system. They are also known as quality
attributes.
 Functional requirements describe how a product must behave, what its features and functions. Transition
requirements. An additional group of requirements defines what is needed from an organization to
successfully move from its current state to its desired state with the new product.
 9

Example:

Use cases: Usually drawn with ovals, use cases represent different use scenarios thatactors might have with the
system (log in, make a purchase, view items, etc.)

System boundaries: Boundaries are outlined by the box that groups various use cases in a system.

Actors: These are the figures that depict external users (people or systems) that interact with the system.
Associations: Associations are drawn with lines showing different types of relationships between actors and use
cases.

Example:
 10

Assignment 9

Define Complete Project plan for Library Management System to be automated using Microsoft Project Tool.

Procedure:

To officially enable auto scheduling we have to change a few things in Microsoft Project Tools to continue

Setting change 1: Make Auto Scheduling the default Click to File -> Option

Setting change: make auto scheduling set to new Tasks

Setting change 2: Enable immediate calculation We want Microsoft Project to re-calculate the project schedule
immediately after we make a change.

Now since we picked up a business idea, we need to go from writing a business plan to a fully established business.
For these steps, we are going to create a project plan.
 11

Step1: Create a new project

First, we create a Project Summery Task

Here what we should see:

Giving an appropriate name:

Step 2: Enter a project start Date

We will enter the start date(for example : 14th September 2020)

Step 3: Enter the list of tasks

 12

In this project, we need to accomplish the following tasks:

 Create business plan

 Get business license
 Set up bank account
 Get funding
 Pick a business location
 Set up office equipment and furniture
 Hire team
 Run promotion

Step 4: Enter task durations

 13

Assignment 10

Test Cases for Functionalities of ATM system.

Purpose:

This document outlines the functional and non-functional requirements for the Bank24 ATM network. It serves as a
reference for software engineers, testers, and stakeholders to ensure system consistency and clarity.

Scope:

Bank24 is a computerized ATM system allowing users to perform banking operations like withdrawals, balance
inquiries, transfers, and deposits through interconnected ATM machines. The system supports access to multiple
banks and ensures secure transactions.

Intended Audience:
This document is intended for software designers, developers, testers, system engineers, and bank stakeholders
involved in the design and deployment of the ATM system.

System Actors:

 User (Customer)
 ATM Machine
 Bank System
Product Perspective:

The ATM system provides a self-service platform for users to perform banking operations without teller assistance.
Users access services by inserting a card and entering a PIN. The machine interfaces with a secure backend bank
server.

Product Functions:
 Login: Authenticate user using card and PIN.
 View Balance: Display account balance.
 Withdraw Cash: Allow user to withdraw within limits.
 Transfer Funds: Transfer money between accounts.
Operating Environment:
The system will run on ATM hardware equipped with a card reader, currency dispenser, touch screen, keypad,
continuous power, and bank network connectivity.

Design Constraints:

Card validity checks (expiry, stolen, disabled), account status, PIN verification, login attempt limits, and error
messages must be implemented as described. Accounts will lock after three failed attempts.

Assumptions and dependencies:

The ATM hardware is assumed to be fault-tolerant and secure. The system assumes daily transaction and cash limits.

External Interfaces:

i. User Interface: Must be intuitive and user-friendly.

ii. Hardware Interface: Must include card reader, keypad, screen, and note dispenser.
iii. Software Interface: Must integrate with systems of State Bank and Indian Overseas Bank.
Safety Requirements

ATMs must be securely installed and enclosed, with access controlled via card swipe. An emergency phone must be
available outside the booth.

Security Requirements

User PINs must be securely handled, with limited login attempts. Users should be advised to change their PIN on first
use.
 14

Common Error Scenarios

Examples include incorrect card insertion, invalid PIN, exceeding withdrawal limits, and transaction cancellation at
various steps.

Here is the simple workflow of the Functionalities of ATM system

Here the test cases are being divided into three parts which are;

 VERIFY CARD AUTHENTICATION,

 VERIFY CASH WITHDRAWL, AND
 VERIFY BALANCE INQUARY.
There are other functionality but the main three are these.
 15

Assignment 11

Test cases for Banking Applications.

Banking applications are among the most complex systems in the software development and testing industry due to
several critical characteristics:

Key Characteristics of Banking Applications (Condensed):

1. High Security and Data Integrity: Transactions must be secure, accurate, and tamper-proof.
2. Complex Business Workflows: Involves multi-step processes and validations across services.
3. High Transaction Volume: Supports thousands of users and transactions per second.
4. Large-Scale Integration: Interfaces with external systems like bill payments and trading.
5. Robust Infrastructure: Includes real-time/batch processing, disaster recovery, and massive storage.
Then the architecture Layers of Banking Systems:

 Web Server: User interaction through browsers.

 Middle Tier: Business logic and data validation.
 Database: Data storage and procedure execution.
 Transaction Processor: High-volume processing, often on mainframes.
And finally, the testing Approach:

End-to-end testing is essential, using a combination of methods to ensure:

 Full workflow and requirement coverage.

 Functional correctness.
 Security and data integrity.
 Performance under concurrent use.
 Positive user experience.

Here is the workflow of Banking application Testing:

The different steps of workflow are given in that chart. In conclusion comprehensive testing across all system
components and workflows is vital for reliable and secure banking applications.
 16

Assignment 12

Test plan document for Library Management System.

Introduction:

This document outlines the test strategy, objectives, resources, and schedule for testing the Library Management
System (LMS). The purpose of testing is to validate the functionality, performance, and reliability of the system
before deployment.

Objective:

To ensure that all modules of the LMS are working according to the specified requirements and are free from
defects.

Scope of Testing

In-Scope:

 User registration and login

 Book search and issue/return process
 Book reservation
 Fine calculation
 Admin functionalities (add/edit/delete books and users)
 Reporting and dashboard
Out-of-Scope:

 Third-party integrations (e.g., external catalog APIs)

 Network performance testing

Test Strategy

Testing Types:

 Functional Testing: Verify each function of the LMS

 Integration Testing: Test data flow between modules
 System Testing: End-to-end workflow testing
 Regression Testing: Verify new changes don't break existing functionality
 Usability Testing: Ensure user-friendliness
 Security Testing: Validate authentication and access controls
Test Environment:

 Frontend: Web interface (browser-based)

 Backend: Database (e.g., MySQL or PostgreSQL)
 Server: Application server with deployed LMS
 Tools: Selenium (for automation), JIRA (for bug tracking), Postman (for API testing)
Test Deliverables:

 Test Plan
 17

 Test Cases
 Test Scripts (if automated)
 Test Data
 Defect Reports
 Test Summary Report

Entry and Exit Criteria

Entry Criteria:

 Complete and stable build available

 Test environment ready
 Requirements reviewed and approved
Exit Criteria:

 All major defects fixed and verified

 Test coverage meets or exceeds 95%
 Test summary reviewed and signed off

Roles and Responsibilities:

Role Responsibility
Test Manager Define test plan, manage resources
QA Engineer Design and execute test cases
Developer Fix defects and provide support
Business Analyst Clarify requirements

Schedule:

Activity Start Date End Date

Requirement Analysis June 5 June 6
Test Case Design June 7 June 10
Environment Setup June 8 June 9
Test Execution June 11 June 20
Bug Fixes & Retesting June 21 June 25
Test Closure June 26 June 27

Risks and Mitigation:

Risk Mitigation Strategy

Delay in build availability Coordinate closely with dev team
Changing requirements Lock scope after review and approval
Test environment instability Allocate dedicated stable environment

In conclusion the test plan ensures a systematic approach to verifying the Library Management System's
functionality and reliability. It aims to identify defects early, ensure quality, and deliver a stable system that meets
user needs.
 18

Assignment 13

Complete documentation of developing the software using SDLC model -1.

Assume a Project of Rohini Infotech Pvt Ltd will start on 7th August 2023.The fiscal year of the manufacturing
company starts on 1st April. The company works by a standard time from 9.00AM to 2.00PM (pre-lunch) and 3:00
PM to 6:00 PM (post-lunch). The working hour for Saturday is 9:00AM to 2:00PM.

The Project consists of following tasks:

ID Tasks Duration (Days) Predecessor

A High level analysis 3 -

B Selection of hardware platform 4 A

C Installation and commissioning of hardware 2 B

D Detailed analysis of core modules 5 B

E Detailed analysis of supporting modules 1 C

F Programming of core modules 3 D

G Programming of supporting modules 6 D

H Quality assurance of core modules 4 F

I Quality assurance of supporting modules 4 G

J Core module training 2 D, H

K Development and QA of accounting reporting 1 I

L Development and QA of management reporting 1 J

M Development of Management Information System 1 K

N Detailed training 4 I, J, K, M

Each employee gets the following statutory holidays:

1st January (New Year's Day); 21st April (Id-Ul-Fitar); 2nd October (Gandhi’s Birthday);
23rd January (Birthday of Netaji); 1st May (May Day); 14th October (Mahalaya);
26th January (Republic Day); 28th June (Id-Uz-Zoha); 20th to 28th October (Durga Puja);
8th March (Doljatra); 29th July (Maharaum); 12th November (Kalipuja & Birthday
of Guru Nanak);
7th April (Good Friday); 15th August (Independence Day);
15th November (Bhatridwitiya);
15th April (Bengali New Year); 6th September (Janmashtami);
25th December (Christmas Day);

Change the ‘Standard (Project Calendar)’ calendar to a customized one (e.g.Roll_CompanyName) in order to reflect
these company-wide working and non-working times as well.

1. Draw the Gantt chart view.

2. Draw the Network Diagram and indicate the Critical path and indicate it in Red.

3. Find also the Minimum time of completion for the Project.

 19

Output:

The minimum time of completion the project:

High Level Analysis + Selection of Hardware Platform + Detailed analysis of core Modules + Programming of
Supporting Modules + Quality assurance of supporting modules + Development and QA of accounting reporting +
Development of Management Information + Detailed training

=3+4+5+6+4+1+1+4

= 28 days.
 20

Assignment 14

Complete documentation of developing the software using SDLC model -2.

Assume a Project of Intelligent GST Accounting Software will start on 2nd September 2023.The fiscal year of the
manufacturing company starts on 1st April. The company works by a standard time from 9.30AM to 1.00PM (pre-
lunch) and 2:30 PM to 6:00 PM (post-lunch). The working hour for Saturday is 8:00AM to 1:00PM.

The 2nd and 4th Saturday of the months are the Bi-Weekly holiday.

The Project consists of following tasks:

ID Tasks Duration (Days) Predecessor

A High level analysis 3 -

B Selection of hardware platform 3 A

C Installation and commissioning of hardware 2 B

D Detailed analysis of core modules 5 B

E Detailed analysis of supporting modules 2 C

F Programming of core modules 3 D, C

G Programming of supporting modules 5 D

H Quality assurance of core modules 4 F

I Quality assurance of supporting modules 3 G

J Core module training 2 D, H

K Development and QA of accounting reporting 1 I

L Development and QA of management reporting 2 J

M Development of Management Information System 2 K

N Detailed training 4 I, J, K

Each employee gets the following statutory holidays:

1st January (New Year's Day); 21st April (Id-Ul-Fitar); 2nd October (Gandhi’s Birthday);
23rd January (Birthday of Netaji); 1st May (May Day); 14th October (Mahalaya);
26th January (Republic Day); 28th June (Id-Uz-Zoha); 20th to 28th October (Durga Puja);
8th March (Doljatra); 29th July (Maharaum); 12th November (Kalipuja & Birthday
of Guru Nanak);
7th April (Good Friday); 15th August (Independence Day);
15th November (Bhatridwitiya);
15th April (Bengali New Year); 6th September (Janmashtami);
25th December (Christmas Day);

Change the ‘Standard (Project Calendar)’ calendar to a customized one (e.g. Roll_CompanyName) in order to reflect
these company-wide working and non-working times as well.

1. Draw the Gantt chart view.

2. Draw the Network Diagram and indicate the Critical path and indicate it in Red.
3. Find also the Minimum time of completion for the Project.
 21

Output:

The minimum time of completion the project:

High Level Analysis + Selection of Hardware Platform + Detailed analysis of core Modules + Programming of Core
Modules + Programming of Supporting Modules + Quality assurance of Core + modules Quality assurance of
supporting modules + Development and QA of accounting reporting + Core Module Training + Detailed training

=3+3+5+3+5+4+3+1+2+4

= 33 days.
 22

Assignment 15

Case Study of developing the software using SDLC model Example

Assume a Project of KnowSolution Software Development will start on 13th February 2023. The fiscal year of the
manufacturing company starts on 1st April. The company works by a standard time from 7.30AM to 5:00PM on
Monday, 8.00 AM to 5:30PM on Tuesday, 9.00AM to 7.00PM on Wednesday, Thursday and Friday. The working hour
for Saturday is 9:00AM to 1:00PM.

The Project consists of following tasks:

ID Tasks Duration (Days) Predecessor Resources

A Problem Identification 3 - Sayan Dey

B Study of Existing System 4 - Sourav Pal, Partho Das

C Task Analysis 2 - Rumpa Pramanik

D SRS Preparation 5 A, B Sayan Dey, Alok Bera

E Form Analysis 1 B Partho Das, Abhirup Bhowmik

F Feasibility Study 3 B Debojyoti Das

G Conceptual Design 6 F, C Gopal Adhikary

H Detailed Design 4 B Satarupa Saha, Sayan Dey

I Coding 4 E, H Tulika Banik

J Testing 2 E, H Sanjukta Sen

K Implementation and Maintenance 1 C, D, F, J Manish Ghosh

L Re-engineering 5 K Mitrajit Chatterjee

Each employee gets the following statutory holidays:

1st January (New Year's Day); 26th June (Id-Ul-Fitar); 18th October (Kalipuja);
23rd January (Birthday of Netaji); 7th August (University Foundation 21st October (Bhatriditya);
Day);
26th January (Republic Day); 4th November (Birthday of Guru
14th August (Janmastami); Nanak);
1st February (Shree Panchami);
15th August (Independence Day); 2nd December (Fateh-Dwaz-
13th March (Doljatra);
Duham);
19th September (Mahalaya);
14th April (Good Friday);
25th December (Christmas Day);
26th September to 5th October
15th April (Bengali New Year Day);
(Durga Puja, Birthday of Gandhiji &
1st May (May Day); Id-Uz-Zoha);

Change the ‘Standard (Project Calendar)’ calendar to a customized one (e.g. Roll_CompanyName) in order to reflect
these company-wide working and non-working times as well.

1. Draw the Gantt chart view.

2. Draw the Network Diagram and indicate the Critical path and indicate it in Red.

3. Find also the Minimum time of completion for the Project.

 23

Output

The minimum time of completion the project:

Study of Existing System + Detailed Design + Testing + Implementation and Maintenance + Re-engineering

= 4 + 4 +2 +1 + 5

= 16 days.
 24

Case Study:

Assume a Software Project on Rapid Solution Software Development starts on 2nd September 2023. The fiscal year
of the development company starts on 1st April. The said company works by a standard time from 8.30AM to
1:00PM (pre-lunch) and 2:00PM to 5:00PM (post-lunch). The working hour for Saturday is from 8:00AM to 1:00PM.
The 2nd and 4th Monday of each Monday are the non-working days. Due to AC maintenance in the month of
December, 2 and 3 week any three days will be half working days i.e work from 8:30 am to 1:30 p.m. Due to the
compensation to this, any one of 2nd and 4th Monday is working day.

Project consists of following tasks:

Each employee gets the following statutory holidays:

1st January (New Year's Day); 21st April (Id-Ul-Fitar); 2nd October (Gandhi’s Birthday);
23rd January (Birthday of Netaji); 1st May (May Day); 14th October (Mahalaya);
26th January (Republic Day & Shree 28th June (Id-Uz- Zoha); 20th to 28th October (Durga Puja);
Panchami);
29th July (Maharaum); 12th November (Kalipuja & Birthday
8th March (Doljatra); of Guru Nanak);
15th August (Independence Day);
7th April (Good Friday); 15th November (Bhatridwitiya);
6th September (Janmashtami);
15th April (Bengali New Year); 25th December (Christmas Day);

1. Draw PERT chart for these activities

2. Draw the Gantt chart view.

3. Draw the Network Diagram and indicate the Critical path and indicate it in Red.

4. Find also the Minimum time of completion for the Project.