QUESTION BANK. Dhulapally, Secunderabad Class : IT III. Subject: OBJECT ORIENTED ANALYSIS AND DESIGN GROUP - A (SHORT ANSWER QUESTIONS)

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "QUESTION BANK. Dhulapally, Secunderabad Class : IT III. Subject: OBJECT ORIENTED ANALYSIS AND DESIGN GROUP - A (SHORT ANSWER QUESTIONS)"

Transcription

1 St.MARTIN S ENGINEERING COLLEGE Dhulapally, Secunderabad Subject: OBJECT ORIENTED ANALYSIS AND DESIGN Class : IT III QUESTION BANK GROUP - A (SHORT ANSWER QUESTIONS) UNIT I 1. Define UML. 2. Explain modelling. 3. Describe the history of uml. 4. List out the method wars. 5. State the goals of UML. 6. Describe the importance of modelling. 7. Define the basic building blocks of uml. 8. Explain the things in uml. 9. Classify structural things. 10. Classify behavioral things in uml. 11. Define grouping things. 12. Define class. 13. Define class and object. 14. Define an Interface. 15. Define collaboration. 16. Describe component. 17. Explain about active class 18. Compare relationships. 19. Define Uml diagrams. 20. Explain common mechanisms in uml.

2 UNIT II 1. Define classes. 2. Explain about name. 3. Describe an attribute. 4. Define responsibilities. 5. Define modelling vocabulary of system. 6. Define distribution of responsibilities in a system. 7. Define dependency. 8. Define generalization. 9. Explain association. 10. Discuss about aggregation. 11. List the simple dependencies. 12. Demonstrate the modeling of single inheritance. 13. Discuss modelling structural relationships. 14. Define note. 15. Define stereotypes. 16. List tagged values. 17. Explain constraints. 18. Illustrate how to model comment. 19. Illustrate how to model different views of a system. 20. Explain modeling of new semantics. 21 Explain about class diagram. 22 State common properties in class diagram. 23 List out contents of class diagram. 24 Illustrate modelling of collaboration. 25 Discuss modelling a schema. 26 Explain how to forward engineer a class diagram. 27 Explain how to reverse engineer a class diagram. 28 Enumerate object diagram. 29 Tabulate common properties in object diagram. 30 Express the contents of object diagram. 31 Discuss modelling object structure. 32 Define an object. 33 Explain how to forward engineer a object diagram. 34 Explain how to reverse engineer a object diagram. 35 Explain collaboration. 36 State the interfaces.

3 UNIT III 1. Define interactions. 2. Explain about context. 3. Describe about association. 4. Discuss about self. 5. Explain about global. 6. Discuss about local scope. 7. Define parameter. 8. Explain messages in uml. 9. Discuss about sequencing. 10. Discuss about procedural sequence. 11. Explain about flat sequence. 12. Discuss How to model flow of control. 13. Explain collaboration diagrams. 14. Discuss how to forward engineers sequence diagrams. 15. Discuss how to reverse engineer collaboration diagrams. 16. State new link. 17. Explain about destroyed. 18. Describe about transient in detail. 19. Illustrate the common properties of interaction diagrams. 20. Explain How to model flow of control by organization. 21 Define Use case. 22 Interpret the relationship between Usecases and actors. 23 Demonstrate the need of Use case diagram. 24 Demonstrate an Actor. 25 Compare System Use case and business use case. 26 Explain types of requirements should not be documented in use cases. 27 Demonstrate the relationship between use cases and test cases. 28 Demonstrate an Activity Diagram. 29 Explain What types of requirements should not be documented in activity diagrams. 30 Discuss components of a activity diagram. UNIT-IV 1. Illustrate the characteristics of a well-structured active class and active object. 2. Define event and signal. 3. Summarize various parts of a transition. 4. Illustrate family of Signals. 5. Demonstrate exceptions in behavioural modelling. 6. State the events modelled by uml. 7. Discuss Event trigger. 8. State Guard condition. 9. Define state Machine. 10. Illustrate the steps to model the distribution of objects. 11 Define Node. 12 Demonstrate how nodes are organized. 13 Explain the steps required to model processors and devices.

4 14 Discuss the contents of component diagrams. 15 State common uses of component diagrams. 16 Compare components and classes. 17 State how component and interface are related. 18 Discuss the properties of components. 19 Discuss the standard stereotypes UML defines. 20 Describe the steps to enumerate executable release. UNIT-V 1. Define Framework. 2 Define Patterns. 3 Explain problem statement for unified library application. 4 Define Mechanism. 5. Discuss actors in library application. 6. Design classes in library application. 7. Illustrate objects in library application. 8. Design use cases in library application. 9. Discuss action states in library application. 10. Define use case for librarian. 11. State nodes in library. 12. Compare sequence and collaboration in library application. 13. Explain packages in library application GROUP-B (LONG ANSWER QUESTIONS) UNIT - I 1 Illustrate How is generalization/specialization contrasted with more code reuse? State Liskov s substitution principle. 2 (a) State Why is it necessary to have a variety of diagrams in a model of a system. (b) State Which UML diagrams give a static view and which give a dynamic view of a system. 3 (a) Explain briefly runtime polymorphism illustrating a program in Java or C++. (b) Discuss the principles of modelling. (c) Explain the antisymmetric and transitive properties of aggregation. 4 Consider a computer-based system that plays chess with a user. Which UML diagrams would be helpful in designing the system. 5 Explain the antisymmetric and transitive properties of aggregation. 6 Pick the ones that are related. Justify. i. Behavioral things, verbs ii. Structural things, nouns iii. Generalization, specialization, adjectives iv. Associations, verbs. 7 Explain the following briefly. i. class/object dichotomy ii. interface Vs. implementation

