Chapter 6 Review Questions

Slides:



Advertisements
Similar presentations
IT KEY SKILLS LEVEL 1 Evidence required for: A poster or Word document.
Advertisements

E-books and E-journals Off-campus This presentation will show you how to log in and access Oxford Brookes Library e-books and e-journals when youre off.
E-books and E-journals Off-campus This presentation will show you how to log in and access Oxford Brookes Library e-books and e-journals when youre off.
The Complete Administration System for the Domiciliary Care Provider.
Session # 2 SWE 211 – Introduction to Software Engineering Lect. Amanullah Quadri 2. Fact Finding & Techniques.
Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
Extended DISC Online System User Instruction: How to Run a Team Analysis.
Chapter 12 Review Questions
Dispatch Web (DW) Logging an Absence.
Agate Ltd Case Study-Requirments Analysis
System Security & Patient Confidentiality General Lesson 1.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Kabel Nathan Stanwicks, Head Circulation and Media Services Department Electronic Reserves Introductory Tutorial for Faculty.
Documenting Requirements using Use Case Diagrams
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Finding Books in the Library Catalog CARSON-NEWMAN COLLEGE.
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
Chapter 5 Determining System Requirements
03/12/2001 © Bennett, McRobb and Farmer Use Case Diagrams Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Library & Information Services Using the Library Catalogue Part 2: My Account Reserving Items Reading lists Rachael Hartiss 2008.
Start the slide show by clicking on the "Slide Show" option in the above menu and choose "View Show”. or – hit the F5 Key.
03/12/2001 © Bennett, McRobb and Farmer Requirements Capture Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Case Study: Agate’s Information System
CSC271 Database Systems Lecture # 21. Summary: Previous Lecture  Phases of database SDLC  Prototyping (optional)  Implementation  Data conversion.
Start the slide show by clicking on the "Slide Show" option in the above menu and choose "View Show”. or – hit the F5 Key.
Start the slide show by clicking on the "Slide Show" option in the above menu and choose "View Show”. or – hit the F5 Key.
Tutorial 6 DFDs vs. Use Case Diagrams (Textbook Chapter 7 & Appendix)
Start the slide show by clicking on the "Slide Show" option in the above menu and choose "View Show”. or – hit the F5 Key.
Welcome to the University of West Florida Online Employment System Applicant Tutorial.
A Guide to the BIZNET Online Filing System STATE OF CONNECTICUT DEPARTMENT OF CHILDREN & FAMILIES (DCF) DEPARTMENT OF DEVELOPMENTAL SERVICES (DDS) DEPARTMENT.
Chapter 8: Systems analysis and design
Automated OUTLAY REPORT. The is an Excel spreadsheet which is used to track all funds related to the project, from beginning to end.
The Account Executive’s Job Description. Account Service Advertising is an ideas business. People create ideas. Good account executives like working with.
PRJ566 Project Planning and Management
Information Session for Accommodation & Hospitality Staff: Electronic Leave Recording using iTrent.
1 WXGC6102: Object-Oriented Techniques Requirements Capture References: Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Requirements Capture Fact Finding Part 2.
CSE323 การวิเคราะห์และออกแบบระบบ (Systems Analysis and Design) Lecture 03: Requirements Capture Requirements Analysis.
Start the slide show by clicking on the "Slide Show" option in the above menu and choose "View Show”. or – hit the F5 Key.
Creating Questionnaires. Learning outcomes Upon completion, students will be able to: Identify the difference between quantitative and qualitative data.
There are many occasions for fact-finding during the database system development lifecycle. fact-finding is particularly crucial to the early stages of.
Fact-finding Transparencies 1. ©Pearson Education 2009 Objectives When fact-finding techniques are used in the database system development lifecycle.
Database Analysis and the DreamHome Case Study
Database Analysis Fact-finding techniques
Requirements Reference: Chapters 5, 6, & 8. CMSC 345, Fall Objectives To introduce the concepts of user and system requirements To explain functional.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
TRW Code Updates for WCRS Document Activity ERD, EAR Changes December, 2006 Highlights: TRW Automotive December, 2006 TRW Automotive December, 2006 Auto.
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
INFO1002 Systems Modelling Lecture 10 Establishing User Requirements Department of information Systems.
Human Centric Computing (COMP106) Assignment 2 PROPOSAL 23.
The techniques involved in systems analysis Explanation of a feasibility study:Explanation of a feasibility study: –economic, –legal, –technical, –time.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination.
Collecting Qualitative Data
Setting Up TGO User Accounts. Creating User Accounts for Other Users If your company has other users who need to use the Active Orders system, your company’s.
Object-Oriented Analysis and Design Use cases Finding classes Collaboration and Sequence diagrams Associations between classes.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake1 Special Relationships between Use Cases Normally it is not.
Start the slide show by clicking on the "Slide Show" option in the below menu or – hit the F5 Key.
Reform Groups and Analyze Preliminary Designs. Schedule Week 6 Lab Small Group Presentations Form into three large teams Agree on problem statement and.
Topic 2 – Techniques involved in Systems Analysis Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Registering your placement on MAP
Start at 17th March 2012 end at 31th March 2012
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Registering your placement on MAP
Presentation transcript:

Chapter 6 Review Questions

6.1 Read the following description of a requirment for FoodCo, and decide which parts of it are functional requirments and non-functional requirments.

