Case study: A museum information system

Slides:



Advertisements
Similar presentations
Brad Berdine Brian Henze Beth Cohlman Bryan Schiele.
Advertisements

Slide 1 Shall Lists. Slide 2 Shall List Statement Categories  Functional Requirements  Non-Functional Requirements.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 12 – 11 – 2011 College Of Computer Science and Information, Information Systems.
System Center Configuration Manager Push Software By, Teresa Behm.
Objectives Overview Define the term, database, and explain how a database interacts with data and information Define the term, data integrity, and describe.
CT1404 Lecture 2 Requirement Engineering and Use Cases 1.
CS 501: Software Engineering Fall 2000 Lecture 14 System Architecture I Data Intensive Systems.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 10 Managing a Database.
Living in a Digital World Discovering Computers 2010.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
EMu and Archives NA EMu Users Conference – Oct Slide 1 EMu and Archives Experiences from the Canada Science and Technology Museum Corporation.
Computer System System Software. Learning Objective Students should understand the different types of systems software and their functions. Students should.
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
INFO 355Week #61 Systems Analysis II Essentials of design INFO 355 Glenn Booker.
Your Interactive Guide to the Digital World Discovering Computers 2012.
Discovering Computers Fundamentals, 2012 Edition Your Interactive Guide to the Digital World.
Objectives Overview Define the term, database, and explain how a database interacts with data and information Define the term, data integrity, and describe.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
System Specification Specify system goals Develop scenarios Define functionalities Describe interface between the agent system and the environment.
Introduction to the Requirements Document
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
Auditing Information Systems (AIS)
1 Texas Regional Entity 2008 Budget Update May 16, 2007.
Objectives Overview Define the term, database, and explain how a database interacts with data and information Describe the qualities of valuable information.
Chapter 1 Introduction to Databases. 1-2 Chapter Outline   Common uses of database systems   Meaning of basic terms   Database Applications  
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
Introduction Database integral part of our day to day life Collection of related database Database Management System : software managing and controlling.
Database Administration
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Chapter 9 Database Management. Objectives Overview Define the term, database, and explain how a database interacts with data and information Describe.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 13 Usability 1.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Hardware & Software Lesson 3 Software KS3 COMPUTING KS3 Computing
AMHS (ATS Message Handling System)
Computer Applications
Information and documentation media systems.
Classifications of Software Requirements
District And Club database
Evaluation Forms for Blockchain- Based System ver. 1.0
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
PastPerfect.
Software Quality Assurance Software Quality Factor
Chapter Ten Managing a Database.
Developing Information Systems
Introduction to Operating System (OS)
Designing Information Systems Notes
Database Management Systems
E5-Requirements? What requirements?
CS & CS Capstone Project & Software Development Project
Chapter 2 Database Environment Pearson Education © 2009.
UNIT II.
Charakteristiky kvality
Introduction to Databases Transparencies
Requirements Walk-through
Database Environment Transparencies
Compliance….GlobalSearch……WHAT?!?!
Pack Your Park by Modernizing Your Business Online
LO2 - Be Able to Design IT Systems to Meet Business Needs
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
Working Group on Rail Transport Statistics:
AUDITS----SINGLE AUDIT CONCEPT, COMPLIANCE
In-house Developed Library Solutions
User Requirements: The user requirement(s) document (URD) or user requirement(s) specification is a document usually used in software engineering that.
ISO/IEC Systems and software Quality Requirements and Evaluation
iSecurity Password-Reset Training
Presentation transcript:

Case study: A museum information system A museum requires an automated information system for use by visitors which helps them locate items in the museum with range of artefacts and to find out more about items which are on display. Due to budget cut backs the new system must run on the existing museum network, which consists of touch screen kiosks and standard PCs. Factors which should be taken into account in specifying and designing this system are: The system must be a 'walk up and use' system for visitors who have no training whatsoever in computer system use. You will need to be able to manage the location of items on that floor plan. Information about specific items should be accessible by indicating their location. You should be able to find an art object by the type, material, age, origin, or other categories you might discover. The system will have to manage multi-media information - sound, images and video. It must be possible for museum staff to change the information in the system and to add information about new exhibits. When you give people information about where to find an item, they respond best to simple instructions made with reference to prominent landmarks rather than maps which they often find difficult to read.

Context Diagram Security System Maintenance Exhibits System Database Museum System Google Maps Museum Maps Museum Stock System

Interact with the system Use Case Diagram MUSEUM SYSTEM Interact with the system

Look for exits/toilets Use Case Diagram MUSEUM SYSTEM Look for exits/toilets Search for an exhibit Get exhibit Details

Look for exits/toilets Use Case Diagram MUSEUM SYSTEM Look for exits/toilets Specify category <<extend>> Search for an exhibit <<include>> Specify exhibit name Get exhibit Details

Functional Requirements Pick 4-6 of the below and write 2-3 sentences about each of them. Indicating whether or not that requirement applies for this case study. Business Rules Transaction corrections, adjustments and cancellations Administrative functions Authentication Authorization levels Audit Tracking External Interfaces Certification Requirements Reporting Requirements Historical Data Legal or Regulatory Requirements

Non-Functional Requirements Pick 4-6 of the below and write 2-3 sentences about each of them. Indicating whether or not that requirement applies for this case study. Serviceability Security Regulatory Manageability Environmental Data Integrity Usability Interoperability Performance – for example Response Time, Throughput, Utilization, Static Volumetric Scalability Capacity Availability Reliability Recoverability Maintainability