Software Development Steps for CSE116

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

Feb 2003 R McFadyen1 Contracts (Ch 13) Used to help understand requirements more completely based on assertions; assertions are applicable to any.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
Web Order Software Requirements Specification. Purpose This Software Requirement Specification provides a complete description of all the functions, constraints.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
6/8/991 Analysis Tuesday 09/14/99 Revised: September 11, 2000 (APM)
Unified Modeling Language 7/12/2015B.Ramamurthy1 The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson, and Jim Rumbaugh.
1 Case Study: Starting the Student Registration System Chapter 3.
Chapter 13: Designing the User Interface
Domain Modeling Chandan R. Rupakheti and Steve Chenoweth Week 5, Day 1.
Chapter 5: Modeling Systems Requirements: Events and Things
Modeling Systems Requirements: Events and Things.
IT 244 Database Management System Data Modeling 1 Ref: A First Course in Database System Jeffrey D Ullman & Jennifer Widom.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
1 ECCF Training 2.0 Platform Specific Model (PSM) ECCF Training Working Group January 2011.
2/6/01D-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Using PARTS to Illustrate Requirements Concepts.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Kyung Hee University System Functional Model OOSD 담당조교 석사과정 이정환.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
Business Analysis with For PG MDI, Gurgaon Kamna Malik, Ph.D.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
Understanding Requirements
UML - Development Process 1 Software Development Process Using UML.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
OO DomainModeling With UML Class Diagrams and CRC Cards Chapter 6 Princess Nourah bint Abdulrahman University College of Computer and Information Sciences.
Chapter 1 © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 1: The Database Environment and Development Process (Contd..) Modern Database.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
 System Requirement Specification and System Planning.
R R R CSE870: UML Component Diagrams Implementation Diagrams.
Why is Design so Difficult? Analysis: Focuses on the application domain Design: Focuses on the solution domain –The solution domain is changing very rapidly.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
Elaboration popo.
Types and Characteristics of Requirements
Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA
Component and Deployment Diagrams
Working in the Forms Developer Environment
CMPE 280 Web UI Design and Development August 29 Class Meeting
Used to help understand requirements more completely
Objectives Importance of Requirement Engineering
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 5: Object Oriented Analysis and Design
Unified Modeling Language
Week 10: Object Modeling (1)Use Case Model
UML Use Case Diagrams.
Today in OOAD Today in Lab Review EU-Lease Assignment (Vision)
OO Domain Modeling With UML Class Diagrams and CRC Cards
FUNCTIONALITIES ON iPAD
Requirements Elicitation – 1
The Process of Object Modeling
Unified Modeling Language
OO Domain Modeling With UML Class Diagrams and CRC Cards
Requirements Reference: Software Engineering, by Ian Sommerville, 6th edition, Chapters 5, 6, & 8.
Software Requirements Specification Document
Real-time (OO) Systems Design Using UML
Analysis models and design models
Software Design Lecture : 15.
Unified Modeling Language
Understanding and Designing with EJB
Accounting Information Systems: A Business Process Approach
Software Development Process Using UML Recap
Presentation transcript:

Software Development Steps for CSE116 B.Ramamurthy 12/25/2018 B.Ramamurthy

Steps in Software Development Problem Statement (Project handout) Requirements (See Ch. 5 of UML book) Use Case (See Ch. 6 of UML book) Conceptual Model (See Ch.9, 10 of UML book) Implementation (Code : use your Java knowledge and Main’s text) Testing (Individual classes/units and the integrated application) 12/25/2018 B.Ramamurthy

Requirements Requirements are description of needs or desires for a product. Primary goal of the requirements phase is to identify what is really needed, in the form that clearly to the client and to the development team. Challenge is to define the requirements such that there is no surprises when the product is delivered. Artifacts: Overview statement (5.3), Customers (5.4), Goals (5.5), System functions (5.6), System attributes (5.7) 12/25/2018 B.Ramamurthy

On to analysis… Overview statement: Customers: Goals: The purpose of this project is to create a wireless device (emulator) for fast-food ordering. Customers: McBurger Queen Inc., a fast food chain. Goals: Allow users to order from anywhere. Avoid long lines at the drive through counter. Enable fast service for the customers. 12/25/2018 B.Ramamurthy

Analysis …(contd.) System Functions: This are a list of what the system is supposed to do. Functional requirements of the form The system should do <X> System function categories: Evident (should perform) Hidden (should perform) Frill (optional) 12/25/2018 B.Ramamurthy

Functional Requirements Ref# Function Category R1.1 Provide interface for customer to place order evident R1.2 Add each item ordered to a list hidden R1.3 Display price for current item evident R1.4 Display total price evident R1.5 Record sales out of scope R1.6 Provide persistent storage out of scope Basic Functions are listed above. You may add on others. Payment related functions will be considered in the next Project. 12/25/2018 B.Ramamurthy

System Attributes System attributes are non-functional qualities of the system such as response time, ease of use, cost, platforms etc. 12/25/2018 B.Ramamurthy

System Attributes Attributes Details, Boundary constraints Response time Reasonable (specify numbers) Interface metaphor Graphical, color Fault tolerance Graceful degradation of services Platform Solaris 2.8 For a large project you may want to relate this to the functional requirement table as shown in page 46. 12/25/2018 B.Ramamurthy

Use Cases Use case is a narrative document that describes the sequence of events of an actor using a system to complete a process. 12/25/2018 B.Ramamurthy

Use Case : example Use Case : Order items Actors : Customer, order taker(cashier/food preparer) Description :A customer arrives at a WD116, looks at display/interface, selects items one by one, confirms choice, may cancel current item. Confirms complete order. Order is delivered to customer. Items ordered include burger, drinks of different sizes, and side order. Money transaction is out of scope for this project. 12/25/2018 B.Ramamurthy

Conceptual Model A conceptual model is a representation of the concepts in a problem domain. It may show: Concepts Association between concepts Attributes of the concepts 12/25/2018 B.Ramamurthy

WD116 Conceptual Model : version1.0 Item MenuDisplay Order Side Burger Drink PriceChart 12/25/2018 B.Ramamurthy