5 8 Explain the various relationships in UML briefly. 9 (a) Explain the following with UML notation i. behavioural things ii. Grouping things iii. Annotational things 10 Define the following: (a) use case driven (b) architecture centric (c) iterative process (d) Incremental process (e) stakeholder (f) artifact (g) use case (h) Active class 11 Explain model? What are the aims of modelling. 12 Explain the conceptual model of UML. 13 Explain briefly about the various diagrams in UML. 14 (a) Enumerate any six artifacts. (b) Explain the extensibility mechanisms in UML. 15 Enumerate the object oriented modelling. 16 Explain the various views considered in modeling a system s architecture? Explain. 17 Enumerate the UML approach to software development life cycle? Explain the various phases. 18 Contrast the following: i. Actors Vs. Stakeholders ii. Use case Vs. Algorithm. 19 Define software architecture. Explain the 4+1 view model of systems architecture. 20 Define using relationship. Give UML notation UNIT II 1 (a) Explain any three features used in creating abstractions. (b) Enumerate the steps to model the vocabulary of a system. 2 Write a simple JAVA applet for printing Hello, World! in a web browser. 3 Define relationship. Explain the four adornments that apply to an association. 4 Enumerate the steps to model single inheritance. 5 Enumerate the steps to model using relationship. 6 (a) Define the following: i. System ii. Model iii. subsystem iv. Use case 7 Illustrate distribution of responsibilities in a system. 8 State modeling different levels of abstraction. 9 ( a) Explain the UML s behaviour diagrams. (b) Contrast is-a relationship with has-a relationship. 10 Explain the following relationships with UML notation i. Using ii. Realization iii. Simple aggregation iv. Composite aggregation

6 11 Contrast interface inheritance with class inheritance. 12 Define modelling non software things and primitive type. 13 Enumerate modelling simple dependencies. 14 a) Interpret relation between interfaces, types and roles. b) Enumerate modelling new building blocks. 15 a) Enumerate the steps to model different views of a system. b) Enumerate modelling comment s and new semantics 16 a) Enumerate the steps to model complex views. b) Enumerate modelling new properties. 17 a) Define idiom. Enumerate the steps to model structural relationships. b) Enumerate modelling seams in a system. 18 Enumerate modelling static and dynamic type. 19 Enumerate modelling group of elements. 20 Contrast simple aggregation with composite aggregation. 21 Design a class diagram that depicts the various relationships in UML. 22 Explain the common properties and uses of class diagrams. 23 Illustrate the contents in class diagrams. 24 Explain the use of forward engineering and reverse engineering class diagrams. 25 Contrast object diagram with class diagram. 26 Enumerate the steps to model concrete instances. 27 Illustrate the following modeling issues with class diagrams. i. Modeling simple collaborations ii. Modeling logical database schema. 28 Enumerate the steps to model prototypical instances. 29 Enumerate the steps to model object structures. 30 Enumerate the steps to forward and reverse engineer object diagram. 31 Demonstrate class diagram. 32 Enumerate the steps to model logical database schema. 33 Enumerate the steps to model logical database schema. Give all example class diagrams. 34 State forward engineering and reverse engineering. UNIT - III 1 Describe interaction diagrams. What are their contents and common properties. 2 Define semantic equivalence between two kinds of interaction diagrams. 3 Enumerate the steps to model flows of control by time ordering. 4 Design a sequence diagrams that specifies the flow of control involved in initiating a simple, two-party phone call. 5 Design a collaboration diagram that specifies the flow of control involved in registering a new student at a school. 6 Explain the sequence diagram and collaboration diagram and draw an example diagram for each one. 7 Consider the use case withdraw amount related to ATM transaction modeling. Draw both the interaction diagrams for the use case. Explain briefly.

7 8 Discuss the properties and common uses of sequence diagrams and collaboration diagrams. 9 Explain the sequence diagram and collaboration diagram and draw an example diagram for each one. 10 Discuss a collaboration diagram that specifies the flow of control involved in registering a new student at a school. 11 Explain forward engineering and reverse engineering of interaction diagrams. 12 Describe Messages and Links. 13 Describe modeling a flow of control. 14 Describe Sequencing in Interaction diagrams. 15 Design a use case diagram to model the behaviour of a cellular phone. Explain briefly. 16 Discuss the contexts, common properties and common uses of use case diagrams. 17 Explain the significance of context in modelling use cases. 18 Demonstrate the various adornments to ends of links denoted as standard stereotypes? Explain about objects and roles. 19 a) Explain the use of forward engineering and reverse engineering use case diagrams. b) Contrast action with activity. Define state and event. 20 Design a use case diagram that depicts the context of a credit card validation system. Explain briefly. 21 a) Design the UML diagram to model the requirements of a system. b) Discuss various parts of a transition. Explain briefly. 22 a)a retail system will interact with customers who place and track orders. Illustrate UML diagram that uses various use cases. b)enumerate steps to model workflow and operation. 23 Sketch the use case diagram for modeling a hospital information system aimed at collecting and storing complete information pertaining to the patients treatment history and disease behavior where actors could be doctor, lab technician, patient, duty nurse, receptionist, visitors etc. 24 Demonstrate actors in use case diagram. UNIT IV 1 Enumerate the steps in modeling timing constraints. Illustrate with a UML diagram and explain. 2 Consider an object diagram that models the distribution of certain objects In a real-time system. Draw the diagram and explain briefly. 3 (a) Enumerate the steps to model a family of signals. (b) Enumerate the steps to model interposes communication. 4 Design a UML diagram which models IPC in a distributed reservation system with processes spread across four nodes. Briefly explain. 5 State the sketch of a state machine for the controller in a home security system, which is responsible for monitoring various sensors around the perimeter of the house. Briefly explain. 6 Illustrate modeling lifetime of an object and modeling exceptions with UML diagram. 7 a) Enumerate the steps to model multiple flows of control. b) Enumerate the steps to model distribution of objects.

