BCS651BCS651H

Software Engineering Lab

L-T-P0-0-2 Credits1 Session2024-25 TypeLab / Practical
Appears in 12 semesters · 12 branches

B.Tech Computer Science & Engineering · Sem 6 (Lab, code BCS651) · B.Tech Information Technology · Sem 6 (Lab, code BCS651) · B.Tech Artificial Intelligence & Machine Learning · Sem 6 (Lab, code BCS651) · B.Tech Artificial Intelligence & Data Science · Sem 6 (Lab, code BCS651) · B.Tech CSE (Artificial Intelligence) · Sem 6 (Lab, code BCS651) · B.Tech CSE (AI & ML) · Sem 6 (Lab, code BCS651) · B.Tech CSE (Data Science) · Sem 6 (Lab, code BCS651) · B.Tech CSE (Cyber Security) · Sem 6 (Lab, code BCS651) · B.Tech CSE (Internet of Things) · Sem 6 (Lab, code BCS651) · B.Tech Computer Science & Design · Sem 6 (Lab, code BCS651) · B.Tech Computer Science (Hindi) · Sem 6 (Lab, code BCS651H) · B.Tech Electronics & Computer Engineering · Sem 6 (Lab, code BCS651)

List of Experiments / Activities

  1. For any given case/ problem statement do the following;
  2. 1Prepare a SRS document in line with the IEEE recommended standards.
  3. 2Draw the use case diagram and specify the role of each of the actors. Also state the precondition, post condition and function of each use case.
  4. 3Draw the activity diagram.
  5. 4Identify the classes. Classify them as weak and strong classes and draw the class diagram.
  6. 5Draw the sequence diagram for any two scenarios.
  7. 6Draw the collaboration diagram.
  8. 7Draw the state chart diagram.
  9. 8Draw the component diagram.
  10. 9Perform forward engineering in java. (Model to code conversion)
  11. 10Perform reverse engineering in java. (Code to Model conversion) 11. Draw the deployment diagram.
  12. Note: The Instructor may add/delete/modify/tune experiments, wherever he/she feels in a justified manner It is also suggested that open source tools should be preferred to conduct the lab ( Open Office , Libra , Junit, Open Project , GanttProject , dotProject, AgroUML, StarUML etc. ) Software Engineering Lab (BCS-651): Mapping with Virtual Lab Name of the Lab Name of the Experiment Identifying the Requirements from Problem Statements Estimation of Project Metrics Modeling UML Use Case Diagrams and Capturing Use Case Scenarios E-R Modeling from the Problem Statements Identifying Domain Classes from the Problem Statements Statechart and Activity Modeling Modeling UML Class Diagrams and Sequence diagrams Modeling Data Flow Diagrams Estimation of Test Coverage Metrics and Structural Complexity Designing Test Suites
Course Outcomes (COs)5 outcomes

After completion of the course student will be able to:

  1. CO1Identify ambiguities, inconsistencies and incompleteness from a requirements specification and state functional and non-functional requirementK2, K4
  2. CO2Identify different actors and use cases from a given problem statement and draw use case diagram to associate use cases with different types of relationshipK3, K5
  3. CO3Draw a class diagram after identifying classes and association among themK4, K5
  4. CO4Graphically represent various UML diagrams, and associations among them and identify the logical sequence of activities undergoing in a system, and represent them pictoriallyK4, K5
  5. CO5Able to use modern engineering tools for specification, design, implementation and testingK3, K4

Note: The AKTU syllabus PDF of some branches prints this subject with small differences in the experiments (AI & ML, AI & Data Science, CSE (AI), CSE (AI & ML), CSE (Data Science), CSE (Cyber Security), CSE (IoT)). Please also check the official AKTU PDF of your branch, linked at the end of your semester page.

Official AKTU syllabus

This subject is on page 32 of the original AKTU PDF.

Official AKTU syllabus PDF ↗