0% found this document useful (0 votes)
49 views1 page

Software Engineering Lab Syllabus

The Software Engineering Lab course (CSE 625) for B.Tech. (CSE) students focuses on practical implementation of software engineering principles, structured around a classical analysis-design-implementation framework. It includes 10 lab experiments covering feasibility studies, software documentation, project management, and various UML diagrams, totaling 20 hours of instruction. The course aims to equip students with skills in software documentation, cost estimation modeling, and the use of UML as a tool.

Uploaded by

5025linux
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
49 views1 page

Software Engineering Lab Syllabus

The Software Engineering Lab course (CSE 625) for B.Tech. (CSE) students focuses on practical implementation of software engineering principles, structured around a classical analysis-design-implementation framework. It includes 10 lab experiments covering feasibility studies, software documentation, project management, and various UML diagrams, totaling 20 hours of instruction. The course aims to equip students with skills in software documentation, cost estimation modeling, and the use of UML as a tool.

Uploaded by

5025linux
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

[Link].

(CSE) 2022-26
Annexure 2
SOFTWARE ENGINEERING LAB
Course Code: CSE 625 Credit Unit: 01
Total Hours: 20

Course Objective:
The course provides a practical implementation of the fundamentals principles of software engineering. The
organization broadly is based on the classical analysis-design-implementation framework.

SOFTWARE REQUIREMENTS: Rational Rose

Course Contents :

Lab Experiments are based on the course Software Engineering (CSE 605)

List of experiments/demonstrations:
1. Learning the concepts of Feasibility Study. (2 Hours)
2. Understanding the concepts of Software Documentation. (2 Hours)
3. Learning Project Management activities and techniques for designing of software. (2 Hours)
4. Getting familiarized with the Unified Modelling Language (UML) Environment. (2 Hours)
5. Working with the Use-case View of UML. (2 Hours)
6. Working with the Class Diagrams of UML. (2 Hours)
7. Working with the State Diagrams of UML. (2 Hours)
8. Working with the Activity Diagrams of UML. (2 Hours)
9. Working with the Collaboration Diagrams of UML. (2 Hours)
10. Study of cost estimation modelling approaches in Software Engineering. (2 Hours)

Course Outcomes:
• Ability to design the proper documentation of software product.
• Ability to implement the cost estimation modelling approaches.
• Ability to use the unified modelling language as a tool.

Examination Scheme:
IA EE
A PR Practical Major Minor
LR Viva
Based Test Experiment Experiment

5 10 15 35 15 10 10

• Note: IA –Internal Assessment, EE- External Exam, A- Attendance PR- Performance, LR – Lab
Record, V – Viva.

Text & References:


• [Link]& Yogesh singh “Software Engineering”, 2nd Ed, New Age International, 2005.
• R.S. Pressmen Software Engineering – A practitioner’s approach”, 5th Ed., McGraw Hill Int. Ed.,
2001.
• P. Jalote, “An Integrated approach to Software Engineering”, Narosa, 1991.

127

Common questions

Powered by AI

Use-case diagrams facilitate understanding by illustrating how users interact with a system, highlighting the functionalities available to different actors. They are essential in UML as they provide a high-level view of requirements and help in identifying system boundaries and interdependencies .

Collaboration diagrams advantageously show object interactions with emphasis on role descriptions and overall structure rather than sequence timing. Unlike sequence diagrams, they focus on structural organization, aiding in understanding system interconnections during object interactions .

Activity diagrams help understand workflow processes by visualizing the sequence of actions and control flow. They are vital for identifying bottlenecks and inefficiencies in processes, guiding optimization and ensuring that system behavior aligns with user requirements effectively .

Understanding feasibility studies is crucial in software engineering as it helps determine whether a project is viable, considering various constraints like technical, economic, and legal factors. It guides decision-making by assessing potential risks and returns, ensuring resources are allocated efficiently .

Studying cost estimation approaches is critical as it enables accurate prediction of resource requirements, helping to avoid budget overruns. This impacts project planning by providing realistic timelines and constraints, which in turn guides effective project execution and ensures stakeholder satisfaction .

State diagrams model the dynamic behavior by representing state changes in response to events, crucial for complex systems where states and transitions are pivotal. They enhance understanding of object lifecycle and behavior under different scenarios, forming an integral part of UML for dynamic modeling .

Mastery of UML is essential for software engineers as it provides a standardized way to visualize system architecture. UML improves design quality by enabling clear representation of functional requirements and system behavior, thus reducing ambiguities and enhancing communication among development teams .

Class diagrams are significant as they depict the static structure of a system by showing its classes, attributes, methods, and relationships. They assist in developing object-oriented systems by providing a blueprint that guides the configuration of items and logical system structure .

Learning project management activities equips software engineers with skills to plan, execute, and close projects efficiently. It involves scheduling, resource allocation, and risk management, ensuring that projects are completed on time, within budget, and meet user requirements .

Software documentation serves as a comprehensive guideline for understanding the system’s architecture and functionality. It promotes communication among stakeholders and serves as a reference for future maintenance and upgrades, thus facilitating the software engineering lifecycle from inception to deployment and beyond .

You might also like