8 a) Define event and signal. Explain the four kinds of events 8 modelled by UML. b) Enumerate the steps to model reactive objects and objects that migrate. 9 Contrast action with activity. Define state and event. What are the various parts of a state? Explain briefly. 10 Explain the four kinds of events modelled by UML. 11 (a) Enumerate the steps to model adaptable systems. Illustrate with a UML diagram. (b)explain the common uses of component diagrams. 12 a) Illustrate modeling source code and executable release. b) Illustrate modeling physical database and adaptable systems. 13 Explain the properties of a well-structured component diagram. 14 Define component. Contrast differences between components and classes? How are component and interface related? 15 (a) Describe the properties of components. (b) Discuss standard stereotypes UML defines that apply to components. 16 Demonstrate the contents, common properties and common uses of component diagrams? Explain briefly 17 Enumerate the steps to model the following. Illustrate UML diagrams and explain briefly. (a) Modeling processes and devices. (b) Modeling distribution of components. 18 a) Define node. Contrast node with components. b) Illustrate modeling Fully distributed system. 19 Enumerate the steps to model an embedded and client server system. Illustrate with a UML diagram. 20 Enumerate the steps to model the following. Illustrate with UML diagrams and explain briefly (a) Tables, files and documents (b) API (c) Source code. UNIT - V 1 Enumerate the steps to model design patterns. Illustrate with a UML diagram 2 Enumerate the steps to model architectural patterns. Illustrate with a UML diagram 3 Define Framework. Illustrate framework with a UML diagram. 4 Explain Patterns and Architecture. 5 Design class diagram for library Application. 6 Design object diagram for library Application. 7 Design use cases diagram for library Application. 8 Design sequence diagram for library Application. 9 Design collaboration diagram for library Application. 10 Design activity diagram for library Application. 11 Design statechart diagram for library Application. 12 Design component diagram for library Application. 13 Design deployment diagram for library Application. 14 Design Class diagram with common mechanisms for library Application.

9 15 Design a sequence diagram for the use case lend item. 16 Draw a class diagram of business objects in the design model and explain. GROUP-III (ANALYTICAL QUESTIONS) UNIT I 1 Explain Software Development Life Cycle (SDLC)? What are the phases (stages) of it? Which phase requires maximum efforts? Also explain why domain analysis i.e. domain class model, domain state model and domain interaction model is important. 2 Illustrate out evolution of UML. 3 Explain Method wars. 4 Define a domain model. 5 Explain the critical ability of object oriented systems. 6 Explain the 3 ways to apply UML. 7 Describe Unified process. 8 Explain the importance of Unified process. 9 Describe the iterative and evolutionary development. 10 Discuss why waterfall is so failure prone. 11 Explain the benefits of iterative development 12 Discuss agile methods. UNIT II 1 Define an abstract class? Mention its use. Can concrete class be a super class? If yes, give example, if no, give reason. Create a class hierarchy to organize the following drink classes: Mineral water, wine, alcoholic, non alcoholic, grape juice, soda, bears. 2 Categorize the following relationship into generalization, aggregation, composition and association. 1. Files contain records. 2. A drawing object is text, a geometrical object or group. 3. Modems and keyboards are input/output devices. 4. Object classes may have several attributes. 5. Car has accelerator, break and wheels as parts. 6. Windows is composed of lot of frames. 7. An account is either type savings or type current. 3 Explain any four standard constraints that apply to generalization relationships. 4 Discuss the stereotype applied to generalization relationships? Give a brief. 5 Compare abstract and concrete operation. 6 Illustrate the ability to navigate from class A to class Bin UML. 7 Explain business entity and service class. 8 Briefly explain the four adornments that apply to all association. 9 Enumerate the steps to model webs of relationships. 10 Prepare object diagram showing at least 10 relationships among the following object classes. Include associations and qualified associations, aggregations, generalizations, and multiplicity. You may add additional objects. Also show attributes and operations. School, playground, principal, school board, classroom, book, student, teacher, canteen, restroom, computer, desk, chair.

10 11 Model the relationship between a car (that has an engine and a colour) and its owners (having a name) in a UML class diagram. A car can have several owners over time, but only one or none owner at a time. Do not forget cardinalities, role names, attributes and their types 12 Draw class diagram for ATM. 13 Draw class diagram for Library Management system. 14 Draw object diagram for ATM. 15 Draw object diagram for Library Management system. 16 Explain composite structure diagram. 17 Discuss reflexive association in class diagram. 18 Design a class diagram for Document editor. 19 Design a class diagram for rotating machine. UNIT - III 1 Create a sequence diagram for the following collaboration. Use the classes and methods on the next slide.a customer wants to draw money from his bank account. He enters his card into an ATM (automated teller machine). The ATM machine prompts Enter PIN. The customer enters his PIN. The ATM (internally) retrieves the bank account number from the card. The ATM encrypts the PIN and the account number and sends it over to the bank. The bank verifies the encrypted Account and PIN number. If the PIN number is correct, the ATM displays Enter amount, draws money from the bank account and pays out the amount. 2 Design sequence diagram for ATM. 3 Design collaboration diagram for ATM. 4 Design sequence diagram for Library Management system. 5 Design collaboration diagram for Library Management system. 6 Compare class and sequence diagram. 7 Design sequence diagram for online shopping. 8 Describe activity diagram for restaurant. 9 Describe activity diagram for hotel canteen. 10 Describe use case diagram for restaurant. 11 Describe use case diagram for library. 12 Describe use case diagram for company. 13 Describe activity diagram for library. 14 Describe activity diagram for online shopping. UNIT IV 1 Describe statechart diagram for telephone line. 2 Describe statechart diagram for restaurant. 3 Describe state chart diagram for school. 4 Describe statechart diagram for library. 5 Describe statechart diagram for atm. 6 Describe statechart diagram for online shopping. 7 Describe component diagram for restaurant. 8 Describe deployment diagram for restaurant. 9 Describe component diagram for library. 10 Describe deployment diagram for atm. 11 Describe component diagram for library. 12 Describe deployment diagram for atm. 13 Explain how uml flows in actual project.

