©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.

Slides:



Advertisements
Similar presentations
How to Register at My. SSS. Before starting, please ensure you have following : Your SSS Number Your account MNCs SSS Number :
Advertisements

Chapter 7 System Models.
Member Access. This presentation will help you familiarize yourself with the functions of Member Access. Throughout this presentation, you can enter the.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagram Corrected to match newer conventions.
Enquiry Progress Give your vendor code In case of incorrect vendor code / no id registered with us, you will get this error message In case of correct.
Robert B. Jackson Brigham Young University John W. Satzinger
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
Informatics 43 – May 7, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases  No.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
Systems Analysis and Design in a Changing World, Fourth Edition
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
PHP Implementation. Requirements Must run on all platforms (Windows, Mac, Linux). Must be compatible with all common browsers. Must be user friendly.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
InceptionPhase Mesekach Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh.
Follow these instructions to pay your dues. Get into your web browser Like Internet Explorer Now you need type in this address in the Address bar. Example.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Object-Oriented Analysis and Design
The chapter will address the following questions:
Chapter 7: The Object-Oriented Approach to Requirements
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Extended Class Diagram.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering 2.
Member Access. This presentation will help you familiarize yourself with the functions of Member Access. Throughout this presentation, you can enter the.
Group 8: Shenanigans Mike Ostrowski Josh Patsey Michelle Boomer Tom Parks Levent Niazi.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyze and.
GSA’s Vendor and Customer Self Service (VCSS)
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
1 CMPT 275 Phase: Design. Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces Data Persistance.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Architectural Design.
Slide 1 Use Case Sequence Diagram Explained. Slide 2 Steps for Building a Sequence Diagram 1)Set the context 2)Identify which objects and actors will.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Chapter 7 System models.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 4: Restaurant.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Analysis Workflow l The primary activities of the Analysis workflow are.
Plan Design Analyze Develop Test Implement Maintain Systems Development Life Cycle eBookSharing.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
AS Computing Verification. Once sensible data has been entered, the second of method of ensuing data integrity can be employed. Verification is the process.
Use Case Modeling Example By: Dr. Issam Al-Azzoni.
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
Analysis Paralysis We spend so much time thinking about the problem and making sure the next step is “perfect” there is a risk that we never actually.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CMSC 345 Fall 2000 OO Design. Characteristics of OOD Objects are abstractions of real-world or system entities and manage themselves Objects are independent.
SMARTSHOP By: EVN BHARGAV NAGARAJU NAIDU – SASHI TERLI Belligerents.
Member Access. This presentation will help you familiarize yourself with the functions of Member Access. Throughout this presentation, you can enter the.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
Informatics 43 – May 5, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases  No.
1 M206 Chapter 31: An Overview of Software Development 1.Defining the problem 2.Analyzing the requirement – constructing initial structural model 3.Analyzing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
Reception volunteers: How to use the membership administration system
Engineering Quality Software
--Valid address --Course ID --Access Code or
Employee Self-Service (ESS) Portal
Presentation transcript:

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 2 Slide 2 Analysis Model -> Design Model What we Have: At this point in development we have the following: 1) a CLASS DIAGRAM that contains DOMAIN classes with attributes and some methods. 2) Interface Definitions and Navigation Matrix 3) Database Table Definitions 4) Use Cases Identified and Use Case Descriptions

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 3 Slide 3 Design Classes l We HAVE l Analysis classes (domain classes) are those classes identified during the analysis phase of the SDLC. They are the classes recognized by the customers as residing in their domain. l l We NEED l Design classes are needed to implement this system in the world of computing. These classes include various types of classes. l Implementation classes are also needed to implement the system in a particular language.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 4 Slide 4 Design Classes l Design classes include: Use Case Controller Classes User Interface Classes Database Table Classes Classes for Patterns Classes for Frameworks (not covered in this class) Others If we identify the classes that we will actually code. The message analysis table, sequence diagram and extended class diagram will help us do this.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 5 Slide 5 Message Analysis Table l To begin the identification and description of these classes, we construct a message analysis table. l A message analysis table is completed for EACH use case. For our class only one per students will be turned in for a grade. l l The message analysis table is used to drive out the needed design classes, their attributes, their methods, and the messages needed to communicate between the design classes.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 6 Slide 6 Message Analysis Table l This lecture defines the steps for creating the message analysis table. l It shows examples of how the diagram is created and what you will derive out of the activity that will help you to code your software correctly.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 7 Slide 7 Message Analysis Table l Step 1 Identify the use case in question l To begin a message analysis table, we need identify which use case we are addressing. Use Case Name Use Case ID Initiating Actor

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 8 Slide 8 Message Analysis Table l Step 1 Identify the use case in question l VRS Register as Member Use Case Name Register As Member Use Case ID3 Initiating Actor Customer

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 9 Slide 9 Message Analysis Table l Step 2 Identify the use case controller class l The first design class will be the use case controller class. Each use case usually has a controller class to allow it to be called from another class. The standard is naming it CtrUseCaseName. Candidate Objects/Classes Use Case Controller

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 10 Slide 10 Message Analysis Table l Step 2 Identify the use case controller class VRS Register as Member Candidate Objects/Classes Use Case Controller CtrRegisterAsMember

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 11 Slide 11 Message Analysis Table l Step 3 Identify the Domain Classes l Domain The first classes we want to consider are those domain classes on the class diagram.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 12 Slide 12 Message Analysis Table l Step 3 Identify the Domain Classes l Domain Member VRS Register As Member Domain Classes

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 13 Slide 13 Message Analysis Table l Step 4 Identify the Database Classes l Database Classes The second group of classes we wish to have are those classes needed to contain the code to create, reference,and update the data on the database. Each table will have a database class.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 14 Slide 14 Message Analysis Table l Step 4 Identify the Database Classes l Database Classes TblMember VRS Register as Member Database Classes

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 15 Slide 15 Message Analysis Table l Step 5 Identify the Screen and Report Classes l Each individual screen or report will have a class. The navigation diagram for the use case should contain those screens and reports. Display Screens or Report

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 16 Slide 16 Message Analysis Table l Step 5 Identify the Screen and Report Classes l VRS Register as Member – Screens and Reports Display Screens or Report MemberApplicationScreen NewUserNamePasswordScreen ConfirmationScreen

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 17 Slide 17 Message Analysis Table l Step 6 Identify any other use cases l Identify any other use cases that are called or used from this use case. For the VRS Register as Member, there are none. Other Use Cases

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 18 Slide 18 Message Analysis Table l Step 7 Identify any other use cases l Begin developing the messages. First look at each step in the use case description. For each step, determine in more detail what is actually going to happen. Then determine which of the classes will perform that task and thus receive the message to complete the tasks.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 19 Slide 19 Message Analysis Table l Step 1.Customer enters name, address, phone number, address, credit card number, and expiration date of credit card. Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 20 Slide 20 Message Analysis Table l Step 1.Customer enters name, address, phone number, address, credit card number, and expiration date of credit card. Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen The screens will accept information entered from the user.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 21 Slide 21 Message Analysis Table l Step 2. System Validates Member Information Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember The domain classes will validate its attribute data.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 22 Slide 22 Message Analysis Table l Step 3. Customer enters new user name and password information Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember 3acceptUserNamePasswordNewUserNamePasswordScreen Again the screen accepts information from the user.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 23 Slide 23 Message Analysis Table l Step 4. System Validates User Name and Password Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember 3acceptUserNamePasswordNewUserNamePasswordScreen 4validateUserNamePasswordMember, TblMember The domain classes will validate its attribute data. And the database will assure it is not a duplicate user name.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 24 Slide 24 Message Analysis Table l Step 5. Customer confirms membership information. Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember 3acceptUserNamePasswordNewUserNamePasswordScreen 4validateUserNamePasswordMember 5acceptConfirmationConfirmationScreen The screen accepts information from the user.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 25 Slide 25 Message Analysis Table l Step 5. Customer confirms membership information. Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember 3acceptUserNamePasswordNewUserNamePasswordScreen 4validateUserNamePasswordMember 5acceptConfirmationConfirmationScreen 5updateMembershipInformationTblMember The database table class creates a new entry.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 26 Slide 26 Message Analysis Table l Step 6. System s membership confirmation to member. Step #Message NameOwner Class Name 1acceptMemberInformationMembershipApplicationScreen 2validateMembershipInformationMember 3acceptUserNamePasswordNewUserNamePasswordScreen 4validateUserNamePasswordMember 5acceptConfirmationConfirmationScreen 6 MembershipConfirmationMember The domain class has the address so a message is sent to the member and it sends the .