Unit 251 Summary  Requirements may be represented in itemized format or in visual modeling (UML). Once the complete set of requirements are in our hand,

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

GCSE ICT By the end of this session, you will be able to: Explain main features of ATM machines Identify features of credit cards, debit cards, smart cards.
Chapter 4: Requirements Engineering
Computer ScienceSoftware Engineering Slide 1 Requirements/Projects l FAA story l Requirements – specify functionality, constraints, domain restrictions.
PLANNING THE TIC TAC TOE GAME BY NEEL DAVE. TIC TAC TOE INSTRUCTIONS Tic Tac Toe Instructions The basic concept of Tic Tac Toe 1.This is a game for two.
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
Slide 6C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
Requirements Analysis Classes & Associations b510.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
Object Oriented Analysis Process
COMP1007 Intro to Systems Requirements © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Intro to Systems Requirements Lecture 4 Identifying.
©TheMcGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter 1 Introduction to Object-Oriented Programming and Software Development.
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.
©TheMcGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter 1 Introduction to Object-Oriented Programming and Software Development.
From Problem Statement to Design
Object-Oriented Design & Patterns Cay S
Use Case modelling 1. Objectives  Document user requirements with a model  Describe the purpose of an actor and a use case  Construct a use case model.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
Use Case Modeling. Watch the video on use cases Review at minute 2:41-3:37.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.
Slide 1 UML Review Chapter 2: Introduction to Object-Oriented Systems Analysis and Design with the Unified Modeling Language, Version 2.0 Alan Dennis,
Unified Modeling Language, Version 2.0
Putting together a complete system Chapter 10. Overview  Design a modest but complete system  A collection of objects work together to solve a problem.
SWE © Solomon Seifu CONSTRUCTION. SWE © Solomon Seifu Lesson 13-2 Testing.
11 Partnership for Performance How to hear this lecture Click on the icon: to hear the narration for each slide.
Faculty of Computer & Information Software Engineering Third year
ICT and Banks Banks use mainframe computers to maintain customer accounts. They store a record of each customer’s withdrawals and deposits. Each bank mainframe.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
CREATING TEMPLATES CREATING CUSTOM CHARACTERS IMPORTING BATCH DATA SAVING DATA & TEMPLATES CREATING SERIES DATA PRINTING THE DATA.
Patterns and Reuse. Patterns Reuse of Analysis and Design.
Systems Analysis & Design 7 th Edition Chapter 5.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
MODULE 13:. Principles of Information Systems Analysis & DesignDesign © 2009 by Dr. Martin Schedlbauer Visualizing Scenarios UML offers three diagrams.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.
Natural Language to Machine Readable Format By: Damian Tamayo Presentation 2 – Nov. 13, 2009 CIS 895 – MSE Project.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
1 Unified Modeling Language, Version 2.0 Chapter 2.
+ TIC-TAC-TOE GAME CAPSTONE PROJECT SEN Team Members Sno.NameITU ID 1Keerthi Alimity Venkata Ganugapati Sujitha Sanku Bavi Bharathan87550.
Identification of Classes. Object Oriented Analysis (OOA) OOA is process by which we identify classes that play role in achieving system goals & requirements.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Distributed Java Programming Distributed Java Programming Class #1 August 20, 2002.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Chapter 2 (Horstmann’s Book) – Part 1 The Object-Oriented Design Process Hwajung Lee.
Bank Reconciliation Chapter 4. PAGE REF #CHAPTER 4: Bank Reconciliation SLIDE # 2 Objectives Reconcile your checking Create bank reconciliation reports.
Introduction to Unified Modeling Language (UML) By Rick Mercer with help from The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, Ivar.
SWE 214 (071) Introduction to UML Slide 1 Introduction to UML.
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
1 Case Study and Use Cases for Case Study Lecture # 28.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Systems Analysis and Design With UML 2
Object-Oriented Static Modeling of the Banking System - I
Systems Analysis and Design With UML 2
Formal Methods in Software Engineering
Unified Modeling Language
Cash Management Training
Unified Modeling Language
Presentation transcript:

Unit 251 Summary  Requirements may be represented in itemized format or in visual modeling (UML). Once the complete set of requirements are in our hand, we move on to the design phase.  The steps of the object-oriented design process in this chapter are 1.Identify the classes and objects. 2.Describe the object collaborations and the classes. 3.Design the class diagram. 4.Sketch the user interface.

