Software Design/Database Design - PowerPoint PPT Presentation

1 / 35
About This Presentation
Title:

Software Design/Database Design

Description:

Title: Agent based constraint checking Author: Praveen Madiraju Last modified by: Admin Created Date: 1/1/1601 12:00:00 AM Document presentation format – PowerPoint PPT presentation

Number of Views:129
Avg rating:3.0/5.0
Slides: 36
Provided by: Prav56
Learn more at: http://www.mscs.mu.edu
Category:

less

Transcript and Presenter's Notes

Title: Software Design/Database Design


1
Software Design/Database Design
Dr. Praveen Madiraju Department of Mathematics,
Statistics, and Computer Science Marquette
University http//www.mscs.mu.edu/praveen/
2
What is Design?
3
What is Design? (contd)
  • What is involved in Design Process?
  • Goals, Ideas
  • Knowledge, Representations
  • Languages, Tools
  • Activities
  • Software is somewhat unique
  • disparate projects
  • changing tools
  • many advances are in programming languages

4
eCase Review Management System
Insurance Companies
Incoming Case
Case Review
Case Transcription
Billing
eCase Management System
5
Software Development Process
6
Software Development Process (contd)
7
SCRUM Agile Software Development
  • SCRUM is an agile, lightweight process for
    managing and controlling software and product
    development in rapidly changing environments.
  • Iterative, incremental process
  • Team-based approach
  • developing systems/ products with rapidly
    changing requirements
  • Improve communication and maximize cooperation
  • A way to maximize productivity

8
SCRUM (contd)
  • Components of Scrum
  • Roles Scrum Master, Team, Product Owner
  • Process Sprint Planning, Sprint, Daily Scrum,
    Sprint Review Meeting

9
Requirements Discovery Process
  • Interviews with clients
  • Gather functional and non-functional requirements
  • Sometimes a quick prototype helps

10
Requirements Discovery Process (contd)
  • Capturing Requirements using Use-Case Modeling

11
Requirements Analysis
12
Software Design
  • System design
  • describes what the software system should do
  • focuses more on desirability
  • typically captures the overall, essential framing
    of the solution
  • Includes database design as well
  • specific technology and database independent
  • Implementation design
  • describes what the implementer should do
  • focuses more on feasibility
  • typically represents a final completed design
  • typically captures a fully detailed roadmap

13
Database Design
  • Basic Concepts of Database
  • Table Row, Column, Primary Key, Foreign Key,
    Index

Primary Key
Table Name
Foreign Key
EMPLOYEE
DEPARTMENT
SSN FName DNO
123 John 1
234 Leela 2
DNO DName
1 Accounting
2 Administration
Row
Column
14
Database Design (contd)
Main Phases of Database Design
15
ER (Entity Relationship) Modeling
  • Conceptual design phase result is a conceptual
    schema
  • ER consists of entities, attributes, and
    relationships
  • Example Company Database System.
  • We store each EMPLOYEEs social security number,
    address, salary, sex, and birthdate. Each
    employee works for one department but may work on
    several projects
  • Entity EMPLOYEE, DEPARTMENT,
  • Attributes SSN, Address, Sex, Birthdate
  • Relationship WORKS_FOR,

Higher Level Requirements
16
ER Modeling (cont'd)
LName
FName
MI
DName
DNO
Name
SSN
WORKS_FOR
1
DEPARTMENT
N
EMPLOYEE
DOB
Sex
Age
Phone
17
ER Modeling (cont'd)
Strong Participation
  • Types of Relationships
  • 11 1N (previous slide)

MANAGES
1
DEPARTMENT
1
EMPLOYEE
  • MN

WORKS_ON
N
PROJECT
M
EMPLOYEE
Hours
PNO
PName
18
ER to Relational Schema
  • Entities ? Tables
  • Attributes ? Columns

EMPLOYEE_PHONE
EMPLOYEE
SSN Phone
123 414-111-
123 262-000
SSN FName LName MI DOB Age Sex
123 John Smith A M
234 Leela B F
19
Database Tools
  • ER Modeling Tools/Technologies
  • Microsoft Visio
  • Oracle Designer
  • Rational Rose
  • ERWin,
  • Database Vendors
  • Commercial Oracle, IBM DB2, Microsoft SQL
    Server,
  • Free Ware MySQL, SQLLite, PostgresSQL,
  • Database Languages
  • Structured Query Language (SQL), PL/SQL

20
Application Design Models
  • Data Flow Diagrams
  • Pseudo code
  • Algorithms
  • Object-Oriented Analysis and Modeling using UML
    (Unified Modeling Language)

21
UML
  • Use Case Diagrams
  • Activity Diagrams
  • Sequence Diagrams
  • Class Diagrams

22
Component Reuse
  • If a component already exists, why re invent the
    wheel?
  • There exists components for almost anything these
    days
  • Risks associated with free or third party
    components

23
User Interface Diagrams
  • Mock-ups, Sketches, User interaction Diagrams,
    Prototype Demos, Browser

24
User Interface Diagrams (contd)
Wireframe
25
Application Design Tools
  • UML Tools
  • Rational Software Modeler, Microsoft Visio,
    Eclipse-Omondo, Dia (free ware),
  • User Interface Tools
  • Your favorite browser, Microsoft .NET framework,
    Java Swing, Visio, WireframeSketcher,

26
Implementation
  • Small stand alone applications
  • Java, Microsoft .NET,
  • Web based applications
  • Java Servlets, Microsoft .NET, PHP-MySQL,
  • Enterprise Resource Planning Applications
  • SAP, Oracle Apps,

27
Multi-tier Application Architecture
Server (Business Logic) (Data Access Logic)
Data Resources
Web Server (Business Logic) (Data Access Logic)
Client (Presentation Logic) (Business
Logic) (Data Access Logic)
Two-tier Architecture
Three-tier Architecture
28
Multi-tier Application Architecture (contd)
29
Construction and Testing
  • Unit testing
  • System testing

30
Installation and Delivery
  • Training Manual

31
System Operation and Maintenance
  • Program Back up, Recovery and Maintenance
  • Technical Support
  • Further System Enhancements
  • Hopefully no bugs

32
Thank you
  • Questions?

33
ER to Relational Schema (contd)
  • Dealing with Relationships 11

DName
DNO
StartDate
SSN
FName
MANAGES
1
DEPARTMENT
1
EMPLOYEE
TRANSLATES TO
EMPLOYEE
DEPARTMENT
SSN FName
123 John
234 Leela
DNO DName MgrSSN MgrStartDate
1 Account.. 234
34
ER to Relational Schema (contd)
  • Dealing with Relationships 1N

DName
DNO
SSN
FName
WORKS_FOR
1
DEPARTMENT
N
EMPLOYEE
TRANSLATES TO
EMPLOYEE
DEPARTMENT
SSN FName DNO
123 John 1
234 Leela 1
DNO DName
1 Account..
2 Admin
35
ER to Relational Schema (contd)
  • Dealing with Relationships MN

FName
SSN
WORKS_ON
N
PROJECT
M
EMPLOYEE
Hours
PNO
PName
PROJECT
EMPLOYEE
WORKS_ON
PNO PName
1001 OceanBlue
1002 EverGreen
SSN FName
123 John
234 Leela
SSN PNO Hours
123 1001 20
123 1002 20
Write a Comment
User Comments (0)
About PowerShow.com