11 UNIT - V 1 Define framework. Illustrate framework with UML diagram. 2 Demonstrate classes in class diagram 3 Demonstrate actors and use cases in sequence diagram 5 Demonstrate components in library system 6 Draw a sequence diagram for the Add title use case. 7 Explain the Process of building a domain model. 8 Draw a class diagram of business objects in the design model and explain. 9 Discuss nodes in library management system 10 Explain active object in library system 11 Explain systems used in deployment diagram of library system 12 Describe activity diagram to inform a person when a loan is due and explain. 13 Design class diagram for user interface classes in the functions menu and explain..

Questions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements

Questions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements

More information

Robust Object Oriented System Analysis

Robust Object Oriented System Analysis Robust Object Oriented System Analysis Dr Jie Zhao, Dunstan Thomas Consulting Summary Uses cases are widely accepted as the best approach to capturing system requirements, in particular, functional requirements.

More information

What is a life cycle model?

What is a life cycle model? What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each

More information

Object-Oriented Systems Analysis and Design

Object-Oriented Systems Analysis and Design Object-Oriented Systems Analysis and Design Noushin Ashrafi Professor of Information System University of Massachusetts-Boston Hessam Ashrafi Software Architect Pearson Education International CONTENTS

More information

Types of UML Diagram. UML Diagrams 140703-OOAD. Computer Engineering Sem -IV

Types of UML Diagram. UML Diagrams 140703-OOAD. Computer Engineering Sem -IV 140703-OOAD Computer Engineering Sem -IV Introduction to UML - UML Unified Modeling Language diagram is designed to let developers and customers view a software system from a different perspective and

More information

COSC 3351 Software Design. Recap for the first quiz. Edgar Gabriel. Spring 2008. For the 1 st Quiz

COSC 3351 Software Design. Recap for the first quiz. Edgar Gabriel. Spring 2008. For the 1 st Quiz COSC 3351 Software Design Recap for the first quiz Spring 2008 For the 1 st Quiz Three large topic areas: UML syntax and diagrams Software architectural styles Object oriented design principles A couple

More information

System Modeling / Class Diagra Diagr m a Week 6

System Modeling / Class Diagra Diagr m a Week 6 System Modeling / Class Diagram Week 6 System modeling Agenda (Lecture) Agenda (Lab) Create CRC cards for your group project Create a system level (analysis level) class diagram (Lab Assignment #6) for

More information

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53 Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software

More information

Karunya University Dept. of Information Technology

Karunya University Dept. of Information Technology PART A Questions 1. Mention any two software process models. 2. Define risk management. 3. What is a module? 4. What do you mean by requirement process? 5. Define integration testing. 6. State the main

More information

A UML Introduction Tutorial

A UML Introduction Tutorial A UML Introduction Tutorial 1/27/08 9:55 PM A UML Introduction Tutorial In this tutorial you will learn about the fundamentals of object oriented modelling, the Unified Modelling Language and the software

More information

Introduction. UML = Unified Modeling Language It is a standardized visual modeling language.

Introduction. UML = Unified Modeling Language It is a standardized visual modeling language. UML 1 Introduction UML = Unified Modeling Language It is a standardized visual modeling language. Primarily intended for modeling software systems. Also used for business modeling. UML evolved from earlier

More information

Applying 4+1 View Architecture with UML 2. White Paper

Applying 4+1 View Architecture with UML 2. White Paper Applying 4+1 View Architecture with UML 2 White Paper Copyright 2007 FCGSS, all rights reserved. www.fcgss.com Introduction Unified Modeling Language (UML) has been available since 1997, and UML 2 was

More information

Chap 1. Introduction to Software Architecture

Chap 1. Introduction to Software Architecture Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)

More information

Designing Real-Time and Embedded Systems with the COMET/UML method

Designing Real-Time and Embedded Systems with the COMET/UML method By Hassan Gomaa, Department of Information and Software Engineering, George Mason University. Designing Real-Time and Embedded Systems with the COMET/UML method Most object-oriented analysis and design

More information

Architectural Design

Architectural Design Software Engineering Architectural Design 1 Software architecture The design process for identifying the sub-systems making up a system and the framework for sub-system control and communication is architectural

More information

CS 487. Week 8. Reference: 1. Software engineering, roger s. pressman. Reading: 1. Ian Sommerville, Chapter 3. Objective:

CS 487. Week 8. Reference: 1. Software engineering, roger s. pressman. Reading: 1. Ian Sommerville, Chapter 3. Objective: CS 487 Week 8 Reading: 1. Ian Sommerville, Chapter 3. Objective: 1. To check the understandibility of the students in life cycle and process model for development of a software product. 2. To check if

More information

i. Node Y Represented by a block or part. SysML::Block,

i. Node Y Represented by a block or part. SysML::Block, OMG SysML Requirements Traceability (informative) This document has been published as OMG document ptc/07-03-09 so it can be referenced by Annex E of the OMG SysML specification. This document describes

More information

Analysis and Design with UML

Analysis and Design with UML Analysis and Design with UML Page 1 Agenda Benefits of Visual Modeling History of the UML Visual Modeling with UML The Rational Iterative Development Process Page 2 What is Visual Modeling? Item Order

More information

Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville

Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville Software Engineering System Models Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain why the context of a system should be modeled as part of the RE process To describe

More information

SL-110: Fundamentals of Java Revision 15 October Sun Educational Services Instructor-Led Course Description

SL-110: Fundamentals of Java Revision 15 October Sun Educational Services Instructor-Led Course Description Sun Educational Services Instructor-Led Course Description Fundamentals of Java SL-110 The Fundamentals of the Java course provides students, with little or no programming experience, with the basics of

More information

To introduce software process models To describe three generic process models and when they may be used

To introduce software process models To describe three generic process models and when they may be used Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software

More information

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice In this Lecture you will Learn: Development Chapter 5C About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities

More information

ATM Case Study Part 1

ATM Case Study Part 1 ATM Case Study Part 1 A requirements document specifies the purpose of the ATM system and what it must do. Requirements Document A local bank intends to install a new automated teller machine (ATM) to

More information

CATALOG DESCRIPTION OF COURSES Offered by the department of Software Engineering

