Specification of IT Systems Mandatory Exercise Week 5 Group 3, Søren Vestergaard, Smari Waage,...
-
date post
21-Dec-2015 -
Category
Documents
-
view
216 -
download
1
Transcript of Specification of IT Systems Mandatory Exercise Week 5 Group 3, Søren Vestergaard, Smari Waage,...
Specification of IT Systems Mandatory Exercise Week 5Group 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>
User
Web services
Payment gateway
OTA - Requirements decomposed
Web interface
Reservetravel
element
Canceltravel
element
Search
Web serviceinterfaceUser
Itinerary
Web service
OTA
Paymentservice
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.