1 Info 1409 Systems Analysis & Design Module Lecture 8 – Modelling tools and techniques HND Year 1 2008/9 De Montfort University.

Slides:



Advertisements
Similar presentations
Systems Development Environment
Advertisements

Info1409 De Montfort University Lecture 3 The Systems Development Life Cycle Systems Analysis & Design Academic Year 2008/9.
Ch 3 System Development Environment
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Systems Analysis and Design 8th Edition
Unified Modeling Language
Object-Oriented Analysis and Design
Systems Analysis and Design in a Changing World, Fourth Edition
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Requirements Analysis 8. 1 Storyboarding b508.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Human.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Requirements Analysis 5. 1 CASE b505.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis CASE Computer.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 2.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Info /7 DMU1 The story so far… Systems Analysis & Design Academic Year 2008/9 Lecture 10.
Info1409 De Montfort University1 Requirements Modelling Systems Analysis & Design Academic Year 2008/9 Info 1409 Lecture 7.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Chapter 7: The Object-Oriented Approach to Requirements
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Your Interactive Guide to the Digital World Discovering Computers 2012.
Lesson 1 Week01.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
©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.
Introduction to UML By: Prof. Aiman Hanna Department of Computer Science, Concordia University, Montreal, Canada.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Chapter 7 System models.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
UML What Is the UML? The Unified Modeling Language (UML) is the successor to the wave of object- oriented analysis and design (OOA&D) methods.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Object-Oriented Analysis and Design Fall 2009.
Systems Analysis & Design 7 th Edition Chapter 5.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
Copyright © 2013 Curt Hill UML Unified Modeling Language.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 8 UML Use Case Modelling.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Systems Analysis and Design in a Changing World, Fourth Edition
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 1: Introduction.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
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.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
Use Cases UML. Use Cases What are Use Cases?  A statement of the functionality users expect and need, organized by functional units  Different from.
Testing Tools & Standards
Unified Modeling Language
Introduction to Object Oriented Analysis, Design and Unified Modeling Language (UML) Shanika Karunasekera.
Tools of Software Development
Introduction to UML.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Software Design Methodologies and Testing
Chapter 5.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Presentation transcript:

1 Info 1409 Systems Analysis & Design Module Lecture 8 – Modelling tools and techniques HND Year /9 De Montfort University

2 Objectives The objectives of this lecture are to explain CASE tools Unified modelling language Use Case diagrams

3 Lecture objectives By the end of this lecture you will: Understand the need for specialist tools and methods in systems modelling Have been introduced to Unified Modelling language and its concepts Understand the need for Use Case models.

4 Introduction to system modelling Producing the logical view of a system means: producing graphical models which use non technical language for descriptions. Representing the system at various stages of development Charting business processes and requirements and interactions.

5 CASE tools Computer Aided Software Engineering CASE helps developers design and construct information systems This module will introduce you to a CASE tool in your Lab sessions in term 2

6 The CASE environment Using a CASE tool can: Speed up the development process Plan ‘business driven’ systems Support the software development process Produce models and comprehensive documentation Giving an industry standard for all the above tasks.

7 Definition of CASE tools As early as the 1960’s programmers used tools such as editors and code debuggers to write programs. Today we live in a ‘software driven’ world. CASE tools are now powerful resources that systems analysts need in order to build complex information systems.

8 Definition of a CASE environment by Carnegie Mellon From Shelley et al

9 CASE terms and concepts A typical CASE tool is a set of individual software tools that share information in what is called a ‘Repository’ CASE tools can be used to model, document, engineer and construct the information system They are software tools which can provide the following functions:

10 Individual tools 1. Documentation tool The CASE environment builds up a database of information about the system model and can then produce the necessary documentation.

11 Individual tools (2) 2. Engineering tools These translate business processes into applications, by producing models like Use Case or Data flow diagrams

12 Individual tools (3) 3. Construction tools- This facility generates code, screen layouts and reports in languages such as Java, C++ and VB)

13 FourGen offers a screen generator that can create Data entry screens, and forms, program code and reports Illustration by permission from Shelley et al

14 Future Trends Quote from Shelley Cashman et al (p551) “Traditional CASE software evolved from functional tools (such as code editors) to help developers envision and construct an entire information system”

15 Future Trends Quote from Shelley Cashman et al (p551) “ It is predicted that the next generation of CASE tools will go even further, working with internal and external business processes for organisations”.

16 Unified Modelling language What is Unified modelling language….? Before proceeding, we really need to know.

17 Activity time To answer this question we are going to discuss and brainstorm. You need to group in 3’s for this one

18 Some facts to help you UML is just a syntax. It says nothing about how too create a model UML is well documented but little understood It was developed by Grady Booch, Jim Rumbaugh and Ivar Jacobon at Rational Software UML specifies 8 different diagrams. Not all are used in practice. A use case diagram shows the functionality of the system from the ‘outside in’ Class diagrams show the static structure of the systems

19 Activity time ( Brainstorming) Think about and talk about how you might answer the following question: What IS Unified Modelling Language and what is if for?

20 Unified modelling language is.. Give your definitions here:

21 UML Benefits UML : Uses Object Oriented design concepts Is a popular method of visualising and documenting software systems. Is independent of any specific programming language

22 Benefits of Unified Modelling language UML : Provides graphical tools for example Use Case models Can represent the info system from Users standpoint.

23 Use Case Diagrams During requirements modelling analysts and users together model the system functions A Use Case diagram visually represents the interaction between Users and the Information system Use Case diagrams can be drawn freehand, or using Case tools.

24 In this diagram the Actor is a customer and the Use Case is a credit validation performed by the system.

25 Use Case components cont.. The Use Case is the function that the Actor (user of the system) wants the system to perform It is represented by an ellipse with a written description of what the function needs to be. The line joining the Actor and the Use Case is called an association

26 Use Case components cont.. The Actor is represented by a human figure (usually a stick person) There is a system boundary which is illustrated by the square box in which the activities of the system take place. Please note that the Actor is external to the system – (at the system interface).

27 Use Case documentation It is always necessary to document diagrams in the modelling process. The reason is that analysts and designers work as a team (with Users and with each other). A model alone can be subject to interpretation. A descriptive table to accompany a diagram ensures clarity

28 This table documents the Credit card validation in the previous example

29 Use Case functions The successful completion part of the table outlines the activities that make up the functions of the Use Case. In this case there are 3 Notice that the three activities consist of an input a process and an output

30 Activity time Draw the Use Case example in slide 24. Label its component parts and note down where the inputs/outputs and processes would occur.

31

32 In conclusion At the end of this lecture you have : Been introduced to UML Learned about the use of CASE tools Been introduced to modelling techniques Seen examples of Use Case models Recognised the need for documentation

33 Background reading Chapter 3 – Modelling tools and techniques Pp Part 5 of the Systems Analysis Toolkit from Systems Analysis & Design. Shelley Cashman and Rosenblatt 6th/7th Edition Thomson Course Technology 2006/7