Lab Manual

Software Engineering Lab (BTCS-407)

Continuous Assessment: 50 L T P
End Term Examination: 50 0 0 4

Objective Understand Importance of SDLC approach & various processes.

Software Development Life cycle involve multiple phases like Requirement analysis, Design,
Coding, Testing & Maintenance. In each phase certain activities are performed to deliver the
deliverables or outcome eg. From Requirement Analysis phase outcome is SRS document which
is input to the Design phase.
Project group is assigned with a project and asked to perform the complete cycle of SDLC.
Following are some instruction related to the project work,
1. Project group has to collect the required information related to the assigned system/project.
2. Project group has to design/develop the project and deliver the deliverables on the timelines
given by the Teacher/Lab Instructor.
3. On the completion of duration, each project group has to submit a project report. The
Teacher/Lab Instructor will evaluate the report.

Experiment 1-2 (Problem Statement and Role of Software)

Objective To prepare problem statement of the project assigned to you
To identify the role of the software in today’s world across a few significant domains related to
day to day life.
Background Software has made the world a global village today. The impact of software spans
across almost all aspect of human life. All organizations, Institutions and companies are
leveraging the potentials of software in automating the critical functions and eliminating
manual interventions. Software is also a predominant are for trade and export especially for
the countries like India. Domains like health care, Airlines , financial Services, Insurance ,
retails, Education, and many more have exploited software and still there a lot of the scope
for software to create impact and add values in multiple dimensions.
Experiment 3 (Software Crisis, Software Development Model)
Objective To identify the problem related to software crisis for a given scenario
To identify the suitable software development model for the given scenario.
Background In the early years of computers applications, the focus of the development
and innovation were on hardware. Software was largely views as an afterthought. Computer
Programming was an art. Programmers did not follow any disciplined or formalized approaches.
This way of doing things was adequate for a while, until the sophisticated of computer
applications outgrow. Software soon took over and more functions which were done manually.
A software houses begin to develop for widespread distribution. Software development projects
produced thousands of source program statement. With the increase in the size and complexity
of the software, following situation resulted is collectively termed as software crisis.

Experiment 4 (Requirement Development and Requirement Classification)

Objective To identify the various requirement development activities viz. elicitation, analysis,
specification and verification for the given scenarios.
To Classify the requirement into functional and non-functional requirements

Background Requirement engineering produces a specification of what a system should do. The
intention of requirement engineering is to provide a clear definition of requirement of the
systems. This phase is a very important phase because, if the customer requirements are not clearly
understood, the ambiguity can get into the other phase of the development. To avoid such
issues, requirement has to be elicited using the right elicitation techniques, to be analyzed
effectively, specified clearly and verified thoroughly. All activities are collectively termed as
requirement development activities.
Functional requirements (FRs) specify the software functionality that the developer must
build into the product to enable users accomplish their tasks, thereby satisfying the business
requirements. Non functional requirement as the name suggest, are those requirements which are
not directly concerned with the specific functions delivered by the system. Many non-functional
requirements (NFRs) related to the system as a whole rather than to individual functional
requirements. While failure to meet an individual functional may degrade the system, failure to
meet a non-functional system requirement may make whole system unusable. NFR’s are of
different types namely usability requirements, reliability requirements etc.
 Experiment 5 ((SRS) Software Requirement Specification)
Objective: To understand the SRS
To write the complete SRS document.

Experiment 6 (Cost Estimation by COCOMO model, Gantt Chart)

Objective: To estimate the cost and time by using COCOMO
To draw the Gantt chart

Experiment 7-8 (Software Design)

Objective Identify the elements and relationship by analyzing the Data Flow Diagram (DFD),
ER Diagram
Background Software Design describes how software is decomposed and organized into
components and the interfaces between those components. It also describes the components at a
level of detail that enable their construction.

Experiment 9-10 (Software Testing)

Objective: To design the test cases by apply different testing mechanism

S. No. Enrolment No Name of the Students Topic Name

1. 2013-310-002 Abdul Rahim Choudhary

2. 2013-310-003 Ahamdulla Firoj Online Chatting

3. 2013-310-004 Amaan Aslam

4. 2013-310-005 Amarjeet Singh Soie

5. 2013-310-006 Anmol Mehta Inventory Control System

6. 2013-310-007 Atif Ahmad Sayeedi

7. 2013-310-008 Babita

8. 2013-310-009 Chirag Ahuja English Hindi Translator

9. 2013-310-010 Christin Abraham Jacob

10. 2013-310-011 Deepanshu Bhatia

11. 2013-310-012 Dishant Kumar Blood Bank System

12. 2013-310-013 Faez Ahmed

13. 2013-310-014 Faizan Qudsi

14. 2013-310-015 H Badri Vishal Railway Reservation System

15. 2013-310-016 Hamza Tariq Khan

16. 2013-310-017 Haroon Iqbal

17. 2013-310-018 Heebah Saleem Hotel Management System

18. 2013-310-019 Javed Khan

19. 2013-310-020 Kapadia Idrish Saifuddin

20. 2013-310-021 Kashish Ahuja E-Ticketing

21. 2013-310-022 Manish Joshi

22. 2013-310-023 Manish Kumar Maurya

23. 2013-310-024 Md Abu Saleh Share Online Trading

24. 2013-310-025 Mohammad Murad

25. 2013-310-026 Mohammad Samran Ali

26. 2013-310-028 Mohd Anzar Hasan Resource Management System

27. 2013-310-029 Mohd Kashif Israr

28. 2013-310-030 Mohd Shameem

29. 2013-310-031 Najibullah Automatic Trailer Machine (ATM)

30. 2013-310-032 Partha Banerjee

31. 2013-310-033 Priyal Shrimali

32. 2013-310-034 Quazi Md Hammadur Rahman Student Result Management System

33. 2013-310-035 Rayam Khan

34. 2013-310-036 Romana Naaz

35. 2013-310-037 Sahil Akhtar Fast Food Billing System

36. 2013-310-038 Saif Ali

37. 2013-310-039 Salman Javed

38. 2013-310-040 Salman Khan Video Library Management System

39. 2013-310-041 Saman Raja

40. 2013-310-042 Sarim Zia Khan

41. 2013-310-043 Shagufta Saba Student Result Management System

42. 2013-310-044 Shahbaz Rahman

43. 2013-310-045 Shahnawaz Ali Choudhary

44. 2013-310-046 Shamshad Malik Automated Banking System

45. 2013-310-047 Sharequa Shams

46. 2013-310-048 Sheikh Mavin

47. 2013-310-049 Shiekh Zeeshan Airline Reservation System

48. 2013-310-050 Shubham Galhotra

49. 2013-310-051 Sonal

50. 2013-310-052 Sourabh Gupta Employee Management System

51. 2013-310-054 Yash Kumar Gogna

52. 2013-310-055 Zaid Saba

53. 2012-310-009 Ahmad Javed

54. 2012-310-010 Ahmad Seyar Library Management System