OOSE Mullana Lab Manual

FORM NO.MMEC-FRM-32 C (REV.NO.00) MMEC M.M.
ENGINEERING COLLEGE MULLANA
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE. : Object Oriented Software Engineering LABORATORY MANUAL NO: MMEC-WI-IT-412 ISSUE NO.00 ISSUE DATE: NA LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01
DISTRIBUTION LIST S.No. 1 2 3 4 5 6 Dr. Manpreet Singh Nidhi Manocha Mr. Purushotam Mr. Janak Raj Sharma Mr. Janak Raj Sharma Mr. Ashish Oberoi LIBRARY I/C LIBRARY I/C MANAGEMENT REPRESENTATIVE 04 05 06 NAME OF THE RECIPIENTS DESIGNATION H.O.D. (IT DEPT.) LAB I/C LAB. TECH. CONTROL COPY NO. 01 02 03 SIGNATURE ON RECEIPT
STATUS
FORM NO.MMEC-FRM-32 A (REV.NO. 00)
1 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
MMEC
M.M. ENGINEERING COLLEGE MULLANA
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : OOSE LABORATORY MANUAL NO: MMEC-WI-IT-412 ISSUE DATE: NA LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 01
MASTER LIST OF EXPERIMENT
S no 1
Experiment MMEC-WIIT-412 IT-412-01
Experiment Description To Obtain a deeper understanding of software process models and software processes. Gain a deeper understanding of the Software Requirement Specification phase and the Software Requirement Specification (SRS). To Study the benefits of visual modeling. To Learn use case diagrams: discovering actors and discovering use cases. To Data model: entity-relationship diagram (ERD) & to make Functional model: data flow diagram (DFD) . How to document use cases in detail & Deeper understanding of UML activity diagrams. To Learn the object-oriented analysis phase by understanding the methods of class elicitation and finding the classes in an object-oriented system. To Get familiar with sequence & collaboration diagrams & Better understanding of the interaction diagrams. To find the relationships between classes to create UML class diagram & understanding of software design and the software design document (SDD). Deeper understanding of UML state diagrams (STD) using Rational Rose. transition
Rev no 00
Rev date
Page no 03
IT-412-02
00
05
IT-412-03
00
07
4 5
IT-412-04 IT-412-05
00 00
10 12
IT-412-06
00
14
IT-412-07
00
15
IT-412-08
00
17
9 10 11 12
IT-412-09 IT-412-10 IT-412-11 IT-412-12
00 00 00 00
19 21
To be familiar with the implementation diagrams: component and deployment diagrams.
write a program to implement hyperlinking using netbeans. To create login window in NetBeans
32 35
FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : To Obtain a deeper understanding of software process models and software processes. EXPERIMENT NO. . :MMEC-WI- IT-412-01 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 02
Objectives Obtain a deeper understanding of software process models and software processes Gain understanding of project management. Learn how to prepare project plans. Learn about project risks. Theory IEEE defined a software process as: a set of activities, practices and transformations that people use to develop and maintain software and the associated products, e.g., project plans, design documents, code, test cases and user manual. Following the software process will stabilize the development lifecycle and make the software more manageable and predictable. It will also reduce software development risk and help to organize the work products that need to be produced during a software development project. A well-managed process will produce high quality products on time and under budget. So following a mature software process is a key determinant to the success of a software project. A number of software processes are available. However, no single software process works well for every project. Each process works best in certain environments Examples of the available software process models include: the Waterfall model (the Linear model), the evolutionary development, the formal systems development, and reuse-based (component-based) development. Other process models support iteration; these include: the Incremental model, the Spiral model, and Extreme Programming. Project management is the process of planning and controlling the development of a system within a specified timeframe at a minimum cost with the right functionality. 1.1 Project Work Plan Prepare a list of all tasks in the work breakdown structure, plus: Duration of task. Current task status. Task dependencies. Key milestone dates. 1.2 Tracking Progress Gantt Chart: o Bar chart format. o Useful to monitor project status at any point in time. PERT Chart:
o o
Flowchart format. Illustrate task dependencies and critical path.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : To Obtain a deeper understanding of software process models and software processes. EXPERIMENT NO. . :MMEC-WI- IT-412-01 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 02 of 02
1.3 Risk Management Risk management is concerned with identifying risks and drawing up plans to minimize their effect on a project. A risk is a probability that some adverse circumstance will occur. Project risks which affect schedule or resources. Product risks which affect the quality or performance of the software being developed. Business risks which affect the organization developing the software. 1.4 Risk Management Process Risk identification: identify project, product and business risks. Risk analysis: assess the likelihood and consequences of these risks. Risk planning: draw up plans to avoid or minimize the effects of the risk. Risk monitoring: monitor the risks throughout the project.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : Gain a deeper understanding of the Software Requirement Specification phase and the Software Requirement Specification (SRS). EXPERIMENT NO. . :MMEC-WI-IT-412-02 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE :01 of 03 Objectives Gain a deeper understanding of the Software Requirement Specification phase and the Software Requirement Specification (SRS). Learn how to write requirements and specifications. Gain exposure to requirements management using RequisitePro. Work plan Review of the requirements engineering process. Write requirements and specifications. Requisite Pro tutorial. Software Requirement Specification (SRS). 2.1 Theory A requirement is a statement of a behavior or attribute that a system must possess for the system to be acceptable to a stakeholder. Software Requirement Specification (SRS) is a document that describes the requirements of a computer system from the user's point of view. An SRS document specifies: The required behavior of a system in terms of: input data, required processing, output data, operational scenarios and interfaces. The attributes of a system including: performance, security, maintainability, reliability, availability, safety requirements and design constraints. Requirements management is a systematic approach to eliciting, organizing and documenting the requirements of a system. It is a process that establishes and maintains agreement between the customer and the project team on the changing requirements of a system. Requirements management is important because, by organizing and tracking the requirements and managing the requirement changes, you improve the chances of completing the project on time and under budget. Poor change management is a key cause of project failure. 2.2 Requirements Engineering Process Requirements engineering process consists of four phases: Requirements elicitation: getting the customers to state exactly what the requirements are. Requirements analysis: making qualitative judgments and checking for consistency and feasibility of requirements. Requirements validation: demonstrating that the requirements define the system that the customer really wants. Requirements management: the process of managing changing requirements during the requirements engineering process and system development, and identifying missing and extra requirements.
2.3 Writing Requirements