CATALOG DESCRIPTION OF COURSES Offered by the department of Software Engineering CATALOG DESCRIPTION OF COURSES Offered by the department of Software Engineering SE 201 Introduction to Software Engineering 3(3, 0, 1) Credits: 3 (3, 0, 1). Prerequisite: None. This course introduces

More information

USING UML FOR OBJECT-RELATIONAL DATABASE SYSTEMS DEVELOPMENT: A FRAMEWORK

USING UML FOR OBJECT-RELATIONAL DATABASE SYSTEMS DEVELOPMENT: A FRAMEWORK USING UML FOR OBJECT-RELATIONAL DATABASE SYSTEMS DEVELOPMENT: A FRAMEWORK Ming Wang, California State University, ming.wang@calstatela.edu ABSTRACT Data model of object-relational databases (ORDBs) is

More information

Object Oriented Design

Object Oriented Design Object Oriented Design Kenneth M. Anderson Lecture 20 CSCI 5828: Foundations of Software Engineering OO Design 1 Object-Oriented Design Traditional procedural systems separate data and procedures, and

More information

Software Engineering. System Modeling

Software Engineering. System Modeling Software Engineering System Modeling 1 System modeling System modeling is the process of developing abstract models of a system, with each model presenting a different view or perspective of that system.

More information

Information Science 1

Information Science 1 Topics covered Information Science 1 Terms and concepts from Week 05 The software development process Program'Development /Algorithms'and'Problem'Solving/'' ' software software life cycle life-cycle models

More information

Names a single, identifiable, and reasonably atomic behavior of the system or part of the system.

Names a single, identifiable, and reasonably atomic behavior of the system or part of the system. Packages are discussed in Chapter 12. As your models get bigger, you will find that many use cases tend to cluster together in groups that are conceptually and semantically related. In the UML, you can

More information

How to Make a Domain Model. Tutorial

How to Make a Domain Model. Tutorial How to Make a Domain Model Tutorial What is a Domain Model? Illustrates meaningful conceptual classes in problem domain Represents real-world concepts, not software components Software-oriented class diagrams

More information

11 November 2015. www.isbe.tue.nl. www.isbe.tue.nl

11 November 2015. www.isbe.tue.nl. www.isbe.tue.nl UML Class Diagrams 11 November 2015 UML Class Diagrams The class diagram provides a static structure of all the classes that exist within the system. Classes are arranged in hierarchies sharing common

More information

THE BCS PROFESSIONAL EXAMINATION Diploma. April EXAMINERS REPORT Systems Analysis and Design

THE BCS PROFESSIONAL EXAMINATION Diploma. April EXAMINERS REPORT Systems Analysis and Design THE BCS PROFESSIONAL EXAMINATION Diploma April 2015 EXAMINERS REPORT Systems Analysis and Design General Comments Section A Questions 2 and 3 were answered by more than half the candidates, possibly because

More information

The Software Development Life Cycle: An Overview. Last Time. Session 5: Agenda. Why Objects? Principles of the O-O Paradigm

The Software Development Life Cycle: An Overview. Last Time. Session 5: Agenda. Why Objects? Principles of the O-O Paradigm The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program Last Time The design process and design methods Design strategies

More information

UML TUTORIALS THE USE CASE MODEL

UML TUTORIALS THE USE CASE MODEL UML TUTORIALS THE USE CASE MODEL www.sparxsystems.com.au Sparx Systems 2004 Page 1/5 describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between

More information

TDDC88 Lab 2 Unified Modeling Language (UML)

TDDC88 Lab 2 Unified Modeling Language (UML) TDDC88 Lab 2 Unified Modeling Language (UML) Introduction What is UML? Unified Modeling Language (UML) is a collection of graphical notations, which are defined using a single meta-model. UML can be used

More information

Architecture Design & Sequence Diagram. Week 7

Architecture Design & Sequence Diagram. Week 7 Architecture Design & Sequence Diagram Week 7 Announcement Reminder Midterm I: 1:00 1:50 pm Wednesday 23 rd March Ch. 1, 2, 3 and 26.5 Hour 1, 6, 7 and 19 (pp.331 335) Multiple choice Agenda (Lecture)

More information

WHITE PAPER DATA GOVERNANCE ENTERPRISE MODEL MANAGEMENT

WHITE PAPER DATA GOVERNANCE ENTERPRISE MODEL MANAGEMENT WHITE PAPER DATA GOVERNANCE ENTERPRISE MODEL MANAGEMENT CONTENTS 1. THE NEED FOR DATA GOVERNANCE... 2 2. DATA GOVERNANCE... 2 2.1. Definition... 2 2.2. Responsibilities... 3 3. ACTIVITIES... 6 4. THE

More information

Course Name: Course in JSP Course Code: P5

Course Name: Course in JSP Course Code: P5 Course Name: Course in JSP Course Code: P5 Address: Sh No BSH 1,2,3 Almedia residency, Xetia Waddo Duler Mapusa Goa E-mail Id: ITKP@3i-infotech.com Tel: (0832) 2465556 (0832) 6454066 Course Code: P5 3i

More information

Electronic Healthcare Design and Development

Electronic Healthcare Design and Development Electronic Healthcare Design and Development Background The goal of this project is to design and develop a course on Electronic Healthcare Design and Development using Unified Modeling Language (UML)

More information

11 Tips to make the requirements definition process more effective and results more usable

11 Tips to make the requirements definition process more effective and results more usable 1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to

More information

Towards Collaborative Requirements Engineering Tool for ERP product customization

Towards Collaborative Requirements Engineering Tool for ERP product customization Towards Collaborative Requirements Engineering Tool for ERP product customization Boban Celebic, Ruth Breu, Michael Felderer, Florian Häser Institute of Computer Science, University of Innsbruck 6020 Innsbruck,

More information

RUP Design Workflow. Michael Fourman Cs2 Software Engineering

