Software Engineering at Azusa Pacific University Conquering the Monster Capstone Project via Structured System Analysis & Design September 2, 2015 1 Azusa.

Slides:



Advertisements
Similar presentations
Requirements gathering
Advertisements

Workshop: Mind-mapping CTL Presentation Skills team …hello!
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
Systems Development Environment
Software Engineering-II
DFD Rules and Guidelines Yong Choi BPA CSUB. 2 DFD example - Hoosier Burger’s food ordering system I * One process (level 0 - the whole system) * No data.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering September 12, 2001 Capturing.
April 30, April 30, 2015April 30, 2015April 30, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
May 3, May 3, 2015May 3, 2015May 3, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
Analysis Concepts, Principles, and Modeling
Data Model driven applications using CASE Data Models as the nucleus of software development in a Computer Aided Software Engineering environment.
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
May 20, May 20, 2015May 20, 2015May 20, 2015 Azusa, CA Sheldon X. Liang Ph. D. Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
May 24, May 24, 2015May 24, 2015May 24, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
CSCE 121, Sec 200, 507, 508 Software Engineering Fall 2010 Prof. Jennifer L. Welch.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
7M701 1 Software Engineering Data Flow Models Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 7
Purpose of Requirements Analysis Process of discover, refinement, modeling, and specification o Bridge gap between system level SW allocation and design.
CSC 395 – Software Engineering Lecture 15: Object-Oriented Design –or– Ask For Whom The Data Tolls.
August 1, August 1, 2015August 1, 2015August 1, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
Recursion: Function and Programming Software Engineering at Azusa Pacific University  Evolutionary Approach  Examples and Algorithms  Programming in.
Approaches to System Development Chapter 3. Methodologies, Models, Tools and Techniques A system development methodology –provides guidelines to follow.
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
August 13, August 13, 2015August 13, 2015August 13, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
Architectural Synthesis Approach Sheldon X. Liang Ph. D. August 18, Software Engineering in CS at APU Architectural Synthesis Approach Azusa Pacific.
August 19, August 19, 2015August 19, 2015August 19, 2015 Azusa, CA Sheldon X. Liang Ph. D. CS 470 Software Engineering I Azusa Pacific University,
 It’s tough work  It’s f.a.i.t.h. work It’s creative work  It’s my work What kind of work SE is: Software Engineering at Azusa Pacific University My.
August 22, August 22, 2015August 22, 2015August 22, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
The Software Development Life Cycle: An Overview
Slide 12.1 © The McGraw-Hill Companies, CS 4310: Software Engineering Lecture 7 Systems Analysis Object-Oriented Design.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Requirements Analysis
Engineering Design Process
ITEC224 Database Programming
Part3 Database Analysis and Design Techniques Chapter 04- Overview of Database Planning, Design and Administration Database Systems Lu Wei College of Software.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
หลักการโปรแกรม เพื่อแก้ปัญหาโดยใช้คอมพิวเตอร์
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide 1- 1 Overview 1.1 Computer Systems 1.2 Programming and Problem Solving.
Software Requirements: Overview and Motivation Gruia-Catalin Roman and Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering.
Chapter Six Documentation. Data Flow Diagrams & Flowcharts Diagrams, Flowcharts, Tables Explain the system Help identify internal control weaknesses Provide.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
CORE 1: PROJECT MANAGEMENT Designing. This stage is where the actual solution is designed and built. This includes describing information processes and.
November 22, November 22, 2015November 22, 2015November 22, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific.
Advanced Accounting Information Systems
Robotics and Computer Vision
Software Engineering Lecture 11: System Analysis.
1 Introduction to Design. 2 Outline Basics of design Design approaches.
RHS Tech Ed The Engineering Design Process. What Is Design?
January 27, January 27, 2016January 27, 2016January 27, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
Architectural Synthesis Approach Sheldon X. Liang Ph. D. February 5, Software Engineering in CS at APU Azusa Pacific University, Azusa, CA 91702,
Chapter 11  2000 by Prentice Hall System Analysis and Design: Methodologies and Tools Uma Gupta Introduction to Information Systems.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
February 19, February 19, 2016February 19, 2016February 19, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific.
PAISE-3-2-1: P erspective-bridged A rchitecture “Automatic Prototype Generating” Restated with re-ADA By Sheldon X. Liang Computer Science Azusa Pacific.
February 27, February 27, 2016February 27, 2016February 27, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific.
March 19, March 19, 2016March 19, 2016March 19, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University,
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
HCC 831 User Interface Design and Evaluation. What is Usability?
Systems Design.
DFD Rules and Guidelines
تحلیل سیستم‌ها مدل‌سازی پردازشی.
Tools of Software Development
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
User Interface Design and Evaluation
Thales Alenia Space Competence Center Software Solutions
Members: Keshava Shiva Sanjeeve Kareena
Presentation transcript:

