Specification of IT Systems Mandatory Exercise Week 5 Group 3, Søren Vestergaard, Smari Waage, Belma Boyraz, Jannick Hoy.

Slides:



Advertisements
Similar presentations
Software Architecture Design Chapter 12 Part of Design Analysis Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Advertisements

Toward an Agent-Based and Context- Oriented Approach for Web Services Composition IEEE TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING, VOL. 17, NO. 5,
Executional Architecture
Architecture. Outline Example Decomposition Style Activity 1.
Software Engineering-II
Practice data flow diagramming as a tool for structured system programming (process modelling) DATA FLOW DIAGRAMs.
DATA FLOW DIAGRAM (PART 2)
WEST Presented By 3s. Introduction Project Overview Project Overview Use Case Diagram Use Case Diagram Domain Model Diagram Domain Model Diagram UI for.
Website For Traveling! by : Hammad Abed, Rabie Loulou Supervisor : Viktor Kulikov Spring 2009 The Faculty of Electrical Engineering - Softlab.
SoITS aflevering 5 Thomas Loftager Nielsen Lasse Deleuran Jacob Mahler-Andersen Gruppe 1.
1 Specification of IT Systems Mandatory Exercise Week 5 Jonas B. Jorgensen, Rune Simonsen, Torsten Aaboe Andersen, Jesper G.
Specification of IT Systems Mandatory Exercise Week 3 Group 3, Søren Vestergaard, Smari Waage, Belma Boyraz, Jannick Hoy.
Design of Web-based Systems IS Development: lecture 10.
Communication Notation Part V Chapter 15, 16, 18 and 19.
1 Discussion Class 9 User Interfaces. 2 Levels of usability interface design functional design data and metadata computer systems and networks conceptual.
Architecture External Web Services Supported Services Repository LMS Services Domain Model Process Container Process Instance Course Sequencing Presentation.
MSc Publishing on the WWW Web Design Week 2. Aims and Objectives To introduce the stages of web design and implementation To introduce needs analysis.
Advanced Accounting Information Systems
Systems Analysis and Design in a Changing World, 6th Edition
Specification of IT Systems Mandatory Exercise Week 4 Group 3, Søren Vestergaard, Smari Waage, Belma Boyraz, Jannick Hoy.
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
CRM WEB UI – ARCHITECTURE- DEFINITIONS For More details please go to
Use Case Diagrams Week 1 – Lab 1.
CC2007N: Design.
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
Requirement Analysis Functional & Non-Functional Requirements Scenarios Use cases: – View Fixtures – Manage Tournament – Register Team – Report Discrepancy.
Data Flow Diagrams.
Data Flow Diagrams (DFD). ScenarioCriteriaTasks Data flow diagram(DFD) is a diagram of the movement of data between external entities.
An Introduction to Software Architecture
History of ERP Some components of this lecture is based on: Watson, E. & Schneider, H. (2000) “Using ERP Systems in Education”. Communications of the AIS.
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 12.
Object Oriented Design Jerry KotubaSYST Object Oriented Methodologies1.
Software Breakdown. Monday, October 26, 2009 CS410 Green Team Fall High Level Architecture.
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 6 - Tutorial Guided Tutorial.
Project Dragon Small Business Website Content Management System.
Network Monitoring Through Mobile (MOBTOP) Developed By : Akanksha Jain. (102199) Deepika Reddy (102210) Team Name: Beans Guided By: Prof. Robert Zhu SUBMITTED.
Intro to Jackson Software Engineering Oct 6, 2005.
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
Lyra – A service-oriented and component-based method for the development of communicating systems (by Sari Leppänen, Nokia/NRC) Traditionally, the design,
Project Methodology May 2, System Development Life Cycle Overview.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 14 Database Connectivity and Web Technologies.
Object Oriented Design Jerry KotubaSYST Object Oriented Methodologies1.
Web application architecture1 Based on Jim Conallen: Web Applications with UML.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
UOFS Information System Version 0.9 Yaodong Bi Copyright 2009, Yaodong Bi.
Context Diagram This section includes two parts. Part 1: Description of a Context Diagram Part 2: How To construct a Context Diagram.
Incorporating Cooperative Portlets in Web Application Development Nathalie Moreno, José Raúl Romero, Antonio Vallecillo Universidad de Málaga {vergara,jrromero,av}
Chapter 5 – Software Tools. 5.1 Introduction Tools valuable for –Specification –Interface Building –Evaluation.
ISMT221 Information Systems Analysis and Design Use case diagram Lab 4 Tony Tam.
Existing architecture GSM network GSM network IMS Voic GSM users migration ?
From Coulouris, Dollimore, Kindberg and Blair Distributed Systems: Concepts and Design Edition 5, © Addison-Wesley 2012 Slides for Chapter 9 Web Services.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
Decomposition of Context Diagram for Seminar Registration System
DATA FLOW DIAGRAM (PART 2)
DATA FLOW DIAGRAM PART 2.
MGMT 340 Enthusiastic Study/snaptutorial.com
INFS 6225 Object-Oriented Systems Analysis & Design
Project 1 Guide System Analysis & Design
Unified Modeling Language
Analysis models and design models
واسط كاربري هوشمند Intelligent User Interface
Activity Model – step-by-step instructions and templates
Software Architecture & Design
Presentation transcript:

Specification of IT Systems Mandatory Exercise Week 5 Group 3, Søren Vestergaard, Smari Waage, Belma Boyraz, Jannick Hoy

OTA - Context diagram Communication between SuD and the external entities that make up the composite system. A user communicates with the system through his browser, which then sends and receives in/output from the SuD, which in turn interfaces with the external web services of the different travel element types to produce the desired system functionality.

OTA - Requirements decomposed

OTA - Decomposition continued Function based architecture. Main functions include: Reserve, cancel, and search, some of which interface directly with the web service. Partly communication oriented. User communicates with system through one common interface, namely the web site. Communication between web services and system is handled by one component.

OTA - Argumentation As a result of the method used in the decomposition, the functional approach, the functions of the diagrams will correspond roughly to the functions defined in the refinement tree. One exception being the “edit” function, which has been shelved because of lacking support in web services.