RUP Design Workflow. Michael Fourman Cs2 Software Engineering RUP Design Workflow Michael Fourman Introduction Design architecture that can meet all requirements Understand non-functional requirements and constraints related to technologies Identify subsystems (overall

More information

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS

SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) VERSION 2.1 SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS 1 TABLE OF CONTENTS INTRODUCTION... 3 About The Service-Oriented Modeling Framework

More information

Software Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville

Software Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville Software Engineering Software Processes Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce software process models To describe three generic process models and when

More information

Case studies: Outline. Requirement Engineering. Case Study: Automated Banking System. UML and Case Studies ITNP090 - Object Oriented Software Design

Case studies: Outline. Requirement Engineering. Case Study: Automated Banking System. UML and Case Studies ITNP090 - Object Oriented Software Design I. Automated Banking System Case studies: Outline Requirements Engineering: OO and incremental software development 1. case study: withdraw money a. use cases b. identifying class/object (class diagram)

More information

BCS Professional Examination 2015 Professional Graduate Diploma. April 2015. Examiners Report. System Design Methods

BCS Professional Examination 2015 Professional Graduate Diploma. April 2015. Examiners Report. System Design Methods BCS Professional Examination 2015 Professional Graduate Diploma April 2015 Examiners Report System Design Methods Question 1 1.a) Discuss why prototyping and agile approaches to systems design are increasingly

More information

Software development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali

Software development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali Software development life cycle Software life cycle: Software Engineering - II ITNP92 - Object Oriented Software Design Dr Andrea Bracciali Module Co-ordinator 4B86 abb@cs.stir.ac.uk Spring 2014 (elicitation)

More information

Masters of Science in Software & Information Systems

Masters of Science in Software & Information Systems Masters of Science in Software & Information Systems To be developed and delivered in conjunction with Regis University, School for Professional Studies Object Oriented Design Table of Contents January

More information

Chapter 4 Software Lifecycle and Performance Analysis

Chapter 4 Software Lifecycle and Performance Analysis Chapter 4 Software Lifecycle and Performance Analysis This chapter is aimed at illustrating performance modeling and analysis issues within the software lifecycle. After having introduced software and

More information

UML. Objectives. Documenting user requirements using the UML notation Description of the various components of UML The use of Use Cases.

UML. Objectives. Documenting user requirements using the UML notation Description of the various components of UML The use of Use Cases. UML cmsc435-1 Objectives Documenting user requirements using the UML notation Description of the various components of UML The use of Use Cases cmsc435-2 Unified Modeling Language The UML is an international

More information

Generating Enterprise Applications from Models

