SE5 Class diagram and Use case diagram

1. Open Dia (Ubuntu: Activities > type Dia; if missing: sudo apt install dia). Ready file: File > Open > the .dia file below
2. Left panel, under the tool icons: click the sheet drop-down (shows Assorted / Flowchart) and pick the sheet named below
3. Use case: sheet UML > Actor (stick man) > click on page; double-click it > Text = Employee. Add Manager, Admin
4. UML > Use case (oval) > click > double-click > Text = Mark Attendance ... (8 ovals)
5. System boundary: top toolbox Box (rectangle) tool > drag around the ovals; title with the T (Text) tool
6. Actor-to-oval: top toolbox Line tool > drag from actor to oval (ends turn red = connected)
7. include: UML > Dependency (dashed arrow) > drag from Apply Leave to Login > double-click > Stereotype = include
8. Class: UML > Class > click; double-click > Class tab: Class name. Attributes tab > New: name, type, Visibility Private
9. Operations tab > New: name, type, Visibility Public (add parameters below). Apply
10. Inheritance: UML > Generalization > drag FROM parent (Employee) TO child (Manager): hollow triangle sits at parent
11. Association: UML > Association > drag Employee to LeaveRequest > double-click > Name applies, Multiplicity A 1, B *
12. Save: File > Save (.dia). Picture for journal: File > Export > choose PNG > Save

Viva

SE6 DFD (Data Flow Diagram) Level 0 and Level 1

1. Open Dia (Ubuntu: Activities > type Dia; if missing: sudo apt install dia). Ready file: File > Open > the .dia file below
2. Left panel, under the tool icons: click the sheet drop-down (shows Assorted / Flowchart) and pick the sheet named below
3. Sheet Flowchart > Ellipse = process: draw, make it a circle, double-click > text 0.0 Office Management System
4. Flowchart > Box = external entity (Employee, Manager, Admin)
5. Sheet Gane and Sarson > Data Store = data store (D1 Employee DB ...) - only in Level 1
6. Arrows: top toolbox Line tool; set the end arrow in the bottom-left arrow selector (or double-click line > End arrow)
7. Label every arrow with the T (Text) tool: login, leave request, payslip ...
8. Level 0 = one circle only. Level 1 = processes 1.0 to 5.0 + data stores. No arrow entity-to-entity or store-to-store
9. Save: File > Save (.dia). Picture for journal: File > Export > choose PNG > Save

Viva

SE7 Activity diagram and State transition diagram

1. Open Dia (Ubuntu: Activities > type Dia; if missing: sudo apt install dia). Ready file: File > Open > the .dia file below
2. Left panel, under the tool icons: click the sheet drop-down (shows Assorted / Flowchart) and pick the sheet named below (UML)
3. Start: UML > State Term (black dot). End: State Term > double-click > tick Is final (bullseye)
4. Action: UML > Activity (rounded box) > double-click > text. Decision: UML > Branch (diamond)
5. Parallel work (if asked): UML > Fork (black bar)
6. Arrows: UML > Transition (or Line tool with end arrow). Double-click Transition > Guard = Yes / No
7. State diagram: UML > State (rounded box: Draft, Submitted ...), Transition > Trigger = submit(), approve() ...
8. Save: File > Save (.dia). Picture for journal: File > Export > choose PNG > Save

Viva

SE10 Test cases using white box testing

1. Write the function (test_leave.py below) and number each statement / decision: nodes 1 to 9
2. Draw the flow graph in Dia: sheet Flowchart > Ellipse (small circles 1-9), Line tool with end arrow, T tool for yes / no
3. Count: E = 11 edges, N = 9 nodes > V(G) = E - N + 2 = 4 (= 3 decisions + 1 = 4 regions)
4. 4 independent paths: 1-2-3-9 | 1-2-4-5-9 | 1-2-4-6-7-9 | 1-2-4-6-8-9
5. One test case per path (table), run: python3 test_leave.py > all PASS
6. Journal table: Test ID | Path | Input | Expected | Actual | Pass/Fail