Unit 252  Focusing on the nouns and verbs of the Requirement statements will help you to identify the classes, responsibilities, and collaborations the program must provide. These are recorded using CRC cards, which also list the data attributes of each class. Data is transferred from CRC cards to class diagrams, which are more convenient to reference during subsequent software development activities.  The final step of the object-oriented design is designing the user interface. The user interface is important because it is visible to the user.  From the class diagrams of the design phase, the corresponding Java templates are generated. From the user interface design, the corresponding html templates are written down. These are the outcome of the design phase.  During the Implementation phase, these Java and html templates are coded with proper comments and documentation. These programs are tested using the techniques of unit testing. Now the modules are ready. Summary (cont ’ d)

Unit 253  During the integration phase, these modules are integrated into a product. The product is tested using the various techniques of integration and system testing. Now the product is ready for installation.  During the Deployment and Maintenance phase, the product is delivered to the customer with the user’s manuals.  The user training is an important part of this phase. Then the software is maintained until the end of the contract. Summary (cont ’ d)

Unit 254 Exercises  Here we list the requirements of three projects.  They are similar to the one we discussed as a case study.  These projects are: 1.Banking 2.Train ticket issuing system 3.Tic-tac-toe.  It is a good exercise for the students to implement the projects applying the principles of software engineering.

Unit Banking  You have been asked to develop a banking system for M&P Banking.  Hardware and network portion has already been bought.  You need to write software to manage savings and checking account transactions as well as ATM services.  M&P has one kind of savings and two kinds of checking accounts.  The savings account bears interest at the prevailing rates, compounded monthly.  Savings transactions are free as long as they are carried out at a branch and not at an ATM.  Two checking account options exist.  The Rich Club Account (RCA) bears interest at 1 percent less than the savings account rate, checks are free, and no monthly fee is applied as long as the total balance of all accounts is at least $5,000.  The Poor Slob Club (PSC) has no minimum balance. PSC accounts are charged a monthly fee of $5.00 and each check costs the customer $0.10.

Unit Train Ticket Issuing System  An automated ticket issuing system sells rail tickets.  Users select their destination, and input a credit card and a personal identification number.  The rail ticket is issued and their credit card account charged with its cost.  When the user presses the start button, a menu display of potential destinations is activated along with a message to the user to select a destination.  Once a destination has been selected, users are requested to input their credit card.  Its validity is checked and the user is then requested to input a personal identifier.  When the credit transaction has been validated the ticket is issued.

Unit Tic – Tac - Toe  The game is played on a 3 by 3 square board between two players.  The player who starts (‘Player X’) chooses a square of the board and puts a cross on it.  The other player (‘Player O’) chooses an empty square and puts a naught on it.  Thereafter the players continue to alternate, placing their own marks in empty squares.  The winner is the first player to complete a straight line (horizontal, vertical, or diagonal) of three of his own tokens.  If the board is filled without either player achieving this, the game is a draw.

Unit 258 Tic – Tac – Toe (cont’d)  To develop a framework, we need to consider the following facts and rules: 1.The game is played by two players. 2.The game is played on a square 3 by 3 board. 3.Players move alternatively. 4.To make a move is to alter the state of the bard by adding, removing and/or moving some tokens, which are things on the board. 5.Any token on the board is owned by one or other player. 6.All relevant information is available to both players. 7.Which moves are legal depends on the state of the board – which tokens are where – possibly together with other factors like the history of the play. 8.Who wins depends on the same factors.

Unit 259 Tic – Tac – Toe (cont’d)  (Hint: the human player interacts with a screen representation of the Naught and Crosses board, controlled by the board.  The player clicks somewhere on the board, which causes (by standard mechanisms) a message to be sent to the board, with information about where the click happened.  The board, with help from its squares, works out from the co-ordinates which square of the board has been clicked in.  The board knows that it is Player X’s turn, so the meaning of the click is that X wishes to place a token on the square.  Immediately after each move, the validity of the placement of X in a particular square is checked.  It is also checked whether or not the game is over.  If it is a valid move of Player X and the game is not over, then it is the turn of Player O.  Now the next move will be made by Player O.  The board will wait for the next click, which will represent O’s move.)

Unit 2510  Grady Booch, James Rumbaugh and Iver Jacobson, The Unified Modeling Language User Guide, The Addison Wesley Object Technology Series,  Stephen Gilbert and Bill McCarthy, Object Oriented Design in Java, The Waite Group Inc.,  Cay Horstmann, Big java, 3 rd edition, John Wily & sons,  Stephan R. Schach, Software Engineering with Java, McGraw Hill Publications,  Ian Sommerville, Software Engineering, 6 th edition, Addison-Wesley, References