Generating Enterprise Applications from Models Generating Enterprise Applications from Models Vinay Kulkarni, R Venkatesh, Sreedhar Reddy Tata Research Development and Design Centre, 54, Industrial estate, Hadapsar, Pune, 411 013, INDIA { vinayk, rvenky,

More information

SysML vs. UML 2: A Detailed Comparison. Pascal Roques MoDELS 11 Tutorial October 16th, 2011

SysML vs. UML 2: A Detailed Comparison. Pascal Roques MoDELS 11 Tutorial October 16th, 2011 SysML vs. UML 2: A Detailed Comparison Pascal Roques MoDELS 11 Tutorial October 16th, 2011 The Speaker: Pascal Roques Senior Consultant & Trainer, > 20 years experience in modeling SADT, OMT, UML, SysML

More information

Tool Support for Software Variability Management and Product Derivation in Software Product Lines

Tool Support for Software Variability Management and Product Derivation in Software Product Lines Tool Support for Software Variability Management and Product Derivation in Software s Hassan Gomaa 1, Michael E. Shin 2 1 Dept. of Information and Software Engineering, George Mason University, Fairfax,

More information

Compliance and Requirement Traceability for SysML v.1.0a

Compliance and Requirement Traceability for SysML v.1.0a 1. Introduction: Compliance and Traceability for SysML v.1.0a This document provides a formal statement of compliance and associated requirement traceability for the SysML v. 1.0 alpha specification, which

More information

The Unified Software Development Process

The Unified Software Development Process The Unified Software Development Process Technieche Universal Darmstadt FACHBEREICH IN-FORMAHK BLIOTHEK Ivar Jacobson Grady Booch James Rumbaugh Rational Software Corporation tnventar-nsr.: Sachgebiete:

More information

Scenario-based Requirements Engineering and User-Interface Design

Scenario-based Requirements Engineering and User-Interface Design Scenario-based Requirements Engineering and User-Interface Institut für Computertechnik ICT Institute of Computer Technology Hermann Kaindl Vienna University of Technology, ICT Austria kaindl@ict.tuwien.ac.at

More information

Use Cases. Massimo Felici. Massimo Felici Use Cases c 2004 2011

Use Cases. Massimo Felici. Massimo Felici Use Cases c 2004 2011 Use Cases Massimo Felici Use Cases 1 Support requirements engineering activities and the requirement process Capture what a system is supposed to do, i.e., systems functional requirements Describe sequences

More information

Requirements engineering

Requirements engineering Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and

More information

Application of UML in Real-Time Embedded Systems

Application of UML in Real-Time Embedded Systems Application of UML in Real-Time Embedded Systems Aman Kaur King s College London, London, UK Email: aman.kaur@kcl.ac.uk Rajeev Arora Mechanical Engineering Department, Invertis University, Invertis Village,

More information

(BA122) Software Engineer s Workshop (SEW)

(BA122) Software Engineer s Workshop (SEW) Training for the Business Analyst (BA122) Software Engineer s Workshop (SEW) Duration: 4 days CDUs (Continuing Development Units): 28 Description: A practical workshop covering the role of the Business-Systems

More information

Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions

Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions Announcements SE 1: Software Requirements Specification and Analysis Lecture 4: Basic Notations Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445 Send your group

More information

New UML 2.0 based models to design WAP applications

New UML 2.0 based models to design WAP applications New UML 2.0 based models to design WAP applications Ricardo Soto De Giorgis School of Informatic Engineering, Pontifical Catholic University of Valparaíso, Chile 56 32 273762 ricardo.soto@ucv.cl Nibaldo

More information

Software Design and Class Diagrams

Software Design and Class Diagrams Software Design and Class Diagrams Massimo Felici Software Design 1 The SEOC course is concerned with software design in terms of objects and components, in particular, object-oriented design Object-oriented

More information

Developing SOA solutions using IBM SOA Foundation

Developing SOA solutions using IBM SOA Foundation Developing SOA solutions using IBM SOA Foundation Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 4.0.3 4.0.3 Unit objectives After completing this

More information

040010203- Software Engineering 2014

040010203- Software Engineering 2014 Module-1Introduction To Software Engineering & Process Models Short Question: 1. Define software. 2. Define software engineering. 3. What do you mean by software doesn t wear out? 4. What do you mean by

More information

REQUIREMENTS ANALYSIS AND SYSTEM DESIGN

REQUIREMENTS ANALYSIS AND SYSTEM DESIGN REQUIREMENTS ANALYSIS AND SYSTEM DESIGN third edition LESZEKA. MACIASZEK ADDISON-WESLEY An imprint of Pearson Education Harlow, England London New York Boston San Francisco Toronto Sydney Singapore Hong

More information

An Approach for Reverse Engineering thorough Complementary Software Views

An Approach for Reverse Engineering thorough Complementary Software Views An Approach for Reverse Engineering thorough Complementary Software Views Niranjan Kumar SIEMENS Technology and Services Pvt. Ltd. #84, KEONICS, Electronics City, Bangalore 560 100, India. e-mail: Niranjan.kumar@siemens.com,

More information

Object Oriented System Development with VB.NET

Object Oriented System Development with VB.NET Chapter 1 Object Oriented System Development with Objectives In this chapter, you will: Learn about OO development and Understand object-oriented concepts Recognize the benefits of OO development Preview

More information

Using UML Part One Structural Modeling Diagrams

Using UML Part One Structural Modeling Diagrams UML Tutorials Using UML Part One Structural Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,

More information

Technical Brief August

Technical Brief August Technical Brief August 2015 SEARCH The National Consortium for Justice Information and Statistics A Unified Modeling Language Approach to Modeling NIEM Exchanges: Analyzing Requirements By Diane Lacy Information

More information

Enterprise Application Development Using UML, Java Technology and XML

Enterprise Application Development Using UML, Java Technology and XML Enterprise Application Development Using UML, Java Technology and XML Will Howery CTO Passage Software LLC 1 Introduction Effective management and modeling of enterprise applications Web and business-to-business

More information

Model Driven Interoperability through Semantic Annotations using SoaML and ODM

Model Driven Interoperability through Semantic Annotations using SoaML and ODM Model Driven Interoperability through Semantic Annotations using SoaML and ODM JiuCheng Xu*, ZhaoYang Bai*, Arne J.Berre*, Odd Christer Brovig** *SINTEF, Pb. 124 Blindern, NO-0314 Oslo, Norway (e-mail:

More information

ENHANCED ATM SECURITY SYSTEM USING BIOMETRICS

ENHANCED ATM SECURITY SYSTEM USING BIOMETRICS www.ijcsi.org 352 ENHANCED ATM SECURITY SYSTEM USING BIOMETRICS Prof. Selina Oko 1 and Jane Oruh 2 1 Department of Computer Science, Ebonyi State University Abakaliki, Nigeria 2 Department of Computer

More information

UML-based Test Generation and Execution

UML-based Test Generation and Execution UML-based Test Generation and Execution Jean Hartmann, Marlon Vieira, Herb Foster, Axel Ruder Siemens Corporate Research, Inc. 755 College Road East Princeton NJ 08540, USA jeanhartmann@siemens.com ABSTRACT

More information

Software Architecture Document

Software Architecture Document Software Architecture Document Natural Language Processing Cell Version 1.0 Natural Language Processing Cell Software Architecture Document Version 1.0 1 1. Table of Contents 1. Table of Contents... 2

More information

Application Of Business Intelligence In Agriculture 2020 System to Improve Efficiency And Support Decision Making in Investments.

Application Of Business Intelligence In Agriculture 2020 System to Improve Efficiency And Support Decision Making in Investments. Application Of Business Intelligence In Agriculture 2020 System to Improve Efficiency And Support Decision Making in Investments Anuraj Gupta Department of Electronics and Communication Oriental Institute

More information

Chapter 3. Technology review. 3.1. Introduction

Chapter 3. Technology review. 3.1. Introduction Technology review Chapter 3 3.1. Introduction Previous chapter covers detail description about problem domain. In this chapter I will discuss the technologies currently available to solve a problem in

More information

Syllabus M.C.A. Object Oriented Modeling and Design usung UML

Syllabus M.C.A. Object Oriented Modeling and Design usung UML I Syllabus M.C.A. (Semester IV) Object Oriented Modeling and Design usung UML INTRODUCTION An overview - Object basics - Object state and properties, Behavior, Methods, Messages. Object Oriented system

More information

Software Architecture

Software Architecture Software Architecture Definitions http://www.sei.cmu.edu/architecture/published_definiti ons.html ANSI/IEEE Std 1471-2000, Recommended Practice for Architectural Description of Software- Intensive Systems

More information

Java (12 Weeks) Introduction to Java Programming Language

Java (12 Weeks) Introduction to Java Programming Language Java (12 Weeks) Topic Lecture No. Introduction to Java Programming Language 1 An Introduction to Java o Java as a Programming Platform, The Java "White Paper" Buzzwords, Java and the Internet, A Short

More information

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction CS 3141: Team Software Project Introduction Ali Ebnenasir Department of Computer Science Michigan Technological University Acknowledgement Betty H.C. Cheng Software Engineering Systematic approach for

More information

Using UML Part Two Behavioral Modeling Diagrams

Using UML Part Two Behavioral Modeling Diagrams UML Tutorials Using UML Part Two Behavioral Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,

More information

Case Studies of Running the Platform. NetBeans UML Servlet JSP GlassFish EJB

Case Studies of Running the Platform. NetBeans UML Servlet JSP GlassFish EJB September Case Studies of Running the Platform NetBeans UML Servlet JSP GlassFish EJB In this project we display in the browser the Hello World, Everyone! message created in the session bean with servlets

More information

ATM Case Study OBJECTIVES. 2005 Pearson Education, Inc. All rights reserved. 2005 Pearson Education, Inc. All rights reserved.

ATM Case Study OBJECTIVES. 2005 Pearson Education, Inc. All rights reserved. 2005 Pearson Education, Inc. All rights reserved. 1 ATM Case Study 2 OBJECTIVES.. 3 2 Requirements 2.9 (Optional) Software Engineering Case Study: Examining the Requirements Document 4 Object-oriented design (OOD) process using UML Chapters 3 to 8, 10

More information

1 UML Tutorial. The Unified Modeling Language has quickly become the de-facto standard for building Object-Oriented software.

1 UML Tutorial. The Unified Modeling Language has quickly become the de-facto standard for building Object-Oriented software. 1 UML Tutorial The Unified Modeling Language has quickly become the de-facto standard for building Object-Oriented software. The OMG specification states: "The Unified Modeling Language (UML) is a graphical

More information

TOGAF usage in outsourcing of software development

TOGAF usage in outsourcing of software development Acta Informatica Pragensia 2(2), 2013, 68 76, DOI: 10.18267/j.aip.25 Section: Online: aip.vse.cz Peer-reviewed papers TOGAF usage in outsourcing of software development Aziz Ahmad Rais 1, Rudolf Pecinovsky

More information

Software Design Models, Tools & Processes *

Software Design Models, Tools & Processes * Software Design Models, Tools & Processes * Lecture 1: Software Design and Software Development Process Cecilia Mascolo * Thanks to Alan Blackwell and Jim Arlow for le7ng me use some of their slides. About

More information

Modeling Web Applications Using Java And XML Related Technologies

Modeling Web Applications Using Java And XML Related Technologies Modeling Web Applications Using Java And XML Related Technologies Sam Chung Computing & Stware Systems Institute Technology University Washington Tacoma Tacoma, WA 98402. USA chungsa@u.washington.edu Yun-Sik

More information

Applying Use Cases to Microcontroller Code Development. Chris Gilbert Cypress Semiconductor

Applying Use Cases to Microcontroller Code Development. Chris Gilbert Cypress Semiconductor Applying Use Cases to Microcontroller Code Development Chris Gilbert Cypress Semiconductor Agenda Why Use Cases Microcontroller Project Development Use Cases Defined Use Cases Composition General Example

More information

Object-Oriented Design Guidelines

Object-Oriented Design Guidelines Adaptive Software Engineering G22.3033-007 Session 8 Sub-Topic 3 Presentation Object-Oriented Design Guidelines Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute

More information

Rapid Development of Modular Dynamic Web Sites using UML

Rapid Development of Modular Dynamic Web Sites using UML Rapid Development of Modular Dynamic Web Sites using UML Tim Schattkowsky 1, Marc Lohmann 2 1 Paderborn University, C-LAB, D-33102 Paderborn, Germany tim@c-lab.de 2 Paderborn University, Department of

More information

Winery A Modeling Tool for TOSCA-based Cloud Applications

Winery A Modeling Tool for TOSCA-based Cloud Applications Institute of Architecture of Application Systems Winery A Modeling Tool for TOSCA-based Cloud Applications Oliver Kopp 1,2, Tobias Binz 2, Uwe Breitenbücher 2, and Frank Leymann 2 1 IPVS, 2 IAAS, University

More information

Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering

Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering Prof. Dr. Armin B. Cremers Sascha Alda Overview Phases during Software Development

More information

Modeling the User Interface of Web Applications with UML

Modeling the User Interface of Web Applications with UML Modeling the User Interface of Web Applications with UML Rolf Hennicker,Nora Koch,2 Institute of Computer Science Ludwig-Maximilians-University Munich Oettingenstr. 67 80538 München, Germany {kochn,hennicke}@informatik.uni-muenchen.de

More information

TECH. Requirements. Why are requirements important? The Requirements Process REQUIREMENTS ELICITATION AND ANALYSIS. Requirements vs.

TECH. Requirements. Why are requirements important? The Requirements Process REQUIREMENTS ELICITATION AND ANALYSIS. Requirements vs. CH04 Capturing the Requirements Understanding what the customers and users expect the system to do * The Requirements Process * Types of Requirements * Characteristics of Requirements * How to Express

More information

Object Oriented Programming. Risk Management

Object Oriented Programming. Risk Management Section V: Object Oriented Programming Risk Management In theory, there is no difference between theory and practice. But, in practice, there is. - Jan van de Snepscheut 427 Chapter 21: Unified Modeling

More information

StarUML Documentation

StarUML Documentation StarUML Documentation Release 2.0.0 MKLab June 24, 2016 Contents 1 Basic Concepts 3 1.1 Project.................................................. 3 1.2 Model vs. Diagram............................................

More information

Use Case Diagrams. Tutorial

Use Case Diagrams. Tutorial Use Case Diagrams Tutorial What is a use case? A requirements analysis concept A case of a use of the system/product Describes the system's actions from a the point of view of a user Tells a story A sequence

More information

Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk. COMP 201 web-page: http://www.csc.liv.ac.

Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk. COMP 201 web-page: http://www.csc.liv.ac. Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk COMP 201 web-page: http://www.csc.liv.ac.uk/~coopes/comp201 Lecture 18 Introductory Case Study Introduction to UML During

More information

Embedded/Real-Time Software Development with PathMATE and IBM Rational Systems Developer

Embedded/Real-Time Software Development with PathMATE and IBM Rational Systems Developer Generate Results. Real Models. Real Code. Real Fast. Embedded/Real-Time Software Development with PathMATE and IBM Rational Systems Developer Andreas Henriksson, Ericsson andreas.henriksson@ericsson.com

More information