Predesign.

Slides:



Advertisements
Similar presentations
The Datastore Presenters: Nicholas Couture – President / CTO Marc Tomkinson – Director of Product Innovation.
Advertisements

Data Model driven applications using CASE Data Models as the nucleus of software development in a Computer Aided Software Engineering environment.
TotalETL:infoServer Chris Fournier Nathan Clark Scott Longley Cyril Shilnikov MQP Project 2005 Sponsored by TotalETL inc.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Objectives By the end of today’s class you will be able to… –Describe the major steps in the interaction design process –Explain the importance of iterative.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
CVSQL 2 The Design. System Overview System Components CVSQL Server –Three network interfaces –Modular data source provider framework –Decoupled SQL parsing.
Page 1 ISMT E-120 Desktop Applications for Managers Introduction to Microsoft Access.
PL/SQL and the Table API. Benefits of Server-Side Code Speedy Pizza MENU NAPOLITAINE PIZZA Reduced network traffic Maintainability Data integrity Triggers.
October 30, 2008 Extensible Workflow Management for Simmod ESUG32, Frankfurt, Oct 30, 2008 Alexander Scharnweber (DLR) October 30, 2008 Slide 1 > Extensible.
Database System Concepts and Architecture Lecture # 3 22 June 2012 National University of Computer and Emerging Sciences.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
MAHI Research Database Data Validation System Software Prototype Demonstration September 18, 2001
4 Copyright © 2009, Oracle. All rights reserved. Designing Mappings with the Oracle Data Integration Enterprise Edition License.
WaveMaker Visual AJAX Studio 4.0 Training Authentication.
Overview of Oracle Designer. Database Development Process Business Information Requirements Operational Database Conceptual Data Modeling Logical Database.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Maintenance and Support Week 15 CMIS570. User Training Need to consider the same 2 groups: End users Use the system to achieve the business purpose Creating,
Maintenance and Support Week 15 CMIS570. User Training Need to consider the same 2 groups: End users Use the system to achieve the business purpose Creating,
ITEC 370 Lecture 16 Implementation. Review Questions? Design document on F, feedback tomorrow Midterm on F Implementation –Management (MMM) –Team roles.
ARCH-09: Transforming a Complex Application Apprise® is a registered trademark of Apprise Software, Inc. Transcendix SM is a service mark and trademark.
Oracle Dependencies Analyzer ODA Over time, in large companies we see many Legacy systems that work with several Databases, this.
Implementation In this presentation… –Methodology –Software Development Life Cycle.
3 Copyright © 2009, Oracle. All rights reserved. Accessing Non-Oracle Sources.
For each customer interface record, a new instance of Workflow main process is kicked off, as below Click to proceed…………
IIA Supervising faculty: David Sarne. “Am I Rational?” Portal Goal: web-site for allowing people test their decision-making/problem- solving.
GOAL User Interactive Web Interface Update Pages by Club Officers Two Level of Authentication.
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.
IT APPLICATIONS TO ELECTRIC POWER PROJECT GUIDE : DR NDR SARMA GROUP - 10 PROJECT MEMBERS ABHISHEK DIXIT, ANUBHAV AGARWAL, E. GIRISH, SANDEEP CHANDNA.
Differences Training BAAN IVc-BaanERP 5.0c: Application Administration, Customization and Exchange BaanERP 5.0c Tools / Exchange.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Object-Oriented Application Development Using VB.NET 1 Chapter 15 Assembling a Three-Tier Windows Application.
ISC321 Database Systems I Chapter 2: Overview of Database Languages and Architectures Fall 2015 Dr. Abdullah Almutairi.
L1Calo Databases ● Overview ● Trigger Configuration DB ● L1Calo OKS Database ● L1Calo COOL Database ● ACE Murrough Landon 16 June 2008.
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
CS 501: Software Engineering Fall 1999 Lecture 23 Design for Usability I.
Keys and adding, deleting and modifying records in an array ● Record Keys ● Reading and Adding Records ● Partition or Sentinels Marking Space in Use ●
Graphical Data Engineering
Business System Development
Open-O Client Project Proposal
Robert Worden Open Mapping Software Ltd
Unit Testing.
Appendix 2 Automated Tools for Systems Development
Open-O Client Project Proposal
Chapter 18 Maintaining Information Systems
Modern Systems Analysis and Design Third Edition
TMA MEPRS Program Office
Modern Systems Analysis and Design Third Edition
Where I am at: Swagatika Sarangi MDM Lead PASS Summit SQL Saturdays
Data, Databases, and DBMSs
Chapter 4 Automated Tools for Systems Development
Case Application Development Method
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
C/S Windows Overview Nigel Pilsbury.
Maintaining Information Systems (SAD- 18)
Dynamics AX Upgrades Microsoft Dynamics AX 2009
CS 240 – Advanced Programming Concepts
Updating Databases With Open SQL
The Database Environment
Windows Forms in Visual Studio 2005: An in-depth look at key features
Modern Systems Analysis and Design Third Edition
Chapter 18 Maintaining Information Systems
INTRODUCTION A Database system is basically a computer based record keeping system. The collection of data, usually referred to as the database, contains.
Updating Databases With Open SQL
SDMX IT Tools SDMX Registry
Presentation transcript:

Predesign

Predesign A prototyping stage Aims of prototyping Last validation of requirements Discovery of new requirements Making of design decisions Applications Database

Deliverables Design Pre-Design Physical Design of Database Physical Design of Applications Pre-Design Standards for GUI, Coding, Naming Conceptual Application Design Plan for Design of DB and Applications

Traditional View of Designer Typical Use of Designer Transform Functions into Modules Develop Modules into Rough Shape in Designer Generate Forms Develop forms in Developer Never look back Application Lost to Designer

Prototyping Approach ‘Capture Design of Form/Report’ utilities capture work done in Developer (except layout) Application can be regenerated instead of reprogrammed Changes to Database can also be Captured

Benefits of Generation Implementation stays connected to requirements and design Redesign (maintenance) much less costly Look & Feel modification much easier

Prototyping Steps Create rough versions of tables, modules, module network with DDT and ADT Generate Database w/o Modification Generate ‘Throw-away’ Forms to Populate Database with Sample Data. Create Basic Structure of Modules in Designer

Prototyping Steps (2) Set Generator Preferences to Establish Design Standards Generate Forms/Reports Use Prototype: Modify Forms/Reports in Developer Modify Database Capture Changes back into Design

Capturing DB Changes Experimentation with prototype results in DB modifications Manual Capture of Changes: Delete extra repository columns Delete unused repository tables Capture design of server New tables New columns

Capturing Application Changes New form or existing form with new code: ‘Capture Design of Form’ utility. Slightly modified or combined or deleted form: make changes manually in RON or DE. Navigation Changes: Manually modify module structure.

Tracking Requirements Are we doing everything that needs to be done? Tracked requirements to functions User extensibility Now track them again to modules. User extensibility manually Via Repository API script