Requirements always need to be correct, unambiguous, complete, consistent, and testable.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET
EXPERIMENT TITLE:Gain a deeper understanding of the Software Requirement Specification phase & the Software Requirement Specification (SRS).
EXPERIMENT NO. . :MMEC-WI-IT-412-02 REV. DATE : NA LABORATORY : CENTER C2 2.3.1 ISSUE NO. 00 ISSUE DATE: NA DEPTT.: INFORMATION TECHNOLOGY SEMESTER : VIII PAGE : 02 of 02
Recommendations When Writing Requirements Never assume: others do now know what you have in mind. Use meaningful words; avoid words like: process, manage, perform, handle, and support. State requirements not features: o Feature: general, tested only for existence. o Requirement: specific, testable, measurable. Avoid: o Conjunctions: ask yourself whether the requirement should it be split into two requirements. o Conditionals: if, else, but, except, although. o Possibilities: may, might, probably, usually.
2.4 Writing Specifications Specification is a description of operations and attributes of a system. It can be a document, set of documents, a database of design information, a prototype, diagrams or any combination of these things. Specifications are different from requirements: specifications are sufficiently complete not only what stakeholders say they want; usually, they have no conflicts; they describe the system as it will be built and resolve any conflicting requirements. Creating specifications is important. However, you may not create specifications if: You are using a very incremental development process (small changes). You are building research or proof of concept projects. You rebuilding very small projects. It is not cheaper or faster than building the product.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : Write 8085 program to add two 8 bit no with carry & subtract two 8 bit nos with borrow. EXPERIMENT NO. . :MMEC-WI-IT-412-02 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 03 2.5 Software Requirement Specification (SRS) Remember that there is no Perfect SRS. However, SRS should be: Correct: each requirement represents something required by the target system. Unambiguous: every requirement in SRS has only one interpretation Complete: everything the target system should do is included in SRS (no sections are marked TBD-to be determined). Verifiable: there exists some finite process with which a person/machine can check that the actual as-built software product meets the requirements. Consistent in behavior and terms. Understandable by customers. Modifiable: changes can be made easily, completely and consistently. Design independent: doesn't imply specific software architecture or algorithm. Concise: shorter is better. Organized: requirements in SRS are easy to locate; related requirements are together. Traceable: each requirement is able to be referenced for later use (by the using paragraph numbers, one requirement in each paragraph, or by using convention for indication requirements) 2.6 CASE Tools RequisitePro is a powerful, easy-to-use requirements management tool that helps teams manage project requirements comprehensively, promotes communication and collaboration among team members, and reduces project risk. It thereby increases the chances of delivering a product that the client wants and does so in a timely manner. RequisitePro offers the power of a database and Microsoft Word and is integrated with other Rational Suite products. 2.7 Exercises a. Perform each of the following tasks using RequisitePro: o Create a new project. o Create a new package. o Create and add some requirements within RequisitePro. o Create a requirement document. o Create a new view.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : Write 8085 program to add two 8 bit no with carry & subtract two 8 bit nos with borrow. EXPERIMENT NO. . :MMEC-WI-IT-412-03 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 03 Objectives Study the benefits of visual modeling. Learn use case diagrams: discovering actors and discovering use cases. Practice use cases diagrams using Rational Rose Work plan Visual modeling. Introduction to UML. Introduction to visual modeling with UML. Use case diagrams: discovering actors and use cases. 3.1 Theory Visual Modeling is a way of thinking about problems using models organized around real-world ideas. Models are useful for understanding problems, communicating with everyone involved with the project (customers, domain experts, analysts, designers, etc.), modeling enterprises, preparing documentation, and designing programs and databases 3.1.1. Visual Modeling Capture the structure and behavior of architectures and components. Show how the elements of the system fit together. Hide or expose details appropriate for the task. Maintain consistency between a design and its implementation. Promote unambiguous communication.
3.1.2 What is UML? The UML is the standard language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. UML can be used with all processes throughout the development life cycle and across different implementation technologies. 3.1.3 History of UML The UML is an attempt to standardize the artifacts of analysis and design: semantic models, syntactic notation and diagrams. The first public draft (version 0.8) was introduced in October 1995. Feedback from the public and Ivar Jacobson's input were included in the next two versions (0.9 in July 1996 and 0.91 in October 1996). Version 1.0 was presented to the Object Management Group (OMG) for standardization in July 1997. Additional enhancements were incorporated into the 1.1 version of UML, which was presented to the OMG in September 1997. In November 1997, the UML was adopted as the standard modeling language by the OMG. 3.1 Putting UML into Work: Use Case Diagram The behavior of the system under development (i.e. what functionality must be provided by the system) is documented in a use case model that illustrates the system's intended functions (use cases), its surroundings (actors), and relationships between the use cases and actors (use case diagrams).
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : Write 8085 program to add two 8 bit no with carry & subtract two 8 bit nos with borrow. EXPERIMENT NO. . :MMEC-WI-IT-412-03 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 02 of 03
. 3.1.2 Actors Are NOT part of the system they represent anyone or anything that must interact with the system. Only input information to the system. Only receive information from the system. Both input to and receive information from the system. Represented in UML as a stickman. 3.1.3 Use Case A sequence of transactions performed by a system that yields a measurable result of values for a particular actor A use case typically represents a major piece of functionality that is complete from beginning to end. A use case must deliver something of value to an actor. 3.1.4 Use Case Relationships Between actor and use case. Association / Communication. Arrow can be in either or both directions; arrow indicates communication. Between use cases (generalization): Uses Where multiple use cases share pieces of same functionality. Extends Optional behavior. Behavior only runs under certain conditions (such as alarm).
who
initiates
3.2 CASE Tools The Rational Rose product family is designed to provide the software developer with a complete set of visual modeling tools for development of robust, efficient solutions to real business needs in the client/server, distributed enterprise and real-time systems environments. Rational Rose products share a common universal standard, making modeling accessible to nonprogrammers wanting to model business processes as well as to programmers modeling applications logic.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : To multiply two 8 bit nos by using rotation method & repeat addition in 8085. EXPERIMENT NO. . :MMEC-WI-IT-412-03 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 03
3.4 Exercises: Read carefully the following problem statement We are after a system that controls a recycling machine for returnable bottles and cans. The machine will allow a customer to return bottles or cans on the same occasion. When the customer returns an item, the system will check what type has been returned. The system will register how many items each customer returns and, when the customer asks for a receipt, the system will print out what he deposited, the value of the returned items and the total return sum that will be paid to the customer. The system is also be used by an operator. The operator wants to know how many items of each type have been returned during the day. At the end of the day, the operator asks for a printout of the total number of items that have been deposited in the machine on that particular day. The operator should also be able to change information in the system, such as the deposit values of the items. If something is amiss, for example if a can gets stuck or if the receipt roll is finished, the operator will be called by a special alarm signal. After reading the above problem statement, find: 1. Actors 2. Use cases with each actor 3. Find extended or uses use cases (if applicable) 4. Finally : draw the main use case diagram:
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE: To Data model: entity-relationship diagram (ERD) & to make Functional model: data flow diagram (DFD) . EXPERIMENT NO. . :MMEC-WI-IT-412-04 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 02 of 02
Objective: Deeper understanding of System modeling: Data model: entity-relationship diagram (ERD). Functional model: data flow diagram (DFD). Work plan : System analysis model elements: Data model: entity-relationship diagram (ERD) Functional model: data flow diagram (DFD) 4.1 Theory Modeling consists of building an abstraction of reality. These abstractions are simplifications because they ignore irrelevant details and they only represent the relevant details (what is relevant or irrelevant depends on the purpose of the model). Why Model Software? Software is getting larger, not smaller; for example, Windows XP has more than 40 million lines of code. A single programmer cannot manage this amount of code in its entirety. Code is often not directly understandable by developers who did not participate in the development; thus, we need simpler representations for complex systems (modeling is a mean for dealing with complexity). A wide variety of models have been in use within various engineering disciplines for a long time. In software engineering a number of modeling methods are also available. 4.2 Analysis Model Objectives To describe what the customer requires. To establish a basis for the creation of a software design. To define a set of requirements that can be validated once the software is built. 4.2.1 The Elements of the Analysis Model The generic analysis model consists of: An entity-relationship diagram (data model). A data flow diagram (functional model). A state transition diagram (behavioral model). NOTE: state transition diagram will be covered in lab 11. 4.3 Entity Relationship Diagram An entity relationship diagram (ERD) is one means of representing the objects and their relationships in the data model for a software product. Entity Relationship diagram notation: Entity Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh Relationship
13
To create an ERD you need to: Define objects by underlining all nouns in the written statement of scope: producers/consumers of data, places where data are stored, and composite data items. Define operations by double underlining all active verbs: processes relevant to the application and data transformations. Consider other services that will be required by the objects. Then you need to define the relationship which indicates connectedness: a "fact" that must be "remembered" by the system and cannot be or is not computed or derived mechanically.
4.4 Data Flow Diagram A data flow data diagram is one means of representing the functional model of a software product. DFDs do not represent program logic like flowcharts do. Data flow diagram notation: External entity
Process
Data flow Control flow
Data store To create a DFD you need to: Review ERD to isolate data objects and grammatical parse to determine operations. Determine external entities (producers and consumers of data). Create a level 0 DFD Context Diagram (one single process). Balance the flow to maintain data flow continuity. Develop a level 1 DFD; use a 1:5 (approx.) expansion ratio. Data Flow Diagram Guidelines: All icons must be labeled with meaningful names. 14 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
Always show external entities at level 0. Always label data flow arrows. Do not represent procedural logic. Each bubble is refined until it does just one thing.
4.5 CASE Tools You can use MS word to create your ERD and DFD since we do not have a license for a case tool that supports these diagrams.
4.6 Exercises a. Create an ERD for an airline reservation system. b. Create a DFD for: i. Student Registration System. ii. (a + b) * ( c + a * d)
Flowchart : repeated addition:
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE: How to document use cases in detail & Deeper understanding of UML activity diagrams. EXPERIMENT NO. . :MMEC-WI-IT-412-05 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 02
Objectives Study how to document use cases in detail. Know about scenarios (flow of events) and its importance. Deeper understanding of UML activity diagrams. Practicing flow of events and activity diagrams using Rational Rose. Work plan Writing flow of events. Flow of events template and example. Activity diagrams. Examples. 5.1 Theory Each use case is documented with a flow of events. The flow of events for a use case is a description of the events needed to accomplish the required behavior of the use case. Activity diagrams may also be created at this stage in the life cycle. These diagrams represent the dynamics of the system. They are flow charts that are used to show the workflow of a system; that is, they show the flow of control from one activity to another in the system, 5.1.1 Flow of Events A description of events required to accomplish the behavior of the use case, that: Show WHAT the system should do, not HOW the system does it. Written in the language of the domain, not in terms of implementation. Written from an actor point of view. A flow of events document is created for each use case: Actors are examined to determine how they interact with the system. Break down into the most atomic actions possible.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE: Write a program to divide two 8 bit nos using repeated subtraction method in 8085. EXPERIMENT NO. . :MMEC-WI-IT-412-05 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 02 of 02
5.1 Contents of Flow of Events When and how the use case starts and ends. What interaction the use case has with the actors. What data is needed by the use case. The normal sequence of events for the use case. The description of any alternate or exceptional flows. 5.2 Template for the flow of events document Each project should use a standard template for the creation of the flow of events document. The following template seems to be useful. X Flow of events for the <name> use case X.1 Preconditions X.2 Main flow X.3 Sub-flows (if applicable) X.4 Alternative flows where X is a number from 1 to the number of use cases. A sample completed flow of events document for the Select Courses to Teach use case follows. 5.3 Flow of Events for the Select Courses to Teach Use Case Preconditions Create course offerings sub-flow of the maintain course information use case must execute before this use case begins. Main Flow This use case begins when the professor logs onto the registration system and enters his/her password. The system verifies that the password is valid (E-1) and prompts the professor to select the current semester or a future semester (E-2). The professor enters the desired semester. The system prompts the Professor to select the desired activity: ADD, DELETE, REVIEW, PRINT, or QUIT.
If the activity selected is ADD, the S-1: add a course offering sub-flow is performed. If the activity selected is DELETE, the S-2: delete a course offering sub-flow is performed. If the activity selected is REVIEW, the S-3: review schedule sub-flow is performed. If the activity selected is PRINT, the S-4: print a schedule sub-flow is performed. If the activity selected is QUIT, the use case ends.
Sub-flows S-1: Add a Course Offering: The system displays the course screen containing a field for a course name and number. The professor enters the name and number of a course (E-3). The system displays the course offerings for the entered course (E-4). The professor selects a course offering. The system links the professor to the selected course offering (E-5). The use case then begins again.
S-2: Delete a Course Offering: The system displays the course offering screen containing a field for a course offering name and number. The professor enters the name and number of a course offering (E-6). The system removes the link to the professor (E-7). The use case then begins again. S-3: Review a Schedule: The system retrieves (E-8) and displays the following information for all course offerings for which the professor is assigned: course name, course number, course offering number, days of the week, time, and location. When the professor indicates that he or she is through reviewing, the use case begins again. S-4: Print a Schedule The system prints the professor schedule (E-9). The use case begins again. 5.4 Alternative Flows E-1: An invalid professor ID number is entered. The user can re-enter a professor ID number or terminate the use case. E-2: An invalid semester is entered. The user can re-enter the semester or terminate the use case. E-3: An invalid course name/number is entered. The user can re-enter a valid name/number combination or terminate the use case. 19 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
E-4: Course offerings cannot be displayed. The user is informed that this option is not available at the current time. The use case begins again. E-5: A link between the professor and the course offering cannot be created. The information is saved and the system will create the link at a later time. The use case continues. E-6: An invalid course offering name/number is entered. The user can re-enter a valid course offering name/number combination or terminate the use case. E-7: A link between the professor and the course offering cannot be removed. The information is saved and the system will remove the link at a later time. The use case continues. E-8: The system cannot retrieve schedule information. The use case then begins again. E-9: The schedule cannot be printed. The user is informed that this option is not available at the current time. The use case begins again. Use case flow of events documents are entered and maintained in documents external to Rational Rose. The documents are linked to the use case. 5.5 Activity Diagrams Activity diagrams are flow charts that are used to show the workflow of a system. They also: Represent the dynamics of the system. Show the flow of control from activity to activity in the system. Show what activities can be done in parallel, and any alternate paths through the flow. Activity diagrams may be created to represent the flow across use cases or they may be created to represent the flow within a particular use case. Later in the life cycle, activity diagrams may be created to show the workflow for an operation. 5.5.1 Activity Diagram Notation Activities- performance of some behavior in the workflow. Transition- passing the flow of control from activity to activity. Decision- show where the flow of control branches based on a decision point: o Guard condition is used to determine which path from the decision point is taken. Synchronization-what activities are done concurrently? What activities must be completed before processing may continue (join).
5.6 CASE Tools Rational Rose (introduced in lab 3). Exercises 1. Take two of the use cases from recycling machine problem (Lab 3) and write flow of events for those. You should work in groups of three to solve this problem. 2. Practice activity diagram from the example in PPT (Lab5) for course catalog creation.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : To Learn the object-oriented analysis phase by understanding the methods of class elicitation and finding the classes in an object-oriented system. EXPERIMENT NO. . :MMEC-WI-IT-412-07 REV. DATE : NA LABORATORY : CENTER C2 ISSUE NO. 00 ISSUE DATE: NA DEPTT.: INFORMATION TECHNOLOGY SEMESTER : VIII PAGE : 01 of 02
Objective Learn the object-oriented analysis phase by understanding the methods of class elicitation and finding the classes in an object-oriented system Work plan Object-Oriented concepts Discovering classes approaches: noun phrase approach, common class patterns, use case driven method, CRC (Class-Responsibility-Collaboration) and mixed approach. Examples. 6.1 Theory Classes: a description of a group of objects with common properties (attributes), common behavior (operations), common relationships to other objects and common semantics. 6.1.1 Object-Oriented Concepts Attribute: the basic data of the class. Method (operation): an executable procedure that is encapsulated in a class and is designed to operate on one or more data attributes that are defined as part of the class. Object: when specific values are assigned to all the resources defined in a class, the result is an instance of that class. Any instance of any class is called an object.
6.1.2 Discovering Classes Discovering and defining classes to describe the structure of a computerized system is not an easy task. When the problem domain is new or unfamiliar to the software developers it can be difficult to discover classes; a cookbook for finding classes does not exist. 6.1.3 Classes Categories Classes are divided into three categories: Entity: models information and associated behavior that is long-lived, independent of the surrounding, application independent, and accomplishes some responsibility Boundary: handles the communication between the system surroundings and the inside of the system, provides interface, and facilitates communication with other systems. Control: model sequencing behavior specific to one or more use cases. Control classes 21 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
coordinate the events needed to realize the behavior specified in the use case, and they are responsible for the flow of events in the use case. 6.2 Discovering Classes Approaches Methods of discovering classes: 6.2.1 Noun Phrase Approach: Examine the requirements and underline each noun. Each noun is a candidate class; divide the list of candidate classes into: Relevant classes: part of the application domain; occur frequently in requirements. Irrelevant classes: outside of application domain Fuzzy classes: unable to be declared relevant with confidence; require additional analysis 6.2.2 Common Class Patterns: Derives candidate classes from the classification theory of objects; candidate classes and objects come from one of the following sources: Tangible things: e.g. buildings, cars. Roles: e.g. teachers, students. Events: things that happen at a given date and time, or as steps in an ordered sequence: e.g. landing, request, interrupt. Interactions: e.g. meeting, discussion. Sources, facilities: e.g. departments. Other systems: external systems with which the application interacts. Concept class: a notion shared by a large community. Organization class: a collection or group within the domain. People class: roles people can play. Places class: a physical location relevant to the system.
6.3 Use Case Driven Method: The scenarios - use cases that are fundamental to the system operation are enumerated. Going over each scenario leads to the identification of the objects, the responsibilities of each object, and how these objects collaborate with other objects. 6.3.1 CRC (Class-Responsibility-Collaboration): Used primarily as a brainstorming tool for analysis and design. CRC identifies classes by analyzing how objects collaborate to perform business functions (use cases). A CRC card contains: name of the class, responsibilities of the class and collaborators of the class. Record name of class at the top; record responsibilities down the left-hand side; record other classes (collaborators) that may be required to fulfill each responsibility on the righthand side. CRC cards are effective at analyzing scenarios; they force you to be concise and clear; they are cheap, portable and readily available. 6.3.2 Mixed Approach: A mix of these approaches can be used, one possible scenario is: Use CRC for brainstorming. Identify the initial classes by domain knowledge. Use common class patterns approach to guide the identification of the classes. 22 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : To Get familiar with sequence & collaboration diagrams & Better understanding of the interaction diagrams. EXPERIMENT NO. . :MMEC-WI-IT-412-07 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 02 of 02
Objectives Better understanding of the interaction diagrams. Get familiar with sequence & collaboration diagrams. Practice drawing the interaction diagrams using Rational Rose. Work plan Interaction diagrams: o Sequence diagrams o Collaboration diagrams 7.1 Theory Interaction diagrams describe how groups of objects collaborate in some behavior. An interaction diagram typically captures the behavior of a single use case. Interaction diagrams do not capture the complete behavior, only typical scenarios. 7.1.1 Analyzing a Systems Behavior UML offers two diagrams to model the dynamics of the system: sequence and collaboration diagrams. These diagrams show the interactions between objects. 7.1.2 Sequence Diagrams Sequence diagrams are a graphical way to illustrate a scenario: They are called sequence diagrams because they show the sequence of message passing between objects. Another big advantage of these diagrams is that they show when the objects are created and when they are destructed. They also show whether messages are synchronous or asynchronous 7.2 Creating Sequence Diagrams You must know the scenario you want to model before diagramming sequence diagrams. After that specify the classes involved in that scenario. List the involved objects in the scenario horizontally on the top of the page. Drop a dotted line beneath every object. They are called lifelines. The scenario should start by a message pass from the first object. You must know how to place the objects so that the sequence is clear. You may start the scenario by an actor. Timing is represented vertically downward. Arrows between life lines represents message passing. Horizontal arrows may pass through the lifeline of another object, but must stop at some other object. You may add constraints to these horizontal arrows. Objects may send messages to themselves. Long, narrow rectangles can be placed over the lifeline of objects to show when the object is active. These rectangles are called activation lines. 7.3 Collaboration Diagrams 24 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
They are the same as sequence diagrams but without a time axis: Their message arrows are numbered to show the sequence of message sending. They are less complex and less descriptive than sequence diagrams. These diagrams are very useful during design because you can figure out how objects communicate with each other. 7.3.1 Notes Always keep your diagrams simple. For IF... then ... else scenarios, you may draw separate sequence diagrams for the different branches of the if statement. You may even hide them, (at least during the analysis phase) and document them by the text description accompanying the sequence diagrams.
7.4 CASE Tools Rational Rose (introduced in lab 5). 7.5 Exercises We all have used an elevator. The following steps describe the scenario of what happens at the elevator door from outside. 1. The passenger presses the button of either up or down depending on where he wants to go. 2. Then he will see that the button he pressed is illuminated. 3. The elevator is now moving to his floor. 4. When the elevator reached his floor it stops. 5. Now the button which was illuminated now off. 6. The door opens and the passenger enters. 7. The door closes. The objects: 3. Passenger (he is the actor). 4. Floor button (this is the interface class, the actor interacts with this object). 5. Elevator controller (this the control class, which coordinates the activities of the scenario). 6. Elevator (the entity class, which represents the machine itself which moves up and down). 7. Door (another entity class, which represents the door which opens and closes). Draw a sequence diagram for the above scenario.
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE :To find the relationships between classes to create UML class diagram & understanding of software design and the software design document (SDD EXPERIMENT NO. . :MMEC-WI- IT-412-08 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 02
Objectives Deeper understanding of software design and the software design document (SDD). Learn how to find the relationships between classes to create UML class diagram 1. Work plan Software design concepts and principals. Software architecture. Specifying the attributes and the operations and finding the relationships between classes. Creating UML class diagram. Software design document. 8.1 Theory The purpose of software design is to produce a workable (implementable) solution to a given problem. David Budgen in Software Design: An Introduction. 8.1.1 The Design Process Software design is an iterative process that is traceable to the software requirements analysis process. Many software projects iterate through the analysis and design phases several times. Pure separation of analysis and design may not always be possible. 8.1.2 Design Concepts The design should be based on requirements specification. The design should be documented (so that it supports implementation, verification, and maintenance). The design should use abstraction (to reduce complexity and to hide unnecessary detail). The design should be modular (to support abstraction, verification, maintenance, and division of labor). The design should be assessed for quality as it is being created, not after the fact. Design should produce modules that exhibit independent functional characteristics. Design should support verification and maintenance.
8.1.3 Software Architecture Software architecture is a description of the subsystems and components of a software system and the relationships between them. You need to develop an architectural model to enable everyone to better understand the system, to allow people to work on individual pieces of the system in isolation, to prepare for extension of the system and to facilitate reuse and reusability. 8.2 Describing an Architecture Using UML All UML diagrams can be useful to describe aspects of the architectural model. Four UML diagrams are particularly suitable for architecture modeling: Package diagrams Subsystem diagrams 26 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
Component diagrams Deployment diagrams
8.3 Specifying Classes Each class is given a name, and then you need to specify: Attributes: initially those that capture interesting object states. Attributes can be public, protected, private or friendly/package. Operations: can be delayed till later analysis stages or even till design. Operations also can be public, protected, private or friendly/package. Object-Relationships: o Associations: denote relationships between classes. o An aggregation: a special case of association denoting a consists of hierarchy. o Composition: a strong form of aggregation where components cannot exist without the aggregate. o Generalization relationships: denote inheritance between classes. This will build the class diagram, which is a graphical representation of the classes (including their attributes and operations) and their relationship with other classes. 8.4 CASE Tools Rational Rose (introduced in lab 7). 8.5 Exercises Refer to Lab 8 exercises; assume that the Video Store needs to know if a video tape is a brand new tape or it was already taped over (this can be captured by an attribute is_taped_over); assume also that the storage capacity of a video disk allows holding multiple versions of the same movie, each in a different language or with different endings. Use the identified classes from Lab 8 and find their attributes, operations and the relationships between the classes (build the UML diagram).
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : Deeper understanding of UML state transition diagrams (STD) using Rational Rose EXPERIMENT NO. . :MMEC-WI- IT-412-09 ISSUE NO. 00 ISSUE DATE: NA REV. DATE : NA DEPTT.: INFORMATION TECHNOLOGY LABORATORY : CENTER C2 SEMESTER : VIII PAGE : 01 of 02
Objectives Deeper understanding of UML state transition diagrams (STD). Practicing using Rational Rose. Work plan UML state diagrams. UML state diagram notation UML state details Examples 9.1 Theory Mainly, we use interaction diagrams to study and model the behavior of objects in our system. Sometimes, we need to study the behavior of a specific object that shows complex behavior to better understand its dynamics. For that sake, UML provides state transition diagrams used to model the behavior of objects of complex behavior. In this Lab, UML state transition diagrams will be introduced. We will study their notation and how can we model them using Rational Rose. 9.2 UML State Diagrams State diagrams show how one specific object changes state as it receives and processes messages: Since they are very specific, they are used for analyzing very specific situations if we compare them with other diagrams. A state refers to the set of values that describe an object at a specific moment in time. As messages are received, the operations associated with the objects parent class are invoked to deal with the messages. These messages change the values of these attributes. There is no need to prepare a state diagram for every class you have in the system. 9.2.1 Creating State Transition Diagrams States are represented by rectangles with rounded corners with an attribute name with a values associated with it. The name of the state is placed within the box. Events are shown by arrows. An event occurs when at an instant in time when a value is changed. A message is data passed from one object to another. The name of a state usually refers to the name of the attribute and the values associated to it. Example, a student object may receive a message to change its name. The state of that object changes from the first name state to the new state name. The name of the state is placed in the top compartment. State variables are placed in the next compartment. The operations associated with the state are listed in the lowest compartment of the state box. In the operations part, we usually use one of the following reserved words: o Entry: a specific action performed on the entry to the state. o Do: an ongoing action performed while in the state. 28 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
o On: a specific action performed while in the state. o Exit: a specific action performed on exiting the state. There are two special states added to the state transition diagram- start state and end state. Notation of start state is a solid black circle and for the end state a bulls eye is used.
9.3 State Transition Details A state transition may have an action and/or guard condition associated with it and it may also trigger an event. An action is the behavior that occurs when the state transition occurs. An event is a message that is sent to another object in the system. A guard condition is a Boolean expression of attribute values that allows a state transition only if the condition is true. Both actions and guards are behaviors of the object and typically become operations. Also they are usually private operations (used by the object itself) Actions that accompany all state transitions into a state may be placed as an entry action within the state. Actions that accompany all state transitions out of a state may be placed as exit actions within the state A behavior that occurs within the state is called an activity. An activity starts when the state is entered and either completes or is interrupted by an outgoing state transition. A behavior may be an action, or it may be an event sent to another object. This behavior is mapped to operations on the object. State transition diagram notation:
State [entry: ] [do: ] [exit:] Event causing transition Action that occurs New State [entry:] [do: ] [exit:] Approved by : Dr. Manpreet Singh
29
Prepared By: Nidhi Mnaocha
9.4 CASE Tools Rational Rose (introduced in Lab 5). 9.5 Exercises Here is what happens in a microwave oven: 1. The oven is initially in an idle state with door open, where the light is turned on. 2. When the door is closed it is now in idle with door closed, but the light is turned off. 3. If a button is pressed, then it moves to initial cooking stage, where the timer is set and lights are on, and heating starts 4. At any moment the door may be opened, the cooking is interrupted, the timer is cleared, and heating stops. 5. Also while cooking, another button can be pushed and extended cooking state starts, where the timer gets more minutes. At any moment door can be opened here also. 6. If the time times out, then cooking is complete, heating stops, lights are off, and it sounds a beep. 7. When the door is open, again the oven is in idle state with the door open. Draw a state transition diagram for the microwave oven.
FORM NO.MMEC-FRM-32 B (REV.NO.00)
MMEC
M.M. ENGINEERING COLLEGE MULLANA
LABORATORY MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET EXPERIMENT TITLE : To be familiar with the implementation diagrams: component and deployment diagrams. EXPERIMENT NO. . :MMEC-WI- IT-412-09 REV. DATE : NA LABORATORY : CENTER C2 ISSUE NO. 00 ISSUE DATE: NA DEPTT.: INFORMATION TECHNOLOGY SEMESTER : VIII PAGE : 02 of 02
Objectives Become familiar with the implementation diagrams: component and deployment diagrams. Practice using Rational Rose Work plan Implementation diagrams: component and deployment diagrams. Examples. 10.1 Theory Implementation diagrams capture design information. The main implementation diagrams in UML are: component and deployment diagrams. In this Lab we will study these diagrams and their notation. 10.1.1 UML Implementation Diagrams The main implementation diagrams we have in UML are: component diagrams and deployment diagrams. These diagrams are high level diagrams in comparison with old diagrams you have already learned. 10.1.2 UML Component Diagram Component diagrams capture the physical structure of the implementation. Remember always that when you talk about components, you are talking about the physical models of code. You can name them and show dependency between different components using arrows. A component diagram shows relationships between component packages and components. Each component diagram provides a physical view of the current model. Component diagrams contain icons representing: o Component packages. o Components. o Main programs. o Packages. o Subprograms. o Tasks. o Dependencies. 10.2 Deployment Diagrams A deployment diagram shows processors, devices and connections. Each model contains a single 31 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh
deployment diagram which shows the connections between its processors and devices, and the allocation of its processes to processors. 10.2.1 Deployment Diagrams: Processor A processor is a hardware component capable of executing programs. A processor is given a name and you should specify the processes that will run on that processor. You can also specify the scheduling of these processes on that processor. Types of scheduling are: o Pre-emptive: a higher priority process may take the process from lower priority one. o Non-preemptive: a process will own the processor until it finishes o Cyclic: control passes from one process to another. o Executive: an algorithm controls the scheduling of the processes o Manual: scheduling buy the user. 10.2.2 Deployment Diagrams: Device A device is a hardware component with no computing power. Each device must have a name. Device names can be generic, such as modem or terminal. 10.2.3 Deployment diagrams: Connection A connection represents some type of hardware coupling between two entities. An entity is either a processor or a device. The hardware coupling can be direct, such as an RS232 cable, or indirect, such as satellite-to-ground communication. Connections are usually bi-directional. 10.3 CASE Tools Rational Rose (introduced in Lab 5). 10.4 Exercises Think about any system and its components and draw deployment and component diagrams.
LABORATORY MANUAL
EXPERIMENT TITLE: write a program to implement hyperlinking using netbeans.

EXPERIMENT NO. . :MMEC-WI-IT-412-11 REV. DATE : NA LABORATORY : CENTER C2 ISSUE NO. 00 ISSUE DATE: NA DEPTT.: INFORMATION TECHNOLOGY SEMESTER : VIII PAGE : 02 of 02
Objectives : write a program to implement hyperlinking using netbeans. 11.1 Index1.jsp <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body> <p> Request for Secure Login Page <a href="Secure.html">here!</a> <p> Request for Login User page<a href="LoginSecure.html">here!</a> </p> <h1>Hello World!</h1> </body> </html> 11.2 Loginsecure.html <html> <head> <title>Admin Secure Area</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <h1>Admin Secure Area</h1> </body> </html>
LABORATORY MANUAL

11.3 Secure.html <html> <head> <title> User Secure Area</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <h1>User Secure Area</h1> </body></html>
LABORATORY MANUAL

11.4 Output
LABORATORY MANUAL
EXPERIMENT TITLE: To create login window in NetBeans

Objectives : To create login window in NetBeans. 12.1 Login.jsp <html> <head> <title></title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <form action="LoginServer.jsp" method="get"> User Name:<input type="text" name="t2"> <br> Password:<input type="password" name="p2"> <br> <input type="submit" name="Login" value="Login"> </form> </body> </html> 12.2 LOGINSERVER: <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body> }
LABORATORY MANUAL

