Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS6359 -- John Cole.

Slides:



Advertisements
Similar presentations
Point of Sale (POS) Client & Back Office Server. Operational Concept What is our Objective? What is our Objective? What are our Goals? What are our Goals?
Advertisements

presents Revcon TechnoloGy Group The Affordable Point-of-Sale Fee Computer Offering you More Power More Flexibility More Options than the higher priced.
Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
Chapter 5 Evolutionary requirements –Expect change! –Learn as you go –Validate as you build Why – 25% requirements change on an average software project.
Cash Register Express POS Software. Why Computerize? ● Speed Customer Checkout (faster than a cash register) ● Reduce Theft (2 %) ● Reduce Shrinkage (2.
© 2003, Educational Institute Chapter 6 Point-of-Sale Technology Managing Technology in the Hospitality Industry Fourth Edition (469T or 469)
Object-Oriented Analysis and Design
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
Requirements Specification
Understanding Requirements
Copyright ©2004 Cezary Z Janikow 1 Use Cases n Within Requirements discipline/workflow n Verbal descriptions of important functional (behavioral, transactional,
NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman.
Inception What needs to be done? Describe the vision and business case for this project. Determine if the project is feasible. Determine if the enterprise.
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
Chapter 3 Case Studies.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Requirements Engineering
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1 Requirements Analysis Document Template 1.Introduction.
The first step in getting what you want is to decide what you want.
TRANSACTION PROCESSING SYSTEM Liew Woei Song Muhammad Hofiz Achoson.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
IDENTIFYING OTHER REQUIREMENTS Write a Supplementary Specification, Glossary, and Vision. Compare and contrast system features with use cases. Relate the.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
Lecture 3: Information Engineering Dr. Taysir Hassan Abdel Hamid November 3, 2014.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
Software Requirements Engineering CSE 305 Lecture-2.
Introduction to the Requirements Document
Software Architecture in Practice Architectural description (The reduced version)
Inception Is there a project in there? What’s the vision, scope & business case?
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
Object-Oriented Analysis and Design Jan 14, 2009.
Chapter 7 Applying UML and Patterns -Craig Larman
Chapter 7 Applying UML and Patterns Craig Larman
Jan 7, A UP project organizes the work and iterations across four major phases: – Inception -- approximate vision, business case, scope, vague estimates.
Control Systems Design Part: FS Slovak University of Technology Faculty of Material Science and Technology in Trnava 2007.
OOSE Use Case. Requirement Functional: –Features, capabilities, and security Non Functional: –Usability: Human factors, help, and documentation –Reliability:
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
Chapter 9 Applying UML and Patterns -Craig Larman
Object-Oriented Analysis and Design Jan 21, 2009.
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
OO Methodology Inception Phase.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Chapter 36 More Object Design with GoF Patterns 1CS6359 Fall 2011 John Cole.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Software Engineering 1 Object-oriented Analysis and Design Chap 24 Iteration 2 More Patterns.
Understanding Requirements Chapter 5 Applying UML and Patterns -Craig Larman.
INTRODUCTION to MIS 12/24/20151 Introduction To MIS Component Overview.
IntellAgile Copyright © 2002 Craig Larman. All rights reserved. Writing Use Cases: Requirements in Context.
Understanding Requirements
Learning Objectives Understand the concepts of Information systems.
Chapter 8: Iteration 1 - Basics.  We review here the requirements for first iteration of our case studies. They are a subset of the requirements as described.
CSC480 Software Engineering Lecture 7 September 16, 2002.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Elaboration popo.
Evolutionary requirements
(Professional Business Analyst Training organisation)
Chapter 5 – Requirements Engineering
Writing Use Cases.
Unified Process(UP) popo.
OCR GCSE ICT Data capture methods.
Database Systems Chapter 1
Evolutionary Requirements
Other Requirement Artifacts
Chapter 6: Principles of Requirements Analysis
Chapter 5 Evolutionary requirements
Software Requirements Specification (SRS) Template.
Software Requirements
Other System Requirements
Presentation transcript:

Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole

Other Requirements Artifacts Supplementary Specification: Such as reports, documentation, packaging, supportability, licensing, etc. Glossary: terms used Vision: Short summary of overall product Business rules: rules that affect more than one application, such as tax laws, employee discounts, etc. 2CS John Cole

How Thorough? At inception, not very. Writing the Vision and the Supplementary Specification clarify a first approximation of the product. Written requirements will seldom be completely accurate. 3CS John Cole

FURPS+ for NextGen POS Functionality Logging and error handling Pluggable rules Security 4CS John Cole

Usability Text visible from 1 meter Avoid colors associated with color blindness Speed and ease of use are essential 5CS John Cole

Reliability Failure of external systems such as payment should be solved with a local solution, such as store and process later Prove critical parts of your system correct Good error handling 6CS John Cole

Performance Quick lookup of items Quick processing of payment (Implies good database design, efficient algorithms) 7CS John Cole

Supportability Adaptability to different kinds of users. Different stores using a POS have different rules. Configurability: network configurations, credit card processes, etc. 8CS John Cole

Implementation Java language Perhaps MySQL 9CS John Cole

Hardware Interfaces Touch screen monitor Barcode scanner Receipt printer Credit card reader Signature reader 10CS John Cole

Software Interfaces Tax calculator Accounting system Inventory 11CS John Cole

Vision Introduction Positioning Stakeholder descriptions High-level goals User-level goals Product overview Summary of features 12CS John Cole

Writing the Feature List Terse is good Use cases are not sufficient 13CS John Cole

Glossary Description Aliases Format (for data elements) Relationship to other elements Range of values Validation rules 14CS John Cole

Domain Rules Could apply to more than one project Should be in a separate document 15CS John Cole