Requirement Analysis with UML
|
|
- Hester Norman
- 7 years ago
- Views:
Transcription
1 Requirement Analysis with UML Pierre-Alain Muller V 2.0 Requirement Analysis 1
2 Pierre-Alain Muller 15+ years experience in OO modeling Assistant professor at ENSISA (a French school of engineering) Former CEO ObjeXion Software Independent Consultant Author of Instant UML, Wrox Press 1997 and Modélisation objet avec UML, Eyrolles 2000 V 2.0 Requirement Analysis 2
3 Course objectives Quick introduction to UML Requirement Analysis Activity modeling Use Cases modeling Object-Oriented modeling V 2.0 Requirement Analysis 3
4 What is UML? Unified Modeling Language for objectoriented developments De facto standard Defined and endorsed by the OMG (Object Management Group) Universally adopted by all major software vendors The Esperanto for the object-oriented methods V 2.0 Requirement Analysis 4
5 A single language UML is the language for the description of the object-oriented models UML can be used by Business analysts Software engineers Quality Assurance and Validation End-Users and Customers V 2.0 Requirement Analysis 5
6 UML is a powerful notation Syntax and semantics formally defined in a metamodel 9 types of diagrams (from business modeling to component modeling) Everything is not needed by everybody Many use a subset of UML V 2.0 Requirement Analysis 6
7 Activity Modeling Understand the business processes Find the actors in the business Find the activities performed by the actors V 2.0 Requirement Analysis 7
8 Scope The focus is on understanding Who is doing What and Where in the business Then the focus shifts on asking What should be provided by the system to help the actors to perform their tasks V 2.0 Requirement Analysis 8
9 Example : Customer : Sales Rep I need X : Provider I will prepare a proposal How much for X? Make a study Brainstorming It will cost 1 $ It will cost 3 $ Too expensive!!! Make it cheaper! V 2.0 Requirement Analysis 9
10 Use Cases Modeling Communicate with users and customers Capture requirements Identify system boundaries Derive objects and objects interactions Design user interface Define test cases Outline the user documentation V 2.0 Requirement Analysis 10
11 What is usually wrong with requirement specification? The customer is focused on business details The SW development is focused on implementation details The customers introduces new ideas without realizing that they are out of the agreed scope V 2.0 Requirement Analysis 11
12 The root of the problem They are too many ways to interpret a requirement specification All the details are correct, but they are out of context Very few, if any, will indicate what the users really need V 2.0 Requirement Analysis 12
13 What is good with Use Cases? The user is involved early in the process The user is aware when there is a change in the model The user sees the cost impact of a change in the model V 2.0 Requirement Analysis 13
14 Who writes the Use Cases? A separate analysis team The designers This is often the best way to get most from Use Cases V 2.0 Requirement Analysis 14
15 Use Case model concepts Actors Use Cases Scenarios System Boundaries Use Case description Actor 1 Use case 1 Use case 2 Actor 2 V 2.0 Requirement Analysis 15
16 What is an Actor? An Actor represents anything that interacts with the system (human, machine or another system) represents roles a user can play can give and receive information is not part of the system V 2.0 Requirement Analysis 16
17 Identifying Actors Who will supply, use or remove information? Who will use this functionality? Who will support and maintain the system? What are the system external resources? V 2.0 Requirement Analysis 17
18 Description of Actors An Actor is described by: Name Brief description Who or what the actor represents Why the actor is needed What interests the actor has in the system V 2.0 Requirement Analysis 18
19 What is a Use Case? A Use Case is a complete and meaningful flow of events A Use Case is initiated by an actor to invoke a certain functionality in the system A Use Case models a dialogue between an actor and the system The collection of all Use Cases constitutes all possible ways of using the system V 2.0 Requirement Analysis 19
20 Identifying Use Cases What are the tasks of an actor? How is the actor informed about certain occurrences in the system? How is the system informed about certain occurrences in the business? Does the system supply the business with the correct behavior? V 2.0 Requirement Analysis 20
21 Use Case and Actors A Use Case can interact with many actors An actor normally interacts with several Use Cases of a system For each actor Each way of using the system is captured in a use case For each use case There is one actor initiating the use case V 2.0 Requirement Analysis 21
22 Use Case description A Use Case has: Name Brief description Flow of events One basic flow Several alternative flows Additional requirements performance, reliability... V 2.0 Requirement Analysis 22
23 How to name a Use Case Name is taken from the actor point of view Name makes sense to the user (not to the system implementor) V 2.0 Requirement Analysis 23
24 Symptoms Beware of functional decomposition A lot of small Use Cases Difficult to understand the model Names like Actions Operation + Object or Function + Data Raise the abstraction level (the larger context) What value will the Use Case add? V 2.0 Requirement Analysis 24
25 Interaction with the system A communication-association between an Actor and a Use Case indicates that they interact The arrow direction shows who started the interaction Bank operation Customer V 2.0 Requirement Analysis 25
26 Interaction description A Use Case is a set of flow of events These flows scenarios are named scenarios The scenarios can be described Textually (in natural language) Graphically (using UML sequence diagrams) Usually both ways Between 5 and 15 pages of documentation V 2.0 Requirement Analysis 26
27 Example The user inserts his/her Credit Card in the ATM The ATM asks the PIN code The User provides the code : Customer Insert Card ATM Ask PIN Code Give Pin Code V 2.0 Requirement Analysis 27
28 Essential Use Cases Focuses on semantics No GUI presentation details : Customer ATM Secure Connection V 2.0 Requirement Analysis 28
29 Recurring Use Cases System start and stop System maintenance System evolution V 2.0 Requirement Analysis 29
30 Sources of information Requirements specification (if any) Customer, end users, and domain experts interviews Business model (if any) Internal standard practices and procedures V 2.0 Requirement Analysis 30
31 Summary Use Cases capture the system requirements Use Cases are user-focused Use Cases are readable by the end-user Use Cases are families of scenarios V 2.0 Requirement Analysis 31
32 Object-Oriented Modeling Move from requirements analysis to objectoriented analysis Prepare the smooth transition to implementation V 2.0 Requirement Analysis 32
33 Object-Oriented Modeling Use cases are realized by societies of collaborating objects These objects are originally drawn from the problem domain V 2.0 Requirement Analysis 33
34 The move to the objects <<Realizes>> Use Case Collaboration <<Participates>> A B C V 2.0 Requirement Analysis 34
35 Sequence diagrams Zoom into the system : Actor 1 The System : Actor 1 X A B C X X1 Y X2 Z Y Z Z1 V 2.0 Requirement Analysis 35
36 Object chaos V 2.0 Requirement Analysis 36
37 Object chaos There are many objects in the real world To understand the world, we group objects by similarities Making groups is known as classifying Humans have classified animals, flowers, mushrooms, atoms Classification is the way humans deal with complexity V 2.0 Requirement Analysis 37
38 Classes A class is an abstract definition of a set of objects Common objects elements are factored out in the class V 2.0 Requirement Analysis 38
39 Graphical representation Classe - Attribute + Operation() Complex - R eal Par t - Im agi nary Part + Add() + Sub() + Mult() + Div() V 2.0 Requirement Analysis 39
40 Class Description Split in two parts The specification (the what part) The implementation (the how part) V 2.0 Requirement Analysis 40
41 Representation of the static structure Class diagrams Classes Relations between classes Association Aggregation Generalization Dependence V 2.0 Requirement Analysis 41
42 Association Bi-directional symmetric semantic connection between classes An abstraction of all the links between the instances of the associated classes Represented by a line drawn between the classes V 2.0 Requirement Analysis 42
43 Exemple Company Person SGS Nadine Claudio IB M PAM : Person : Person V 2.0 Requirement Analysis 43
44 Naming of associations Company < Works for Person Company Employs > Person V 2.0 Requirement Analysis 44
45 Naming of the roles A role describes one end of an association +Employee Company Person +Employer V 2.0 Requirement Analysis 45
46 Role multiplicity +Employee Company 0..1 Person +Em ployer 1..* 1 One and only one 0..1 Zero or one M.. N From M to N (naturals) * Many 0.. * From zero to many 1.. * From one to many V 2.0 Requirement Analysis 46
47 Class-associations Adding attributes and/or operations to the relation +Employee 0..1 Company Person +Employer 1..* Contract - Start Date V 2.0 Requirement Analysis 47
48 Aggregation Bi-directional asymmetric semantic connection between classes Some kind of stronger association Represents master and slave relations whole and part relations composite and component relations V 2.0 Requirement Analysis 48
49 Examples Car Door V 2.0 Requirement Analysis 49
50 Correspondences An object is instance of a class A link is instance of a relation Links connect objects, relations connect classes A link between two objects implies a relation between the classes of these objects V 2.0 Requirement Analysis 50
51 Class Hierarchies Master complexity Hierarchies of abstractions Generalization Superclasses Specialization Subclasses Superclass Subclass More specialized More general V 2.0 Requirement Analysis 51
52 Generalization Factor out the common elements attributes, operations, relations, constraints Vehicle Air Vehicle Ground Vehi cle Plane Truck Car V 2.0 Requirement Analysis 52
53 Specialization Extension of a set of classes Contract Partial Time Full Time Manager V 2.0 Requirement Analysis 53
54 Properties of generalization Always means : is a or is a kind of Bird + Fly() Good!!! W rong!!! Sparrow Ostrich V 2.0 Requirement Analysis 54
55 Properties of generalization Non-reflexive, non-symmetric, transitive B A B A Not possible!!! C B Not possible!!! V 2.0 Requirement Analysis 55
56 Substitution principle It must be possible to substitute any object instance of a subclass for any object instance of a superclass without affecting the semantics of a program written in terms of the superclass. V 2.0 Requirement Analysis 56
57 Multiple Generalization Carpet Vehicle Land Vehicle Air Vehicle Flying Carpet V 2.0 Requirement Analysis 57
58 Inheritance Most often used technique for implementing generalization Build one class from another by sharing attributes, operations, relations and constraints within a class hierarchy Not always available in the implementation language / environment V 2.0 Requirement Analysis 58
59 Dependence Poorly semantically loaded relation Dependence shows obsolescence rules Include, With, Instantiation Licence Motor Bike Trial Trial Enduro V 2.0 Requirement Analysis 59
60 Summary Classes are connected by relations Associations are bi-directional symmetric semantic connections between classes Aggregations are bi-directional asymmetric semantic connections between classes Generalization orders classes within hierarchies Dependence shows obsolescence rules V 2.0 Requirement Analysis 60
61 Summary UML is the standard language for objectoriented models UML provides notational support for requirement analysis Business modeling Use Cases modeling Domain Modeling V 2.0 Requirement Analysis 61
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 informationChapter 8 The Enhanced Entity- Relationship (EER) Model
Chapter 8 The Enhanced Entity- Relationship (EER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 Outline Subclasses, Superclasses, and Inheritance Specialization
More informationQuestions? 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 informationObject 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 informationSysML Modelling Language explained
Date: 7 th October 2010 Author: Guillaume FINANCE, Objet Direct Analyst & Consultant UML, the standard modelling language used in the field of software engineering, has been tailored to define a modelling
More informationSoftware 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 informationSystem 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 informationHow To Design Software
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 informationLectures 2 & 3: Introduction to Modeling & UML. Getting started
Lectures 2 & 3: Introduction to Modeling & UML Why Build Models? What types of Models to build Intro to UML Class Diagrams Relationship between UML and program code Uses of UML 202 Steve Easterbrook. This
More informationIn this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?
In this Lecture you will Learn: Systems Development Methodologies What a systems development methodology is Why methodologies are used The need for different methodologies The main features of one methodology
More informationIV. The (Extended) Entity-Relationship Model
IV. The (Extended) Entity-Relationship Model The Extended Entity-Relationship (EER) Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of EER Diagrams
More informationUsing 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 informationSoftware 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 informationATM 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 informationAnnouncements. 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 informationTypes 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 information11 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 informationAssuming the Role of Systems Analyst & Analysis Alternatives
Assuming the Role of Systems Analyst & Analysis Alternatives Nature of Analysis Systems analysis and design is a systematic approach to identifying problems, opportunities, and objectives; analyzing the
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT SYSTEMS ANALYSIS & DESIGN EXAMINERS REPORT
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT SYSTEMS ANALYSIS & DESIGN EXAMINERS REPORT Monday 28 th September 2015 Case Study for both sections A and
More informationUsing 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 informationA technical discussion on modeling with UML 06/11/03 Entity Relationship Modeling with UML
A technical discussion on modeling with UML 06/11/03 Entity Relationship Modeling with UML Davor Gornik Improving software development capability 2 Table of Contents Entity Relationship Modeling... 1 Core
More informationBCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT. September 2013 EXAMINERS REPORT
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT September 2013 EXAMINERS REPORT Systems Analysis and Design Section A General Comments Candidates in general
More informationLecture 9: Requirements Modelling
A little refresher: What are we modelling? Lecture 9: Requirements Modelling Requirements; Systems; Systems Thinking Role of Modelling in RE Why modelling is important Limitations of modelling Brief overview
More informationScenario-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 informationRequirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
More informationTutorial - Building a Use Case Diagram
Tutorial - Building a Use Case Diagram 1. Introduction A Use Case diagram is a graphical representation of the high-level system scope. It includes use cases, which are pieces of functionality the system
More informationContents. 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 informationLecture 12: Entity Relationship Modelling
Lecture 12: Entity Relationship Modelling The Entity-Relationship Model Entities Relationships Attributes Constraining the instances Cardinalities Identifiers Generalization 2004-5 Steve Easterbrook. This
More informationUsing Use Cases for requirements capture. Pete McBreen. 1998 McBreen.Consulting
Using Use Cases for requirements capture Pete McBreen 1998 McBreen.Consulting petemcbreen@acm.org All rights reserved. You have permission to copy and distribute the document as long as you make no changes
More informationCPS122 Lecture: State and Activity Diagrams in UML
CPS122 Lecture: State and Activity Diagrams in UML Objectives: last revised February 14, 2012 1. To show how to create and read State Diagrams 2. To introduce UML Activity Diagrams Materials: 1. Demonstration
More informationObject Oriented Software Models
Software Engineering CSC 342/ Dr Ghazy Assassa Page 1 Object Oriented Software Models Use case diagram and use case description 1. Draw a use case diagram for a student-course-registration system. Show
More informationAnalysis 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 informationWhat is a metamodel: the OMG s metamodeling infrastructure
Modeling and metamodeling in Model Driven Development Warsaw, May 14-15th 2009 Gonzalo Génova ggenova@inf.uc3m.es http://www.kr.inf.uc3m.es/ggenova/ Knowledge Reuse Group Universidad Carlos III de Madrid
More informationUse-Case Analysis. ! What is it? ! From where did it come? ! Now part of UML
Use-Case Analysis Use-Case Analysis! What is it?! An informal, user-friendly, technique useful for functional requirements analysis and specification! From where did it come?! Ivar Jacobson, a Swedish
More informationTransaction-Typed Points TTPoints
Transaction-Typed Points TTPoints version: 1.0 Technical Report RA-8/2011 Mirosław Ochodek Institute of Computing Science Poznan University of Technology Project operated within the Foundation for Polish
More informationCommunication Diagrams
Communication Diagrams Massimo Felici Realizing Use cases in the Design Model 1 Slide 1: Realizing Use cases in the Design Model Use-case driven design is a key theme in a variety of software processes
More informationIntroduction. 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 informationUML basics. Part III: The class diagram. by Donald Bell IBM Global Services
Copyright Rational Software 2003 http://www.therationaledge.com/content/nov_03/t_modelinguml_db.jsp UML basics Part III: The class diagram by Donald Bell IBM Global Services In June 2003, I began a series
More informationSoftware Development: An Introduction
Software Development: An Introduction Fact: Software is hard. Imagine the difficulty of producing Windows 2000 29 million lines of code 480,000 pages of listing if printed a stack of paper 161 feet high
More informationCSC 742 Database Management Systems
CSC 742 Database Management Systems Topic #4: Data Modeling Spring 2002 CSC 742: DBMS by Dr. Peng Ning 1 Phases of Database Design Requirement Collection/Analysis Functional Requirements Functional Analysis
More informationA terminology model approach for defining and managing statistical metadata
A terminology model approach for defining and managing statistical metadata Comments to : R. Karge (49) 30-6576 2791 mail reinhard.karge@run-software.com Content 1 Introduction... 4 2 Knowledge presentation...
More informationAN ONTOLOGICAL APPROACH TO WEB APPLICATION DESIGN USING W2000 METHODOLOGY
STUDIA UNIV. BABEŞ BOLYAI, INFORMATICA, Volume L, Number 2, 2005 AN ONTOLOGICAL APPROACH TO WEB APPLICATION DESIGN USING W2000 METHODOLOGY ANNA LISA GUIDO, ROBERTO PAIANO, AND ANDREA PANDURINO Abstract.
More informationApplying 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 informationSequence Diagrams. Massimo Felici. Massimo Felici Sequence Diagrams c 2004 2011
Sequence Diagrams Massimo Felici What are Sequence Diagrams? Sequence Diagrams are interaction diagrams that detail how operations are carried out Interaction diagrams model important runtime interactions
More informationXV. The Entity-Relationship Model
XV. The Entity-Relationship Model The Entity-Relationship Model Entities, Relationships and Attributes Cardinalities, Identifiers and Generalization Documentation of E-R Diagrams and Business Rules The
More informationDesigning a Semantic Repository
Designing a Semantic Repository Integrating architectures for reuse and integration Overview Cory Casanave Cory-c (at) modeldriven.org ModelDriven.org May 2007 The Semantic Metadata infrastructure will
More informationUML FOR OBJECTIVE-C. Excel Software www.excelsoftware.com
UML FOR OBJECTIVE-C Excel Software www.excelsoftware.com Objective-C is a popular programming language for Mac OS X computers. The Unified Modeling Language (UML) is the industry standard notation for
More informationMeta-Model specification V2 D602.012
PROPRIETARY RIGHTS STATEMENT THIS DOCUMENT CONTAINS INFORMATION, WHICH IS PROPRIETARY TO THE CRYSTAL CONSORTIUM. NEITHER THIS DOCUMENT NOR THE INFORMATION CONTAINED HEREIN SHALL BE USED, DUPLICATED OR
More informationObject-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 informationUnit I Page No. 1 System Development Object Basics Development Life Cycle Methodologies Patterns Frameworks Unified Approach UML
Unit I Page No. 1 System Development Object Basics Development Life Cycle Methodologies Patterns Frameworks Unified Approach UML System Development (SD) : - o SD refers to all activities that go into producing
More informationChapter 7 Data Modeling Using the Entity- Relationship (ER) Model
Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Outline Using High-Level Conceptual Data Models for
More informationi. 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 informationWhy & How: Business Data Modelling. It should be a requirement of the job that business analysts document process AND data requirements
Introduction It should be a requirement of the job that business analysts document process AND data requirements Process create, read, update and delete data they manipulate data. Process that aren t manipulating
More informationExercise 8: SRS - Student Registration System
You are required to develop an automated Student Registration System (SRS). This system will enable students to register online for courses each semester. As part of the exercise you will have to perform
More informationAlgorithms, Flowcharts & Program Design. ComPro
Algorithms, Flowcharts & Program Design ComPro Definition Algorithm: o sequence of steps to be performed in order to solve a problem by the computer. Flowchart: o graphical or symbolic representation of
More informationDatabase Design Methodology
Database Design Methodology Three phases Database Design Methodology Logical database Physical database Constructing a model of the information used in an enterprise on a specific data model but independent
More informationII. Conceptual Modeling
II. Conceptual Modeling Engineering Software Models in Software Engineering What is Conceptual Modeling? Origins 2003 John Mylopoulos and Steve Easterbrook Conceptual Modeling -- 1 Engineering Software
More informationInteraction Diagrams. Use Cases and Actors INTERACTION MODELING
Karlstad University Department of Information Systems Adapted for a textbook by Blaha M. and Rumbaugh J. Object Oriented Modeling and Design Pearson Prentice Hall, 2005 INTERACTION MODELING Remigijus GUSTAS
More informationTool 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 informationUmbrello UML Modeller Handbook
2 Contents 1 Introduction 7 2 UML Basics 8 2.1 About UML......................................... 8 2.2 UML Elements........................................ 9 2.2.1 Use Case Diagram.................................
More informationSoftware Project Management and UML
Software Project Management and UML Ali Bigdelou Computer Aided Medical Procedures (CAMP), Technische Universität München, Germany Outline Intro to Software Project Management Project Requirements Specification
More informationGraphical Systems Modeling with UML / SysML Class diagrams
Graphical Systems Modeling with UML / SysML Class diagrams Piotr Ciskowski Perspectives - views: architecture class diagram object diagram composite structure diagram package diagram Logical view Use case
More informationEnterprise Architecture at Work
Marc Lankhorst et al. Enterprise Architecture at Work Modelling, Communication and Analysis Third Edition 4y Springer Contents 1 Introduction to Enterprise Architecture 1 1.1 Architecture 1 1.2 Enterprise
More informationUML Diagram Types. Use Cases do the Following. Use Case Diagram
UML Diagram Types Dynamic Models activity diagrams statechart diagrams interaction diagrams sequence diagrams collaboration diagrams use case diagrams Structural Models class diagrams object diagrams packages
More informationRose/Architect: a tool to visualize architecture
Published in the Proceedings of the 32 nd Annual Hawaii International Conference on Systems Sciences (HICSS 99) Rose/Architect: a tool to visualize architecture Alexander Egyed University of Southern California
More informationUML for the C programming language.
Functional-based modeling White paper June 2009 UML for the C programming language. Bruce Powel Douglass, PhD, IBM Page 2 Contents 2 Executive summary 3 FunctionalC UML profile 4 Functional development
More informationHow 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 informationSofware Requirements Engineeing
Sofware Requirements Engineeing Three main tasks in RE: 1 Elicit find out what the customers really want. Identify stakeholders, their goals and viewpoints. 2 Document write it down (). Understandable
More informationFundamentals of Information Systems, Fifth Edition. Chapter 8 Systems Development
Fundamentals of Information Systems, Fifth Edition Chapter 8 Systems Development Principles and Learning Objectives Effective systems development requires a team effort of stakeholders, users, managers,
More information4.4 What is a Requirement? 4.5 Types of Requirements. Functional Requirements
4.4 What is a Requirement? It is a statement describing either 1) an aspect of what the proposed system must do, or 2) a constraint on the system s development. In either case it must contribute in some
More informationUML 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 informationConcepts of Database Management Seventh Edition. Chapter 9 Database Management Approaches
Concepts of Database Management Seventh Edition Chapter 9 Database Management Approaches Objectives Describe distributed database management systems (DDBMSs) Discuss client/server systems Examine the ways
More informationObject 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 informationTDDC88 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 informationProgramming Language Constructs as Basis for Software Architectures
Programming Language Constructs as Basis for Software Architectures 1 From individual parts to components In the 50s: Machine/Assembler programs: bound to specific hardware In the 60s-70s: Higher programming
More information1 Class Diagrams and Entity Relationship Diagrams (ERD)
1 Class Diagrams and Entity Relationship Diagrams (ERD) Class diagrams and ERDs both model the structure of a system. Class diagrams represent the dynamic aspects of a system: both the structural and behavioural
More informationModeling 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 informationDesign by Contract beyond class modelling
Design by Contract beyond class modelling Introduction Design by Contract (DbC) or Programming by Contract is an approach to designing software. It says that designers should define precise and verifiable
More informationSemTalk BPMN Tutorial APRIL 2015 Email: support@semtalk.com. Tutorial SemTalk 4.3 BPMN Edition for Business Process Analysis
Tutorial SemTalk 4.3 BPMN Edition for Business Process Analysis Contents 1. About Business Process Modeling Notation (BPMN)... 3 2. Starting SemTalk BPMN Edition... 4 3. Editing a Process... 7 3.1. Adding
More informationManaging Variability in Software Architectures 1 Felix Bachmann*
Managing Variability in Software Architectures Felix Bachmann* Carnegie Bosch Institute Carnegie Mellon University Pittsburgh, Pa 523, USA fb@sei.cmu.edu Len Bass Software Engineering Institute Carnegie
More informationDesign Patterns for Complex Event Processing
Design Patterns for Complex Event Processing Adrian Paschke BioTec Center, Technical University Dresden, 01307 Dresden, Germany adrian.paschke AT biotec.tu-dresden.de ABSTRACT Currently engineering efficient
More informationA Proposal for Constructing Relational Database from Class Diagram
A Proposal for Constructing Relational Database from Class Diagram Mohd Zainuri Saringat Faculty of Information Technology and Multimedia Universiti Tun Hussein Onn Malaysia Parit Raja, Batu Pahat, 86400,
More informationBusiness Process Redesign and Modelling
Business Process Redesign and Modelling The Business Process Redesign the Process Handbook the key idea of the Process Handbook approach is that a richly structured online repository about business processes
More informationAdvanced Service Creation: Bridging the Gap Between Requirements Elicitation and Service Design
Advanced Service Creation: Bridging the Gap Between Requirements Elicitation and Service Design Dionisis X. Adamopoulos 1, Constantine A. Papandreou 2 1 University of Piraeus, Greece and Centre for Communication
More informationAutomated Modeling of Legacy Systems Using the UML
Automated Modeling of Legacy Systems Using the UML by Pan-Wei Ng Software Engineering Specialist Rational Software Singapore Poor documentation is one of the major challenges of supporting legacy systems;
More information6-1. Process Modeling
6-1 Process Modeling Key Definitions Process model A formal way of representing how a business system operates Illustrates the activities that are performed and how data moves among them Data flow diagramming
More informationCOSC 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 informationATM 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 informationDetecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality
Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality Current Research Team: Prof. Victor R. Basili Forrest Shull, Ph.D. Guilherme H. Travassos, D.Sc. (1)
More informationThe «include» and «extend» Relationships in Use Case Models
The «include» and «extend» Relationships in Use Case Models Introduction UML defines three stereotypes of association between Use Cases, «include», «extend» and generalisation. For the most part, the popular
More information1.. This UI allows the performance of the business process, for instance, on an ecommerce system buy a book.
* ** Today s organization increasingly prompted to integrate their business processes and to automate the largest portion possible of them. A common term used to reflect the automation of these processes
More informationChapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More informationSemantic Modeling of Mortgage Backed Securities: Case Study. Mike Bennett, Enterprise Data Management Council Yefim Zhuk, Sallie Mae
Semantic Modeling of Mortgage Backed Securities: Case Study Mike Bennett, Enterprise Data Management Council Yefim Zhuk, Sallie Mae 1 Overview EDM Council Semantics Repository Regulatory challenges Project
More information[1] http://en.wikipedia.org/wiki/first-mover_advantage [2] http://www.acunote.com
-Gene Sher Software Development Processes: Those in engineering and science will sooner or later either be members of teams solving some large project, or be managing teams solving some large project.
More informationMenouer Boubekeur, Gregory Provan
Software Requirements Menouer Boubekeur, Gregory Provan Lectures Introduction to UML Introduction to Requirements Analysis Advanced techniques for Requirement Analysis M. Boubekeur, CSL, University College
More informationER modelling, Weak Entities, Class Hierarchies, Aggregation
CS344 Database Management Systems ER modelling, Weak Entities, Class Hierarchies, Aggregation Aug 2 nd - Lecture Notes (Summary) Submitted by - N. Vishnu Teja Saurabh Saxena 09010125 09010145 (Most the
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 13 Refactoring Part 3 1 Dealing with Generalization: Pull Up Constructor Body Pull Up Constructor Body You have constructors on subclasses with
More informationBPMN Business Process Modelling Notation
BPMN Business Process Modelling Notation Knut Hinkelmann This chapter is based on the BPMN Tutorial of Stephen A. White and the book White, S.A., Miers, D. (2008) BPMN - Modeling and Reference Guide. Future
More informationMODERN OBJECT-ORIENTED SOFTWARE DEVELOPMENT
MODERN OBJECT-ORIENTED SOFTWARE DEVELOPMENT A.N. Dunlop University of Southampton, SO17 1BJ, England Abstract Object-oriented (OO) programming has been around for a few years and there are many users of
More informationUML: Classes -- Association
UML: Classes -- Association Class1 You can indicate that two classes have an association by using a simple line connector. Class2 Web Development for Business 69 UML: Classes -- Association Class1 You
More information