<% String name=request.getParameter("t2"); String passward=request.getParameter("p2"); if(name.equals("ruby") && passward.equals("12345")) { out.println("vallid user"); response.sendRedirect("Secure.html"); } else { out.println("Invallid user"); } %> </body> </html> 12.3 SECURE.JSP <html> <head> <title> User Secure Area</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <h1>User Secure Area</h1> </body> </html>
LABORATORY MANUAL

12.4 Output:

OOSE Mullana Lab Manual

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OOSE Mullana Lab Manual

Enviado por

Direitos autorais:

Formatos disponíveis

FORM NO.MMEC-FRM-32 C (REV.NO.00) MMEC M.M.

ENGINEERING COLLEGE MULLANA

FORM NO.MMEC-FRM-32 A (REV.NO. 00)

1 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

M.M. ENGINEERING COLLEGE MULLANA

MASTER LIST OF EXPERIMENT

Experiment MMEC-WIIT-412 IT-412-01

IT-412-09 IT-412-10 IT-412-11 IT-412-12

To be familiar with the implementation diagrams: component and deployment diagrams.

2 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

3 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

Flowchart format. Illustrate task dependencies and critical path.

4 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

5 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

2.3 Writing Requirements

6 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

PRACTICAL EXPERIMENT INSTRUCTION SHEET

7 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

8 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

9 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

10 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

11 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

12 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

Data flow Control flow

15 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

16 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

17 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

18 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

20 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

23 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

25 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

Component diagrams Deployment diagrams

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

27 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

Prepared By: Nidhi Mnaocha

FORM NO.MMEC-FRM-32 B (REV.NO.00)

30 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

M.M. ENGINEERING COLLEGE MULLANA

32 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

PRACTICAL EXPERIMENT INSTRUCTION SHEET

EXPERIMENT TITLE: write a program to implement hyperlinking using netbeans.

33 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

PRACTICAL EXPERIMENT INSTRUCTION SHEET

EXPERIMENT TITLE: write a program to implement hyperlinking using netbeans.

34 Prepared By: Nidhi Mnaocha Approved by : Dr. Manpreet Singh

FORM NO.MMEC-FRM-32 B (REV.NO.00) MMEC M.M. ENGINEERING COLLEGE MULLANA

PRACTICAL EXPERIMENT INSTRUCTION SHEET

EXPERIMENT TITLE: write a program to implement hyperlinking using netbeans.