BCA SOFTWARE ENGINEERING LAB FILE
INDEX
Project 1: Credit Card Processing System (Experiments 1-10)
Project 2: Recruitment System (Experiments 1-10)
PROJECT 1: CREDIT CARD PROCESSING SYSTEM
Experiment 1: Problem Statement
Objective: To develop a Credit Card Processing System.
• Manages credit card transactions electronically.
• Validates card information before payment.
• Checks available credit limit.
• Maintains transaction records.
• Generates reports for administration.
• Improves security and efficiency.
Result: Problem statement studied successfully.
Experiment 2: Software Requirement Specification (SRS)
Functional Requirements: User Login, Card Validation, Payment Processing, View Transactions,
Report Generation.
Non-Functional Requirements: Security, Reliability, Performance.
Hardware: 4GB RAM, Intel Processor.
Software: Windows, StarUML, MySQL.
Result: SRS prepared successfully.
Experiment 3: Feasibility Study
Technical Feasibility: Required technology is available.
Economic Feasibility: Development cost is affordable.
Operational Feasibility: Easy for users and administrators.
Schedule Feasibility: Can be completed within semester duration.
Result: Project found feasible.
Experiment 4: Requirement Analysis
User Requirements: Login, Make Payment, Check Credit Limit, View Transactions.
System Requirements: Validate cards, Store transaction data, Generate reports.
Benefits: Fast processing, Secure transactions, Reduced errors.
Result: Requirements analyzed successfully.
Experiment 5: Study and Usage of CASE Tools
CASE Tools assist in software analysis and design.
Advantages: Better documentation, Improved productivity, Error reduction.
Tools Used: StarUML, [Link], Visual Paradigm.
Result: CASE tools studied successfully.
Experiment 6: Use Case Diagram
Objective: To identify user interactions with the system.
Description: Shows Customer, Bank and Admin actors; major system functions; user requirements.
Result: Use Case Diagram drawn successfully.
(Paste Use Case Diagram Here)
Experiment 7: Sequence Diagram
Objective: To show sequence of operations.
Description: Displays message flow between Customer, System and Bank; payment processing
sequence; interaction order.
Result: Sequence Diagram drawn successfully.
(Paste Sequence Diagram Here)
Experiment 8: Class Diagram
Objective: To represent classes and relationships.
Description: Shows Customer, Card, Transaction and Admin classes; attributes, methods and
system structure.
Result: Class Diagram drawn successfully.
(Paste Class Diagram Here)
Experiment 9: Data Flow Diagram (DFD)
Objective: To show movement of data.
Description: Shows data flow between entities, processes and data stores.
Result: DFD drawn successfully.
(Paste DFD Diagram Here)
Experiment 10: Testing Techniques
White Box Testing, Black Box Testing, Unit Testing, Integration Testing, Alpha Testing, Beta
Testing, Acceptance Testing.
Result: Testing techniques studied successfully.
PROJECT 2: RECRUITMENT SYSTEM
Experiment 1: Problem Statement
Objective: To develop a Recruitment System.
Automates recruitment activities, manages job vacancies, stores applicant information, schedules
interviews, tracks recruitment status and generates reports.
Result: Problem statement studied successfully.
Experiment 2: Software Requirement Specification (SRS)
Functional Requirements: Candidate Registration, Job Posting, Job Application, Interview
Scheduling, Report Generation.
Non-Functional Requirements: Security, Reliability, Scalability.
Hardware: 4GB RAM, Intel Processor.
Software: Windows, StarUML, MySQL.
Result: SRS prepared successfully.
Experiment 3: Feasibility Study
Technical, Economic, Operational and Schedule feasibility are satisfied.
Result: Project found feasible.
Experiment 4: Requirement Analysis
User Requirements: Register, Apply for Jobs, Upload Resume, Check Status.
Recruiter Requirements: Post Jobs, Review Applications, Schedule Interviews.
Benefits: Faster recruitment, Better management, Reduced paperwork.
Result: Requirements analyzed successfully.
Experiment 5: Study and Usage of CASE Tools
Tools Used: StarUML, [Link], Visual Paradigm.
Advantages: Better quality, documentation and maintenance.
Result: CASE tools studied successfully.
Experiment 6: Use Case Diagram
Objective: To identify user interactions.
Description: Shows Applicant, Recruiter and Admin actors and recruitment functions.
Result: Use Case Diagram drawn successfully.
(Paste Use Case Diagram Here)
Experiment 7: Sequence Diagram
Objective: To show recruitment workflow.
Description: Displays interactions between Applicant and System; application and interview
process.
Result: Sequence Diagram drawn successfully.
(Paste Sequence Diagram Here)
Experiment 8: Class Diagram
Objective: To represent system classes.
Description: Shows Applicant, Recruiter, Job and Application classes with relationships.
Result: Class Diagram drawn successfully.
(Paste Class Diagram Here)
Experiment 9: Data Flow Diagram (DFD)
Objective: To show movement of recruitment data.
Description: Shows flow of applicant and job information.
Result: DFD drawn successfully.
(Paste DFD Diagram Here)
Experiment 10: Testing Techniques
White Box Testing, Black Box Testing, Unit Testing, Integration Testing, Alpha Testing, Beta
Testing, Acceptance Testing.
Result: Testing techniques studied successfully.
Teacher's Signature: ___________
Student's Signature: ___________
Submitted By: ___________
Roll No.: ___________
Course: BCA Software Engineering Lab (BCAP-007)