Software Tools Lecture 10: Software Tools Dr Valentina Plekhanova University of Sunderland, UK.

Slides:



Advertisements
Similar presentations
Chapter 26 Legacy Systems.
Advertisements

Chapter 27 Software Change.
© Keith G Jeffery, Anne G S Asserson GL 11 Washington Keith G Jeffery Director, IT & International Strategy, STFC
ASYCUDA Overview … a summary of the objectives of ASYCUDA implementation projects and features of the software for the Customs computer system.
Configuration management
1 UML ++ Mohamed T IBRAHIM University of Greenwich -UK.
Lecture 1: Software Engineering: Introduction
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software processes 2.
Lecture 9: Implementation Dr Valentina Plekhanova University of Sunderland, UK.
Lecture 6: Software Design (Part I)
Lecture 5: Requirements Engineering
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 1: Introduction.
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Prescriptive Process models
Database Administration
14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Improving System Safety through Agent-Supported User/System Interfaces: Effects of Operator Behavior Model Charles SANTONI & Jean-Marc MERCANTINI (LSIS)
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Alternate Software Development Methodologies
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
11.1 Lecture 11 CASE tools IMS Systems Design and Implementation.
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Lecture 2: Software Production & Processes Dr Valentina Plekhanova University of Sunderland, UK
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Introduction to Systems Analysis and Design
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 System and Software Engineering.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Overview of the Database Development Process
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
SEMINAR ON :. ORGANISATION Organizations are formal social units devoted to attainment of specific goals. Organizations use certain resources to produce.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Melissa Armstrong – Sponsor Dr. Eck Doerry – Mentor Greg Andolshek Alex Koch Michael McCormick Department of Computer Science SolutionProblemDesign User.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
Where it all comes together.  The Adaptive Mosaic Reporting Technology begins with the concept of a Mosaic.  A Mosaic Report is constructed by assembling.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Lecture 2 Intro. To Software Engineering and Object-Oriented Programming (1/2)
Lecture 4: Software Process Management Dr Valentina Plekhanova University of Sunderland, UK
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
 Many models have been proposed to deal with the problems of defining activities and associating them with each other  The first model proposed was the.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
CASE (Computer-Aided Software Engineering) Tools
Appendix 2 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Business System Development
Tools of Software Development
Chapter 4 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
Object Oriented Analysis and Design
Modern Systems Analysis and Design Third Edition
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Software Tools Lecture 10: Software Tools Dr Valentina Plekhanova University of Sunderland, UK

Lecture 10Valentina Plekhanova 2 Background There is currently a great deal of activity within the software engineering community in efforts to provide automated support for many aspects of the software development process.

Lecture 10Valentina Plekhanova 3 Background Producing complex software systems of high quality, on time, to budget, and with adequate documentation to allow them to be maintained and enhanced is the goal of most organisations producing computer- based systems.

Lecture 10Valentina Plekhanova 4 Background CASE (Computer Aided Software Engineering) has been proposed as one approach that can help to make this happen. However, individual CASE tools that provide “islands of automation” are not sufficient to realise this goal.

Lecture 10Valentina Plekhanova 5 The two CASE cultures The concept of CASE has occasionally been associated with the market of diagramming and graphics editing tools. [Schefsrom and G. van den Broek, 1993]

Lecture 10Valentina Plekhanova 6 The two CASE cultures CASE tool A CASE tool is a computer-based product aimed at supporting one or more software engineering activities within a software development process. [Brown, A.W., Carney, D. J., Morris, E.J., Smith, D.B., Zarrella, P.F., 1994.]

Lecture 10Valentina Plekhanova 7 The two CASE cultures The promise of CASE is that automated support for some aspects of software development and maintenance will:  increase productivity and reduce the cost of software development;  improve the quality (e.g. reliability, usability, performance) of software products;  keep documentation in step with software products as they evolve;  facilitate maintenance of existing software systems;  make the software engineers’ task less odious and more enjoyable.

Lecture 10Valentina Plekhanova 8 CASE Environment CASE environment A CASE environment is a collection of CASE tools and other components together with an integration approach that supports most or all of the interactions that occur among the environment components, and between the users of the environment and the environment itself.

Lecture 10Valentina Plekhanova 9 Categories of Systems Engineering Tools Requirements Definition, Analysis, and Design Tools Construction, Testing and Implementation Tools Management and Project Support Tools

Lecture 10Valentina Plekhanova 10 CASE Tool Integration Problem While individual tools provide useful services assisting in specific activities, tools commonly do not work well together to support the sequences of activities and the multiple of users involved in the software engineering process. [Brown, A.W., Carney, D. J., Morris, E.J., Smith, D.B., Zarrella, P.F., 1994.]

Lecture 10Valentina Plekhanova 11 CASE Tools – Expectations…? and Problems Current interest in CASE tools and environments is based on expectations about productivity, savings, extensibility, and similar features. Current experiences, however, suggest that the technology of CASE tools and environments is as yet insufficient to provide all of those promised benefits. [Brown, A.W., Carney, D. J., Morris, E.J., Smith, D.B., Zarrella, P.F., 1994.]

Lecture 10Valentina Plekhanova 12 CASE Tools – … and Problems Organisations typically experience one or more of the following problems:  inability to combine tools easily to cover the complete software development life cycle (e.g. a requirements tool and a design tool with different implementation architectures, supporting incompatible methods);  lack of well-defined procedures for moving data from one tool to another and for synchronising the communication between the tools so that one tool can easily be invoked from another;

Lecture 10Valentina Plekhanova 13 CASE Tools – … and Problems  few facilities to support tailoring and adaptation of the tools to different organisations’ development needs;  no well-proven approaches to the introduction and adoption of collections of tools  significant system management and maintenance problems with the installation, operation, and evolution of collection of tools due to the size and complexity of many of the tools and their relative immaturity.

Lecture 10Valentina Plekhanova 14 Agent based Software Engineering Agent based software engineering is a rapidly developing area of research and practical applications. Development of high quality software is getting more difficult as the requirements and problems get more complex. Agent-oriented approaches can build complex systems faster/better.

Lecture 10Valentina Plekhanova 15 Agent based Software Engineering Software agents Software agents are a unique generation of software tools that independently perform various tasks on behalf of human user(s) or other software agents. It is recognised that agent-based approaches is a future of Computer Science; and agents would gradually be evolved into more complicated applications.