1 Domain Analysis Model  A Domain Analysis Model (DAM) is a structured way to describe and docu- ment the information requirements of a particular area.

Slides:



Advertisements
Similar presentations
Embedded System, A Brief Introduction
Advertisements

1 Introducing the Specifications of the Metro Ethernet Forum.
© 2011 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary. Towards a Model-Based Characterization of Data and Services Integration Paul.
Computer Science Dept. Fall 2003 Object models Object models describe the system in terms of object classes An object class is an abstraction over a set.
© Copyright 2008, SoftWell Performance AB 1 Performance Testing Distributed Systems Concepts and Terminology v0.6.1.
Chapter 1 Object-Oriented System Development
CLAReT PERSONAS AND SCENARIOS. When? Personas were used in the CLAReT workshops as a role play activity. Participants were required to assume a persona.
Concepts of Systems Theory
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
CSE 322: Software Reliability Engineering Topics covered: Software Reliability Models.
1 درس مهندسي نيازمندي استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت Meaning of Requirement.
OBJECT ORIENTED ANALYSIS & DESIGN Vassilka Kirova Department of Computer & Information Science NJIT.
HAS. Patterns The use of patterns is essentially the reuse of well established good ideas. A pattern is a named well understood good solution to a common.
The meaning of requirements Vahid Jalali October 2007 Amirkabir university of technology, Department of computer engineering and information technology,
Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.
Feb. 23, 2004CS WPI1 CS 509 Design of Software Systems Lecture #5 Monday, Feb. 23, 2004.
Architectural Styles, Design Patterns, and Objects Architectural Styles, Design Patterns, and Objects By Robert T. Monroe, Andrew Kompanek, Ralph Melton,
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Abstraction of Design Motifs. Association In psychology and marketing, two concepts or stimuli are associated when the experience of one leads to the.
Foundations This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the.
Trisha Cummings.  Most people involved in application development follow some kind of methodology.  A methodology is a prescribed set of processes through.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
CIMI + FHIR Grahame Grieve 10-August 2015 Salt Lake City.
Representing variables according to the ISO/IEC standard.
Computer Science School of Computing Clemson University Introduction to Formal Specification Murali Sitaraman Clemson University.
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
11 August 2010Abstract Test Cases 1 Abstract Test Case Development Phil Beecher (BCC) Edge / Enterprise Conformity.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
UNIT 2.
NI ©UNITEN 2000/01 1 Faculty of Applied Engineering and Urban Planning Software Engineering Department Class Diagram Faculty of Information system Technology.
Some Ruminations on the Nature of Software Engineering Dr. M.S. Jaffe
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Engineering 5895: Software Design 9/11/01Class Diagrams 1.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
Software Design: Principles, Process, and Concepts Getting Started with Design.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Data Structures and Algorithms Dr. Tehseen Zia Assistant Professor Dept. Computer Science and IT University of Sargodha Lecture 1.
IT-SOC 2002 © 스마트 모빌 컴퓨 팅 Lab 1 RECONFIGURABLE PLATFORM DESIGN FOR WIRELESS PROTOCOL PROCESSORS.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Assignment Help From Requirements Elicitation to Elicitation.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
ISO/IEC/JTC1 SC32/WG2 Jeju Meeting 2009/06/22-27 Updated 2009/08/17 Masaharu Obayashi (kanrikogaku Ltd.) Basic Idea on MFI-2 core Model.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Fundamentals, Design, and Implementation, 9/e Appendix B The Semantic Object Model.
1 Database Environment. 2 Objectives of Three-Level Architecture u All users should be able to access same data. u A user’s view is immune to changes.
Naming – Concept – Sense – Reference. In semantics, there are two major ways to find out the meaning of a word which then becomes the two major branches.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Class Diagrams Revisited. Parameterized Classes Parameterized Classes - are used to represent relationships between templates.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
IT 5433 LM2 ER & EER Model. Learning Objectives: Explain importance of data modeling Define and use the entity-relationship model Define E/R terms Describe.
ENTITY RELATIONSHIP DIAGRAM. Objectives Define terms related to entity relationship modeling, including entity, entity instances, attribute, relationship.
CPA, MBA BY RACHELLE AGATHA, CPA, MBA Participation & Attendance Chapter 6 Slides by Rachelle Agatha, CPA,
HCS 451 Week 2 Individual Risk Management Assessment Summary To purchase this material click below link 451-Week-2-Individual-Risk-Management-
HCS 451 Week 3 Individual Quality Management Assessment Summary To purchase this material click below link
Data Model Basic Building Blocks
Domain Model Refinement
Theoretical Definition Conceptual Model
פחת ורווח הון סוגיות מיוחדות תהילה ששון עו"ד (רו"ח) ספטמבר 2015
Domain Analysis Model A Domain Analysis Model (DAM) is a structured way to describe and docu-ment the information requirements of a particular area of.
FRAMEWORK OF EVALUATION QUESTIONS
The Generic Statistical Information Model
SDMX Information Model: An Introduction
DATA MODELS.
Chapter 16 Class Diagrams.
Presentation transcript:

1 Domain Analysis Model  A Domain Analysis Model (DAM) is a structured way to describe and docu- ment the information requirements of a particular area of interest (or domain).  It describes the business terms (con- cepts), their characteristics (attributes) and relations.

2 BRIDG

3 Analysis vs. Implementation > ANALYSIS IMPLEMENTATION WHAT to represent HOW to represent  Defines how the concepts are represented on the physical level  Needs to consider constraints of the chosen technology  There may be many different implementation models for one analysis model (typically one per technology)  Depending on its purpose the concepts may not be represented completely  Defines the concepts and the relations of a given domain  Creates an unambiguous terminology to describe the domain  Abstracts away from any implementation issues

4 WHY?  Communication  Communication between humans  Communication between machines

5