6.1 The allocation of staff to production lines should be mostly automated. A process will be run once a week to carry out the allocation based on the skills and experience of operatives. Details of holidays and sick leave will also be taken into account. A first draft Allocation List will be printed off by 12:00 noon on Friday for the following week. Only staff in Production Planning will be able to amend the automatic allocation to fine-tune the list. Once the amendments have been made, the final Allocation List must be printed out by 5:00 pm. The system must be able to handle allocation of 100 operatives at present, and should be capable of expansion to handle double that number.

6.1 Answer Examples of functional requirements are: the need for a process to be run that allocates staff to lines based on their skills and experience, holidays and sick leave; printing out an allocation list; amending the allocation list.

6.1 Answer Examples of non-functional requirements include: printing the allocation list by 12.00 noon; the need to handle 200 operatives’ details.

6.2 Name the five main fact-finding techniques and list one advantage and one disadvantage.

6.2 Answer Background reading: Advantage: helps to understand the organization before meeting the people and starting to work on site. Disadvantage: written documents may be out of date or not match up to the reality of the organization.

6.2 Answer Interviewing: Advantage – the interviewer can respond to what the interviewee says and direct the interview appropriately. Disadvantage – interviews are time-consuming and thus a costly way of fact-gathering.

6.2 Answer Observation: Advantage – provides firsthand experience of the way the current system operates. Disadvantage – when being observed people may behave differently from how they normally do.

6.2 Answer Document sampling: Advantage – can be used to gather quantitative data on existing volumes of data. Disadvantage – if the system is going to change dramatically, existing documents may not be a good indication of what is required.

6.2 Answer Questionnaires: Advantage – economical way of gathering information from a large number of people. Disadvantage – postal questionnaires can suffer from low response rates.

6.3 Imagine that you will be interviewing one of the three staff in Production Planning at FoodCo. Draw up a list of ten questions that you would want to ask him or her.

6.3 Answer Am I right in thinking that you are responsible to the Chief Planner? There are three of you. Do you all do the same work or do you have different responsibilities? Do you work with any of the other people in this department, for example the Production Control staff? What other parts of the company do you get information from? What other parts of the company do you provide with information?

6.3 Answer What happens when you begin planning the next week’s allocation? Where do you get the information about what factory operatives are available? Where do you get information about what needs to be manufactured? How much of what is manufactured is the same every week? What paper forms do you use in your work?

6.4 What is the purpose of producing use cases?

6.4 Answer Use cases are produced to model the functionality of the system from the users’ point of view and to show which users will communicate with the system.

6.5 Describe in your own words the differences between the <<extend>> and <<include>> relationships in use case diagrams.

6.5 Answer The «include» relationship between use cases is used to separate out common behaviour that takes place in a number of use cases, and put it into a separate use case. All the use cases that require this behaviour then have an «include» relationship with the new use case that contains it. The included use case is always included in the including use case.

6.5 Answer The «extend» relationship between use cases is used to model optional behaviour. Under certain circumstances, the base use case will be extended by the addition of the behaviour in the extending use case. This takes place at an extension point described in the use case description of the base use case and optionally shown in a compartment in the use case on the diagram.

6.5 Example 1.RequirmentTo record which staff are working on which campaigns, including the campaign manager for each campaign. 1.Use caseAssign staff to work on a campaign. 2.RequirmentTo schedule the dates when adverts will be run. 2.Use case Add a new advert to a campaign.

6.5 Example 3. Requirment To check on the status of campaigns and whether they are within budget. 3.Use case Check campaign budget. 4. Requirment When the campaign’s budget is checked the system must be capable of printing campaign summary and invoice.

6.7 Write a use case description in the extended form, used for the Assign staff to work on a campaign and for Create concept note.

6.7 Answer Assign staff to work on a campaign

6.7 Answer Assign staff to work on a campaign Actor Action 1. The actor enters the client name. System Response 2.Lists all campaigns for that client. 3. Select the relevant campaign. 4.Displays a list of all staff members not already allocated to this campaign.

6.7 Answer Assign staff to work on a campaign Actor Action 5. Highlights the staff members to be assigned to this campaign. System Response 6. Presents a message confirming that staff has been allocated.

6.7 Answer Create Concept Note A member of staff working on a campaign can create a concept note, which records ideas, concepts and themes that will be used in advertising campaign. The note is in text form. Each note has a title. The data of the person who created the note, the date and time are also recorded.

6.7 Answer Create Concept Note

6.7 Answer Create Concept Note Actor Action 1. The member of staff requests a list of clients. System Response 2. The system displays a list of clients. 3. The member of staff selects a particular client. 4. The system displays a list of campaigns for that client.

6.7 Answer Create Concept Note Actor Action 5. The member of staff selects a particular campaign. System Response 6. The system displays details of the campaign. 7.The member of staff enters the title of the note. 8. The member of staff enters the full text of the note.

6.7 Answer Create Concept Note System Response 9. The system displays the date and time. Actor Action 10. The member of staff enters his/her name. 11. The system checks that the member of staff is authorized to add notes to that campaign. 12. The member of staff instructs the system to save the concept note. 13. The system saves the concept note.

6.8 Think of the different possible uses you could make of a library computer system and draw a use case diagram to represent these use cases.

6.8 Answer Typical use cases for a library system from the point of view of the user are: Search for a book by title. Search for a book by author. Search for a book by key words. View details of a book. Reserve a book.

6.8 Answer <<include>> Search for book by title View details of a book Reserve a book Search for book by title author Library User key words <<extend>> <<include>>

6.9 List some non-functional requirments of a library computer system that you would not model using use cases.

6.9 Answer The system must be capable of holding details of 20,000 users and 500,000 books. The system will begin to respond to all user search enquiries within 5 seconds. Personal details of users will only be accessible to authorized staff and will be protected using a password system.