SOFTWARE ENGINEERING LAB - MAIT

1 MAIT/CSE 1 | P a g e LAB MANUAL OF SOFTWARE ENGINEERING LAB ETCS -353 Maharaja Agrasen Institute of Technology, PSP area, Sector 22, Rohini, New Delhi 110085 ( Affiliated to Guru Gobind Singh Indraprastha University, New Delhi ) MAIT/CSE 2 | P a g e INDEX OF THE CONTENTS Introduction to the lab. ( Details of H/w & S/w to be used in the lab. ) List of Programs ( as per the syllabus prescribed by ) Format of the lab record to be prepared by the students. Steps to be followed ( for each practical ) Sample Diagram/s List/Details of the additional things.

2 ( extra programs, projects etc. ) Marking scheme MAIT/CSE 3 | P a g e INTRODUCTION TO THE LAB Requirement of the lab Hardware Requirements: Pentium 4 processor ( GHz), 128 Mb RAM, Standard keyboard n mouse, colored monitor. SOFTWARE Requirements: Rational Rose, Windows XP/2000,ms-office MAIT/CSE 4 | P a g e This lab deals with the analysis and design of a SOFTWARE problem .the tool used in a lab is rational rose .this tool is used for a object oriented design of a problem . We draw a uml diagram in a rational rose which deals with the objects and classes in a system.

3 The unified modeling language or UML is is a mostly graphical modelling language that is used to express designs. It is a standardized language in which to specify the artefacts and components of a SOFTWARE system. It is important to understand that the UML describes a notation and not a process. It does not put forth a single method or process of design, but rather is a standardized tool that can be used in a design process. The unified modeling language (UML) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of SOFTWARE systems, as well as for business modeling and other non- SOFTWARE systems. The UML represents a collection of best ENGINEERING practices that have proven successful in the modeling of large and complex The UML is a very important part of developing object oriented SOFTWARE and the SOFTWARE development process.

4 The UML uses mostly graphical notations to express the design of SOFTWARE projects. Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the SOFTWARE . Goals of UML The primary goals in the design of the UML were: 1. Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models. 2. Provide extensibility and specialization mechanisms to extend the core concepts. 3. Be independent of particular programming languages and development processes. 4. Provide a formal basis for understanding the modeling language . 5. Encourage the growth of the OO tools market. 6. Support higher-level development concepts such as collaborations, frameworks, patterns and components.

5 7. Integrate best practices. Why Use UML? As the strategic value of SOFTWARE increases for many companies, the industry looks for techniques to automate the production of SOFTWARE and to improve quality and reduce cost and time-to-market. These techniques include component technology, visual programming, patterns and frameworks. Businesses also seek techniques to manage the complexity of systems as they increase in scope and scale. In particular, they recognize the need to solve recurring architectural problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance. MAIT/CSE 5 | P a g e SOFTWARE ENGINEERING LAB Paper Code: ETCS-353 Paper: SOFTWARE ENGINEERING Lab Tool Required: Rational Rose Enterprise Edition List of Experiments: (As prescribed by ) 1.

6 Write down the problem statement for a suggested system of relevance. 2. Do requirement analysis and develop SOFTWARE Requirement Specification Sheet (SRS) for suggested system. 3. To perform the function oriented diagram: Data Flow Diagram (DFD) and Structured chart. 4. To perform the user s view analysis for the suggested system: Use case diagram. 5. To draw the structural view diagram for the system: Class diagram, object diagram. 6. To draw the behavioral view diagram : State-chart diagram, Activity diagram 7. To perform the behavioral view diagram for the suggested system : Sequence diagram, Collaboration diagram 8. To perform the implementation view diagram: Component diagram for the system. 9. To perform the environmental view diagram: Deployment diagram for the system. 10. To perform various testing using the testing tool unit testing, integration testing for a sample code of the suggested system.

7 11. 10 Perform Estimation of effort using FP Estimation for chosen system. 12. 11 To Prepare time line chart/Gantt Chart/PERT Chart for selected SOFTWARE project. Text Books: 1. Aggarwal & Yogesh Singh, SOFTWARE ENGINEERING , New Age International, 2005 2. Pankaj Jalote, An Integrated Approach to SOFTWARE ENGINEERING , Second Edition, Springer. NOTE:- At least 8 Experiments out of the list must be done in the semester. MAIT/CSE 6 | P a g e List of Practical s (As per the syllabus prescribed by University ) Choose any one project and do the following exercises for that project a. Student Result Management System b. Library management system c. Inventory control system d.

8 Accounting system e. Fast food billing system f. Bank loan system g. Blood bank system h. Railway reservation system i. Automatic teller machine j. Video library management system k. Hotel management system l. Hostel management system m. E-ticking n. Share online trading o. Hostel management system p. Resource management system q. Court case management system MAIT/CSE 7 | P a g e 1. Write the complete problem statement 2. Write the SOFTWARE requirement specification document 3. Draw the entity relationship diagram 4. Draw the data flow diagrams at level 0 and level 1 5. Draw use case diagram 6. Draw activity diagram of all use cases. 7. Draw state chart diagram of all use cases 8.

9 Draw sequence diagram of all use cases 9. Draw collaboration diagram of all use cases 10. Assign objects in sequence diagram to classes and make class diagram . MAIT/CSE 8 | P a g e Report Format (instruction for the students for the preparation of lab record ) Cover page: Name of the Lab ( size 20 , italics bold , Times New Roman ) Faculty Name: Student Name: ( 12 , Times New Roman ) Roll No.: Semester: Batch : ( 12 , Times New Roman ) College s Logo Maharaja Agrasen Institute of technology, PSP area, Sector 22, Rohini, New Delhi 110085 ( 18 bold Times New Roman ) MAIT/CSE 9 | P a g e INDEX Name of the Program Date Signature & Date Remarks MAIT/CSE 10 | P a g e EXCERCISE NO.

10 1 AIM: To prepare PROBLEM STATEMENT for any project. REQUIREMENTS: Hardware Interfaces Pentium(R) 4 CPU GHz, 128 MB RAM Screen resolution of at least 800 x 600 required for proper and complete viewing of screens. Higher resolution would not be a problem. CD ROM Driver SOFTWARE Interfaces Any window-based operating system (Windows 95/98/2000/XP/NT) WordPad or Microsoft Word THEORY: The problem statement is the initial starting point for a project. It is basically a one to three page statement that everyone on the project agrees with that describes what will be done at a high level. The problem statement is intended for a broad audience and should be written in non-technical terms. It helps the non-technical and technical personnel communicate by providing a description of a problem.