Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

1342 Final Studio Presentations

Mobile Library & Event Management System (MLEMS)
by

Stephen Tracy

on 13 August 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of 1342 Final Studio Presentations

Mobile Library & Event
Management System

Mobile Library & Event Management System (MLEMS)
Agenda
Combining Library Management and Event Planning for a Mobile Library Event Management System (MLEMS)

Agent- and Goal-Modeling for Architecture



Architectural Style and Design

Requirements Change and Architectural Change

Questions?
Tropos Models
NFR Models
Combining Library Management and Event Planning
Original Project: Mobile Library Management System (MLMS) makes it easy to use library web site functionality on mobile devices.

Added Project: Campus Events Planner (CEP) provides a single portal to discover events going on around campus.

Combined Project: Mobile Library Event Management System (MLEMS) combines these functions to assist university students at both work and play.
4
3
2
Major Stakeholders of MLEMS
5
Actor Diagram for MLEMS
5
Extended Actor Diagram
6
7
Capability
8
9
NFR Framework
9
10
Security
11
Performance
12
Usability
Scalabilty
13
13
Conceptual correlation catalogue
14
15
Architectural Block Diagram
16
17
18
Library Retrieval Services – these functions refer to accessing required to access library and catalogue resources, including call numbers for physical resources and links to online resources.

Bibliographic Information Services – these functions refer to ways to use bibliographic data about physical and online resources, including saving, emailing, or sending to a third party citation manager.

Communication Services – these services refer to communication between the user and the library, and include live chat with librarians as well as requests to renew materials and receiving notification about overdue items and marked events.
Event Information Submission Services – these functions refer to posting an event, including submitting an event to be posted, updating a posted event and pre-approving a user as a pre-approved event poster.

Event Information Retrieval Services – these functions refer to event discovery, including searching for events, subscribing to an event RSS, marking, emailing, responding to and commenting on events.
Event Info Services
Library Catalogue Services
System Services, and Mixed Library and Event Services
System Services – these services allow the user to access restricted services, and include login and updating user information.

Event/Library Locator Services – these functions refer to locating a physical resource in a library, or to locating an event.
Inputs & Outputs
19
20
21
All blocks in the architecture are derived from TROPOS Step 1.
22
All blocks in the architecture are derived from TROPOS Step 1.
All blocks in the architecture are derived from TROPOS Step 1.
23
All blocks in the architecture are derived from TROPOS Step 1.
24
Main blocks are derived from the main system actors.
More deeply embedded blocks refer sub-actors in the system.
One distinction is that there are two logically distinct but physically identical systems, namely the library locator and the event locator. These are distinguished in the TROPOS diagram because they refer to sub-actors of different actors, but they are united in the architecture, because the functions are ultimately performed by the same mechanism.
There is a terminological difference, in that the TROPOS model refers to actors within the system where the architecture block diagram refers to the function
The TROPOS diagram displays both the logical architecture (in terms of goals and actors) and how this architecture was derived, whereas the architectural block diagram displays only the final architectural design. This makes the block diagram easier to understand, but it means that the block diagram does not convey as much information.
Comparing Agent- and Goal-Models with Architectural Block Diagrams
Requirement Change and Architectural Redesign
The change that we introduced into our application is the introduction of the ability to pay library fees for overdue materials online, using a credit card.

We anticipated that this new requirement would have a serious impact on our security requirements, because we now have to manage access to credit information.
25
26
NFR Redesign
NFR Redesign
Before change
After change
Actor Diagram Redesign
Extended Actor Diagram Redesign
Block Diagram Redesign
27
28
29
30
Capability
Questions?
Full transcript