Navigation through Source Code

Slides:

Advertisements

Similar presentations

Select the Workout Modification order form.. Click on Order.

Advertisements

Object-oriented Software Change Dynamic Impact Analysis Lulu Huang and Yeong-Tae Song Dept. of Computer and Information Sciences Towson University Towson,

Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.

Software Requirements Engineering

US Army Corps of Engineers BUILDING STRONG ® Creating a Data Dictionary for Your Local Data USACE SDSFIE Training Prerequisites: Preparing Your Local Data.

UML – Class Diagrams.

Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.

Chapter 4: Requirements Elicitation 4.5: Managing Requirements Elicitation Supervised by: Dr. Qutaibah Malluhi Software Engineering Done by: Sarah Al-Aqailly.

1 CS 691z / 791z Topics on Software Engineering Chapter 17: Interfaces and Subsystems [Arlow & Neustadt, 2002] March 6, 2007.

ACM/JETT Workshop - August 4-5, 2005 UML Modeling using MagicDraw UML for Java Programmers.

Architecture, Implementation, and Testing Architecture and Implementation Prescriptive architecture vs. descriptive architecture Prescriptive architecture:

UML CLASS DIAGRAMS. Basics of UML Class Diagrams What is a UML class diagram? Imagine you were given the task of drawing a family tree. The steps you.

Future of MDR - ISO/IEC Metadata Registries (MDR) Larry Fitzwater, SC 32 WG 2 Convener Computer Scientist U.S. Environmental Protection Agency May.

Overview Dennis L. Johnson What is GIS? Geographic Information System Geographic implies of or pertaining to the surface of the earth Information implies.

The Data Attribution Abdul Saboor PhD Research Student Model Base Development and Software Quality Assurance Research Group Freie.

Attribute Data in GIS Data in GIS are stored as features AND tabular info Tabular information can be associated with features OR Tabular data may NOT be.

MT311 Java Application Development and Programming Languages Li Tak Sing( 李德成 )

Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.

SharePoint and Open XML Using SharePoint as a Data Source for your custom Open XML Documents Presented by Becky Bertram MCSD, MCAD, MCTS

Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.

ITEC 370 Lecture 10 Design. Review Design –Why is it part of the process? –Who is the audience for design?

What is MOF? The Meta Object Facility (MOF) specification provides a set of CORBA interfaces that can be used to define and manipulate a set of interoperable.

Object-Oriented Analysis and Design An Introduction.

1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.

Binding UI Components to Data. Adding UI Components to the Page You can create components on a page by: Dragging a component from the Component Palette.

CLASS DIAGRAM. What is a class diagram? Imagine you were given a task of drawing a family tree. The steps you would take would be: What is a class diagram?

Week III  Recap from Last Week Review Classes Review Domain Model for EU-Bid & EU-Lease Aggregation Example (Reservation) Attribute Properties.

Navigation Timing Studies of the ATLAS High-Level Trigger Andrew Lowe Royal Holloway, University of London.

Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.

Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.

N. HARIKA Lecturer(csc). 3 General Structure Of A Java Program.

® IBM Software Group © 2009 IBM Corporation Essentials of Modeling with the IBM Rational Software Architect, V7.5 Module 15: Traceability and Static Analysis.

07 - OODCSC4071 OOA/OOD/OOP Example example OODCSC4072 Requirements See eg/req.htmleg/req.html Want a program to help a software company plan new.

Object Oriented Programming and Data Abstraction Earl Huff Rowan University.

DBS201: Data Modeling. Agenda Data Modeling Types of Models Entity Relationship Model.

Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,

September 20051© GEFEG – - Context Inspired Component Architecture Creating ASC X12 CICA Constructs with the CICA Editor.

ثبت و شناسايي درآمدها در دانشگاه علوم پزشکي تهيه و تنظيم : حسن اسحقي

Building Enterprise Applications Using Visual Studio®

Reuse Separate classes could be developed for all the different objects that are needed in each program. However that would be wasteful. Often many functionalities.

Documentation control

Design Class Diagrams

Chapter 11: Software Configuration Management

Architecture Concept Documents

Object-Oriented Techniques

Requirements analysis, representation and validation

Introduction to Unified Modeling Language (UML)

Project Topic 2: Migration to Java 9

Satisfying Open/Closed Principle

The enhancement concept allows you to add your own functionality to SAP's standard business applications without having to modify the original applications.

UML: Unified modeling language

2.1 Latest features of JDemetra+ 2.2

Advanced Database Models

Computer Programming.

Object Oriented Analysis and Design

SYS466 Domain Classes – Part 1.

Accounting, Controlling, Treasury

Introduction to Computer Science for Majors II

Analysis models and design models

Software Design Lecture : 15.

Software Design Lecture : 14.

Representing Data Unit 1 Lesson 3.

Chapter 11: Software Configuration Management

Software Requirements Specification (SRS) Template.

Review B.Ramamurthy 4/6/2019 BR.

Brandon Roman CS300.

Unit Testing for the Absolute Beginner

Final Review B.Ramamurthy 5/8/2019 BR.

Unit – V Data Controls.

Presentation transcript:

Navigation through Source Code Prepared by Soha Makady

Problem Statement As the software changes, documents become obsolete, hence the source code becomes the only reliable documentation for the developer But … as the software size increases, code navigation becomes a hard task So… We need to provide a visual representation for the relationships between the source code elements

Data An XML-based representation for source code. Includes info about: Packages Classes (including attributes and operations) Relationships Inheritance: for classes and interfaces Calls: records calls between different methods References: for field references from a different class, or a method

Related Work Locates a feature within the code

To Do (1) Visualize method calls to trace any feature Class1 attribute1 attribute2 method1() method2() method3() Class2 Attribute3 Attribute4 method7() method8() method9() m1() calls m9() m3() calls m7() …. m2() calls m9()

To Do (2) – May be  Visualize the affected test cases by code modification TestClass2 testMethod4() testMethod5() testMethod6() Class1 attribute1 attribute2 method1() method2() method3() TestClass1 testMethod1() testMethod2() testMethod3()