1 Specification of IT Systems Mandatory Exercise Week 2 – Group 7 Ebbe Oberlin Flarup Henrik Skaarup Andersen Thomas John Hørlyck Christensen.

Slides:



Advertisements
Similar presentations
Use-Cases.
Advertisements

Artificial Intelligence 2005/06 Partial Order Planning.
Computer System Organization Computer-system operation – One or more CPUs, device controllers connect through common bus providing access to shared memory.
StaffOnline The New Look & Feel January StaffOnline Introduction In keeping up with new technology the StaffOnline has a new look and feel. This.
The paragraph is a series of sentences developing one topic.
MIS 325 PSCJ. 2  Business processes can be quite complex  Process model: any abstract representation of a process  Process-modeling tools provide a.
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
Discovery Jason Gurgal. © SAP AG All rights reserved. / Page 2 Discovery Sherlock Holmes Video:
INVESTMENT GAME IN SOCIAL NETWORK Academic Advisor: Dr. Yuval Alovici Professional Advisor: Dr. Mayer Goldberg Team Members: Ido Bercovich Dikla Mordechay.
© Janice Regan, CMPT 102, Sept CMPT 102 Introduction to Scientific Computer Programming The software development method algorithms.
1 Specification of IT Systems Mandatory Exercise Week 2.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
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.
Academic Advisor: Prof. Ronen Brafman Team Members: Ran Isenberg Mirit Markovich Noa Aharon Alon Furman.
Object Oriented Analysis Process
11 SUPPORTING LOCAL USERS AND GROUPS Chapter 3. Chapter 3: Supporting Local Users and Groups2 SUPPORTING LOCAL USERS AND GROUPS  Explain the difference.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
SoITS assignment 2 Thomas Loftager Nielsen Lasse Deleuran Jacob Mahler-Andersen Group 1.
Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 12. september 2006 Assignment 2 Function Notations for Scoreboard.
1 Introduction Introduction to database systems Database Management Systems (DBMS) Type of Databases Database Design Database Design Considerations.
Introductory case study. 2 The problem The most difficult part of any design project is understanding the task you are attempting You have been contacted.
1 Modeldrevet softwareudvikling – 7. september 2004 Design Methods for Reactive Systems, R.J. Wieringa Part II: Function Notations Jens Bæk Jørgensen,
Administrator’s Guide
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 11 System Test Design
Software Engineering Case Study Slide 1 Introductory case study.
DB Audit Expert v1.1 for Oracle Copyright © SoftTree Technologies, Inc. This presentation is for DB Audit Expert for Oracle version 1.1 which.
Identity & Purpose Desired State Vision 2012 Target Achievements Projection into the external environment Key Successful factors / Value Drivers / Internal.
Object-Oriented Analysis - Instructor Notes
Use Cases 2 ENGR ♯10 Peter Andreae
Data Flow Diagrams.
Systems Analysis and Design in a Changing World, 6th Edition
Requirements Functional requirements  Use-cases
1 BTS330 Vision and Scope. √ Determine a vision for the business √ Create initial use-case model showing key actors and use cases by business area Benefits.
Interaction Modeling Interaction model describes how objects interact to produce useful results. Interactions can be modeled at different levels of abstraction:
1 CSC 221: Introduction to Programming Fall 2012 Functions & Modules  standard modules: math, random  Python documentation, help  user-defined functions,
Understanding User Requirements. Documenting Use Cases 2 At this stage of the exploration, the participants should be thinking of essential use cases.
System Specification Specify system goals Develop scenarios Define functionalities Describe interface between the agent system and the environment.
Introduction to Arrays. definitions and things to consider… This presentation is designed to give a simple demonstration of array and object visualizations.
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
Belgrade stock Exchange
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
1 Meeting the Fiscal Challenge The Achievements of the University of Alberta in Cost Containment and Revenue Enhancement.
Welcome to RISE WEEK 2011 Hosted by. RISE Specialty Membership Groups In addition to our global online memberships, RISE supports specialty membership.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Systems Analysis and Design in a Changing World, 6th Edition
ABM 2009 SERVICE PACK 1 NEW FEATURES. Analysis code now shown when viewing sales If the user has selected one sales analysis code per sale then that analysis.
Sequence Models.
Object Oriented Analysis and Design COM327 week 7 COM252 week 1 Register! (Not petition!)
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Behavior Modeling (based on Alistair Cockburn book) PA116 – L11 (c) Zdenko Staníček, Sept 2010.
INFO1408 Database Design Concepts Week 16: Introduction to Database Management Systems Continued.
REPORTING, ANALYSIS AND PLANNING SYSTEM RAPS Budgeting User Forum April 13, 2011.
G045 Lecture 08 DFD Level 1 Diagrams (Data Flow Diagrams Level 1)
Week 4-5 DBMS Database Design. Database design process can be divided into 6 major steps: 1.Requirements Analysis 2.Conceptual Database Design 3.Logical.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Your Thoughts How are you using technology or how do you want to use technology to help improve the running of your Branch or Centre?
Integrated ISO ILL for staff users Borrowing requests – part two Yoel Kortick 2007.
Now login to your Distributor Panel on
Blackboard Learn 9.1 Communicating with Students © 2010 Blackboard Inc. All rights reserved.
Business Processes A business process describes a set of activities that are necessary to complete a response to a stimulus applied to an organization.
Groundwork to Create a Professional Organization
Business Processes A business process describes a set of activities that are necessary to complete a response to a stimulus applied to an organization.
Requirements Engineering Process
We are living in Society, where everyone wants to live a simple life without any complications in Society Management. But as they live in housing societies,
Customer Contract Management Scenario Overview
An example design for an Amadeus APIv2 Web Server Application
Customer Contract Management Scenario Overview
Transactions and Concurrency
Simplify Your Sales Process
Presentation transcript:

