- 1 - © Houman Younessi 2010 MGMT 6170 - Advanced Systems Analysis and Design A dvanced S ystems A nalysis and D esign Fall 2010 Convener: Houman Younessi.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.
Chapter 2: Software Process
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Prescriptive Process models
COMPSCI 105 S Principles of Computer Science 12 Abstract Data Type.
Lecture # 2 : Process Models
Unified Modeling Language
Delmar Learning Copyright © 2003 Delmar Learning, a Thomson Learning company Nursing Leadership & Management Patricia Kelly-Heidenthal
7M701 1 Software Engineering Object-oriented Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 12 )
Lecture 9 ISM- © 2010 Houman Younessi Information Systems Spring 2011 Convener: Houman Younessi
MGMT ASAD HO 7 © HY 2006 Lecture 7 A dvanced S ystems A nalysis and D esign Fall 2006 Convener: Houman Younessi
- 1 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design A dvanced S ystems A nalysis and D esign Fall 2010 Convener: Houman Younessi.
- 1 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design A dvanced S ystems A nalysis and D esign Fall 2010 Convener: Houman Younessi.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
HAS. Patterns The use of patterns is essentially the reuse of well established good ideas. A pattern is a named well understood good solution to a common.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Design Patterns.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
CSCI Research Methods HO 10 © Houman Younessi 2013 Lecture 10 Qualitative Procedures A paradigm shift: A paradigm is a way of thinking. It.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
1 SYS366 Lecture 1: Introduction to Systems. 2 What is Software Development? Software Development implies developing some software – but it does not involve.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
SOFTWARE DESIGN.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
1 Introduction to Software Engineering Lecture 1.
The Systems Development Life Cycle
Chapter 7 Software Engineering Introduction to CS 1 st Semester, 2015 Sanghyun Park.
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
SFDV Principles of Information Systems Lecture 5: Designing the Solution.
A Context Model based on Ontological Languages: a Proposal for Information Visualization School of Informatics Castilla-La Mancha University Ramón Hervás.
 What is Modeling What is Modeling  Why do we Model Why do we Model  Models in OMT Models in OMT  Principles of Modeling Principles of Modeling 
HYMES (1964) He developed the concept that culture, language and social context are clearly interrelated and strongly rejected the idea of viewing language.
Modeling as a Design Technique Chapter 2 Part 1: Modeling Concepts Object-Oriented Modeling and Design Byung-Hyun Ha
Dale Roberts Object Oriented Programming using Java - Introduction Dale Roberts, Lecturer Computer Science, IUPUI Department.
The Rational Unified Process 1 EECS810: Software Engineering.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
Copyright ©2004 Cezary Z Janikow 1 OOAD Overview n OO language – Necessary for OO systems? – Sufficient for OO systems? Owning a hummer doesn’t make you.
Csci 490 / Engr 596 Special Topics / Special Projects Software Design and Scala Programming Spring Semester 2010 Lecture Notes.
Software Architectural Views By the end of this lecture, you will be able to: list and describe the views in the 4+1 view model of software architecture.
“Using a Story-Based Approach to Teach Grammar”
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
Engr 691 Special Topics in Engineering Science Software Architecture Spring Semester 2004 Lecture Notes.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Training processes for extension education
The Semiotic Engineering of Human-Computer Interaction Section I Foundation Chapter 1 Introduction.
Design Patterns Damian Gordon.
By Dr. Abdulrahman H. Altalhi
Frequently asked questions about software engineering
Design and Implementation
Software Analysis.
Uml diagrams In ooad.
Presentation transcript:

- 1 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design A dvanced S ystems A nalysis and D esign Fall 2010 Convener: Houman Younessi Lecture 1

- 2 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design A system is identified in terms of the single goal it is to achieve. A system name is a cognitive handle that allows the identification and communication of a particular coherent and purposeful set of activities. A system name is usually presented in the form of: “A system to do/be/achieve X” Example: A system to generate birth certificates A system to generate reusable components A system to provide a uniform computing platform across government agencies All these may actually refer to the same application software!

- 3 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Software Development is a form of System Development System Development entails the processes of: Finding out what is the problem Arriving at a solution Delivering on a good solution Discovery Invention Construction

- 4 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Analysis Design Implementation So “analysis and design” is all about identifying what the problem is and to propose one or several solutions to rectify the problem. What is the problem? What is a solution? How do we deliver on a good solution? Discovery Invention Construction

- 5 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Figuring out the problem. The problem that is to be figured out is immersed in the real world. The real world (the problem situation) is a web of interactions of amazing complexity To have a chance, we need to be able to focus only on what is: RELEVANT

- 6 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design We need therefore to concentrate on: Those elements about which we need to ask questions, Those elements about which we need to answer questions We also need to make sure that: Only those elements that are of our direct and immediate concern are focused on at any one time.

- 7 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design The first of these is called: The second is called: CONTEXTUALIZATION ABSTRACTION

- 8 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Once we have understood the problem, we need to: Communicate our understanding: To ourselves at a later time To others To do so, we need to capture, retain and communicate what is relevant and in context. This is called Modeling

- 9 - © Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Modeling is therefore a fundamental element of analysis and as such a vital part of software development. In order to capture, retain and communicate what is needed, the modeler has to use a language. This is called: The Modeling Language The modeling language has to contain the vocabulary and the grammar of the modeling approach utilized.

© Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Activity 1 Model a Person

© Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Activity 2 Model a Refinery

© Houman Younessi 2010 MGMT Advanced Systems Analysis and Design What’s there? How does it happen? When does it happen? (or in what sequence?) Things and static relationships Change Order and timing of change

© Houman Younessi 2010 MGMT Advanced Systems Analysis and Design Things and static relationships Change Order and timing of change Structure Transformations Causal (sequential) relationships For all deterministic systems we must capture all that is relevant of these three aspects, if we are to have sufficient understanding of them.