# Exp 10: function under test + white-box test cases (run: python3 test_leave.py)
def leave_status(balance, days):
    if days <= 0:                      # decision 1
        return "Invalid"
    elif days > balance:               # decision 2
        return "Rejected"
    elif days > 5:                     # decision 3
        return "Needs Manager Approval"
    else:
        return "Approved"

# one test per independent path (V(G) = 3 decisions + 1 = 4)
tests = [
    ("TC1", 10, 0, "Invalid"),
    ("TC2", 3, 5, "Rejected"),
    ("TC3", 10, 7, "Needs Manager Approval"),
    ("TC4", 10, 2, "Approved"),
]
for tc, bal, d, expected in tests:
    actual = leave_status(bal, d)
    print(tc, "balance =", bal, "days =", d, "| expected:", expected,
          "| actual:", actual, "|", "PASS" if actual == expected else "FAIL")

Viva

SE4 Cost estimation using metrics (COCOMO, Function Points)

1. Pick size: OMS = 12 KLOC, organic (small team, known problem)
2. Effort E = a x KLOC^b, Duration D = c x E^d, People = E / D, Cost = E x salary per month
3. Run cost.py (box) to calculate, or do it on paper with the table
4. Function Points: count EI, EO, EQ, ILF, EIF x weights = UFP; FP = UFP x (0.65 + 0.01 x sum Fi)

# Exp 4: Basic COCOMO + Function Point calculator (run: python3 cost.py)
MODES = {"organic": (2.4, 1.05, 2.5, 0.38), "semi-detached": (3.0, 1.12, 2.5, 0.35),
         "embedded": (3.6, 1.20, 2.5, 0.32)}

kloc = float(input("Enter size in KLOC (e.g. 12): "))
mode = input("Mode (organic / semi-detached / embedded): ").strip().lower() or "organic"
cost_pm = float(input("Cost per person-month in Rs (e.g. 50000): "))

a, b, c, d = MODES[mode]
effort = a * kloc ** b            # person-months
time = c * effort ** d            # months
people = effort / time
print(f"Effort   E = {a} x {kloc}^{b} = {effort:.2f} person-months")
print(f"Duration D = {c} x {effort:.2f}^{d} = {time:.2f} months")
print(f"Staff    P = E / D = {people:.2f} people")
print(f"Cost       = {effort:.2f} x {cost_pm:.0f} = Rs {effort * cost_pm:,.0f}")

# Function points (average weights)
counts = {"EI": 6, "EO": 4, "EQ": 3, "ILF": 5, "EIF": 1}
weights = {"EI": 4, "EO": 5, "EQ": 4, "ILF": 10, "EIF": 7}
ufp = sum(counts[k] * weights[k] for k in counts)
fi_sum = 35                       # 14 factors rated 0-5, total
fp = ufp * (0.65 + 0.01 * fi_sum)
print(f"UFP = {ufp}, VAF = {0.65 + 0.01 * fi_sum:.2f}, FP = {fp:.1f}")

Viva

SE9 Version control using Git and GitHub

1. Terminal: git --version (if missing: sudo apt install -y git)
2. Set name / email once, then init, add, commit (box)
3. Make a branch, commit there, merge back to main
4. On github.com: New repository 'oms' > copy URL > git remote add origin URL > git push (login with token)
5. Screenshot: git log --oneline and the GitHub repo page

git --version
git config --global user.name "Your Name"
git config --global user.email "you@example.com"

mkdir oms && cd oms
git init
echo "# Office Management System" > README.md
git add .
git commit -m "Initial commit"
git status
git log --oneline

git branch feature-login
git checkout feature-login
echo "login module" > login.txt
git add login.txt
git commit -m "Add login module"
git checkout main          # (or master)
git merge feature-login