1 Specification of IT Systems Mandatory Exercise Week 2 – Group 7 Ebbe Oberlin Flarup Henrik Skaarup Andersen Thomas John Hørlyck Christensen

2 Mission statement z#1: Mission statement z***************** zThe following mission statement was made, after the creation of a goal tree and 3 refinement trees, which made it easier to map out the specific responsibilities the system should handle. There is a form of mapping from responsibilities to goals and thus we get a sort of consistency when reading through all the project material. zName : Netcafe Management System zAcronym : NCMS zPurpose : z- To support effective and efficient management of Net Cafes zResponsibilities : z- Support automatic administration of user groups z- Support automatic tracking of time and money z- Support efficient and effective administration of user PCs z- Support effective security management zExclusions : z- Does not manage sales. z- Does not manage inventory z- Does not handle staff work planning z- Does not support user waiting lists z- Does not support reservation of user PCs

3 Goal tree

4 Function refinement tree

5

6

7 Service descriptions zName : Unlock PC zTriggering event : The administrator selects a PC from the administrator panel and unlocks it. zDelivered sercice : The selected PC unlocks and the automatic timer starts. zAssumptions : The administration panel detects that the PC is online and locked. zName : Create member zTriggering event : The administrator enters member data and requests that the member is created. zDelivered sercice : A member is created with the entered member data. zAssumptions : A guest requests membership of the netcafe. zName : End user session zTriggering event : An administrator locks a PC. zDelivered sercice : The session timer stops and the system calculates the amount of money owed by the user based on price structure, time used and membership type. zAssumptions : The PC was online and in use by a user.

8 Solution discussion zMission statement: zOur responsibilities of our system are inspired by our goals which we identified in the goal tree. However we tried to remind ourselves of which value they had for our system and what they would contribute with when organizing them, Our exclusion list is pretty elaborate as there is a number of things we want to point out to stakeholders that they can not expect the system to do. We’ve tried to follow the guidelines put up in the book and to keep the mission statement clear, simple and explanatory. zFunction refinement trees (FRT): zWe have tried to organize our FRTs such that the subfunctions combined describes the higher level functions, so that everything combine describes the desired effect we want. Furthermore we have tried to keep the functions true to the responsibilities in the mission statement as described in the book. zService description: zThe service descriptions are kept value-oriented. This means that we have saved all the individual details, condtions and preconditions for later and strictly focused on which value the service gives to the environment. Short yet explanatory as according to the book.

9 Connections zOur mission statement is an abstract representation of the desired functionality. zThe SuD is, according to our mission statement, responsible for tasks such as zmaking user group administration and tracking of time and money, automatic. zFurthermore it's responsible for making administration og user PC's and security zmore efficient and effective. zOur goal tree takes the abstract representation og our SuD from the mission statement zand subdivides it into goals we need to fulfill to make our system live up to our zoverall goals. zThe function refinement trees moves on from the goal tree to further specify what it ztakes to make a specific function do what it is supposed to do. zLastly we need to specify some of the services in the system, what triggers them, and zwhat they need to deliver. The services in the SuD has been chosen based some of the zthings that makes the function refinement trees fulfill their purpose.