Software Engineering at Azusa Pacific University Conquering the Monster Capstone Project via Structured System Analysis & Design September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science,

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Software Engineering Project is like a monster that overwhelms and frustrates us all the time -- It seems to be a BIG headache to develop a software engineering project:  How to get a project started is really weird You have to start with a big cloud, and what is next step is still up in the air.  How to get the job done is more headachy You start with a cloud, you may have done a big mess – endless work makes you feel hopeless.

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Tar pit Warning Tar pit Warning Surgical Way to survive Surgical Way to survive Passing the word Documents do the trick Passing the word Documents do the trick No Silver Bullet Work to do No Silver Bullet Work to do MMM What? MMM What? Our Recognition: The Monster of W 5  PR#1-1 / PR#2-1 What seems to be the problem?  PR#1-2 Warning in advance!  PR#1-3 / 1-4 Way to survive  PR#2-4 Word to communicate  PR#3-1/3-2 Work out anyway

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Our Recognition: creative boss & calm operator Tar pit Warning Tar pit Warning Surgical Way to survive Surgical Way to survive Passing the word Documents do the trick Passing the word Documents do the trick No Silver Bullet Work to do No Silver Bullet Work to do MMM What? MMM What?

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Conceptual System Operational System SSAD Approach: conceptual  operational system  PR#2-2 Who should design?  PR#2-3 What are design constraints  PR#4-1 / PR#4-2 How to design  PR#3-3 Prepositions of MMM  PR#3-4 MMM after 20 Years

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Conceptual System Operational System SSAD Question ourselves  PR#2-2 Who should design?  PR#2-3 What are design constraints  PR#4-1 / PR#4-2 How to design  PR#3-3 Prepositions of MMM  PR#3-4 MMM after 20 Years What we have learned? How to apply to design?

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Conceptual System Operational System SSAD There is a gap between conceptual system and operational system Big problem with SSAD How to start with conceptual sys? How to bridge the gap in between?? How to end at operational system???

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster New, creative ideas expected PADT streamlined SSAD

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster PADT streamlined SSAD Perspectives Activities (Tech vs Client) Documents (  stage-products) Tools Conceptual  What-to-do Defining Decomposing Review Revising PRD/PSD  prototype  SPMP Context diagram Visual Basic Technical  How-to-do Design Describe Revising Refining SDD / WDSC  ATP  IPO DFD / SC / ERD / GUI / Pseudo Operational  Going-to-do DevelopingRunning WDSC/SOM  API  product API / IPE Programming Language Hooray / Runaway Wine / TearPLD

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science,

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science,

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science,

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Inspirational question:  How to convert coffee beans to grounds?  How to refine / decompose a context diagram in PRD to high level Data Flow Diagram in PSD?  How to expand PSD from PRD?  Why SPMP is with PSD, and what is the key for SPMP?

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Context Diagram in PRD High level DFD in PSD Any problems?  A cloud is lost  unspecified dataflow

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, High level DFD in PSD Conquering the Monster Consistent Decomposition Context Diagram in PRD

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Review (PRD)  Revise (PSD)  Refine (SDD) PRD PSD SDD Document-DrivenCore tools appliedFormulated approach DFD 0 PRD = DFD 0 + Description DFD 1 PSD = DFD 1 + SC + ERD SC / ERD DFD * SDD = DFD + + SC * + ERD * + GUI GUI /API

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Review (PRD)  Revise (PSD)  Refine (SDD) PRD PSD SDD Document-Driven Core tools applied Formulated approach PRD = DFD 0 + Description PSD = DFD 1 + SC + ERD SDD = DFD + + SC * + ERD * + GUI Context Diagram High level DFD Hierarchical DFD

Software Engineering at Azusa Pacific University September 2, Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department of Computer Science, Conquering the Monster Document-Driven Management Plan