git remote add origin https://github.com/<username>/oms.git
git branch -M main
git push -u origin main

Viva

SE3 Project plan using a project management tool (Gantt chart)

1. Open GanttProject (or ProjectLibre). If not installed: use mermaid.live with the Gantt box
2. Project > New > name 'Office Management System', start date
3. Add tasks from the table (Ctrl+T), set duration in days
4. Link tasks: select two tasks > Link (finish-to-start). Add milestone 'Deployment'
5. Resources tab: add team members, assign to tasks. Export chart as PNG

gantt
  title OMS project plan
  dateFormat YYYY-MM-DD
  section Analysis
  Requirement gathering      :a1, 2026-07-14, 7d
  SRS document               :a2, after a1, 5d
  section Design
  UML and DFD                :d1, after a2, 10d
  section Development
  Inc 1 Login + Directory    :i1, after d1, 10d
  Inc 2 Attendance + Leave   :i2, after i1, 12d
  Inc 3 Payroll + Inventory  :i3, after i2, 12d
  section Release
  Testing                    :t1, after i3, 8d
  Deployment                 :milestone, after t1, 0d

Viva

SE2 SRS document in IEEE format

1. Write the headings below in order (IEEE 830)
2. Fill each with 2-4 lines for your project (OMS example given)
3. Functional requirements numbered FR1, FR2 ...; non-functional NFR1 ...

1. Introduction
  1.1 Purpose      : SRS for Office Management System (OMS) v1.0
  1.2 Scope        : web app for attendance, leave, payroll, inventory, room booking
  1.3 Definitions  : OMS, HR, PM, SRS
  1.4 References   : IEEE 830-1998
  1.5 Overview     : rest of this document
2. Overall Description
  2.1 Product perspective : new standalone web system replacing spreadsheets
  2.2 Product functions   : login, attendance, leave, payroll, inventory, directory
  2.3 User classes        : Employee, Manager, Admin
  2.4 Operating environment: browser, Ubuntu/Windows server, MySQL
  2.5 Constraints         : 150 users, must run on office LAN
  2.6 Assumptions         : every employee has a login
3. Specific Requirements
  3.1 Functional
      FR1 User shall log in with email and password
      FR2 Employee shall mark attendance (in / out time)
      FR3 Employee shall apply for leave; manager approves / rejects
      FR4 Admin shall generate monthly payroll
      FR5 Admin shall update inventory stock
  3.2 Non-functional
      NFR1 Performance : page loads in < 2 s for 150 users
      NFR2 Security    : passwords hashed, role-based access
      NFR3 Availability: 99% during office hours
      NFR4 Usability   : new user learns in < 30 min
  3.3 External interfaces : web UI, email (SMTP) notifications
4. Appendices

Viva

SE8 RMMM plan (Risk Mitigation, Monitoring, Management)

1. List 4-5 risks of your project
2. For each: probability, impact, mitigation (avoid), monitoring (watch), management (if it happens)
3. Risk exposure RE = Probability x Cost of impact

Viva

SE1 DSP (Detailed Statement of Problem) and process model

1. Write: Title, Problem statement, Objectives, Scope, Users, Challenges
2. Choose a process model and justify (OMS = Incremental)
3. Draw the model and list increments
4. Draw the model in Dia: sheet Flowchart > Box for each phase, Line tool with end arrow, T tool for labels

Title     : Office Management System (OMS)
Problem   : 150-employee office uses paper logs, spreadsheets and email for attendance,
            leave, payroll and inventory -> data loss, delays, 15 man-hours/week wasted.
Objectives: automate attendance, leave approval, payroll, inventory, room booking.
Scope     : web app for Employees, Managers, Admin inside the office.
Users     : Employee, Manager, Admin
Model     : Incremental - modules are independent, deliver the most needed first,
            early feedback, lower risk, no big-bang change.

Viva

VIVA general SE questions